Hi,

On Mon, 15 Sep 2003 14:34:03 +0100 Paul Hutchings <[EMAIL PROTECTED]> wrote:

> > Pardon me while I expose my ignorance.  What's a smarthost, and given
> > me by which provider?   All I get from my so-called ISP is a wire with
> > an IP address, or do you mean dyndns?
> 
> It's your ISPs outbound smtp server.  The idea is you can set your MTA to
> forward all outbound mail to it and it'll handle delivery to the final
> destination.  As it has a static IP it's supposed to be more reputable (for
> lack of a better word) than your smtp server on a dynamic IP address.
> 
> Personally I'm not a big fan, I prefer having direct control over any queued
> mail and anything that goes out from a box of mine.

As do I, though I'm a bit more discriminating as to what my box will
accept; just try getting your ISP to use SpamAssassin or to drop traffic
from open proxies and relays, or other misconfigured boxes. While it's
not always an option depending on your budget and location, you really
ought to have a static IP address if you're going to operate a mail
server.

Also, you really need to configure smarthosting, even if you send mail
directly, because you never know when RoadRunner, et. al. will
arbitrarily block your mail solely because it comes from a DSL
connection[1]. It's best to have a tested contingency plan for rerouting
outbound mail because complaining about being inadvertently blacklisted
doesn't get the mail delivered.

-- Bob

[1] Never mind that my network is a static allocation with correct whois
(domain contacts & SWIP), proper forward DNS, RFC-compliant abuse
reporting addresses (not listed on RFCI), and no open relays or proxies
as verified by RR's persistent port-scanning. Never mind that both RR
customers and I explained the situation to RR's security department
and asked for them to whitelist my network (to no effect.) Never mind
that RR's mail acceptance policy changes on a daily basis and it's never
clear what hoops you need to jump through to get mail into RR. I
smarthosted only the RR-bound mail through SBC's mail servers (though
not everything since I don't trust any ISP's mail system, given
week-long outages with ALGX/Hosting.com and given RR's behavior above.)

Adding the line:

.rr.com smtp:smtp.sbcglobal.net

to /etc/postfix/transport worked around RR's broken policy long enough
to SBC to delegate rDNS for my /29 and for me to adjust my nameservers
to take advantage of it.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to