Following up on https://ask.fedoraproject.org/t/getting-fedora-email-alias/19890 I like to note the following:
I am part of the fedora-join FAS group, and so have CLA+1. However, emailing ingli AT fedoraproject DOT org does not get a positive response from the fedora server.
ingli AT fedoraproject DOT org
So, something does not seem quite to work in the automatic creation of aliases.
no priority
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
The problem is that newaliases isn't getting run somehow.
The script is roles/fasjson/templates/fasjson-aliases.j2
-rw-------. 1 root root 493017 Jan 25 19:05 /etc/aliases -rw-r--r--. 1 root root 827392 Jan 6 19:36 /etc/aliases.db
Metadata Update from @kevin: - Issue untagged with: medium-gain, medium-trouble, ops - Issue priority set to: Needs Review (was: Waiting on Assignee)
Metadata Update from @mobrien: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
In the interests of making this work for existing users I went and ran 'newaliases' so they should be all up to date...it still needs fixed however.
New failure messages: The recipient server did not accept our requests to connect. Learn more at https://support.google.com/mail/answer/7720 [fedorapeople.org 2600:2701:4000:5211:dead:beef:a7:9474: timed out] [fedorapeople.org 152.19.134.199: FAILED_PRECONDITION: connect error (113): No route to host]
fedorapeople.org? The aliases we provide are @fedoraproject.org :)
OK, sorry. What really happened is that test messages to @fedoraproject.org were swallowed without any bounce, but never forwarded to my fas E-mail account.
Did you send it from your gmail account?
If so, thats expected, as google "helpfully" doesn't ever show you emails you send to yourself.
You will need to have someone else send to you. I went ahead and sent you a test message.
OK, Kevin. Sorry for all the noise. I received your test message. Thank you.
Metadata Update from @aheath1992: - Issue assigned to aheath1992
It appeaser the issue was /etc/aliases had the incorrect Selinux context, added a function to the script to set the correct context. This has fixed the issue, closing the ticket.
Metadata Update from @aheath1992: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.