From: bytehd <by...@us...> - 2009-06-30 23:43:40
|
all im saying is Comcast changed something today guys..... and i found a work around you cant have ASSP listening on port 25 on both interfaces or a bunch of routing loops ensue in my config here incoming --> port 25 --> (pub)assp(prv) --> mta on private box (listening on 25) assp box runing iptables outgoing mta on private box (sending on 25) -- assp's box(with ASSP relaying turned off) -->out public interface to destination NOT via ISP mta if i turn on ASSP's relayport to listen via 25 (you have to split listening on an internet interface from a private interface) mail goes all over and the mta piles up stuff in the deferred queue comcast complains and sends back the bad relaying messages from the mta itself its quite the mess problem is groupwise 6.5 cant have split ports for in/out like i use with exchange if gwia could send OUT on 125 and Assp relayport was set to 125, then all would work. then i can ELECT to use the relayhost parameter of smtp.comcast.net:25 1) if I wanted to use the Comcast mta as a smarthost, but you cant anymore since they changed their dns requirements. IE the mail would be seen as needing to come from x,x.x.x where the rdns points from. but if you relay through comcast, the rdns for my mx record will not match the comcast mta ip address and we get nasty messages from them. its their fault everything worked fine until today I just lose my inline-auto whitelist because gwia only can send on the same port it listens on 2) what happens when i enable ASSP relayport=25 to match the incoming? a shitload of either mail relaying errors, nasty 554 messages from comcast or mail stuck in the outbox ah computers..... -- View this message in context: http://www.nabble.com/Comcast-screws-with-outbound-mail-tp24276038p24281799.html Sent from the assp-user mailing list archive at Nabble.com. |