Project

General

Profile

Actions
Copy link

action #110920

closed

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 over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Urgent
Assignee:
tinita
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 2 (0 open — 2 closed)

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_overviewResolvedtinita2022-05-04

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

Actions
Actions
Copy link
 #1

Updated by tinita over 1 year 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
Actions
Copy link
 #2

Updated by tinita over 1 year ago

  • Project changed from openQA Project to openQA Infrastructure
  • Category deleted (Feature requests)
Actions
Copy link
 #3

Updated by okurz over 1 year ago

  • Target version set to Ready
  • Parent task set to #99306
Actions
Copy link
 #4

Updated by livdywan over 1 year 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
Actions
Copy link
 #5

Updated by okurz over 1 year ago

  • Target version changed from Ready to future
Actions
Copy link
 #6

Updated by okurz over 1 year 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.

Actions
Copy link
 #7

Updated by tinita over 1 year ago

Actions
Copy link
 #8

Updated by tinita over 1 year 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.

Actions
Copy link
 #9

Updated by okurz over 1 year ago

  • Assignee set to okurz

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

Actions
Copy link
 #10

Updated by jbaier_cz about 1 year ago

I believe this one is no longer blocked, we might want to give it another try.

Actions
Copy link
 #11

Updated by okurz about 1 year ago

  • Status changed from Blocked to Workable
  • Assignee deleted (okurz)

sure, we can go ahead

Actions
Copy link
 #12

Updated by okurz about 1 year ago

  • Priority changed from High to Urgent
Actions
Copy link
 #13

Updated by tinita about 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to tinita
Actions
Copy link
 #14

Updated by tinita about 1 year ago

It's not possible to send emails with a suse.de sender address, I checked with Bernhard Wiedemann:
https://suse.slack.com/archives/C029APBKLGK/p1657882472570089

I still don't understand why this works on osd, but it looks like we have to set some "external" sender address and add a reply-to, like Oliver suggested.

Actions
Copy link
 #15

Updated by tinita about 1 year ago

  • Status changed from In Progress to Feedback

I set the sender to noreply@openqa.opensuse.org for now, in /etc/postfix/sender_canonical.
To have an effect, one needs to call

postmap /etc/postfix/sender_canonical
systemctl restart postfix.service

Emails to my own suse.de address is arriving, but it still needs to be confirmed if emails are arriving at the o3-admins list.

Waiting for feedback from the list owner @okurz.

Actions
Copy link
 #16

Updated by tinita about 1 year ago

  • Status changed from Feedback to In Progress

I can now administrate the list.
I had to explicitly allow the sender address noreply@openqa.opensuse.org.

I also set the sender adress for openqa-monitor, so the logwarn emails should go through now.

Todo:

  • Add Reply-To header to logwarn and openqa-review emails
Actions
Copy link
 #17

Updated by tinita about 1 year ago

  • Status changed from In Progress to Feedback

Actually the reply-to is not necessary.

The Sender address is now set via postfix to noreply@openqa.opensuse.org, but the "From" header can now be o3-admins@suse.de.

I set the from_email in openqa.ini to o3-admins@suse.de.

Added that email to the allowed senders in mailman as well.

Now all emails should go through.

Actions
Copy link
 #18

Updated by tinita about 1 year ago

  • Status changed from Feedback to Resolved

Ok, I just saw a successful logwarn email, and a test email to o3-admins plus slack also works.

Resolving.

Actions
Copy link

Also available in: Atom PDF