> -----Original Message-----
> From: Jeremy Harris [mailto:jgh@wizmail.org]
> Sent: Wednesday, June 08, 2005 2:34 PM
> To: andrew.johnson@???
> Subject: Re: [exim] Message ID's / Message tracking
>
> Andrew Johnson wrote:
> > Not sure how useful that will be given 50 million messages a month,
> > and also
>
> That's the sticking point indeed, but mightly be worth trying.
>
> Hmm, 20/sec plus a bit for catching up after daytime peaks
> (you don't absolutely need realtime access, do you?).
> Doesn't sound like a totally impossible DB load.
>
> > we can't guarantee unique message id's using the supplied one...
>
> Indeed; but at least you should only get false-pos', and
> relatively few of them.
>
> For those generated by your exim, check the localhost_number option.
>
We estimate at peak time a shade over 50 messages per second, and as you say
it's not an impossible DB load.
No, we don't need realtime access, infact we were thinking of possibly
parsing the logs overnight (after rotation) into a database (Probably Oracle
- which exilog doesn’t support unless I missed something)
We use the localhost_number option to ensure uniqueness of our generated
ID's.
One issue is that as it goes through each of the stages (Reception, deliver
to AV appliacnce, reception from AV appliance, delivery to remote
destination) we would need to log each as a separate transaction - this
would be confusing if the ID was not unique... Therefore I'd like to
log/process the exim one.
Thanks for the ideas though - it's nice to bounce possibilities off others
:)
-Andy-
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.6.5 - Release Date: 07/06/2005
