Re: [exim] Hint for build farmers of "pony" (krot) and "boar" (univie)
Jeremy Harris via Exim-users (So 16 Okt 2022 13:06:06 CEST): > On 16/10/2022 11:06, Heiko Schlittermann via Exim-users wrote: > Also animals marmot & goundhog > - which I suspect means any Debian 9 platform. Yes, that are mine :) and I'm in progress updating them from Debian 9 via 10 to 11. So they should turn green in some minutes (I was out for this afternoon, so no progress in updating). -- Heiko 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/
Re: [exim] Hint for build farmers of "pony" (krot) and "boar" (univie)
Kirill Miazine via Exim-users (So 16 Okt 2022 18:34:19 CEST): > • Heiko Schlittermann via Exim-users [2022-10-16 12:06]: > > Hi, > > > > a recent change in the dmarc.c makes your animals failing the DMARC > > checks for tests using HEAD (default branch "master"). > > As for pony (FreeBSD): none of my animals have DMARC enabled, but both > pony (FreeBSD) and mole (OpenBSD) are referencing *DANE* in errors. Didn't I see there DMARC related build errors? Hm. If that was my fault, just ignore "pony" and my mail :) -- Heiko 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/
Re: [exim] Hint for build farmers of "pony" (krot) and "boar" (univie)
• Heiko Schlittermann via Exim-users [2022-10-16 12:06]: > Hi, > > a recent change in the dmarc.c makes your animals failing the DMARC > checks for tests using HEAD (default branch "master"). As for pony (FreeBSD): none of my animals have DMARC enabled, but both pony (FreeBSD) and mole (OpenBSD) are referencing *DANE* in errors. mole is being built with LibreSSL and this patch should help: https://github.com/openbsd/ports/blob/master/mail/exim/patches/patch-src_dane-openssl_c For pony I have no idea, I set it up initially as jgh wanted a FreeBSD animal... Maybe time to retire it, as there are other FreeBSD animals there. -- Kirill -- ## 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] Backup/Restore Messages in the Input Queue
Thank you both for the clarification. -Patrick On 10/16/2022 5:56 AM, Jeremy Harris via Exim-users wrote: On 16/10/2022 11:24, Patrick Porteous via Exim-users wrote: I am trying to troubleshoot a sending issue on my server. I have a few hundred messages that are stuck in the /var/spool/exim/input queue. Can I shutdown the exim server process and move those files to another location and then move them back if that doesn't resolve the issue? In short, yes. There are other ways too, but that one is fine. Take care about file ownerships & permissions, of course. -- ## 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] Hint for build farmers of "pony" (krot) and "boar" (univie)
On 16/10/2022 11:06, Heiko Schlittermann via Exim-users wrote: a recent change in the dmarc.c makes your animals failing the DMARC checks for tests using HEAD (default branch "master"). If you link against the 1.3.x libopendmarc, you need an additional Local/Makefile option "DMARC_API=100300" (see the "src/EDITME" file). Also animals marmot & goundhog - which I suspect means any Debian 9 platform. -- Cheers, Jeremy -- ## 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] Backup/Restore Messages in the Input Queue
On 16/10/2022 11:24, Patrick Porteous via Exim-users wrote: I am trying to troubleshoot a sending issue on my server. I have a few hundred messages that are stuck in the /var/spool/exim/input queue. Can I shutdown the exim server process and move those files to another location and then move them back if that doesn't resolve the issue? In short, yes. There are other ways too, but that one is fine. Take care about file ownerships & permissions, of course. -- Cheers, Jeremy -- ## 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] Backup/Restore Messages in the Input Queue
Patrick Porteous via Exim-users (So 16 Okt 2022 12:24:27
CEST):
> Hello,
>
> I am trying to troubleshoot a sending issue on my server. I have a few
> hundred messages that are stuck in the /var/spool/exim/input queue. Can I
> shutdown the exim server process and move those files to another location
> and then move them back if that doesn't resolve the issue? Here are the
> exact steps I plan to follow:
Once there is no Exim process running anymore, it is safe to remove/move
the queued files (there are two files per message, -H, and -D). In a
perfect world you'll move/remove the msglogs too.
> 1. Shutdown Exim
> 2. Move all messages in /var/spool/exim/input to a backup location
> 3. Start Exim server
> 4. Send a few test messages to see if my sending issue is corrected
> 5. Shutdown Exim
> 6. Move the messages back into the /var/spool/exim/input folder a few
>at a time
> 7. Start Exim server
> 8. Manually force a queue run
Without deeper insight into how Exim works, this approach is safe. There
are some shortcuts possible, but this requires knowledge about the
inner workings (locked files, …)
If you want to operatate on a more abstract level (as the spool
hierarchy should be considered as a kind of black box to the avarage
operator), you can use Exim's named queues feature and move the messages
into an alternative queue using the Exim command line:
exim -MG hold ID...
later you can inspect this queue:
exim -qGhold -bp
and move the messages back
exim -qGhold -MG '' ID…
> My goal is retain the queued messages and not force my users resend the
> messages that are hung in the queue presently. My suspicion is that I have
> a malformed message in the queue that is causing the other messages to hang
> up.
The queue runners that process your queued messages should not fail
totally if there is one "bad" messages, as they start at random messages
in your queue and should manage to empty the queue over the time, just
leaving the bad message there.
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] Backup/Restore Messages in the Input Queue
Hello, I am trying to troubleshoot a sending issue on my server. I have a few hundred messages that are stuck in the /var/spool/exim/input queue. Can I shutdown the exim server process and move those files to another location and then move them back if that doesn't resolve the issue? Here are the exact steps I plan to follow: 1. Shutdown Exim 2. Move all messages in /var/spool/exim/input to a backup location 3. Start Exim server 4. Send a few test messages to see if my sending issue is corrected 5. Shutdown Exim 6. Move the messages back into the /var/spool/exim/input folder a few at a time 7. Start Exim server 8. Manually force a queue run My goal is retain the queued messages and not force my users resend the messages that are hung in the queue presently. My suspicion is that I have a malformed message in the queue that is causing the other messages to hang up. Thanks for the help, -Patrick -- ## 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] Hint for build farmers of "pony" (krot) and "boar" (univie)
Hi,
a recent change in the dmarc.c makes your animals failing the DMARC
checks for tests using HEAD (default branch "master").
If you link against the 1.3.x libopendmarc, you need an additional
Local/Makefile option "DMARC_API=100300" (see the "src/EDITME" file).
This should enable the "legacy" function call. The default is now to use
the 1.4.x API. Unfortunately the OpenDMARC project doesn't provide a
suitable macro/definition for easy autodetection.
References:
- Exim Bug 2728: https://bugs.exim.org/show_bug.cgi?id=2728
- OpenDMARC Issue 167:
https://github.com/trusteddomainproject/OpenDMARC/issues/167
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/
