https://bugs.exim.org/show_bug.cgi?id=2813
Jeremy Harris changed:
What|Removed |Added
Status|NEW |WAIT_FIX_CONFIRMATION
--- Comment #11 from Jerem
https://bugs.exim.org/show_bug.cgi?id=2672
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.exim.org/show_bug.cgi?id=2821
Jeremy Harris changed:
What|Removed |Added
Status|NEW |WAIT_FIX_CONFIRMATION
--
You are receiving this
https://bugs.exim.org/show_bug.cgi?id=2819
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |FIXED
Summary|/usr/sbin/sendmail
https://bugs.exim.org/show_bug.cgi?id=2265
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.exim.org/show_bug.cgi?id=2823
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|NEW
https://bugs.exim.org/show_bug.cgi?id=2145
Jeremy Harris changed:
What|Removed |Added
CC||fied...@schlittermann.de
--- Comment #5 from Jer
https://bugs.exim.org/show_bug.cgi?id=2816
Renaud Allard changed:
What|Removed |Added
CC||ren...@allard.it
--- Comment #13 from Renaud All
https://bugs.exim.org/show_bug.cgi?id=2822
--- Comment #6 from Ferry ---
Until they fix it, it might be wise to set the dhparams, load the referenced
ones from RFC7919 or not ignoring tls_dhparam.
Without it, it's broken.
--
You are receiving this mail because:
You are on the CC list for the b
https://bugs.exim.org/show_bug.cgi?id=2822
Jeremy Harris changed:
What|Removed |Added
See Also||http://bugs.debian.org/9681
|
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #10 from Git Commit ---
Git commit:
https://git.exim.org/exim.git/commitdiff/51be321b27825c01829dffd90f11bfff256f7e42
commit 51be321b27825c01829dffd90f11bfff256f7e42
Author: Adam Lackorzynski
AuthorDate: Sat Oct 16 16:30:07 2021 +0100
C
https://bugs.exim.org/show_bug.cgi?id=2813
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #9 from Git Commit ---
G
https://bugs.exim.org/show_bug.cgi?id=2815
--- Comment #6 from Git Commit ---
Git commit:
https://git.exim.org/exim.git/commitdiff/32b11385ddced7eafe68c60eebbb2c81979ce35f
commit 32b11385ddced7eafe68c60eebbb2c81979ce35f
Author: Jeremy Harris
AuthorDate: Sat Oct 16 00:24:07 2021 +0100
Commit
https://bugs.exim.org/show_bug.cgi?id=2821
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
Hardware|
https://bugs.exim.org/show_bug.cgi?id=2821
--- Comment #3 from Git Commit ---
Git commit:
https://git.exim.org/exim.git/commitdiff/df618101a5ea15dc90c4a2968798ef2be9dba16f
commit df618101a5ea15dc90c4a2968798ef2be9dba16f
Author: Jeremy Harris
AuthorDate: Mon Oct 18 11:01:47 2021 +0100
Commit
https://bugs.exim.org/show_bug.cgi?id=2815
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #5 from Git Commit ---
G
https://bugs.exim.org/show_bug.cgi?id=2822
--- Comment #4 from Ferry ---
Hi,
GnuTLS matrix channel referred to:
https://gitlab.com/gnutls/gnutls/-/issues/1077
According to the responses there either:
gnutls_certificate_set_dh_params or gnutls_certificate_set_known_dh_params
should be called.
I
https://bugs.exim.org/show_bug.cgi?id=2822
Jeremy Harris changed:
What|Removed |Added
Component|Exigrep |TLS
Summary|Issues with DHE ciphers -
https://bugs.exim.org/show_bug.cgi?id=2822
--- Comment #2 from Andreas Metzler ---
Hello,
I can reproduce this with exim 4.95, and gnutls 3.7.2. Minimal testcase is
running "sslscan --tls12" against
a) exim without custom gnutls priority string
and
b) ex-serv-x509.c from the gnutls distribution
https://bugs.exim.org/show_bug.cgi?id=2819
Sebastian Fiedler changed:
What|Removed |Added
URL||https://bugs.debian.org/996
https://bugs.exim.org/show_bug.cgi?id=2823
Bug ID: 2823
Summary: test2
Product: Exim
Version: 4.95
Hardware: x86-64
OS: Linux
Status: NEW
Severity: wishlist
Priority: medium
Component: T
https://bugs.exim.org/show_bug.cgi?id=2822
--- Comment #5 from Ferry ---
Hi,
I myself unfortunately don't have any other exim systems readily available. The
bug report I linked concerned debian, presume they know how to link.
Would it be possible for you to run sslscan against some running inst
https://bugs.exim.org/show_bug.cgi?id=2822
--- Comment #4 from Jeremy Harris ---
Exim feeds the string from the tls_require_ciphers option pretty much direct
into the library gnutls_priority_init() function. You might get a more
informed response from the gnutls mailinglist.
Is it possible that
https://bugs.exim.org/show_bug.cgi?id=2822
--- Comment #3 from Ferry ---
a) GnuTLS 3.6.16 & Exim 4.92.2 in our case - but the link to the bug filed at
sslscan by someone else indicates issues with exim in debian (he filed here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968145 - no respons
https://bugs.exim.org/show_bug.cgi?id=2822
--- Comment #2 from Jeremy Harris ---
a) you didn't say what version of GnuTLS, nor distribution of Exim
b) working out what you are trying to say in that wall of text is tiring
--
You are receiving this mail because:
You are on the CC list for the bug
https://bugs.exim.org/show_bug.cgi?id=2821
Jeremy Harris changed:
What|Removed |Added
Status|ASSIGNED|WAIT_FIX_CONFIRMATION
--- Comment #1 from Jeremy
https://bugs.exim.org/show_bug.cgi?id=2822
--- Comment #1 from Ferry ---
Guidelines here btw:
https://english.ncsc.nl/publications/publications/2021/january/19/it-security-guidelines-for-transport-layer-security-2.1
For just ciphersuites jumping to Appendix C is the quick win :).
--
You are re
https://bugs.exim.org/show_bug.cgi?id=2822
Bug ID: 2822
Summary: Issues with DHE ciphers - problems with GnuTLS
implementation?
Product: Exim
Version: 4.94
Hardware: x86
OS: Linux
Status: NEW
https://bugs.exim.org/show_bug.cgi?id=2820
Simon Arlott changed:
What|Removed |Added
Version|4.96|4.89
Status|NEW
https://bugs.exim.org/show_bug.cgi?id=2145
Simon Arlott changed:
What|Removed |Added
CC||z11p...@163.com
--- Comment #5 from Simon Arlott
https://bugs.exim.org/show_bug.cgi?id=2813
Jeremy Harris changed:
What|Removed |Added
Status|REOPENED|ASSIGNED
--
You are receiving this mail because
https://bugs.exim.org/show_bug.cgi?id=2813
Jeremy Harris changed:
What|Removed |Added
Status|ASSIGNED|WAIT_FIX_CONFIRMATION
--
You are receiving this
https://bugs.exim.org/show_bug.cgi?id=2821
Jeremy Harris changed:
What|Removed |Added
Assignee|unalloca...@exim.org|jgh146...@wizmail.org
Status|NEW
https://bugs.exim.org/show_bug.cgi?id=2820
--- Comment #1 from Jeremy Harris ---
Please confirm the release version; 4.96 is not out yet and log.c line 1006
in the current git HEAD is not a read.
--
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=2821
Bug ID: 2821
Summary: exiqgrep -r and -f options match all messages if no
regex defined
Product: Exim
Version: 4.94
Hardware: All
OS: FreeBSD
Status: NE
https://bugs.exim.org/show_bug.cgi?id=2820
Bug ID: 2820
Summary: out-of-bounds read
Product: Exim
Version: 4.96
Hardware: x86-64
OS: Linux
Status: NEW
Severity: bug
Priority: medium
Comp
https://bugs.exim.org/show_bug.cgi?id=2687
--- Comment #13 from Simon Arlott ---
I've just realised that there is a much simpler solution to this problem:
Exim supports multiple lines in strings/lists/expansions/etc.
RFC 2595 does not allow CR or LF in any of the response values, because they
h
https://bugs.exim.org/show_bug.cgi?id=2687
--- Comment #12 from Simon Arlott ---
(In reply to Jasen Betts from comment #10)
> wouldn't changing to a list just move the problem to quoting trailing and
> leading whitespace?
The existing "client_send" is already a list. You must quote whitespace an
https://bugs.exim.org/show_bug.cgi?id=2687
--- Comment #11 from Jeremy Harris ---
To be fair, you have to quote the current to handle a trailing space. At least
moving to a list per comment 9 makes such quoting needs the same as all lists.
I'm unclear where you're getting $item from in your lis
https://bugs.exim.org/show_bug.cgi?id=2687
Jasen Betts changed:
What|Removed |Added
CC||ja...@treshna.com
--- Comment #10 from Jasen Betts
https://bugs.exim.org/show_bug.cgi?id=2687
--- Comment #9 from Simon Arlott ---
(In reply to Jeremy Harris from comment #8)
> Perhaps we should add new options for the client side of the plaintext
> authenticator (say, "client_send_1", "client_send_2").
> Define them as just (expanded) string, wi
https://bugs.exim.org/show_bug.cgi?id=2615
Jeremy Harris changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.exim.org/show_bug.cgi?id=2687
--- Comment #8 from Jeremy Harris ---
Perhaps we should add new options for the client side of the plaintext
authenticator (say, "client_send_1", "client_send_2").
Define them as just (expanded) string, without any interpretation of ^,
and that they will
https://bugs.exim.org/show_bug.cgi?id=2691
Jeremy Harris changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.exim.org/show_bug.cgi?id=2265
Jeremy Harris changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #25 from Jeremy Harris ---
Commit 51be321b27
--
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
details at http://www.exim.org/ ##
https://bugs.exim.org/show_bug.cgi?id=2672
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.exim.org/show_bug.cgi?id=2819
Jeremy Harris changed:
What|Removed |Added
Status|WAIT_FIX_CONFIRMATION |RESOLVED
Resolution|---
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #23 from Jeremy Harris ---
Aha. We stash info in the head of the malloc'd block, so our free wrapper
would have to be used. So we have to lose the aforementioned accounting.
I'm *really* disliking PAM now.
--
You are receiving this mail b
https://bugs.exim.org/show_bug.cgi?id=2813
Adam Lackorzynski changed:
What|Removed |Added
Attachment #1402|0 |1
is obsolete|
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #22 from Jeremy Harris ---
(In reply to Adam Lackorzynski from comment #19)
> This change does change anything for me. Also, in libpam's test suite the
> pamc structure is placed in static memory, and thus allocating this
> dynamically does n
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #18 from Jeremy Harris ---
We prefer to use exim's internal interface, so that memory accounting for
debug purposes is consistent. Is anyone in a position to test
https://bugs.exim.org/attachment.cgi?id=1401&action=diff ?
--
You are recei
https://bugs.exim.org/show_bug.cgi?id=2819
--- Comment #4 from Andreas Metzler ---
(In reply to Jeremy Harris from comment #3)
> Commit 1843f70b73 should fix.
Samuel confirmed the issue to be fixed by this commit. - Thank you!
--
You are receiving this mail because:
You are on the CC list for
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #21 from Adam Lackorzynski ---
(In reply to Fabian Groffen from comment #17)
> (In reply to Adam Lackorzynski from comment #16)
> > Created attachment 1402 [details]
> > Possible fix for the described issue.
>
> Hey thanks, just as a suggest
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #24 from Adam Lackorzynski ---
(In reply to Jeremy Harris from comment #23)
> Aha. We stash info in the head of the malloc'd block, so our free wrapper
> would have to be used. So we have to lose the aforementioned accounting.
> I'm *really
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #19 from Adam Lackorzynski ---
(In reply to Jeremy Harris from comment #18)
> We prefer to use exim's internal interface, so that memory accounting for
> debug purposes is consistent. Is anyone in a position to test
> https://bugs.exim.org/a
https://bugs.exim.org/show_bug.cgi?id=2813
Adam Lackorzynski changed:
What|Removed |Added
CC||a...@l4re.org
--- Comment #15 from Adam Lack
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #17 from Fabian Groffen ---
(In reply to Adam Lackorzynski from comment #16)
> Created attachment 1402 [details]
> Possible fix for the described issue.
Hey thanks, just as a suggestion, the following might just work as well:
- reply[i
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #16 from Adam Lackorzynski ---
Created attachment 1402
--> https://bugs.exim.org/attachment.cgi?id=1402&action=edit
Possible fix for the described issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## L
https://bugs.exim.org/show_bug.cgi?id=2816
Jeremy Harris changed:
What|Removed |Added
Status|NEW |WAIT_FIX_CONFIRMATION
--
You are receiving this
https://bugs.exim.org/show_bug.cgi?id=2819
Jeremy Harris changed:
What|Removed |Added
Status|ASSIGNED|WAIT_FIX_CONFIRMATION
--- Comment #3 from Jeremy
https://bugs.exim.org/show_bug.cgi?id=2816
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|WAIT_FIX_CONFIRMATION
https://bugs.exim.org/show_bug.cgi?id=2815
Jeremy Harris changed:
What|Removed |Added
Status|NEW |WAIT_FIX_CONFIRMATION
--- Comment #5 from Jeremy
https://bugs.exim.org/show_bug.cgi?id=2819
--- Comment #2 from Andreas Metzler ---
(In reply to Jeremy Harris from comment #1)
> Thanks for the excellent diagnosis.
All Samuel's work.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lis
https://bugs.exim.org/show_bug.cgi?id=2819
--- Comment #1 from Jeremy Harris ---
Thanks for the excellent diagnosis.
--
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
details at http://www.ex
https://bugs.exim.org/show_bug.cgi?id=2819
Jeremy Harris changed:
What|Removed |Added
Summary|/usr/sbin/sendmail |command line inefficient at
|i
https://bugs.exim.org/show_bug.cgi?id=2819
Bug ID: 2819
Summary: /usr/sbin/sendmail interface inefficient at reading
mail
Product: Exim
Version: 4.95
Hardware: x86
URL: https://bugs.debian.org/996282
https://bugs.exim.org/show_bug.cgi?id=2815
Heiko Schlittermann changed:
What|Removed |Added
Group|exim-security |
CC|
https://bugs.exim.org/show_bug.cgi?id=2816
Heiko Schlittermann changed:
What|Removed |Added
Group|exim-security |
CC|
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #14 from Jeremy Harris ---
Created attachment 1401
--> https://bugs.exim.org/attachment.cgi?id=1401&action=edit
proposed patch
Compiles, untested
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List det
https://bugs.exim.org/show_bug.cgi?id=2813
Jeremy Harris changed:
What|Removed |Added
Assignee|unalloca...@exim.org|jgh146...@wizmail.org
Status|RESOLVE
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #12 from Arkadiusz Miskiewicz ---
Also pam(3):
The pam_start(3) function creates the PAM context and initiates the PAM
transaction.
[...]
The pam_end(3) function terminates the PAM transaction and is the last function
an application should
https://bugs.exim.org/show_bug.cgi?id=2813
Arkadiusz Miskiewicz changed:
What|Removed |Added
CC||ar...@maven.pl
--- Comment #11 from Arkad
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #10 from Fabian Groffen ---
I'll shut down papua, it clearly doesn't have any purpose. Thanks.
--
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-
https://bugs.exim.org/show_bug.cgi?id=2814
Kai Risku changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.exim.org/show_bug.cgi?id=2813
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://bugs.exim.org/show_bug.cgi?id=2813
Jeremy Harris changed:
What|Removed |Added
See Also||https://bugs.exim.org/show_
|
https://bugs.exim.org/show_bug.cgi?id=2489
Jeremy Harris changed:
What|Removed |Added
See Also||https://bugs.exim.org/show_
|
https://bugs.exim.org/show_bug.cgi?id=2814
--- Comment #1 from Jeremy Harris ---
I set up a testcase for this in the testsuite (0610, committed as 7dd249088b),
and it seems to properly remove records.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List detail
https://bugs.exim.org/show_bug.cgi?id=2818
Bug ID: 2818
Summary: gsasl always defines server side
Product: Exim
Version: 4.95
Hardware: x86
OS: Linux
Status: NEW
Severity: bug
Priority: medium
https://bugs.exim.org/show_bug.cgi?id=2817
Bug ID: 2817
Summary: readconf authenticator confusion
Product: Exim
Version: 4.95
Hardware: x86
OS: Linux
Status: NEW
Severity: bug
Priority: medium
https://bugs.exim.org/show_bug.cgi?id=2806
--- Comment #11 from Jeremy Harris ---
I can't tell in general. I've not had any reports of similar from users on
my own servers, but you'll be handling more traffic than me. Probably worth
your while scanning logs for other yahoo destinations, in case
https://bugs.exim.org/show_bug.cgi?id=2806
--- Comment #10 from David Carter ---
Yes, hosts_avoid_pipelining has fixed the dropped connections, and email is now
delivered immediately:
2021-10-10 10:03:54 +0100 1mZUkM-00037M-se <= dp...@ppsw.cam.ac.uk U=dpc22
P=local S=562 for kohe...@yahoo.co.jp
https://bugs.exim.org/show_bug.cgi?id=2806
--- Comment #9 from Jeremy Harris ---
Yup, that's a useful debuglog. They're screwing up pipelining. Let's disable
it for these hosts and run another test:
hosts_avoid_pipelining = *.yahoo.co.jp
set on the transport.
--
You are receiving this mai
https://bugs.exim.org/show_bug.cgi?id=2806
--- Comment #8 from David Carter ---
Created attachment 1397
--> https://bugs.exim.org/attachment.cgi?id=1397&action=edit
debuglog for 1mZF9E-000LUC-rJ
Hopefully the correct ticket this time around.
--
You are receiving this mail because:
You are on
https://bugs.exim.org/show_bug.cgi?id=2622
David Carter changed:
What|Removed |Added
Attachment #1396|0 |1
is obsolete|
https://bugs.exim.org/show_bug.cgi?id=2622
David Carter changed:
What|Removed |Added
CC||dp...@cam.ac.uk
--- Comment #2 from David Carter
https://bugs.exim.org/show_bug.cgi?id=2806
--- Comment #7 from David Carter ---
My user states:
"Yes, I have received 6 copies each of your first and second mail test mails."
(sent using Exim 4.95)
Yes indeed, I received only one copy of your "third test" mail.
(send using Exi 4.94.2 from th
https://bugs.exim.org/show_bug.cgi?id=2806
--- Comment #6 from David Carter ---
I have a debuglog, but "control = debug" in the ACL only captured the initial
delivery attempt (which failed),
2021-10-09 17:25:08 +0100 1mZF9E-000LUC-rJ <= dp...@cam.ac.uk
H=ppsw-50.csi.cam.ac.uk (me) [131.111.8.15
https://bugs.exim.org/show_bug.cgi?id=2806
--- Comment #5 from Jeremy Harris ---
There might be something different about the .123 host which allowed it
to give a definitive response. It's only seen in that one case, above.
But that doesn't tell us why the others fail.
The delivery line for 1m
https://bugs.exim.org/show_bug.cgi?id=2806
--- Comment #4 from David Carter ---
Just to add:
This isn't a transcient problem at the yahoo.co.jp end.
That was my immediate assumption based on a collection of dropped connections
following by a single successful delivery in my logs (see below).
H
https://bugs.exim.org/show_bug.cgi?id=2806
--- Comment #3 from David Carter ---
I was using "invalid_t...@yahoo.co.jp" as a test address, as I do't have an
account on that system. Presumably we could create one if we find someone who
speaks Japanese, or we could ask my user to translate for the p
https://bugs.exim.org/show_bug.cgi?id=2806
--- Comment #2 from Jeremy Harris ---
The test using "invalid_t...@yahoo.co.jp" doesn't appear to have delivered
at all, according to our end's visibility. I'm unclear how this ties up to
the complaint about a legitimate account there getting multiple c
https://bugs.exim.org/show_bug.cgi?id=2806
--- Comment #1 from David Carter ---
For what it is worth, I see exactly the same behaviour with 4.95 if I
disable:
DKIM signing
tls_require_ciphers.
hosts_randomize
Also: "message_linelength_limit = 100" which was a configuration change
from 4
https://bugs.exim.org/show_bug.cgi?id=2805
--- Comment #3 from Jeremy Harris ---
Yes, so one element of the list - and each element includes a length prefix.
Perhaps you are right - but the manpage is
capable of interpretation the way I did.
--
You are receiving this mail because:
You are on th
https://bugs.exim.org/show_bug.cgi?id=2805
--- Comment #2 from jannik.hoell...@gmail.com ---
The example on the manpage includes the length since it's an example for the
protocol/wire format.
The 'out' variable itself is not in that format since it's only a single
protocol, it can point to a part
https://bugs.exim.org/show_bug.cgi?id=2805
--- Comment #1 from Jeremy Harris ---
We don't generally do "pull request" handling.
Also, the manpage you referenced says to include the length; see the example.
We could do with clarification from the OpenSSL project on that, if you are
seeing the leng
https://bugs.exim.org/show_bug.cgi?id=2805
Jeremy Harris changed:
What|Removed |Added
Version|N/A |4.85
Target Milestone|Exim 4.95
https://bugs.exim.org/show_bug.cgi?id=2813
--- Comment #8 from Jeremy Harris ---
I agree it's a regression, but I don't think it's Exim's fault.
I think you should open a bug against the library; if there are restrictions
on the memory that can be indicated to the library then the users of the
l
https://bugs.exim.org/show_bug.cgi?id=2814
Bug ID: 2814
Summary: Retry hints not correctly expunged on successful
delivery if interface value set in transport
Product: Exim
Version: 4.95
Hardware: x86
OS: Li
701 - 800 of 3063 matches
Mail list logo