Alias for email@example.com
We need discuss for address firstname.lastname@example.org. It is used on other project as outbound email. So when someone update ticket, he will received email from email@example.com.
This is difference when on opensuse-admin project. we will receive email from firstname.lastname@example.org as outbound email when get update or send comment from email.
We need confirm. is address email@example.com work for send and receive email from outside? are configs on redmine/progress or mail server?
On Progress vm, we have setup postfix alias for firstname.lastname@example.org.
- Private changed from Yes to No
are configs on redmine/progress or mail server?
If "email@example.com" needs to be publicly available, the aliasing happens on our mailservers, mx.o.o.
I'm happy to set that up, just let me know. It can also be done quickly for testing etc.
#6 Updated by tuanpembual 3 months ago
I created ticket for testing.
When I create and update. I got email from firstname.lastname@example.org. (done for notify)
But when I reply the email. Ticket wont update. (need more debug).
cboltz Do you have any idea?
maybe not really related to this issue, but worth a look nevertheless:
/var/log/mail on progress.i.o.o says:
2020-09-07T05:00:22.213840+00:00 progress postfix/pipe: AF96623B4D: to=<email@example.com>, orig_to=<firstname.lastname@example.org>, relay=redmineprivate, delay=0.51, delays=0.02/0.01/0/0.47, dsn=5.7.0, status=bounced (permission denied. Command output: Request was denied by your Redmine server. Possible reasons: email is sent from an invalid email address or is missing some information. )
This seems to (mostly?) affect bounce mails with the
<> empty sender.
I sent a mail to email@example.com, and after hunting it through the mail logs on several servers, this is the last trace:
2020-09-07T19:52:53.758337+00:00 baloo postfix/smtpd: connect from unknown[192.168.47.96] 2020-09-07T19:52:53.768843+00:00 baloo postfix/smtpd: NOQUEUE: reject_warning: RCPT from unknown[192.168.47.96]: 554 5.7.1 <unknown[192.168.47.96]>: Client host rejected: Access denied; from=<SRS0=Z9Uk=CQfirstname.lastname@example.org> to=<email@example.com> proto=ESMTP helo=<mx2.opensuse.org> 2020-09-07T19:52:53.783794+00:00 baloo postfix/smtpd: BF48C116D2: client=unknown[192.168.47.96] 2020-09-07T19:52:53.787581+00:00 baloo postfix/cleanup: BF48C116D2: message-id=<3566213.9yPnoMeVd3@tux.boltz.de.vu> 2020-09-07T19:52:53.791087+00:00 baloo postfix/qmgr: BF48C116D2: from=<SRS0=Z9Uk=CQfirstname.lastname@example.org>, size=2520, nrcpt=1 (queue active) 2020-09-07T19:52:53.792278+00:00 baloo postfix/smtpd: disconnect from unknown[192.168.47.96] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 2020-09-07T19:52:53.807277+00:00 baloo postfix/local: BF48C116D2: to=<email@example.com>, relay=local, delay=0.04, delays=0.02/0.01/0/0.01, dsn=2.0.0, status=sent (delivered to command: /usr/bin/mlmmj-recieve -L /var/spool/mlmmj/admin/) 2020-09-07T19:52:53.807987+00:00 baloo postfix/qmgr: BF48C116D2: removed 2020-09-07T19:52:53.813853+00:00 baloo /usr/bin/mlmmj-process: mlmmj-process.c:828: Found To: firstname.lastname@example.org: Success 2020-09-07T19:52:53.814357+00:00 baloo /usr/bin/mlmmj-process: mlmmj-process.c:857: Discarding /var/spool/mlmmj/admin//incoming/528405ae07b64ff8 because list address was not in To: or Cc:, and From: was the list or notoccdenymails was set: Success
Per, it looks like you'll need to allow
redmine@ as valid
To in the admin@ ML.
Alternative solution: simplify the setup, and let mx*.o.o deliver directly to progress.i.o.o. Having a mailinglist with (AFAIK) one subscriber might be a bit ;-) overkill. (Doing this for redmine@ would allow us to do some testing, and if everything works, we could also simplify admin@.) Disclaimer: I have no idea why we have the mailinglist between the world and progress - it might be for historical reasons or for a good technical reason ;-)
Disclaimer: I have no idea why we have the mailinglist between the world and progress -
it might be for historical reasons or for a good technical reason ;-)
Mainly historical reasons from the initial Redmine setup: when we implemented the first Redmine instance, we were not 100% sure that everything will work as expected. Therefor we kept a "backup" of every mail in the mailing list (which also allowed some people like Darix or me to subscribe and check for some problems there).
The only technical reason today might be the same as in the past: the mailing list might be more reliable and storing/searching Emails there might be a bit more easy. But that should not be a big issue, as I see no real problems with the current Redmine setup since some years any more.
Therefor I recommend to forward Emails directly from MX to the Redmine server.
Per, it looks like you'll need to allow
Toin the admin@ ML.
I don't believe that is possible, it is a basic mlmmj check, not an admin rule.
Alternative solution: simplify the setup, and let mx*.o.o deliver directly to progress.i.o.o. Having a mailinglist with (AFAIK) one subscriber might be a bit ;-) overkill.