[exim] Configuration progress.

2023-04-13 Thread Peter via Exim-users
From: Peter via Exim-users Date: Thu, 13 Apr 2023 13:28:07 -0700 Better to test with a distinct domain. gmail.com for example. The result from exim -d+all+noutf8 -odf petereasth...@gmail.com &1 | tee ~/NY/ex1 | less is in http://easthope.ca/ex1 . 17:31:09 8486 easthope.ca in "imager.h

Re: [exim] From header with encoding not parsed?

2023-04-13 Thread Jeremy Harris via Exim-users
On 13/04/2023 23:24, Martin D Kealey via Exim-users wrote: On Thu, 13 Apr 2023 at 19:36, Slavko wrote in exim-users@exim.org: Dňa 12. apríla 2023 16:50:29 UTC používateľ MRob via Exim-users < exim-users@exim.org> napísal: Hi, I have a variable to extract the email address in from header set

Re: [exim] From header with encoding not parsed?

2023-04-13 Thread Martin D Kealey via Exim-users
On Thu, 13 Apr 2023 at 19:36, Slavko wrote in exim-users@exim.org: > Dňa 12. apríla 2023 16:50:29 UTC používateľ MRob via Exim-users < > exim-users@exim.org> napísal: > > Hi, I have a variable to extract the email address in from header set > like this: > > > > ${lc:${address:$h_From:}} > > Heade

[exim] Configuration progress; was Re (2): Configuring exim to use an non-TLS connection to port 587.

2023-04-13 Thread Peter via Exim-users
From: Andrew C Aitchison via Exim-users Date: Thu, 13 Apr 2023 11:06:24 +0100 (BST) Jeremy's last message mentioned that this failure was correct given the content of /etc/exim4/passwd.client I think that means you need a line for easthope.ca in /etc/exim4/passwd.client - a line for mail.

Re: [exim] Re (2): Configuring exim to use an non-TLS connection to port 587.

2023-04-13 Thread Andrew C Aitchison via Exim-users
On Wed, 12 Apr 2023, Peter via Exim-users wrote: From: Graeme Fowler via Exim-users Date: Tue, 11 Apr 2023 18:44:22 +0100 ... problem is on your filesystem rather than on-the-wire. Another helpful tip is in https://wiki.debian.org/Exim4Gmail. /etc/exim4/passwd.client had permissions 600.

Re: [exim] From header with encoding not parsed?

2023-04-13 Thread Jeremy Harris via Exim-users
On 13/04/2023 09:54, Victor Ustugov via Exim-users wrote: I'm not talking about what should be encoded, but about what can be received in a real email from a spammer, some kind of script or something like that. A mail sender could send you *anything*. -- Cheers, Jeremy -- ## List details at

Re: [exim] From header with encoding not parsed?

2023-04-13 Thread Victor Ustugov via Exim-users
Slavko via Exim-users wrote on 12.04.2023 22:38: Hi, I have a variable to extract the email address in from header set like this: ${lc:${address:$h_From:}} >>> >>> Header is valid, but after decoding it contains comma without >>> qoutes, the comma is address separator and thus

Re: [exim] From header with encoding not parsed?

2023-04-13 Thread Victor Ustugov via Exim-users
Jasen Betts via Exim-users wrote on 13.04.2023 10:07: > On 2023-04-12, Victor Ustugov via Exim-users wrote: >> Slavko via Exim-users wrote on 12.04.2023 20:42: >>> Dňa 12. apríla 2023 16:50:29 UTC používateľ MRob via Exim-users >>> napísal: Hi, I have a variable to extract the email address

Re: [exim] From header with encoding not parsed?

2023-04-13 Thread Jasen Betts via Exim-users
On 2023-04-12, Victor Ustugov via Exim-users wrote: > Slavko via Exim-users wrote on 12.04.2023 20:42: >> Dňa 12. apríla 2023 16:50:29 UTC používateľ MRob via Exim-users >> napísal: >>> Hi, I have a variable to extract the email address in from header set like >>> this: >>> >>> ${lc:${address:$

Re: [exim] OT: are BCC header lines legitimate ?

2023-04-13 Thread Jasen Betts via Exim-users
On 2023-04-12, Olaf Hopp (SCC) via Exim-users wrote: > Sorry for being a bit off topic: > recently we had incoming phishing mails which all had a BCC header line. > So I thought, that's easy to defend and I introduced a data ACL > > deny condition = ${if def:h_BCC: {yes}{no}} > > My logs