Re: [exim] problem with mails in queue while config changes routers
On Tue, Dec 28, 2021 at 01:26:54PM +0100, Cyborg via Exim-users wrote: > No idea how exim interally handles this, but exim does not seem to be > flexibel enough to react on dynamic changes in the environment.This is bad > luck, because freezing the mail in the queue is exactly there to wait for > things to change ;) (i.e. an external mx become online again ) No, "frozen" mails are waiting for human attention. They should be handled manually. It is documented in several places, in particular: [ https://www.exim.org/exim-html-current/doc/html/spec_html/ch-how_exim_receives_and_delivers_mail.html ] | "... when a message can neither be delivered to its recipients nor | returned to its sender, the message is marked “frozen” on the spool, | and no more deliveries are attempted. | | An administrator can “thaw” such messages when the problem has been | corrected, and can also freeze individual messages by hand if | necessary. In addition, an administrator can force a delivery error, | causing a bounce message to be sent." [...] So, if you want to keep message in queue with periodic delivery attempts, you should avoid situations which Exim cosiders as "permanent delivery failure" and put message to "frozen" state. -- Eugene Berdnikov -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] problem with mails in queue while config changes routers
Version : 4.94.2 Release : 2.fc34 Architecture: x86_64 Hi, I have found a curios problem in exim: mails, that are in the queue, do not update route status on config changes. We have these two routers, nothing fancy, besides the clever sql to find out, if a local domain has in reality an external domain: externalmx: driver = dnslookup domains = +local_domains condition = .. sql for condition match on premise "domain has external mx".. not important how that works transport = transportselector .. also not important ( decides to use gpg or not ) ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8 no_more dnslookup: driver = dnslookup domains = ! +local_domains transport = transportselector .. also not important ( decides to use gpg or not ) ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8 IF the condition on "externalmx" matches, i.e. because of an wrongfully made entry in the database, but the domain does not really have an external mx, the mail ends up in queue to try to deliver it later. 2021-12-27 11:47:06 1n1nWy-006Ps5-Uo <= SENDER H=ip-XXX (X) [X] P=esmtpsa X=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=no A=LOGIN:X S=385112 id=X 2021-12-27 11:47:06 1n1nWy-006Ps5-Uo lowest numbered MX record points to local host: receiver.domain 2021-12-27 11:47:06 1n1nWy-006Ps5-Uo == to@receiver.domain R=externalmx defer (-1): lowest numbered MX record points to local host 2021-12-27 11:47:06 1n1nWy-006Ps5-Uo Frozen That's fine so far. Now, lets say at 15:00, the db entry is removed, because someone found out, that this is a wrongfully made entry or it simply got outdated by reality(DNS-TTL). The next retry on the stored message does not recognize the necessarity to switch to the now matching router. 2021-12-27 11:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-27 12:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-27 13:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-27 14:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-27 15:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-27 16:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-27 17:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-27 18:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-27 19:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-27 20:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-27 21:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-27 22:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-27 23:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-28 00:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-28 01:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-28 02:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-28 03:53:02 1n1nWy-006Ps5-Uo Message is frozen 2021-12-28 04:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-28 05:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-28 06:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-28 07:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-28 08:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-28 09:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-28 10:52:58 1n1nWy-006Ps5-Uo Message is frozen 2021-12-28 11:52:58 1n1nWy-006Ps5-Uo cancelled by timeout_frozen_after 2021-12-28 11:52:58 1n2A6E-00BYBW-OW <= <> R=1n1nWy-006Ps5-Uo U=exim P=local S=2395 And here it failed permanently. It was stuck on "externalmx". The same mail, send after 15:00 got handles correctly. No idea how exim interally handles this, but exim does not seem to be flexibel enough to react on dynamic changes in the environment.This is bad luck, because freezing the mail in the queue is exactly there to wait for things to change ;) (i.e. an external mx become online again ) Can this already be avoided with implemented functions/settings, or is this something you need to implement in the coming exim 5? Best regards, Marius -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] Running our own email server on GCP
Terrance Devor via Exim-users (Di 28 Dez 2021 00:28:37
CET):
> I have read that google blocks port 25 and 465. We absolutely need to run
> our email own email servers on GCP using our Kubernetes cluster. Did anyone
> succeed in this?
Your message is a bit vague.
- blocks ingress our egress?
- mailserver for ingress (MX) or egress?
- read - where? Any reference?
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --- key ID: F69376CE -
signature.asc
Description: PGP signature
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Truncated warning messages (again)
Hello, Nearly exactly 2 years later, let me remind you all of this thread: https://www.mail-archive.com/exim-users@exim.org/msg54030.html Which ended in a rather frustrating "talking to oneself" session if I may say so. Having run into this in a pre-production testing setup with Debian Bullseye (Exim 4.94.2) I find it to be a massive regression compared to the previous behavior. It makes something that is already hard for most people (as in dealing with warning/error messages esp. for non-native speakers) nearly impossible, esp. when helpful URLs are also cut off. Example in my case: --- The address to which the message has not yet been delivered is: redac...@gmail.com Delay reason: H=alt4.gmail-smtp-in.l.google.com [2607:f8b0:4001:c56::1b]: SMTP error from remote mail server after RCPT TO:: 452-4.2.2 The em --- The actual message (on an older version of Exim) reads of course: --- 452-4.2.2 The email account that you tried to reach is over quota. Please direct 452-4.2.2 the recipient to 452 4.2.2 https://support.google.com/mail/?p=OverQuotaTemp d13si4123901jaq.118 - gsmtp --- Reading the old thread I'd like to point out that this was the only message in the queue and/or destined for gmail. Is there any hope that this will be fixed? Can it be done via some config option to increase the DBM record size? Regards, Christian -- Christian BalzerNetwork/Systems Engineer ch...@gol.com Rakuten Communications -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
