https://bugs.exim.org/show_bug.cgi?id=2595
Bug ID: 2595
Summary: Allow custom socket path for SYSLOG
Product: Exim
Version: N/A
Hardware: x86
OS: All
Status: NEW
Severity: bug
Priority: medium
https://bugs.exim.org/show_bug.cgi?id=2595
--- Comment #2 from Mike Rochford ---
The environment is scaled globally where we have roughly 50+ Exim instances
accepting email to relay to the internet. All push the logs to a distributed
log collection service. The local log files are never used for
https://bugs.exim.org/show_bug.cgi?id=2595
--- Comment #3 from Jeremy Harris ---
That's not gong to work, though. "syslogd", the one true original one, reads
log items from the kernel. So if you're about to try and use some lash-up, you
need to specify it. Most people would be using the
On 08/06/2020 14:51, Viktor Dukhovni via Exim-dev wrote:
> On Mon, Jun 08, 2020 at 12:48:22PM +, admin--- via Exim-dev wrote:
>
>> https://bugs.exim.org/show_bug.cgi?id=2594
>>
>> --- Comment #1 from Jeremy Harris ---
>> Can you locate a standards document specifying the name that should be
https://bugs.exim.org/show_bug.cgi?id=2595
--- Comment #1 from Jeremy Harris ---
Justification needed: why the usual log files don't work for you.
Also, any work done on this would need a specification for the comms to this
"private syslog daemon".
--
You are receiving this mail because:
You
On 08/06/2020 14:51, Viktor Dukhovni via Exim-dev wrote:
> On Mon, Jun 08, 2020 at 12:48:22PM +, admin--- via Exim-dev wrote:
>
>> https://bugs.exim.org/show_bug.cgi?id=2594
>>
>> --- Comment #1 from Jeremy Harris ---
>> Can you locate a standards document specifying the name that should be
https://bugs.exim.org/show_bug.cgi?id=2596
Bug ID: 2596
Summary: Changing the default value for the hosts_noproxy_tls
option breaks the use of smtp authorization
Product: Exim
Version: 4.93
Hardware: All
On Tue, Jun 09, 2020 at 04:41:33PM +0100, Jeremy Harris via Exim-dev wrote:
> On 08/06/2020 14:51, Viktor Dukhovni via Exim-dev wrote:
> > Yes: https://tools.ietf.org/html/rfc6125#appendix-B.4
> >
> > The original reported is right.
>
> No, it's worse. If you take that RFC 3207 wording
https://bugs.exim.org/show_bug.cgi?id=2596
--- Comment #1 from Jeremy Harris ---
Could you clarify what you mean by "authorization", and show what is broken?
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at
On 09/06/2020 18:33, Viktor Dukhovni via Exim-dev wrote:
> Perhaps so, but in the context of everything else in RFC6125, and the
> specs for other protocols, ... it is fairly clear (to me anyway) that
> the intent is to match the SMTP server name prior to CNAME expansion,
> just like the
https://bugs.exim.org/show_bug.cgi?id=2594
--- Comment #6 from Chris Paulson-Ellis ---
(In reply to Phil Pennock from comment #5)
> In the original bug-report here:
>
> """
> Cert hostname to check: "mail.edesix.local"
> Setting TLS SNI "mail.dev.edesix.com"
> """
>
> That is clearly an
11 matches
Mail list logo
