I just realized, that mails for registering an account and/or resetting ones password are obviously sent from postorius@SERVE_FROM_DOMAIN. Why are they not sent from MAILMAN_ADMIN_EMAIL?
The problem is:
- an account is trying to register with a mailaddress from a HostEurope-server
- HostEurope-Servers are doing Sender-Callouts (bad practise :-D) to verify that a mailaccount exists
- mail is then bouncing, b/c those are not answered (shoud I?): status=bounced (host [80.237.138.5] said: 550-Sender verification is required but failed.
- bounce then can't be processed, since mailaccount does not exist :-D status=bounced (mail for SERVE_FROM_DOMAIN loops back to myself)
Am I missing something are shouldn't it be better to send those mails from MAILMAN_ADMIN_EMAIL? (I don't want to mess with these sender callouts or change anything, HostEurope has been a little bit of a pain in the ... with mailinglists and not much help at all).
Thanks in advance, Jens.
The addresses are defined in Django settings if I'm not mistaken. And callout isn't evil.
On Wed, Jun 7, 2023, 23:31 Jens Günther <jens.guenther@posteo.de> wrote:
I just realized, that mails for registering an account and/or resetting ones password are obviously sent from postorius@SERVE_FROM_DOMAIN. Why are they not sent from MAILMAN_ADMIN_EMAIL?
The problem is:
- an account is trying to register with a mailaddress from a HostEurope-server
- HostEurope-Servers are doing Sender-Callouts (bad practise :-D) to verify that a mailaccount exists
- mail is then bouncing, b/c those are not answered (shoud I?): status=bounced (host [80.237.138.5] said: 550-Sender verification is required but failed.
- bounce then can't be processed, since mailaccount does not exist :-D status=bounced (mail for SERVE_FROM_DOMAIN loops back to myself)
Am I missing something are shouldn't it be better to send those mails from MAILMAN_ADMIN_EMAIL? (I don't want to mess with these sender callouts or change anything, HostEurope has been a little bit of a pain in the ... with mailinglists and not much help at all).
Thanks in advance, Jens.
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to odhiambo@gmail.com
Thank you for your reply.
Am 07.06.23 um 23:03 schrieb Odhiambo Washington:
The addresses are defined in Django settings if I'm not mistaken.
The more important question would be, where :-) since I already checked if I can set it to something alse, I might need a hint where exactly I can find it. In the SERVE_FROM_DOMAIN/admin I did not stumble upon it. If you don't know it, no problem, let's just wait for somebody who does, thanks.
And callout isn't evil.
Well, I wasn't talking about evil but bad practise - especially if they bounce the mail only because of this. Why would almost all other mail providers accept those mails!? Good questions with probably a complex answer :-D so let's just stick to the problem and a possible solution. Thanks again.
Kind regards, Jens.
On 6/7/23 14:13, Jens Günther wrote:
The more important question would be, where :-) since I already checked if I can set it to something alse, I might need a hint where exactly I can find it. In the SERVE_FROM_DOMAIN/admin I did not stumble upon it. If you don't know it, no problem, let's just wait for somebody who does, thanks.
It's the EMAIL_CONFIRMATION_FROM setting in your Django settings.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks for the hint. Unfortunately it's not working as expected. I'm using the docker-setup and tried it in 2 different locations, but neither got the expected effect:
I put the variable in the mm-web-container-environment: mm-web: environment:
- EMAIL_CONFIRMATION_FROM=myaddress@something.org
Then I tried settings_local.py with: EMAIL_CONFIRMATION_FROM = 'myaddress@something.org'
What am I missing, where do I have to set this value correctly?
Thanks for the help! Jens.
Am 08.06.23 um 01:57 schrieb Mark Sapiro:
On 6/7/23 14:13, Jens Günther wrote:
The more important question would be, where :-) since I already checked if I can set it to something alse, I might need a hint where exactly I can find it. In the SERVE_FROM_DOMAIN/admin I did not stumble upon it. If you don't know it, no problem, let's just wait for somebody who does, thanks.
It's the EMAIL_CONFIRMATION_FROM setting in your Django settings.
On 6/14/23 14:35, Jens Günther wrote:
Thanks for the hint. Unfortunately it's not working as expected. I'm using the docker-setup and tried it in 2 different locations, but neither got the expected effect:
- I put the variable in the mm-web-container-environment: mm-web: environment: - EMAIL_CONFIRMATION_FROM=myaddress@something.org
That won't work
- Then I tried settings_local.py with: EMAIL_CONFIRMATION_FROM = 'myaddress@something.org'
That is the correct place. It should work. Did you restart the container after making this change?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Am 15.06.23 um 00:34 schrieb Mark Sapiro:
- Then I tried settings_local.py with: EMAIL_CONFIRMATION_FROM = 'myaddress@something.org'
That is the correct place. It should work. Did you restart the container after making this change?
Mh, unfortunately it does not work. postorius@$SERVE_FROM_DOMAIN as shown in the screenshot.
- I changed the file and rebuilt the container.
- I also restarted all 3 containers again.
- I checked in the container the settings_local.py to verify that the change "arrived" and found it.
- It still sends the "reset-password"-email with
Is there any other way to test or check it? Any more ideas? Thank you in advance.
Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt.
Content-Type: image/png Name: Bildschirmfoto_2023-06-15_22-55-29.png
On 6/15/23 14:03, Jens Günther wrote:
Am 15.06.23 um 00:34 schrieb Mark Sapiro:
- Then I tried settings_local.py with: EMAIL_CONFIRMATION_FROM = 'myaddress@something.org'
Sorry, this is actually a different setting. There are actually two more that control this. These are DEFAULT_FROM_EMAIL <https://docs.djangoproject.com/en/4.2/ref/settings/#default-from-email> and SERVER_EMAIL <https://docs.djangoproject.com/en/4.2/ref/settings/#server-email>. Note that the defaults mentioned in the Django docs are probably overridden in your settings.py, but you should set them in settings_local.py
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Am 16.06.23 um 01:10 schrieb Mark Sapiro:
On 6/15/23 14:03, Jens Günther wrote:
Am 15.06.23 um 00:34 schrieb Mark Sapiro:
- Then I tried settings_local.py with: EMAIL_CONFIRMATION_FROM = 'myaddress@something.org'
Sorry, this is actually a different setting. There are actually two more that control this. These are DEFAULT_FROM_EMAIL <https://docs.djangoproject.com/en/4.2/ref/settings/#default-from-email> and SERVER_EMAIL <https://docs.djangoproject.com/en/4.2/ref/settings/#server-email>. Note that the defaults mentioned in the Django docs are probably overridden in your settings.py, but you should set them in settings_local.py
Thank you Mark. I changed now DEFAULT_FROM_EMAIL to my address, restartet container and it works.
Also it works if I delete the EMAIL_CONFIRMATION_FROM-line again and do not put the SERVER_EMAIL, at least for the password-reset. Can you tell the diffenrence between the 3? Would you recommend to set all 3 to my admin-mailaddress?
participants (3)
-
Jens Günther -
Mark Sapiro -
Odhiambo Washington