The relevant part of the SA output I was thinking of is below
=============================
debug: Initialising learner
debug: received-header: parsed as [ ip=216.131.194.35 rdns=psh-note-26.corp.peop
lesoft.com helo=psh-note-26.corp.peoplesoft.com by=mail03.peoplesoft.com ident=
]
debug: is Net::DNS::Resolver available? yes
debug: servers: int.billsden.org
debug: Looking up MX records for user specified servers: int.billsden.org
debug: trying (3) int.billsden.org...
debug: looking up MX for 'int.billsden.org'
debug: MX for 'int.billsden.org' exists? 1
debug: MX lookup of int.billsden.org succeeded => Dns available (set dns_availab
le to hardcode)
debug: is DNS available? 1
debug: looking up PTR record for '216.131.195.63'
debug: PTR for '216.131.195.63': 'unk-131-195-63.peoplesoft.com'
debug: received-header: parsed as [ ip=216.131.195.63 rdns=unk-131-195-63.peoplesoft.com helo= by=psh-note-26.corp.peoplesoft.com ident= ]
debug: received-header: 'by' mail03.peoplesoft.com has public IP 192.206.43.75
debug: received-header: relay 216.131.194.35 trusted? no
debug: received-header: relay 216.131.195.63 trusted? no
======================================
In reading Received.pm and EvalTests.pm, it appears as though it only goes as far as MX lookup on domain and rDNS to confirm the identity of the MX host. So the callback you mentioned isn't there. But perhaps this could prove a starting point to which the callback could be added for a Coruier::Filter?
I have found information suggesting Exim has such functionality (From conf file examples):
sender_verify_hosts_callback = * sender_verify_callback_domains = *
In fact, it would appear this is what SourceForge is using. According to their docs, the SMTP dialog looks like this:
220 mail.server.tld ESMTP Sendmail 8.9.3/8.9.3; Thu, 19 Jul 2001 11:03:19 -0700 (PDT)
helo foo
220 welcome foo
mail from: <>
250 <>... Sender ok
rcpt to: [EMAIL PROTECTED]
250 [EMAIL PROTECTED] Recipient ok
rset
250 Reset state
mail from: <>
250 <>... Sender ok
rcpt to: [EMAIL PROTECTED]
250 [EMAIL PROTECTED] Recipient ok
quit
221 mail.server.tld closing connection
So maybe a combination of SA functionality (to do basic MX lookup testing) followed by a full MX callback? I tracked the callback function to verify.c in the Exim source. Now just to find time to sit down and write code. :-)
Bill
Jeff Potter wrote:
Doesn't SA have a check for this very thing? Not sure if you're using it with amavisd-new as a courierfilter or not. But then I suppose it wouldn't be too had to graft the code from SA into a Courier::Filter script and drop it in as a filter to cause such messages to bounce upon submission. :-)
That would be great, actually -- we are running amavis-new, so it's easy enough to add the spam assassin rule. If I could just find what it's called! I looked at the list (spamassassin.org/tests.html) but didn't find one that did actual dial-back. You wouldn't happen to know the name, or know if it's an external addition?
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
