I do not understand, rDNS has been a long used method in checking a hostname on an email server. Some go further than rDNS, and actually look at the rDNS name, and make sure it has a email server sitting at it.
Some want to even see the rDNS in a certain format. That is a little aggressive for my liking. Either way, you need to have rDNS, so I do not think this is a comcast issue. If this really is your problem, it is not just comcast, many other places are not going to accept your email as well. There is a difference between not having rDNS, and not having specifically named rDNS. Are you sure you are not getting the two confused? Not many are even delegated to be able to add their own PTR records. You can use `dig -x ip.add.ress` to find out. On Jun 30, 2009, at 10:18 AM, bytehd wrote: > Now I cant point my MTA to ASSP anymore for outgoing. > I have to point it straight to the outbound router IP for outgoing > mail to > be accepted. > They started requiring a reverse DNS record this morning. > Guess what, they never setup a RDNS MX for me...until today. > But now that its active, I lose the ability to auto-add to whitelist > through > ASSP. > > ASSP Relaying settings have not changed AT ALL. > Seems whatever Comcast is using for mail filtering doesnt like ASSP > relaying > stuff out. > ASSP 1.4.3.1.1 > relayhost:smtp.comcast.net > relayport: 25 > > mta points outgoing to ASSP IP > ASSP has dual NICs: Public and Private > IPTables doing the routing. -- Scott * If you contact me off list replace talklists@ with scott@ * ------------------------------------------------------------------------------ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
