Project

General

Profile

tickets #116938

sending o.o mails to gmail account not possible

Added by docb@opensuse.org 4 months ago. Updated 4 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Email
Target version:
-
Start date:
2022-09-21
Due date:
% Done:

0%

Estimated time:

Description

Hi,

following
https://lists.opensuse.org/archives/list/support@lists.opensuse.org/thread/
ICAGUUQJWDYIRT6A6JZZJAMW43AQ4QLC/

mails from o.o accounts to mail provider like gmail is not possible due to
failed SPF check:

host gmail-smtp-in.l.google.com [66.102.1.26]
SMTP error from remote mail server after pipelined end of data:
550-5.7.26 This message does not pass authentication checks (SPF and DKIM both
550-5.7.26 do not pass). SPF check for [opensuse.org] does not pass with ip:
550-5.7.26 [178.254.4.101].To best protect our users from spam, the message
has
550-5.7.26 been blocked. Please visit
550-5.7.26 https://support.google.com/mail/answer/81126#authentication for
more
550 5.7.26 information. p11-20020a05600c204b00b003b4b2707425si9307880wmg.75 -
gsmtp

What can we do on that?

Cheers
Axel


Related issues

Related to openSUSE admin - tickets #109025: gmail rejects mails from cboltz@o.o - SPF/DKIM/DMARC issueIn Progress2022-03-27

Related to openSUSE admin - tickets #113342: ARC support for openSUSE MTAsNew2022-07-07

History

#1 Updated by pjessen 4 months ago

  • Related to tickets #109025: gmail rejects mails from cboltz@o.o - SPF/DKIM/DMARC issue added

#2 Updated by pjessen 4 months ago

  • Category set to Email
  • Private changed from Yes to No

Hi Axel,
yeah, it is a well-known issue. See #109025.

As far as I can tell, it is Google who have tightened their restrictions.
We (opensuse.org) publish an SPF record that permits our own IP-ranges to send emails from @opensuse.org, but we also use a ~all, a "softfail", which says not to bounce mails being sent from other addresses. As you can tell from that other issue, we/I have already spent a lot of time on trying to fix this, without really getting anywhere.
We also public a DMARC policy which is set to 'none' for all email, so there should not be any issue.

#3 Updated by pjessen 4 months ago

#4 Updated by DocB 4 months ago

Thanks for the update Per.
Reading throught the other ticket it is indeed a long-lasting issue.

#5 Updated by pjessen 4 months ago

  • Status changed from New to Closed

I suggest you follow #109025.
My tests so far show that Google simply ignores the +all setting in the SPF record.

Also available in: Atom PDF