Project

General

Profile

tickets #108215

Reply-to by mail fails for code.opensuse.org

Added by docb@opensuse.org 11 months ago. Updated 26 days ago.

Status:
Workable
Priority:
Normal
Assignee:
pjessen
Category:
Git(lab)/ Pagure
Target version:
-
Start date:
2022-03-11
Due date:
% Done:

50%

Estimated time:

Description

Hello Heroes,

when I reply by mail to a notification coming from code.o.o, I get a bounce
notice (see attached)

Can you please look into it? I feel this is a feature that should work....

Thanks
Axel

Mail delivery failed_ returning message to sender (13.7 KB) Mail delivery failed_ returning message to sender docb@opensuse.org, 2022-03-11 11:56

Related issues

Related to openSUSE admin - tickets #101244: mails to code.o.o bounce ("Connection timed out")Resolved2021-10-21

Related to openSUSE admin - tickets #122596: postfix config on pagure01.i.o.oNew2023-01-02

Related to openSUSE admin - tickets #123757: pagure01.i.o.o (code.o.o) rejects mails to @code.o.oNew2023-01-28

Has duplicate openSUSE admin - tickets #122872: pagure01.i.o.o (code.o.o) rejects mails to @code.o.oNew2023-01-09

History

#1 Updated by pjessen 11 months ago

  • Private changed from Yes to No

My guess - the mailserver on code.o.o is dead. It looks like mails to code.o.o are going directly to code.o.o without passing through mx12.

#2 Updated by pjessen 11 months ago

  • Category set to Git(lab)/ Pagure

FWIW, the mailserver on pagure01 does not listen on any external address, only localhost.
I did not look at it in any detail, but I don't see that mailserver being able to do any special processing of such mails.

#3 Updated by Pharaoh_Atem 11 months ago

In order for reply-by-email to work, it needs some configuration: https://docs.pagure.org/pagure/install_pagure_milter.html#configure-your-system

That also includes the MTA being able to receive mail, which we don't have configured and I don't know how to do...

#4 Updated by pjessen 11 months ago

Pharaoh_Atem wrote:

That also includes the MTA being able to receive mail, which we don't have configured and I don't know how to do...

I'll be happy to help with that. Usually this sort of thing means setting up a dedicated transport in postfix, to feed the mail to a script for processing. I would suggest we route the mails through mx12, and then forward them internally. That way pagure doesn't have to do much.

#5 Updated by pjessen 11 months ago

pagure01: I have enabled it to receive mails internally.
mx12: I have routed @code.o.o to pagure01.
We need an MX record for code.o.o to point to mx12 - I'm not sure if I have access or not.

#6 Updated by pjessen 10 months ago

  • % Done changed from 0 to 50

pjessen wrote:

We need an MX record for code.o.o to point to mx12 - I'm not sure if I have access or not.

Christian set that up yesterday, and I have now also amended /etc/postfix/main.cf, adding 'code.opensuse.org' to relay_domains.
I have also amended the firewall on pagure01 to accept internal smtp traffic.

#7 Updated by pjessen 10 months ago

pjessen wrote:

pjessen wrote:

We need an MX record for code.o.o to point to mx12 - I'm not sure if I have access or not.

Christian set that up yesterday, and I have now also amended /etc/postfix/main.cf, adding 'code.opensuse.org' to relay_domains.
I have also amended the firewall on pagure01 to accept internal smtp traffic.

I forgot to mention, of course pagure01 will so far only refuse any incoming mails, because it does not know what to do with them.
I'll have a look at setting up the milter, but I have no idea how to test it.

#8 Updated by pjessen 10 months ago

Okay, this seems fairly straight forward - there is a pagure_milter which provides a socket that postfix can talk to.
I tried enabling and starting it, but running as postfix:postfix, it cannot read /etc/pagure/pagure.cfg - having /etc/pagure/pagure.cfg world-readable is discussed a bit here: https://pagure.io/pagure/issue/1053
Config instructions: https://docs.pagure.org/pagure/install_pagure_milter.html

#9 Updated by DocB 10 months ago

I guess this is ongoing:

host pagure01.infra.opensuse.org[192.168.47.84] said: 554 5.7.1
reply+193d15a42272cda44e6aa54c12f8a3ae7f10bf854090b66d978e972dc846c437427260c5305bcd00f1b3f507728eab022afeb96822bc03fc4068df45b1300562@code.opensuse.org:
Relay access denied (in reply to RCPT TO command)

#10 Updated by pjessen 10 months ago

  • Status changed from New to Feedback
  • Assignee set to pjessen

DocB wrote:

I guess this is ongoing:

Yes, see comment 8 above.

#11 Updated by pjessen 10 months ago

I was going to change the group of /etc/pagure/pagure.cfg from 'git' to 'postfix', but I think that would likely cause an issue for pagure. The alternative might be to make /etc/pagure/pagure.cfg world readable, does anyone see an issue in that?

#12 Updated by pjessen 9 months ago

  • Related to tickets #101244: mails to code.o.o bounce ("Connection timed out") added

#13 Updated by hellcp 2 months ago

You could also set it up in salt so that we have 2 identical copies of the configuration in different places, one with permissions for one and the other for other

#14 Updated by pjessen 26 days ago

  • Has duplicate tickets #122872: pagure01.i.o.o (code.o.o) rejects mails to @code.o.o added

#15 Updated by pjessen 26 days ago

  • Status changed from Feedback to Workable

pjessen wrote:

I have now also amended /etc/postfix/main.cf, adding 'code.opensuse.org' to relay_domains.

I guess this was overwritten by a highstate ?

#16 Updated by pjessen 26 days ago

#17 Updated by pjessen 8 days ago

  • Related to tickets #123757: pagure01.i.o.o (code.o.o) rejects mails to @code.o.o added

Also available in: Atom PDF