Re: [exim] SMTP response on restricted alias

Top Page
Delete this message
Reply to this message
Author: Tony Finch
Date:  
To: Illtud Daniel
CC: exim-users
Subject: Re: [exim] SMTP response on restricted alias
On Tue, 2 May 2006, Illtud Daniel wrote:
>
> My only problem is that if an alias is restricted, and you're
> not on the allow list, you get an 'unknown user' SMTP response.


This is probably because when the precondition fails, Exim goes on to try
the other routers, and will eventually hit the last router, which in the
default configuration has cannot_route_message = Unknown user

> How can I add a 'not authorized to send to $local_part' SMTP
> response? I suspect I'll have to split it into another router.


That would probably be easier - it's what we do for obsolete domains.

# Decommissioned domains with special error messages.
# The lookup returns the error message in $domain_data.
#
domainlist obsolete_domains =    cdb;DB/obsolete.cdb


domain_obsolete:
  driver        = redirect
  domains        = +obsolete_domains
  data            = :fail: $domain_data
  allow_fail


> Another problem that has arisen (discovered when I couldn't
> post to this list!) is that somehow this senders precondition
> is causing exim to answer with a 550 to a null MAIL FROM:
> address. Why would that be?


I'm not sure about that. Try seeing if a debug run provides enlightenment.

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}}