On Tue, 10 Aug 2004, LuKreme wrote:My mail server does double duty as my secondary MX, so the r-DNS for
64.140.43.68 is ns2.covisp.net instead of mail.covisp.net. Is the fact
that the domain and tld are the same good enugh for
whitelist_from_rcvd?
I think that you didn't understanding me. I was talking about the sending mail server, not the receiving mail server.
I was trying to white list admin cron notices, so the sender and receiver are the same. They keep getting marked as spam (probably because the contain the logged IP's, envelope froms, and EHLO's of rejected senders)
Maybe a little example will clarify things. One of my incoming MX servers is: server15.icaen.uiowa.edu and its IP is in my 'trusted_networks' list.
I think I need to look at trusted networks. I thought it was only for external networks.
whitelist_from_rcvd [EMAIL PROTECTED] united.com
And the relevant header from a mail message looks like:
Received: from ulsmlbx02.mail.united.com (ulsmlbx02.mail.united.com [209.87.114.72])
AH, that's good. That will work. I thought the second argument had to be a FQDN.
Thus if the DNS servers for united.com get barfed up whitelist_from_rcvd
does not work. Of course, it also depends upon your MTA generating
proper headers that SA can parse to extract the pertinate info.
I'll continue with a few tests on this.
whitelist_from_rcvd [EMAIL PROTECTED] mail.covisp.net
did not work (at least today's cron mailing did not contain anything in the headers to indicate it did)
X-Spam-Status: No, hits=1.7 required=5.0 tests=ALL_TRUSTED=-0.842,AWL=0.438,
BAYES_00=-2.599,URIBL_SBL=1.723,
This one did not get tagged as spam, but about 1 per week do.
--
Far away, across the fields, the tolling of the iron bell calls the faithful to their knees to hear the softly spoken magic spells.
smime.p7s
Description: S/MIME cryptographic signature
