×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Charles Wilt wrote:
The problem with going direct is that the recipient SMTP server may
refuse if the System i SMTP server isn't in the DNS as the senders
public SMTP server.
Actually this isn't the case at all ... any system can send mail, the system doesn't have to be listed as a Mail eXchanger (MX) for the domain.
For example: Up until a few months ago, midrange.com sent from two servers ... one server was the MX for the midrange.com domain, so it received all midrange.com mail, it also sent my private mail and administrative messages from the various services I run. The other server just sent list mail.
It's also critical that whatever system you use a reverse IP DNS entry (PTR,
http://en.wikipedia.org/wiki/PTR_Record#PTR). Many mail servers will block, out of hand, a sending server that does not have a PTR dns entry.
What will get you blocked, sometimes, is if your system appears to be in a IP block that's marked as consumer DSL.
One thing that _might_ get you past this kind of problem is to list your sending mail servers using SPF (Sender Policy Framework,
http://www.openspf.org). This let's the recipient servers verify that the server you are sending from is indeed legitimately sending for your domain.
david
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
