On Mittwoch, 9. April 2008 Paul J Stevens wrote: > This could be a race condition where two dbmail-lmtpd or dbmail-smtp > processes try to store the same headername at the same time. > > Solving this type of concurrency issue is a driver for 2.3+ > development.
I thought about this too. A simple quick solution would be not to break the transaction because of this, in order to make a successful delivery. But as it's not too often, it can be ignored, I guess. What happens to the e-mail whose transaction is aborted? Lost, or thrown back at postfix which retries again later? Horrible would be an error back to the sender (looks unprofessional). mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: www.keyserver.net Key-ID: 1C1209B4
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
