I still do not follow. Port 25 for all in and out mail is normal, unless you are acting as a smart host or something similar.
Why not let your MTA stand on it's own, and act like a MTA, sending it's own email. You would only ever get email going across smtp.comcast.net if you had an outbound message for them. Same for inbound, you would only get email on smtp.comcast.net if that email server had email destined for you. The spelling of your rDNS does not matter, they are only checking for existence, if it is there, that is the only qualification you need to make. The reasons to name it a certain way are to prevent getting stuck in a filter or DNS list that bases their lists on patterns that your rDNS may appear to fall into. For example, mine is c-67-166-201-21.hsd1.ca.comcast which clearly looks dynamic, and may be blocked by other ISP's, but I am also not going to run an email server on a dynamic/semi-static IP. You can not have two rDNS records, that is not possible, each IP can only have one PTR. You mentioned you are on comcast business. What is your IP, you can drop the last /24 off the ip if you do not want to share, it, so just give the first 3 octets. I just found this range, listed as comcast business class: 75.144.0.0 - 75.151.255.255, picking a random one of ;; QUESTION SECTION: ;100.123.150.75.in-addr.arpa. IN PTR ;; ANSWER SECTION: 100.123.150.75.in-addr.arpa. 3600 IN PTR 75-150-123-100- NewEngland.hfc.comcastbusiness.net. They have rDNS, there is only one PTR, and that meets the qualifications to run an email server or proxy that anyone can send and receive email from. Can you explain exactly what the issue is? You were not able to deliver email outbound? You were sending it to smtp.comcast.net? If so, why, why not use your MTA as it was intended? If you are not able to send outbound, what are the errors you are getting? I have a hunch, you are hitting DNSBL's, and just need to contact them to let them know they have comcast IP space listed as dynamic, when it is in fact static. Or ask to be whitelisted. On Jun 30, 2009, at 3:37 PM, bytehd wrote: > > thanks for all the help guys > > here is what i had to do. > > i reverted to using port 25 for all incoming and outgoing mail. > i cant run two copies of groupwise mta on the same netware box, so > we are > looking to go GW8 or > another linux OSS solution. > we are NOT using smtp.comcast.net in ASSP for an outbound relay > because > Comcast started sending a new message back at 8am this morning:" 554 > please > go to our site and look at the VBOB warning" > > THEY changed behavior, not me. > Supposedly they blew away my RDNS record in the past. > When they put the new mta checks in place, my lack of one triggered > their > error message. > > When I did the dig -x command, they have two entries for us, one is > misspelled. > > Its typical of Comcast to NOT tell their business clients of network- > wide > changes > > like how 1/2 the mid-atlantic service area is down today etc. > > time for a new MTA too... -- 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
