On 2023-03-14, Yves Goergen via Exim-users wrote:
> Hello,
>
> I'd like to hide the IP address of authenticated users sending their
> messages over my SMTP server. The address always appears in the
> "Received" header and remains there for the final recipient.
>
> A web search has only led to
On 14/03/2023 13:17, Victor Ustugov via Exim-users wrote:
Office365 OAutn2 access token response size is over 4K)
You are seriously stretching the original intent of Exim's
string-handling with this.
[ Have you considered writing an Exim authenticator module? ]
Entering this expression
Dňa 14. marca 2023 22:02:24 UTC používateľ Yves Goergen via Exim-users
napísal:
>I couldn't find any information about the suggested solution. That all-caps
>name is mentioned in very long Debian package listings, but I couldn't find
>any documentation. The name also doesn't appear in Exim's
Hi Yves,
On 14.03.23 23:02, Yves Goergen via Exim-users wrote:
I'd like to hide the IP address of authenticated users sending their messages over my
SMTP server. The address always appears in the "Received" header and remains
there for the final recipient.
You can remove headers in router
Yves Goergen via Exim-users wrote on 15.03.2023 00:02:
> Hello,
Hello
> I'd like to hide the IP address of authenticated users sending their
> messages over my SMTP server. The address always appears in the
> "Received" header and remains there for the final recipient.
You may set the value of
On 14/03/2023 22:02, Yves Goergen via Exim-users wrote:
Is there some explanation about this? Does it work? What does it do? Should I
create the mentioned file if I don't have it yet?
It's a macro definition, in Exim terms. What having it defined means
depends on the rest of the
Hello,
I'd like to hide the IP address of authenticated users sending their
messages over my SMTP server. The address always appears in the
"Received" header and remains there for the final recipient.
A web search has only led to this information:
Le 13/03/2023 à 22:28, Slavko via Exim-users a écrit :
All 3 lines seem to me to relate to receiving the message. I don’t see a line
that is about sending the message, or signing it.
Yes, received. The line has no DKIM= field, which is logged by default,
thus seems that message had not valid
Jeremy Harris via Exim-users wrote on 14.03.2023 14:18:
>> exim: length limit exceeded (386 > 256) for: recipient
>
> Yes, I've run into that (just this week!)
>
> I assume the "-be " was a retrofit after the use
> of a trailing arg for a mail recipient, and just uses the same
> machinery.
>
>
On 13/03/2023 15:59, Jim Lamers via Exim-users wrote:
This solution does not seem to work in all situations,
Can you characterize the nonworking ones?
headers_add Authentication-Results TEST
Did you miss a colon there?
--
Cheers,
Jeremy
--
## List details at
On 14/03/2023 11:46, Victor Ustugov via Exim-users wrote:
When I tried to run exim with a long value of -be option, I got an error:
exim: length limit exceeded (386 > 256) for: recipient
Yes, I've run into that (just this week!)
I assume the "-be " was a retrofit after the use
of a trailing
Hello.
I need to check if the HTTP response is a JSON.
I did not find a function like isjson, so I decided to check HTTP
response with a regular expression.
When I tried to run exim with a long value of -be option, I got an error:
exim: length limit exceeded (386 > 256) for: recipient
But
Hello list,
I am trying to implement ARC in our Exim setup. While reading
experimental-spec.txt[1] I noticed the follwing: "Note that it would
be wise to strip incoming messages of A-R headers that claim to be
from our own ." I have some difficulty with realizing
this. I tried a few things and
13 matches
Mail list logo
