Project

General

Profile

action #110920

QA - coordination #99303: [saga][epic] Future improvements for SUSE Maintenance QA workflows with fully automated testing, approval and release

openQA Project - coordination #99306: [epic] Future improvements: Make reviewing openQA results per squad easier

Emails from o3 are rejected by mx2.suse.de for certain sender/recipients size:S

Added by tinita about 2 months ago. Updated 3 days ago.

Status:
Blocked
Priority:
High
Assignee:
okurz
Target version:
openQA Project - Ready
Start date:
Due date:
% Done:

0%

Estimated time:

Description

We would like to send notification emails on openqa.opensuse.org.

There are certain combinations of Sender and recipients that are rejected by mx2.suse.de.

I'm testing with

echo "body" | mailx -s "subject" -r "from@example.org" "to@example.org"

Sending from a suse.de address to an suse.com, an external address or a slack channel address works.
Sending from a suse.com address to a suse.com or suse.de address is rejected.
Sending from a suse.com address to an external address works.

Sending from a suse.de address to a suse.de address is rejected.

If rejected, the recipient gets an email from mailer daemon:

<timueller@suse.de>: host mx2.suse.de[ip] said: 554 5.7.1
    <o3-admins@suse.de>: Sender address rejected: We don't accept our own
    addresses as sender address on this host! (in reply to RCPT TO command)

Acceptance criteria

  • AC1: Emails are no longer rejected

Suggestions

  • File tickets with SUSE IT and openSUSE heroes

Related issues

Copied from openQA Project - action #110629: openqa-label-known-issues: Fallback notification address in openqa-label-known-issues if no email address could be parsed from group_overviewResolved2022-05-04

Copied to openQA Infrastructure - action #112673: Cannot send emails from o3 size:MWorkable

History

#1 Updated by tinita about 2 months ago

  • Copied from action #110629: openqa-label-known-issues: Fallback notification address in openqa-label-known-issues if no email address could be parsed from group_overview added

#2 Updated by tinita about 2 months ago

  • Project changed from openQA Project to openQA Infrastructure
  • Category deleted (Feature requests)

#3 Updated by okurz about 2 months ago

  • Target version set to Ready
  • Parent task set to #99306

#4 Updated by cdywan about 2 months ago

  • Subject changed from Emails from o3 are rejected by mx2.suse.de for certain sender/recipients to Emails from o3 are rejected by mx2.suse.de for certain sender/recipients size:S
  • Description updated (diff)
  • Status changed from New to Workable

#5 Updated by okurz about 1 month ago

  • Target version changed from Ready to future

#6 Updated by okurz 10 days ago

  • Priority changed from Normal to High
  • Target version changed from future to Ready

We have not seen emails from o3 logwarn as well for some time so this might be broken in general.

#7 Updated by tinita 10 days ago

#8 Updated by tinita 4 days ago

  • Status changed from Workable to Blocked

I would say this is blocked by #112673. No emails are sent at all.
At best when talking to the mail server admins, both issues can be mentioned.

#9 Updated by okurz 3 days ago

  • Assignee set to okurz

please use "Blocked" with an assignee that tracks the blocked states. Taking over.

Also available in: Atom PDF