On 2/12/26 13:58, Ibiam Chihurumnaya via Mailman-users wrote:
I created an admin user and when I try to sign in with that user, I get a page that tells me that a confirmation email has been sent and I should confirm the user.
I created another user with a different email, and I got the same thing, didn't receive the confirmation emails in my inbox.
Do you mean you are creating these users by adding them as list owner or moderator or are you creating them via the https://example.com/accounts/signup/ page.
I looked at mailman smtp logs, and didn't see any event related to the confirmation emails. The uwsgi logs show the events though.
If this is the latter, it has nothing to do with Mailman core or the smtp log. It is via django-allauth and the mail comes from Django.
The only place I see something about it is in uwsgi; 3050415 [pid: 1985548|app: 0|req: 518823/979759] 127.0.0.1 () {54 vars in 1197 bytes} [Thu Feb 12 21:52:32 2026] GET /accounts/confirm-email/ => generated 1556 bytes in 48 msecs (HTTP/1.0 200) 9 headers in 359 bytes (1 switches on core 0)
OK, this is Django. The default EMAIL_BACKEND from mailman_web/settings/base.py is django.core.mail.backends.smtp.EmailBackend and unless you've changed that or added overrides various other defaults are
EMAIL_HOST = "localhost" EMAIL_PORT = 25 EMAIL_HOST_USER = "" EMAIL_HOST_PASSWORD = "" EMAIL_USE_TLS = False EMAIL_USE_SSL = False EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = None
Are those appropriate? Do you have an outgoing MTA listening on
localhost:25? What's in it's logs?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan