Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Floyd Arguello (floyd.listsgmail.com)
Date: Tue Jan 29 2008 - 11:32:30 CST
Anders Norrbring wrote:
> Victor Duchovni skrev:
>> On Mon, Jan 28, 2008 at 07:53:02PM +0100, Anders Norrbring wrote:
>>> They block 25 to "protect their users against SPAM".
>> This makes no sense, most ISPs that block port 25 for customer IPs do so
>> only outbound. That protects the rest of the world (including to a small
>> extent their customers) from spam emanating from botnet machines. But
>> blocking of port 25 inbound to a customer IP is in no way an anti-spam
>> measure. It prevents one from running an MX host.
>> Are they really planning to block inbound connections to port 25? Or
>> are they just miscommunicating their intentions.
>> Perhaps they believe that inbound connections on port 25 are delivering
>> unwanted Hormel canned meat products.
> Actually their intention was to only block outbound, but they
> misconfigured, and it's "not easy to correct".. *sigh*
> Since they're HUGE (Telia), it's not easy for a customer to have them
> redo things.
I replied to this yesterday, but replied to sender and not list :P
Would the following work?
Setup a public server (outside of your ISP's network), and have that
accept incoming mail and forward it to the current mail server using
transport maps (specifying a different port):
Then configure your current server to listen on 587
127.0.0.1:587 inet n - n - - smtpd #using proper IP
Modify the mx record to point to the public server.