Re: [exim] Queue ID format

On 24/12/2020 23:30, Yves Goergen via Exim-users wrote: Well, if that log was intended for humans, would it be an interesting idea to write a machine-readable log as well? See bugs 2142 and 2610. So far, not enough actual interest to get anyone to put the effort into the developement and

Re: [exim] Queue ID format

Thanks for the links. That makes me more confident that I can restrict parsing on that format. The regex you referenced is exactly what I have thought of. So that's good. :-) -Yves Ursprüngliche Nachricht Von: Graeme Fowler via Exim-users Gesendet: Donnerstag, 24. Dezember

Re: [exim] Queue ID format

On 24/12/2020 22:17, Yves Goergen via Exim-users wrote: I'm parsing Exim log files, specifically the mainlog. Man, that's a complex structure and it's hard to find all necessary details from the documentation and by reading my actual log files. I'm using several regular expressions for

Re: [exim] Queue ID format

On 24 Dec 2020, at 22:17, Yves Goergen via Exim-users wrote: > What assumptions can I make about the format of a queue message ID? For now, > I use this regex: https://www.exim.org/exim-html-current/doc/html/spec_html/ch-how_exim_receives_and_delivers_mail.html#SECTmessiden You may

[exim] Queue ID format

Hello, I'm parsing Exim log files, specifically the mainlog. Man, that's a complex structure and it's hard to find all necessary details from the documentation and by reading my actual log files. I'm using several regular expressions for different kinds of lines. But a stateful parser (the

Re: [exim] Taint mismatch, string_nextinlist: expand_getlistele 1309

On 23/12/2020 22:05, Jeremy Harris via Exim-users wrote: On 21/12/2020 12:50, Bart Noordervliet via Exim-users wrote: Taint mismatch, string_nextinlist: expand_getlistele 1309 The fix will be available in the next few days. Commit 942f0be6c2. -- Cheers, Jeremy -- ## List details at

[exim] MX record exists but exim doesn't detect it

I'm having many confusions while setting up exim. I use Parabola GNU OS (Arch) I'm executing exim -bt -d-resolver anonym...@designman.org I get DNS lookup of designman.org(MX) gave TRY_AGAIN but "dig @8.8.8.8 designman.org MX" shows a record designman.org.  3599   IN   MX

Re: [exim] Forward from external immediately without queue

DSN (Delivery Status Notification) is another name for the bounches. Basically, if the remote delivery fails, DONT send a bounce back to the sender. Same domain = the domain the server is authorative for. Basically, IF sender == "" and receiver != "*@yourdomain.com" then redirect to

Re: [exim] Forward from external immediately without queue

Do I have a DSN at all? Exim is doing the second delivery (forward) itself and fails itself, it is not sent a bounce back that it needs to forward. Also, what is "the same domain"? -Yves Ursprüngliche Nachricht Von: Sebastian Nielsen via Exim-users Gesendet: Donnerstag,

Re: [exim] Forward from external immediately without queue

Simple solution is to configure the server to not send any DSNs for forwards at all. Since DSNs do have a blank sender, a trick is to have a router which detects a blank sender, and if receiver of the bounce isn't someone on the same domain, then blackholes it. (use :blackhole: as redirect data)