[exim] Re: failure to transfer data from subprocess
Which log files since I don’t see anything in mainlog for example. Looks like I find a backtrace from earlier 2023-04-24 09:24:14 1pqyz8-0006yH-1A SIGSEGV (fault address: 0x30) 2023-04-24 09:24:14 1pqyz8-0006yH-1A SIGSEGV (null pointer indirection) 2023-04-24 09:24:14 1pqyz8-0006yH-1A SIGSEGV (27310 proxying TLS connection for continued transport to complaints.maro post.com ) 2023-04-24 09:24:14 1pqyz8-0006yH-1A backtrace 2023-04-24 09:24:14 1pqyz8-0006yH-1A --- 2023-04-24 09:24:14 1pqyz8-0006yH-1A/usr/sbin/exim() [0x428e6e] 2023-04-24 09:24:14 1pqyz8-0006yH-1A/usr/sbin/exim() [0x428fd3] 2023-04-24 09:24:14 1pqyz8-0006yH-1A/lib64/libpthread.so.0(+0xf630) [0x7fb00f7c9630] 2023-04-24 09:24:14 1pqyz8-0006yH-1A/lib64/libssl.so.10(SSL_read+0) [0x7fb00f1bc680] 2023-04-24 09:24:14 1pqyz8-0006yH-1A/usr/sbin/exim() [0x489596] 2023-04-24 09:24:14 1pqyz8-0006yH-1A/usr/sbin/exim() [0x4b5fa9] 2023-04-24 09:24:14 1pqyz8-0006yH-1A/usr/sbin/exim() [0x425878] 2023-04-24 09:24:14 1pqyz8-0006yH-1A/usr/sbin/exim() [0x4164f8] 2023-04-24 09:24:14 1pqyz8-0006yH-1A/usr/sbin/exim() [0x42f610] 2023-04-24 09:24:14 1pqyz8-0006yH-1A /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fb00f40e555] 2023-04-24 09:24:14 1pqyz8-0006yH-1A/usr/sbin/exim() [0x40a119] 2023-04-24 09:24:14 1pqyz8-0006yH-1A --- Don’t seem to see an abundance of backtraces mainlog-20230430:2023-04-24 09:24:14 1pqyz8-0006yH-1A backtrace paniclog-20230430:2023-04-24 09:24:14 1pqyz8-0006yH-1A backtrace > On May 13, 2023, at 3:52 PM, Jeremy Harris via Exim-users > wrote: > > On 13/05/2023 21:42, Robert Nicholson via Exim-users wrote: >> Another thing I don’t quite understand with this is my .forward has >> something like this before the pipe >> save $home/Maildir/.INBOX.intray.backup/ >> this is catch all to save all mail. >> However when I see these errors with the SIGSEGV it’s as if the above step >> never completed either. > > The "save" command only sets up another delivery to be done for the message > (to file) - it's doesn't perform that delivery. The crash is before > we get to that delivery being actioned. > > > [ Exim version 4.96 will be doing it's best to give a stackdump > of itself, on a SIGSEGV, to the logfiles. I assume you're > running something a bit earlier. > ] > > -- > 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/ -- ## 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: failure to transfer data from subprocess
What would a basic .forward file look like if all I wanted to do is to have a .forward file in place but for everything to go it’s default places? > On May 13, 2023, at 3:52 PM, Jeremy Harris via Exim-users > wrote: > > On 13/05/2023 21:42, Robert Nicholson via Exim-users wrote: >> Another thing I don’t quite understand with this is my .forward has >> something like this before the pipe >> save $home/Maildir/.INBOX.intray.backup/ >> this is catch all to save all mail. >> However when I see these errors with the SIGSEGV it’s as if the above step >> never completed either. > > The "save" command only sets up another delivery to be done for the message > (to file) - it's doesn't perform that delivery. The crash is before > we get to that delivery being actioned. > > > [ Exim version 4.96 will be doing it's best to give a stackdump > of itself, on a SIGSEGV, to the logfiles. I assume you're > running something a bit earlier. > ] > > -- > 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/ -- ## 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: failure to transfer data from subprocess
On Sat, 13 May 2023, Robert Nicholson via Exim-users wrote: What would a basic .forward file look like if all I wanted to do is to have a .forward file in place but for everything to go it’s default places? The single line: # Exim filter <<== Do not edit or remove this line ! -- 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: How to test my userforward ie. forward?
On Sat, 13 May 2023 at 00:10, Ian Z via Exim-users < exim-users@lists.exim.org> wrote: > If exim.conf is not readable by normal users, I'd consider it a > serious misconfiguration. Talk to the admin about that. > The exim binary is usually setuid root, so there's no need for the config file to be readable by regular users. e.g. $ ls -al /usr/sbin/exim4 -rwsr-xr-x 1 root root 1512616 Jul 13 2021 /usr/sbin/exim4 -- ## 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] heads-up: some spam bots started RCPT flooding
Hi! Maybe you've already noticed some spam bots trying to deliver spam to exactly 100 recipients in one wash up. They take a list of common user names, add your domain name, and then loop through 100 RCPT TOs per mail. To slow them down you could use the settings smtp_ratelimit_hosts and smtp_ratelimit_rcpt. Be careful not to bother your customers/users with too large delays. Lowering recipients_max is not really feasible as RFC 5321 clearly states a minimum of 100. ciao Markus -- / Markus Reschke \ \ madi...@theca-tabellaria.de / -- ## 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: heads-up: some spam bots started RCPT flooding
On 14/05/2023 18:56, Markus Reschke via Exim-users wrote: They take a list of common user names, add your domain name, and then loop through 100 RCPT TOs per mail. An escalating delay per RCPT *reject* isn't hard. -- 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: How to test my userforward ie. forward?
On Sun, May 14, 2023 at 11:51:35AM +0100, Martin A. Brooks wrote: > > If exim.conf is not readable by normal users, I'd consider it a > > serious misconfiguration. Talk to the admin about that. > The exim binary is usually setuid root, so there's no need for the config > file to be readable by regular users. e.g. On my systems, it is usually setuid root but not world executable. Another program takes the role of a submission agent. But that's quite beside the point. exim.conf should be world readable for the sake of users reading it with cat, less or emacs, to figure out what the configuration is. Anything else amounts to security by obscurity. -- Ian -- ## 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] Will there be an exim 4.97?
Please do not interpret it as pressure or anything. I am just trying to decide if I should really start tracking the git master instead of waiting for a release announcement (or a CVE patch). -- Ian -- ## 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/
