[exim] Re: Imposing a conditional delay on incoming emails
On 22. januára 2025 10:32:40 UTC, Odhiambo Washington via Exim-users wrote: >the_local_p...@mydomain.name * sender@some_domain_name F,24h,1m Try to use: local@mydomain * senders=sender@domain ... regards -- Slavko https://www.slavino.sk/ -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Re: Imposing a conditional delay on incoming emails
On Wed, Jan 22, 2025 at 2:01 PM Slavko via Exim-users < exim-users@lists.exim.org> wrote: > On 22. januára 2025 10:32:40 UTC, Odhiambo Washington via Exim-users < > exim-users@lists.exim.org> wrote: > > >the_local_p...@mydomain.name * sender@some_domain_name F,24h,1m > > Try to use: > > local@mydomain * senders=sender@domain ... > > regards > Thank you very much. I had to read the whole chapter again to find this. Lesson learnt. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Re: Imposing a conditional delay on incoming emails
On Wed, 22 Jan 2025, Odhiambo Washington via Exim-users wrote:
Happy New Year to everyone.
I have the need to impose a 24-hr delay on emails from john...@johndoe.com
to a local recipient.
I have found this config snippet:
https://github.com/Exim/exim/blob/master/doc/doc-src/FAQ.src#L6892
So I created a router as suggested:
delay_incoming:
driver = redirect
domains = mydomain.name
local_parts = the_local_part
senders = sender@some_domain_name
condition = ${if < {$message_age}{86400}{yes}{no}}
allow_defer
data = :defer: message not old enough
no_verify
I tested the router and the email from sender@some_domain_name stayed in
the queue for some time, then it got delivered, I suppose on the next queue
run.
The FAQ says one may want to set a special retry rule, so I figured out I
must create a specific rule for this sender and the recipient.
Looking at the Exim spec, I am missing something on the form this rule is
supposed to take. I have:
the_local_p...@mydomain.name * sender@some_domain_name F,24h,1m
Do you mean to retry every minute for 24 hours ?
--
Andrew C. Aitchison Kendal, UK
and...@aitchison.me.uk
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscr...@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Re: Imposing a conditional delay on incoming emails
On Wed, Jan 22, 2025 at 6:40 PM Leonardo Boselli wrote: > On Wed, 22 Jan 2025, Odhiambo Washington via Exim-users wrote: > (…) > > The whole exercise is not being implemented because there is any problem, > > but because we do not want > > emails from the sender, addressed to a Mailman ML, to be delivered > > immediately due to some 'political' reasons :) > > I could also use Mailman's moderation bit, but that would create a job > for > > the moderators so it better happens without human intervention. > > but later he wrote: > > > The true intention is to delay emails from the sender from hitting the > > Mailman3 ML. > > That way we can decide on its (in)appropriateness to our Mailing List. > > Sender -> Exim -> Mailman3 -> Mailing List subscribers - for now, we > > cause Exim not to deliver it to MM3 until we decide. > > so in any case moderator are involved. so i do not understand why you want > a different treatment for that sender. > The only reason would be that if moderator do not find an agreement the > messge is automatically released after 24 hours. > But i would not like such a list. You don't have to like the list. This is a measure taken only for 1 individual. Several other thousands of subscribers are not subjected to this. I think I mentioned it's a 'political' decision. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Re: Imposing a conditional delay on incoming emails
On Wed, Jan 22, 2025 at 2:31 PM Andrew C Aitchison via Exim-users <
exim-users@lists.exim.org> wrote:
> On Wed, 22 Jan 2025, Odhiambo Washington via Exim-users wrote:
>
> > Happy New Year to everyone.
> >
> > I have the need to impose a 24-hr delay on emails from
> john...@johndoe.com
> > to a local recipient.
> > I have found this config snippet:
> > https://github.com/Exim/exim/blob/master/doc/doc-src/FAQ.src#L6892
> > So I created a router as suggested:
> >
> > delay_incoming:
> > driver = redirect
> > domains = mydomain.name
> > local_parts = the_local_part
> > senders = sender@some_domain_name
> > condition = ${if < {$message_age}{86400}{yes}{no}}
> > allow_defer
> > data = :defer: message not old enough
> > no_verify
> >
> > I tested the router and the email from sender@some_domain_name stayed in
> > the queue for some time, then it got delivered, I suppose on the next
> queue
> > run.
> > The FAQ says one may want to set a special retry rule, so I figured out I
> > must create a specific rule for this sender and the recipient.
> > Looking at the Exim spec, I am missing something on the form this rule is
> > supposed to take. I have:
> >
> > the_local_p...@mydomain.name * sender@some_domain_name F,24h,1m
>
> Do you mean to retry every minute for 24 hours ?
>
Wait a moment! I think I missed a point on that timing.
I need the email to stay in the queue and be delivered after 24hrs.
So is the correct retry I need written as F,1d,24h - to mean, retry every
24hrs for 1d?
Thanks for offering me a 3rd eye.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions:
http://www.catb.org/~esr/faqs/smart-questions.html]
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscr...@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Re: Imposing a conditional delay on incoming emails
On Wed, Jan 22, 2025 at 3:37 PM Slavko via Exim-users < exim-users@lists.exim.org> wrote: > On 22. januára 2025 11:54:51 UTC, Odhiambo Washington via Exim-users < > exim-users@lists.exim.org> wrote: > > >So is the correct retry I need written as F,1d,24h - to mean, retry every > >24hrs for 1d? > > F,1d,24h: > > + F = retry at fixed intervals > + 1d = retry for 1day, after that go to next definition or bounce > + 24h = retry after every 24 hours > > IMO, it can work, but will be less than optimal, as on any delivery > problem (even short time) at time of delivery will result in bounce. > I am not sure what will really happen, as end of retry time happens > in the same as first retry (1d = 24h), someone other must comment. > > Anyway, you will want to retry multiple times. I would copy default > (on debian) retry times after that, adjusted to that first 24h delay, > eg.: > > F,1d,24h; F,2h,15m; G,16h,1h,1.5; F,3d,6h > The whole exercise is not being implemented because there is any problem, but because we do not want emails from the sender, addressed to a Mailman ML, to be delivered immediately due to some 'political' reasons :) I could also use Mailman's moderation bit, but that would create a job for the moderators so it better happens without human intervention. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Re: Imposing a conditional delay on incoming emails
On 22/01/2025 12:35, Slavko via Exim-users wrote: IMO, it can work, but will be less than optimal Yeah, abusing the retry mech for this (I assume the delay is to permit manual inspection of outbound messages) is not wonderful. I'd be tempted to divert the message to an alternate named-queue. -- Cheers, Jeremy -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Re: Imposing a conditional delay on incoming emails
On Wed, Jan 22, 2025 at 3:53 PM Jeremy Harris via Exim-users < exim-users@lists.exim.org> wrote: > On 22/01/2025 12:35, Slavko via Exim-users wrote: > > IMO, it can work, but will be less than optimal > > Yeah, abusing the retry mech for this (I assume the > delay is to permit manual inspection of outbound messages) > is not wonderful. > > I'd be tempted to divert the message to an alternate named-queue. > The true intention is to delay emails from the sender from hitting the Mailman3 ML. That way we can decide on its (in)appropriateness to our Mailing List. Sender -> Exim -> Mailman3 -> Mailing List subscribers - for now, we cause Exim not to deliver it to MM3 until we decide. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Re: Imposing a conditional delay on incoming emails
On Wed, 22 Jan 2025, Odhiambo Washington via Exim-users wrote: (…) The whole exercise is not being implemented because there is any problem, but because we do not want emails from the sender, addressed to a Mailman ML, to be delivered immediately due to some 'political' reasons :) I could also use Mailman's moderation bit, but that would create a job for the moderators so it better happens without human intervention. but later he wrote: The true intention is to delay emails from the sender from hitting the Mailman3 ML. That way we can decide on its (in)appropriateness to our Mailing List. Sender -> Exim -> Mailman3 -> Mailing List subscribers - for now, we cause Exim not to deliver it to MM3 until we decide. so in any case moderator are involved. so i do not understand why you want a different treatment for that sender. The only reason would be that if moderator do not find an agreement the messge is automatically released after 24 hours. But i would not like such a list. -- Leonardo Boselli Firenze, Toscana, Europa http://i.trail.it -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Re: Imposing a conditional delay on incoming emails
On 22. januára 2025 11:54:51 UTC, Odhiambo Washington via Exim-users wrote: >So is the correct retry I need written as F,1d,24h - to mean, retry every >24hrs for 1d? F,1d,24h: + F = retry at fixed intervals + 1d = retry for 1day, after that go to next definition or bounce + 24h = retry after every 24 hours IMO, it can work, but will be less than optimal, as on any delivery problem (even short time) at time of delivery will result in bounce. I am not sure what will really happen, as end of retry time happens in the same as first retry (1d = 24h), someone other must comment. Anyway, you will want to retry multiple times. I would copy default (on debian) retry times after that, adjusted to that first 24h delay, eg.: F,1d,24h; F,2h,15m; G,16h,1h,1.5; F,3d,6h regards -- Slavko https://www.slavino.sk/ -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Imposing a conditional delay on incoming emails
Happy New Year to everyone.
I have the need to impose a 24-hr delay on emails from john...@johndoe.com
to a local recipient.
I have found this config snippet:
https://github.com/Exim/exim/blob/master/doc/doc-src/FAQ.src#L6892
So I created a router as suggested:
delay_incoming:
driver = redirect
domains = mydomain.name
local_parts = the_local_part
senders = sender@some_domain_name
condition = ${if < {$message_age}{86400}{yes}{no}}
allow_defer
data = :defer: message not old enough
no_verify
I tested the router and the email from sender@some_domain_name stayed in
the queue for some time, then it got delivered, I suppose on the next queue
run.
The FAQ says one may want to set a special retry rule, so I figured out I
must create a specific rule for this sender and the recipient.
Looking at the Exim spec, I am missing something on the form this rule is
supposed to take. I have:
the_local_p...@mydomain.name * sender@some_domain_name F,24h,1m
But Exim gives the error below. Line 2245 contains the above retry rule.
Jan 22 13:26:56 FQDN exim4[503251]: Starting MTA:
Jan 22 13:26:56 FQDN exim4[503256]: 2025-01-22 13:26:56 cwd=/ 2 args:
/usr/sbin/exim4 -bV
Jan 22 13:26:56 FQDN exim4[503256]: 2025-01-22 13:26:56 Exim configuration
error in line 2245 of /etc/exim4/exim4.conf:
Jan 22 13:26:56 FQDN exim4[503256]: comma expected
Jan 22 13:26:56 FQDN exim4[503251]: Warning! Invalid configuration file for
exim4. Exitingfailed.
Jan 22 13:26:56 FQDN systemd[1]: exim4.service: Control process exited,
code=exited, status=1/FAILURE
Kindly advise on where the mistake it.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions:
http://www.catb.org/~esr/faqs/smart-questions.html]
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscr...@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Re: Imposing a conditional delay on incoming emails
On 2025-01-22 Odhiambo Washington via Exim-users
wrote:
> Happy New Year to everyone.
> I have the need to impose a 24-hr delay on emails from john...@johndoe.com
> to a local recipient.
> I have found this config snippet:
> https://github.com/Exim/exim/blob/master/doc/doc-src/FAQ.src#L6892
> So I created a router as suggested:
> delay_incoming:
> driver = redirect
> domains = mydomain.name
> local_parts = the_local_part
> senders = sender@some_domain_name
> condition = ${if < {$message_age}{86400}{yes}{no}}
> allow_defer
> data = :defer: message not old enough
> no_verify
> I tested the router and the email from sender@some_domain_name stayed in
> the queue for some time, then it got delivered, I suppose on the next queue
> run.
> The FAQ says one may want to set a special retry rule, so I figured out I
> must create a specific rule for this sender and the recipient.
> Looking at the Exim spec, I am missing something on the form this rule is
> supposed to take. I have:
> the_local_p...@mydomain.name * sender@some_domain_name F,24h,1m
[...]
Hello,
I think the FAQ-response is too short. (But I fail to quickly come up with
a better one)
A9807: Set up a router like this:
[... router ... ]
| Of course, this will also have the effect of setting a retry time for
| the address. You may want to set a special retry rule for it. Note the
| use of \no_verify\ to ensure that this router is not used when Exim is
| verifying addresses.
Afaiui the reason that retry rules need to changed is to avoid delaying
longer than 24 hours. - Since every message is defered retry rules with
long intervals will hit. Using the default config
* * F,2h,15m; G,16h,1h,1.5; F,4d,6h
messages will be delayed by not 24 but 24+6 hours. (They defered for a
long time and hit the F,4d,6h-part) So you would want to modify this to
have small retry intervals (15m?) for up to 25 hours. Setting a long
interval for the first 24 hours would just be an optional performance
optimization. Deferal is caused by the router, not the retry rule.
I think reception of a second or third to-be-deferred message while the
first one is still deferred does not make difference BTW. (Unless exim
does not retry the oldes message first and messages queu up until the
*newset* one is 24 hours old. - If it does not the whole scheme
breaks and messages queue up until the *newset* one is 24 hours old.)
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscr...@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Re: Blocking incoming mail from domains using a specific MX entry
Am 22.01.25 um 08:21 schrieb Evgeniy Berdnikov via Exim-users: On Wed, Jan 22, 2025 at 08:02:22AM +0100, Martin Waschbüsch via Exim-users wrote: And yes, this is not something to use lightly, but there are literally several hundred fake domains I identified all using this one MX... I am quite sure in this instance. ;-) If so, you can easily block this MX by IP address. You misunderstand, I think. The domains have loads of different relays, with loads of different IPs. The mails are not sent from / by the MX. And none of those IPs match their MX's IP. But all domains happen to have the same MX. -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
