https://bugs.exim.org/show_bug.cgi?id=2273
Bug ID: 2273
Summary: Queue runners race with cutthrough delivery
Product: Exim
Version: 4.91
Hardware: x86
OS: Linux
Status: NEW
Severity: bug
https://bugs.exim.org/show_bug.cgi?id=2273
--- Comment #1 from Tim Stewart ---
Maybe this bug is related to bug 1322?
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev
https://bugs.exim.org/show_bug.cgi?id=2269
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.exim.org/show_bug.cgi?id=2272
Jeremy Harris changed:
What|Removed |Added
Status|NEW |WAIT_FIX_CONFIRMATION
https://bugs.exim.org/show_bug.cgi?id=2266
--- Comment #4 from Jeremy Harris ---
We used to do a new TLS conn for every message, within a continued SMTP conn.
To the extent that still holds, the multi-domain changes in the proposed coding
might not be needed. On the other
https://bugs.exim.org/show_bug.cgi?id=2265
Jeremy Harris changed:
What|Removed |Added
CC||jgh146...@wizmail.org
https://bugs.exim.org/show_bug.cgi?id=2276
--- Comment #1 from Nigel Metheringham ---
This sounds like it is an selinux policy issue. The selinux policy for Fedora
is written by the Fedora folks, and fixing it is outside our skillset.
Exim is a setuid program for good reason,
https://bugs.exim.org/show_bug.cgi?id=2276
Bug ID: 2276
Summary: Exim triggers DAC_OVERRIDE when running on SELinux
enabled system
Product: Exim
Version: 4.91
Hardware: x86
OS: Linux
Status: NEW
https://bugs.exim.org/show_bug.cgi?id=2275
--- Comment #4 from Tim Stewart ---
I will test this and reply soon, likely tomorrow. Thanks for the patch!
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at
https://bugs.exim.org/show_bug.cgi?id=2276
Phil Pennock changed:
What|Removed |Added
CC||p...@exim.org
--- Comment #2 from
https://bugs.exim.org/show_bug.cgi?id=2264
--- Comment #1 from Jeremy Harris ---
Created attachment 1084
--> https://bugs.exim.org/attachment.cgi?id=1084=edit
proposed patch
This needs testing against a real resolver, unlike the facilities of the
Exim test-harness.
https://bugs.exim.org/show_bug.cgi?id=2264
Jeremy Harris changed:
What|Removed |Added
Assignee|ni...@exim.org |jgh146...@wizmail.org
https://bugs.exim.org/show_bug.cgi?id=2273
--- Comment #5 from Tim Stewart ---
I did the sleep() test after getting your patch and all looks well.
I also appreciate the extra return value checks.
I will deploy this to a few of our servers and do some heavier testing.
https://bugs.exim.org/show_bug.cgi?id=2274
Bug ID: 2274
Summary: exim 4.91: segfault ... error 4 in libc-2.17.so
Product: Exim
Version: 4.91
Hardware: x86-64
OS: Linux
Status: NEW
Severity: bug
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #4 from Jeremy Harris ---
To get more info, configure your system to take corefiles (see "man core",
including the setuid specifics), and install the debuginfo package for glibc.
Once you have a coredump, run (as root)
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #5 from Alex ---
Hello Heiko,
Thanks for your reply.
(In reply to Heiko Schlittermann from comment #1)
> So, the next time the same message is delivered via the same transport, it
> does not segfault?
Yes, as soon as we
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #2 from Heiko Schlittermann ---
Do you know how to enable core dumps on set-uid binaries? This could help for
further tracing.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List
https://bugs.exim.org/show_bug.cgi?id=2274
Heiko Schlittermann changed:
What|Removed |Added
CC|
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #6 from Alex ---
Hello Jeremy,
Thanks for your reply.
(In reply to Jeremy Harris from comment #4)
> To get more info, configure your system to take corefiles (see "man core",
> including the setuid specifics), and install
https://bugs.exim.org/show_bug.cgi?id=2272
Bug ID: 2272
Summary: better handling for multiple, multiline headers
Product: Exim
Version: 4.91
Hardware: All
OS: All
Status: NEW
Severity: wishlist
https://bugs.exim.org/show_bug.cgi?id=2273
--- Comment #6 from Tim Stewart ---
While testing this fix, I also found bug 2275.
I still believe this bug is legitimate and the fix is correct.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
https://bugs.exim.org/show_bug.cgi?id=2275
Bug ID: 2275
Summary: MIME ACL prematurely releases spool data file lock
Product: Exim
Version: 4.91
Hardware: x86
OS: Linux
Status: NEW
Severity: bug
https://bugs.exim.org/show_bug.cgi?id=423
--- Comment #10 from Simon Arlott ---
I want to be able to do verify checks in the DATA ACL and then log additional
information about the message if the outcome is defer/fail before
deferring/rejecting the message.
I
https://bugs.exim.org/show_bug.cgi?id=423
--- Comment #12 from Simon Arlott ---
(In reply to Jeremy Harris from comment #11)
> Using a warn verb will only log an additional warning if you put a logging
> modifier on it, so I don't understand your "not only" point.
https://bugs.exim.org/show_bug.cgi?id=423
--- Comment #15 from Simon Arlott ---
(In reply to Simon Arlott from comment #14)
> (In reply to Jeremy Harris from comment #13)
> > > Yes, the user message is impossible to reconstruct.
> >
> > What did it say, and why
https://bugs.exim.org/show_bug.cgi?id=423
--- Comment #13 from Jeremy Harris ---
> it logs on any warn verb that defers. There is no message or log_message on
> it.
So I'm confused. I had the impression that you had a warn verb, which would
not result in a defer, and
https://bugs.exim.org/show_bug.cgi?id=423
--- Comment #14 from Simon Arlott ---
(In reply to Jeremy Harris from comment #13)
> > it logs on any warn verb that defers. There is no message or log_message on
> > it.
>
> So I'm confused. I had the impression that
https://bugs.exim.org/show_bug.cgi?id=177
Jeremy Harris changed:
What|Removed |Added
See Also|
https://bugs.exim.org/show_bug.cgi?id=423
--- Comment #11 from Jeremy Harris ---
Using a warn verb will only log an additional warning if you put a logging
modifier on it, so I don't understand your "not only" point.
With your final, eventual, defer verb you get the
https://bugs.exim.org/show_bug.cgi?id=2137
Jeremy Harris changed:
What|Removed |Added
See Also|
https://bugs.exim.org/show_bug.cgi?id=423
--- Comment #16 from Jeremy Harris ---
What I meant by reconstruct was something along these lines:
${if eq {$sender_verify_failure}{postmaster} \
{Postmaster verification failed while checking <$sender_address>} \
https://bugs.exim.org/show_bug.cgi?id=423
--- Comment #17 from Jeremy Harris ---
For interest, what do you find in $acl_verify_message ?
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
## List details at
https://bugs.exim.org/show_bug.cgi?id=423
--- Comment #18 from Simon Arlott ---
(In reply to Jeremy Harris from comment #16)
> What I meant by reconstruct was something along these lines:
>
> ${if eq {$sender_verify_failure}{postmaster} \
>
https://bugs.exim.org/show_bug.cgi?id=2275
Jeremy Harris changed:
What|Removed |Added
Assignee|t...@duncanthrax.net |jgh146...@wizmail.org
https://bugs.exim.org/show_bug.cgi?id=2275
--- Comment #2 from Tim Stewart ---
Ah, I see, so MIME ACLs can still be useful. Thanks for the examples. I admit
I didn't think too hard about it :)
I'm happy to help test any fixes. I found the issue rather easy to
https://bugs.exim.org/show_bug.cgi?id=2275
--- Comment #3 from Jeremy Harris ---
Created attachment 1085
--> https://bugs.exim.org/attachment.cgi?id=1085=edit
Possible fix, for testing
--
You are receiving this mail because:
You are on the CC list for the bug.
--
##
https://bugs.exim.org/show_bug.cgi?id=2265
--- Comment #5 from Jeremy Harris ---
You're right about $tls_out_dane not being set early enough, and I do see the
simplicity point. It does see a shame to lose the flexibility of being able to
set an SNI to something
https://bugs.exim.org/show_bug.cgi?id=2273
Jeremy Harris changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://bugs.exim.org/show_bug.cgi?id=2265
--- Comment #4 from Phil Pennock ---
(Patch is reversed.)
The issue I see is that we don't switch transports based upon DANE or not, or
have a way to skip a router if DANE fails (since that's something for later, at
SMTP time, when
https://bugs.exim.org/show_bug.cgi?id=2273
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #3 from
https://bugs.exim.org/show_bug.cgi?id=2273
--- Comment #4 from Jeremy Harris ---
I don't think the solution was wrong, but I wanted to keep open the possibility
of dealing more fully with an error from the fclose(), so I complexified it
somewhat.
If it's possible to do
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #14 from Alex ---
Will the following help?
[root@server ccpp-2018-05-15-15:38:54-18615]# gdb /usr/sbin/exim coredump
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-110.el7
Copyright (C) 2013 Free Software Foundation, Inc.
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #15 from Alex ---
> Perhaps if os_getcwd() fails? Could it be that the spam-checker has
> chdir()'d to a directory which it unlinks, but calls Exim from inside,
> so that Exim's os_getcwd() fails?
It seems:
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #17 from Phil Pennock ---
https://git.exim.org/exim.git/commitdiff/805fd869d551c36d1d77ab2b292a7008d643ca79
Alex, does applying this as a patch solve your problem?
--
You are receiving this mail because:
You are on the CC
https://bugs.exim.org/show_bug.cgi?id=2274
Phil Pennock changed:
What|Removed |Added
Assignee|t...@duncanthrax.net |p...@exim.org
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #13 from Alex ---
Hello Phil,
Directadmin manages Exim the following way:
1. at a moment of installation of a new server a pre-compiled package is
installed from DA's repository, it's called da_exim for CentOS.
2. then
https://bugs.exim.org/show_bug.cgi?id=2275
--- Comment #5 from Tim Stewart ---
This patch looks good so far after testing for ~3 hours on a relatively busy
system. I left our MIME ACL in place and verified that rejects the message
back to the sender and cancels the
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #18 from Alex ---
Hello Phil,
Thanks for the patch, it's applied now. I will let you know results. It might
take a while.
Regards,
Alex.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
##
https://bugs.exim.org/show_bug.cgi?id=2278
Jeremy Harris changed:
What|Removed |Added
Status|NEW |WAIT_FIX_CONFIRMATION
https://bugs.exim.org/show_bug.cgi?id=2278
--- Comment #4 from Simon Arlott ---
This can be fixed for 4.86 using ea18931d9b1e9b73b699a2f3eb661d70b7f52fab:
Index: exim4-4.86.2/src/pdkim/pdkim.c
===
https://bugs.exim.org/show_bug.cgi?id=2278
Bug ID: 2278
Summary: Invalid outgoing DKIM header signature
Product: Exim
Version: 4.86
Hardware: x86-64
OS: Linux
Status: NEW
Severity: bug
Priority:
https://bugs.exim.org/show_bug.cgi?id=2278
Phil Pennock changed:
What|Removed |Added
CC||p...@exim.org
--- Comment #2 from
https://bugs.exim.org/show_bug.cgi?id=2278
Simon Arlott changed:
What|Removed |Added
Priority|medium |high
--- Comment
https://bugs.exim.org/show_bug.cgi?id=2278
--- Comment #5 from Simon Arlott ---
(In reply to Phil Pennock from comment #2)
> Per the RFC, `b=;` and `b= ;` at the end are equivalent and anything
> assigning semantic value to the whitespace there, and failing
https://bugs.exim.org/show_bug.cgi?id=2278
Jeremy Harris changed:
What|Removed |Added
Resolution|FIXED |INVALID
--
You are
https://bugs.exim.org/show_bug.cgi?id=2278
Simon Arlott changed:
What|Removed |Added
Resolution|INVALID |FIXED
Target
https://bugs.exim.org/show_bug.cgi?id=2278
Jeremy Harris changed:
What|Removed |Added
Status|WAIT_FIX_CONFIRMATION |RESOLVED
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #8 from Jeremy Harris ---
Unhelpful. We need the stack trace.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #9 from Alex ---
Do you mean the one that attached as an attachment 1086? Or something else
different?
Regards,
Alex.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #10 from Jeremy Harris ---
Something else; that doesn't include a stack trace
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #11 from Alex ---
So in this case I need to start a gdb session and feed the process of
`/usr/sbin/exim -oMr spam-scanned -bS` with an email which caused the crash. If
this is the case... we don't have the email
https://bugs.exim.org/show_bug.cgi?id=2275
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #6 from
https://bugs.exim.org/show_bug.cgi?id=2273
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.exim.org/show_bug.cgi?id=177
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #3 from
https://bugs.exim.org/show_bug.cgi?id=2275
Jeremy Harris changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://bugs.exim.org/show_bug.cgi?id=2276
--- Comment #3 from Jaroslav Å karvada ---
(In reply to Phil Pennock from comment #2)
Thanks for response.
> There are two distinct areas here: logs and spool.
>
> Logs: wontfix, we write as root, if there's any kind of
https://bugs.exim.org/show_bug.cgi?id=2276
--- Comment #6 from Phil Pennock ---
Er, in the second paragraph I meant *readable* as group Exim, which is all
that's required here. Sorry, mis-wrote. The points stand.
--
You are receiving this mail because:
You are on the CC list
https://bugs.exim.org/show_bug.cgi?id=2276
--- Comment #7 from Phil Pennock ---
Hrm, we _always_ open the spool data file O_RDWR. That's slightly
disconcerting.
I've just pushed an untested "this couldn't possibly go wrong, could it?"
code-change, specifying O_NOFOLLOW if that
https://bugs.exim.org/show_bug.cgi?id=2276
--- Comment #4 from Jeremy Harris ---
The spool error is for opening the -D file, but we also open the -H right after
that. We need to be root at some point after reading the -H file, from which
we
get the recipients, in case we
https://bugs.exim.org/show_bug.cgi?id=2276
Phil Pennock changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.exim.org/show_bug.cgi?id=2277
Marc Perkel changed:
What|Removed |Added
Priority|medium |low
--- Comment #2 from Marc
https://bugs.exim.org/show_bug.cgi?id=2277
Bug ID: 2277
Summary: DNS error causes router to fail
Product: Exim
Version: N/A
Hardware: x86
OS: Linux
Status: NEW
Severity: bug
Priority: medium
https://bugs.exim.org/show_bug.cgi?id=2277
--- Comment #1 from Jeremy Harris ---
The manualroute router has an option "host_find_failed"; does this control
what you need?
http://exim.org/exim-html-current/doc/html/spec_html/ch-the_manualroute_router.html#SECTprioptman
--
https://bugs.exim.org/show_bug.cgi?id=2274
Phil Pennock changed:
What|Removed |Added
CC||p...@exim.org
--- Comment #12
https://bugs.exim.org/show_bug.cgi?id=2274
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #21 from Git Commit ---
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #20 from Jeremy Harris ---
(In reply to Alex from comment #15)
> > Perhaps if os_getcwd() fails? Could it be that the spam-checker has
> > chdir()'d to a directory which it unlinks, but calls Exim from inside,
> > so that Exim's
https://bugs.exim.org/show_bug.cgi?id=2264
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #2 from Git Commit ---
https://bugs.exim.org/show_bug.cgi?id=2260
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #4 from Git Commit ---
https://bugs.exim.org/show_bug.cgi?id=2282
vsevo...@highsecure.ru changed:
What|Removed |Added
CC||vsevo...@highsecure.ru
--- Comment #1
https://bugs.exim.org/show_bug.cgi?id=2280
Bug ID: 2280
Summary: Allow INET socket for dovecot auth server_socket
Product: Exim
Version: N/A
Hardware: All
OS: All
Status: NEW
Severity: wishlist
https://bugs.exim.org/show_bug.cgi?id=2280
Heiko Schlittermann changed:
What|Removed |Added
Assignee|jgh146...@wizmail.org |h...@schlittermann.de
--
You are
https://bugs.exim.org/show_bug.cgi?id=2281
Bug ID: 2281
Summary: DSN charset should allow non-ASCII
Product: Exim
Version: N/A
Hardware: All
OS: All
Status: NEW
Severity: wishlist
Priority:
https://bugs.exim.org/show_bug.cgi?id=2282
Bug ID: 2282
Summary: Support HTTP-based & JSON-parsing content scanning
(rspamd)
Product: Exim
Version: N/A
Hardware: All
OS: All
Status: NEW
https://bugs.exim.org/show_bug.cgi?id=2272
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |FIXED
Status|WAIT_FIX_CONFIRMATION
https://bugs.exim.org/show_bug.cgi?id=2246
Jeremy Harris changed:
What|Removed |Added
Assignee|ni...@exim.org |jgh146...@wizmail.org
Status|NEW
https://bugs.exim.org/show_bug.cgi?id=2277
--- Comment #3 from Jeremy Harris ---
You say "route_list" but that is not documented as being
expanded. So I assume you mean "route_data".
Is "hosts_randomize" set?
--
You are receiving this mail because:
You are on the CC list for the bug.
--
##
https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #19 from Alex ---
Sorry to say that, the patch did not help. Another crash happened recently on
- 2018-06-04 12:00:10 at 14:27
Seems to be all the same:
[root@server ccpp-2018-06-04-12:00:10-14027]# gdb /usr/sbin/exim coredump
GNU gdb
https://bugs.exim.org/show_bug.cgi?id=2282
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #4 from Git Commit ---
https://bugs.exim.org/show_bug.cgi?id=1802
--- Comment #16 from Git Commit ---
Git commit:
https://git.exim.org/exim.git/commitdiff/dd0b893238d03a9bb38e793f3d935272ed73da6d
commit dd0b893238d03a9bb38e793f3d935272ed73da6d
Author: Jeremy Harris
AuthorDate: Sat Jun 16 14:45:40 2018 +0100
https://bugs.exim.org/show_bug.cgi?id=1802
--- Comment #17 from Jeremy Harris ---
The above was part of a general removal of rspamd support, it apparently being
nonfunctional against current rspamd.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details
https://bugs.exim.org/show_bug.cgi?id=1802
--- Comment #18 from vsevo...@highsecure.ru ---
This commit likely changes nothing but a whitespace after comma.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at
https://bugs.exim.org/show_bug.cgi?id=2260
Jeremy Harris changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.exim.org/show_bug.cgi?id=2272
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #1 from
https://bugs.exim.org/show_bug.cgi?id=2272
Lena changed:
What|Removed |Added
CC||l...@lena.kiev.ua
--- Comment #2 from
https://bugs.exim.org/show_bug.cgi?id=2272
--- Comment #3 from Jeremy Harris ---
Yes, they're actually expansion items, though there isn't much difference.
I'll change the one comment I found; thanks for spotting this.
--
You are receiving this mail because:
You are on
https://bugs.exim.org/show_bug.cgi?id=2271
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://bugs.exim.org/show_bug.cgi?id=2267
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.exim.org/show_bug.cgi?id=2235
Heiko Schlittermann changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.exim.org/show_bug.cgi?id=2239
Jeremy Harris changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2
https://bugs.exim.org/show_bug.cgi?id=2239
--- Comment #3 from Gedalya ---
Yes. The documentation could be read as suggesting the flag is stored with the
message, not with a recipient address item.
Coming to think of it, it would fit better in many configurations if this
1 - 100 of 2998 matches
Mail list logo