Curious on how restrictive others are making their subscriber_networks filter, And how forgiving of servers who's reverse DNS matches the filter. What "best practices" are others following, and whats reasonable in your opinions.
What brings this up is I spent half the day arguing with some list provider because their HELO is an IP address, and is not ip-literal as the RFC asks. I kept quoting the RFC and they said they believed they were following and would not change. Whats funny is the thread started with a quote from them to my customer saying they often have problems with spam filters blocking them... I wonder why.. LOL And now today this regexp is causing 'greif' /(.*\.customer\..*)/ REJECT ACL subscriber_network, (customer) ..... Oct 8 11:58:30 mx1 postfix1/smtpd[35821]: 37D0E1FB326: reject: RCPT from tri-lakes-net-130.bran.customer.centurytel.net[69.29.40.130]: 554 <tri-lakes-net-130.bran.customer.centurytel.net[69.29.40.130]>: Client host rejected: ACL subscriber_network, (customer) see http://mx.nwfl.net/?a=sn&m=tri-lakes-net-130.bran.customer.centurytel.net; from=<[EMAIL PROTECTED]> to=<[EMAIL PROTECTED]> proto=ESMTP Now their MX does point to that IP, And they have several ips in that range delegated to them, But it looks like centurytel.net still has authority. Now a quick fix on my part is a DUNNO of course, But I'de rather see them get their own REVDNS without the word "customer" or maybe with "mx" somewhere in there... Do you guys thing that's reasonable? What are others doing? Thanks in advancce, Tom
