Re: [exim] A Tight Exim Config

Top Page
Delete this message
Reply to this message
Author: Jon Hardcastle
Date:  
To: exim-users, Heiko Schlittermann
Subject: Re: [exim] A Tight Exim Config


--- On Tue, 15/9/09, Heiko Schlittermann <hs@???> wrote:

> From: Heiko Schlittermann <hs@???>
> Subject: Re: [exim] A Tight Exim Config
> To: exim-users@???
> Date: Tuesday, 15 September, 2009, 10:11 AM
> Hello Jon,
> Jon Hardcastle <jd_hardcastle@???>
> (Di 15 Sep 2009 10:27:43 CEST):
> >
> > Thank you for your reply to my email. When i say
> arrived I mean delivered. It is *all* about making sure with
> as much certainty as possible that the message has been
> delivered.
> >
>
> Exim is reliable. It delivers the message to the next hop
> or it returns
> the message. If the delivery fails temporarly, it retries
> (based on
> configurable rules). If your application uses a proper
> return address
> (envelope-from), exim will return the message on delivery
> errors and it
> is up to you to parse the returned message (bounce). There
> is no need to
> parse any log file.
>
> If the return address is an local address on the exim host,
> you have
> several options to receive the bounces: delivery into an
> mbox file,
> delivery via a command pipe into your application, or
> delivery via LMTP
> into your application (LMTP via a local socket or via
> network).
>
> > How do the 'captains of industry' do this? If i turn
> the retry details in exim right down and manage that myself
> will that work? Alternatively does anyone parse the log to
> find the status of their message?
> >
>
> I'm not sure why you don't want to rely on exim's retry
> rules. They're
> „industry proven“. But of course, you could strip them
> down to get
> bounces immediatly if exim faces a temporary problem.
>
> Alternativly you could inspect the message spool to get
> information about
> *pending* messages: „expick …“ will help you.
>
>     Best regards from Dresden/Germany
>     Viele Grüße aus Dresden
>     Heiko Schlittermann
> --
>


So is that how it is then? you have to check the bounce back? I was hoping that exim could tell my code while the smtp connection was up? What is the standard way of doing this programatically?


-----------------------
N: Jon Hardcastle
E: Jon@???
'Do not worry about tomorrow, for tomorrow will bring worries of its own.'
-----------------------