tickets #108215
openReply-to by mail fails for code.opensuse.org
50%
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
Files
Updated by pjessen about 2 years 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.
Updated by pjessen about 2 years ago
- Category set to Git(lab|hub)
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.
Updated by Pharaoh_Atem about 2 years 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...
Updated by pjessen about 2 years 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.
Updated by pjessen about 2 years 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.
Updated by pjessen about 2 years 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.
Updated by pjessen about 2 years 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.
Updated by pjessen about 2 years 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
Updated by DocB about 2 years 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)
Updated by pjessen about 2 years ago
- Status changed from New to Feedback
- Assignee set to pjessen
DocB wrote:
I guess this is ongoing:
Yes, see comment 8 above.
Updated by pjessen about 2 years 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?
Updated by pjessen almost 2 years ago
- Related to tickets #101244: mails to code.o.o bounce ("Connection timed out") added
Updated by hellcp over 1 year 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
Updated by pjessen over 1 year ago
- Has duplicate tickets #122872: pagure01.i.o.o (code.o.o) rejects mails to @code.o.o added
Updated by pjessen over 1 year 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 ?
Updated by pjessen over 1 year ago
- Related to tickets #122596: postfix config on pagure01.i.o.o added
Updated by pjessen about 1 year ago
- Related to tickets #123757: pagure01.i.o.o (code.o.o) rejects mails to @code.o.o added
Updated by pjessen 9 months ago
- Related to tickets #133163: Fwd: Undelivered Mail Returned to Sender added
Updated by pjessen 9 months ago
- Related to deleted (tickets #133163: Fwd: Undelivered Mail Returned to Sender)
Updated by pjessen 9 months ago
- Has duplicate tickets #133163: Fwd: Undelivered Mail Returned to Sender added
Updated by pjessen 9 months ago
pjessen wrote:
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 ?
As mails to code.o.o are to be received and processed locally, for starters, we ought to have mydestination = code.opensuse.org I think. I have amended the postfix config.
Next there is the issue of comment 8 and comment 11 above - about making /etc/pagure/pagure.cfg world readable. It seems to me this whole setup needs some TLC and someone who cares about it. I am very happy to lend a hand when it comes to the mail setup.