Re: [exim] where's the deny message?

Αρχική Σελίδα
Delete this message
Reply to this message
Συντάκτης: W B Hacker
Ημερομηνία:  
Προς: exim users
Αντικείμενο: Re: [exim] where's the deny message?
Jeff Lasman wrote:
> Running exim version 4.60
>
> Our deny message is disappearing:
>
> Here's the acl that otherwise works:
>
> <snip>
> # deny email addresses in blacklist_senders
> deny message = Email blocked by BSAL - to unblock see
> http://www.spamblocked.net/blocked.html
> domains = use_rbl_domains
> deny senders = +blacklist_senders
> </snip>
>
> note that your email client may have wrapped the line beginning with
> "deny message"; it's NOT wrapped in our exim.conf.
>
> But this is what shows up in the logs (the email address has been
> slightly munged, to a nonexistent sender to avoid problems caused by
> scraping from archives:
>
> <snip>
> 2007-01-10 18:04:10 H=da12.namelessnet.net [4.79.140.132]
> F=<jlasman@???> rejected RCPT <jlasman@???>
> 2007-01-10 18:04:10 H=da12.namelessnet.net [4.79.140.132] incomplete
> transaction (QUIT) from <jlasman@???>
> </snip>
> note there are two lines above, each wrapped.
>
> Whereas the acls based on blocklists appear to work as they should:
>
> <snip>
> 2007-01-07 04:04:26 H=([195.218.197.22]) [195.218.197.22]
> F=<example@???> rejected RCPT <example@???>: Email
> blocked by CBL - to unblock see http://www.spamblocked.net/
> 2007-01-07 04:04:27 H=([195.218.197.22]) [195.218.197.22] incomplete
> transaction (connection lost) from <example@???>
> </snip>
> the above consists of two lines each beginning with the date; the email
> addresses are munged.
>
> I don't know if this is a new behavior based on a recent version
> upgrade, or if it's been around; it was just brought to my attention
> today.
>
> Any ideas?
>
> Jeff


First thing I would suggest is to check the log timestamp of that lost
connection against the timestamp of the initial connect for the same session.

Second would be to (temporarily) add BOTH a 'logwrite' AND a 'log_message' to
that acl clause to see if in fact it is even being involved in the incomplete
transaction.

You may be timing-out on a lookup, or some other acl than the one you are
looking for may be involved.

HTH,

Bill