I got a call from a client that stated his vm to email stopped working. So, I looked about and nothing seem too wrong. Then I read the asterisk email... Seemed that Qwest had started blocking.
Now, in a way I support this as it helps to slow the tide of zombies. Think Kraken...
Here is the entry from Spamhaus:
"Ref: PBL171468
75.172.0.0/17 is listed on the Policy Block List (PBL)
Outbound Email Policy of Qwest for this IP range:
It is the policy of Qwest that email sent from a dynamically assigned IP address should be sent out only via the designated outbound mail server allocated to Qwest customers. To find the hostname of the correct mail server to use, customers should consult the original signup documentation as provided by their ISP or contact Qwest Technical Support.
Removal Procedure
If you are not using normal email software but instead are running a mail server and you are the owner of a Static IP address in the range 75.172.0.0/17 and you have a legitimate reason for operating a mail server on this IP, you can automatically remove (suppress) your static IP address from the PBL database."
So, I went thru the policy removal and in about 30 minutes email started to flow again.
It is still a time bomb as the IP seems to change a lot. So, I should probably dig out Ward's gmail solution and have a go.
Wednesday, April 16, 2008
Subscribe to:
Post Comments (Atom)
Posts
1 comments:
There's a couple of ways around this, though they all require relaying via another system:
- Set up your SMTP server as a "smart host", which is effectively just relaying all SMTP out to your ISP's email server.
- If you have your own external mail server you want to send through (again, with your system as smart host), set it up to accept connections on an alternate port (This is what I do).
- Use an outbound mail service that many of the dynamic hostname companies offer. Typically this is also just an alternate smtp port that will relay traffic for your system.
Post a Comment