Nick Smith wrote:
On Thu, 2005-01-20 at 09:53 -0500, Keith P Hassen wrote:
Nick Smith wrote:
Let me see if I have this right:
[SMTP_A] ---- [COMCAST GW] ---- [SMTP_B]
And you are saying that SMTP_A can _receive_ email, but cannot _send_ email?
that is correct, they are recieving mail on theirdomain.org and sending on smtp.comcast.net which is now blocked.
Ok, so what you'll have to do is use SMTP_B as a relay. Get the SMTP_B server listening on some random port (say 2500) and then have SMTP_A send to SMTP_B on that port. You can do this entirely by using iptables, without changing the SMTP configuration.
I do not believe that Comcast is preventing relays through their SMTP server. I am very suspicious actually -- either they have blocked SMTP_A for a very specific reason (have they been spamming? not paying on their account? etc?), the Comcast IT department is ridiculously incompetent or their new policy-makers are idiots.
_k
well i understand that, but SMTP_B would be whoever im sending mail to, for example, an address @yahoo.com, i dont have control over yahoo's smtp server so i wouldnt be able to change any ports, the only one i have control over is SMTP_A, so what else can i do?
No, SMTP_B would be a server _you_ control, which will act _strictly_ as a relay agent for SMTP_A. I have done this many times before and it is very straightforward provided that you actually have SMTP_B available to use.
If you do not have another box _outside_ the comcast domain that you can control, then you have no other solutions except getting a) comcast to change their policy (not likely) or b) relocating your server.
_k
-- [email protected] mailing list
