RE: [exim] callout in the name of another origin address tha…

Página Inicial
Delete this message
Reply to this message
Autor: Philip Hazel
Data:  
Para: hauser
CC: 'Tony Finch', exim-users
Tópicos Antigos: RE: [exim] callout in the name of another origin address than the current smtp "from" - e.g. the server admin or any other address of the operating domain - use_postmaster --> temporarily rejected
Novos Tópicos: RE: [exim] callout recipient problems continued: "no_cache" ignored and still "use_postmaster" results in "time value in ACL condition in 10s, defer_ok, random, use_postmaster"
Assunto: RE: [exim] callout in the name of another origin address than the current smtp "from" - e.g. the server admin or any other address of the operating domain - use_postmaster --> temporarily rejected b
On Mon, 22 Nov 2004, Ralf Hauser wrote:

> 1) I might want to specify another local part than "postmaster"


There is currently no way to specify another local part.

> <<5633 H=adsl-62-167-146-248.adslplus.ch (RalfHauser) [62.167.146.248]
> F=<ralfhauser@???> temporarily rejected RCPT <aaaaa1@???>: bad time
> value in ACL condition "verify
> recipient/callout=defer_ok,random,use_postmaster">>


I will check this out. Meantime, try giving it a timeout value:

verify = recipient/callout=10s,defer_ok,random,use_postmaster

> 3) on a 4.31 where I specify neither use_postmaster nor use_sender, a domain
> answers with << 29833 H=217-162-236-62.dclient.hispeed.ch (DELL8600CCA)
> [217.162.236.62] F=<christian@???> rejected RCPT <a.lue@???>:
> response to "MAIL FROM:<christian@???>" from mailgate1.admin.ch
> [162.23.37.19] was: 553 5.1.8 <christian@???>... Domain of sender
> address christian@??? does not exist
> 29833 LOG: smtp_connection MAIN>>, so it appears to have taken use_sender
> and not the empty '<>'?


Did you HUP the daemon after changing the configuration?

> 4) the above then leads to a caching problem: Apparently, the chache is only
> based on the recipient address and not the sender (assume that use_sender
> was set), so once the domain "stgag.om" was corrected to "stgag.com", the
> mail would not go through despite a.lue@??? was correct all the
> time.


Are you using the latest release? Various bugs of this type were mended
in previous releases. Ah, I see you are using 4.31. The following was
fixed in 4.32, for instance:

16. Change 71 for release 4.31 proved to be much less benign that I imagined.  
    Three changes have been made:                                              


    (a) There was a serious bug; a negative response to MAIL caused the whole  
        recipient domain to be cached as invalid, thereby blocking all messages
        to all local parts at the same domain, from all senders. This bug has  
        been fixed. The domain is no longer cached after a negative response to
        MAIL if the sender used is not empty.                                  


    (b) The default behaviour of using MAIL FROM:<> for recipient callouts has 
        been restored.                                                         


    (c) A new callout option, "use_sender" has been added for people who want  
        the modified behaviour.        


Please upgrade to 4.43, the current release.


-- 
Philip Hazel            University of Cambridge Computing Service,
ph10@???      Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book:    http://www.uit.co.uk/exim-book