>Is the SMTP server you are using your own server or is it your ISPs?
>Many ISPs have SMTP servers that are configured to only relay mail from
>their own users (which would explain why it works for you but not your
>testers). If that's the case the solution is to either use one that
>doesn't limit who uses it (bad idea... most SMTP servers like that are,
>or should be, on every spam blocking list that ever existed and you
>still may not get your mail) or to use one that supports authentication
>and code that authentication routine into your app...
You can easily get around this problem IF you are always sending to the
exact same email address. In Floyd's use, it sounds like he is always
sending the email back to himself, so he would always be using the same
email address.
In that situation, use the SMTP server that hosts the email address. So
for Floyd it would be swbell.net's smtp server (mail.swbell.net?). If you
use that as the SMTP server AND are sending to an account hosted on that
server, you won't need to authenticate 99% of the time (that 1% is for
companies that block connections from non subscriber IPs, in those
instances, you need to do a bit more DNS research to find the inbound
SMTP gateway server and use that instead).
The reason you won't need to authenticate is because mail delivered to
local accounts never requires authentication. If it did, there would be
no way for other ISPs to deliver mail from their customers.
-chris
<http://www.mythtech.net>
---
A searchable archive of this list is available at:
<http://support.realsoftware.com/listarchives/search.php>
Unsubscribe:
<mailto:realbasic-nug-off at lists dot realsoftware dot com>
Subscribe to the digest:
<mailto:realbasic-nug-digest at lists dot realsoftware dot com>
.
|