Why is that, when 90% ++ of the transactions are between a limited set of
providers, and even after that, within the long tail, there will be a similar
bell curve so that most of your regular recipients that use ARC will eventually
trust you?
Beyond that, converting authentication into “trust”
On 4/22/24 09:16, Matus UHLAR - fantomas via mailop wrote:
I'm afraid this is very long term solution - the recipient needs to
trust your ARC signatures.
IMHO the "the recipient needs to trust your ARC signature" is ARC's
Achilles' heel.
I have not seen any way to get around this -- what I c
It appears that Paul Menzel via mailop said:
> The following message to was undeliverable.
> The reason for the problem:
> 5.3.0 - Other mail system problem 550-'5.7.26 This mail has been
>blocked because the sender is unauthenticated.\n5.7.26 Gmail requires
>all senders to authenti
But In this case, envelope sender domain is different from domain in
header From: and then SPF checks don't apply to DMARC.
So, if you want to have proper DKIM, you must set From: to your domain
and DKIM-sign it.
To be finicky: DKIM does not care what domain is used in its d=
parameter.
Hi Alexandre,
Thank you for your reply and apologies for my late response.
Jeremy from Orange replied (to my original post) off-list and the
problem is now sorted.
Best,
Mark
Original Message
From: Alexandre Schmit-Baverel
Sent: Thursday, April 18, 2024 at 08:09 UTC
> Howdy,
On 22.04.24 10:00, Marco Moock via mailop wrote:
Google makes forwarding really hard. They want you to set up ARC.
https://support.google.com/a/answer/13198639?sjid=6036584522181943107-EU
I know this is nasty, but this are Google's rules.
Forwarded mails will always have an SPF failure, DKIM wil
On 22.04.24 10:39, Matus UHLAR - fantomas via mailop wrote:
> On 22.04.24 10:00, Marco Moock via mailop wrote:
>> Google makes forwarding really hard. They want you to set up ARC.
>> https://support.google.com/a/answer/13198639?sjid=6036584522181943107-EU
>> I know this is nasty, but this are Googl
> The SPF of molgen.mpg.de has `~all` (soft fail):
>
> $ dig txt molgen.mpg.de +short
> "v=spf1 ip4:141.14.0.0/16 ~all"
But this is irrelevant. The envelope-from of a forwarded message is
the original one - if you do not deliberately rewrite it - and in such
a case, the SPF that is evalua
On 22.04.24 09:28, Paul Menzel via mailop wrote:
A users sends a message to x...@uni-potsdam.de, and the user X there has
a forward set up to their y...@gmail.com address. Now
smtpin.uni-potsdam.de returns a delivery failure from Google Mail:
The following message to was undeliverable.
Am 22.04.2024 um 09:28:20 Uhr schrieb Paul Menzel via mailop:
> The SPF of molgen.mpg.de has `~all` (soft fail):
>
> $ dig txt molgen.mpg.de +short
> "v=spf1 ip4:141.14.0.0/16 ~all"
>
> and I would expect `~all` to result in Google Mail not rejecting the
> message, when another server
Dear mail operators,
A users sends a message to x...@uni-potsdam.de, and the user X there has a
forward set up to their y...@gmail.com address. Now smtpin.uni-potsdam.de
returns a delivery failure from Google Mail:
The following message to was undeliverable.
The reason for the probl
11 matches
Mail list logo
