Thanks for that tony, it helps a good deal.
-----Original Message-----
From: Tony Finch [
mailto:fanf2@hermes.cam.ac.uk] On Behalf Of Tony Finch
Sent: 12 April 2006 17:02
To: Catherine Morrisroe
Cc: exim-users@???
Subject: RE: [SPAM] - Re: [exim] How to deal with '<>' mails - Bayesian
Filter detected spam
On Wed, 12 Apr 2006, Catherine Morrisroe wrote:
>
> I am trying to get it to check for the null sender address and then do
> the verify on the recipient but I just can't get it to work, its
failing
> on the check for the null sender address and not getting as far as the
> verify.
The start of the section about "address lists" in the spec explains the
pertinent point:
http://www.exim.org/exim-html-4.60/doc/html/spec.html/ch10.html#SECTaddr
esslist
> Address lists contain patterns that are matched against mail
addresses.
> There is one special case to be considered: the sender address of a
> bounce message is always empty. You can test for this by providing an
> empty item in an address list. For example, you can set up a router to
> process bounce messages by using this option setting:
>
> senders = :
>
> The presence of the colon creates an empty item. If you do not provide
> any data, the list is empty and matches nothing. The empty sender can
> also be detected by a regular expression that matches an empty string,
> and by a query-style lookup that succeeds when $sender_address is
empty.
The actual check we have in our configuration is:
# Require valid recipient addresses on bounce messages.
deny
senders = :
! verify = recipient/callout=CALLTIME
The CALLTIME macro is defined with:
# standard callout timeouts
#
CALLTIME = 4m,maxwait=4m,connect=30s
Tony.
--
<fanf@???> <dot@???>
http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}
