On Mon, 31 Mar 2014, Jacco van Gent wrote: > From: Jacco van Gent <[email protected]> > To: Exim-users <[email protected]> > Date: Mon, 31 Mar 2014 07:08:12 > Subject: Re: [exim] retry timeout exceeded
... > I am using Mailscanner together with Baruwa 2.0, their setup > suggest deferring the message, so that Mailscanner can process > it and write message data to a postgresql database. If I am not > mistaken, this is the same approach Mailscanner suggests on their > website. > > They to suggest deferring the message (for message scans), > scanning the message and then calling exim to send it out. The > missing link to me seems the part where the retry database isn't > updated when that second step successfully sends the message to > the backend SMTP server. ... I've never used Mailscanner. However I thought the recommended use was to have two exim processes. The first runs in queue-only mode accepting messages. Mailscanner picks up the messages from the spool directory for this exim process, processes them, and then puts them in the spool directory for a second exim process that performs the actual delivery. The above procedure is described in: http://www.mailscanner.info/exim.html -- Dennis Davis <[email protected]> -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
