On 2022-11-10 06:23:43 (+0800), MRob via mailop wrote:
On 2022-11-09 13:54, Kevin A. McGrail via mailop wrote:
Just a note that it is not necessarily a free trial. It's the
onboarding domain for M365.
I would NOT agree that it reflects legitimate traffic and have rules
in the KAM ruleset for t
yes, I have one customer who sends me email using that format
jxx@xx.onmicrosoft.com
and the emails come to us from outlook.com servers.
-bill
On 11/9/2022 2:23 PM, MRob via mailop wrote:
On 2022-11-09 13:54, Kevin A. McGrail via mailop wrote:
Just a note that it is not necessarily
On 2022-11-09 13:54, Kevin A. McGrail via mailop wrote:
Just a note that it is not necessarily a free trial. It's the
onboarding domain for M365.
I would NOT agree that it reflects legitimate traffic and have rules
in the KAM ruleset for the onmicrosoft domains. They are being
abused.
Does a
On 2022-11-09 13:37, Bill Cole via mailop wrote:
On 2022-11-09 at 06:47:55 UTC-0500 (Wed, 09 Nov 2022 11:47:55 +)
MRob via mailop
is rumored to have said:
On 2022-11-09 08:40, Slavko via mailop wrote:
Dňa 9. 11. o 0:34 MRob via mailop napísal(a):
... But if microsoft agree to DKIM-sign us
On 11/8/2022 2:03 PM, Mary via mailop wrote:
've seen this before, when the header above the From header is broken:
Authentication-Results: server;
dkim=blah reason="blah";
From: "Valid"
To: mailop
The parser thinks that the From: header is part of the previous header, thus
i
These sound likely different, but I wonder if the German app mistakenly is
translating the From header name into German. It could also be doing
something wrong with adding non-ascii characters to the From header
contents, though our parser should be more lenient about that.
In general, though, th
Hello,
I am also seeing this error sending to Gmail.
In our case, the client/sender seems to be using the Email client feature on a
Samsung android mobile and it happens when used on German language. I tested
this locally on my own Samsung and had the same result.
Is a non-English language al
Just a note that it is not necessarily a free trial. It's the
onboarding domain for M365.
I would NOT agree that it reflects legitimate traffic and have rules in
the KAM ruleset for the onmicrosoft domains. They are being abused.
Regards,
KAM
On 11/8/2022 7:01 PM, Suresh Ramasubramanian v
I appreciate the feedback from you both! I'll see if this is something we
can confirm/exclude.
J
On Tue, Nov 8, 2022 at 3:15 PM Brandon Long via mailop
wrote:
> Another one I've seen is an extra newline which ends the headers, ie:
>
> Subject: foo
> To: b...@example.net
>
> From: campa...@exam
On 2022-11-09 at 06:47:55 UTC-0500 (Wed, 09 Nov 2022 11:47:55 +)
MRob via mailop
is rumored to have said:
On 2022-11-09 08:40, Slavko via mailop wrote:
Dňa 9. 11. o 0:34 MRob via mailop napísal(a):
... But if microsoft agree to DKIM-sign using envelope-from
(**signature including the FROM
On 2022-11-09 08:40, Slavko via mailop wrote:
Dňa 9. 11. o 0:34 MRob via mailop napísal(a):
... But if microsoft agree to DKIM-sign using envelope-from
(**signature including the FROM header**) shouldnt that mean it is
seeing the headers and can of course validate FROM header? For me that
show
Dňa 9. 11. o 0:34 MRob via mailop napísal(a):
... But if microsoft agree to DKIM-sign using
envelope-from (**signature including the FROM header**) shouldnt that
mean it is seeing the headers and can of course validate FROM header?
For me that show extra proof microsoft allowing free-form unche
PowerMTA does it not by default.
Simon Luger
sendeffect - mehr erreichen
--
WEBanizer AG
Schulgasse 5
84359 Simbach am Inn
Telefon: +49 (0) 8571 - 97 39 690
Handelsregister: Amtsgericht Landshut HRB 5177 | Ust. ID.: DE 2068 62 070
WEBanizer AG
Vorstand
Envelope sender often manifests itself in the Return-Path:. This /should/ only
be added by the final delivering system based on the envelope sender as it was
handed the message, but who knows how many final delivery systems do add it,
and what do they do if an inbound message already has a Retu
On Tue, Nov 08, 2022 at 11:10:56PM +, MRob via mailop wrote:
> Why isnt it standard to put the envelope sender into the RECEIVED header?
> Does any MTA do it?
Exim does; the default received_header_text contains
"${if def:sender_address {(envelope-from <$sender_address>)\n\t}}"
--
Thomas Mec
15 matches
Mail list logo