Stephen J. Turnbull wrote:
> Ibiam Chihurumnaya via Mailman-users writes:
> > Confirmation emails aren't being sent to users and there's nothing
> > in the logs that make it obvious what's happening.
> > As I explained earlier, this backtrace
> > 233830   File 
> > "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/view_helpers.py",
> >  line 137, in inner
> > [...]
> > 233908   File 
> > "/opt/mailman/venv/lib/python3.10/site-packages/mistune/core.py", line 214, 
> > in parse_method
> > 233909     assert lastgroup
> > 233910 AssertionError
> > is a known issue with mistune, which used by HyperKitty to display
> messages from the archives.
> Whatever is happening with the confirmation messages, it's unrelated
> to this.
> 

Yes, the traceback tells me that. I'd shared as Mark had asked for the log from 
mailmanweb.

> What confirmation messages are missing?  Mailman may ask for
> confirmation if a user adds an email address via Postorius, if the
> user asks for a password reset from Postorius, if a user who is not
> logged in subscribes to a list (either by email or by Postorius),
> and there may be other cases.  Please describe all that apply.

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.

> What makes you think that they are missing?  Sometimes users or sites
> have filters that throw them away, or they may be swallowed by MTAs
> because of misconfigurations.

I looked at mailman smtp logs, and didn't see any event related to the 
confirmation emails.
The uwsgi logs show the events though.

> Is your "virgin" runner and "out" runner running?  (Usually "ps aux
> | grep mailman" will list only the processes running under mailman.
> The full command at the end of the line will tell you the names of
> the runners each process is handling.)

Yes, the virgin and out runners are running, output from ps;

mailman  1983940  0.0  1.3 117980 82720 ?        Ss   Feb05   0:00 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/master -C 
/etc/mailman3/mailman.cfg
mailman  1983951  0.0  1.4 120184 85832 ?        S    Feb05   2:05  \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=archive:0:1
mailman  1983952  0.0  1.4 121268 86564 ?        S    Feb05   0:44  \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=bounces:0:1
mailman  1983953  0.0  1.4 121052 86164 ?        S    Feb05   2:04  \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=command:0:1
mailman  1983954  0.0  1.5 126908 93096 ?        S    Feb05   5:02  \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=in:0:1
mailman  1983955  0.0  1.6 194792 98128 ?        Sl   Feb05   1:03  \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=lmtp:0:1
mailman  1983956  0.0  1.4 124092 90144 ?        S    Feb05   2:40  \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=out:0:1
mailman  1983957  0.0  1.4 122000 87164 ?        S    Feb05   2:11  \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=pipeline:0:1
mailman  1983958  0.0  1.4 122392 87964 ?        S    Feb05   2:06  \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=rest:0:1
mailman  1983988  0.1  1.5 138368 95736 ?        S    Feb05  13:10  |   \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=rest:0:1
mailman  1983989  0.1  1.4 132692 90420 ?        S    Feb05  13:03  |   \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=rest:0:1
mailman  1983959  0.0  1.3 117984 82764 ?        S    Feb05   0:01  \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=retry:0:1
mailman  1983960  0.0  1.5 126932 91712 ?        S    Feb05   1:17  \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=task:0:1
mailman  1983961  0.0  1.4 120932 86232 ?        S    Feb05   2:10  \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=virgin:0:1
mailman  1983962  0.0  1.4 120948 86440 ?        S    Feb05   2:04  \_ 
/opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C 
/etc/mailman3/mailman.cfg --runner=digest:0:1

> Are there messages collecting in the "virgin" or "out" queues?

How can I check both queues?

> Are there messages collecting in the MTA queue (the mailq utility
> will usually tell you about those)?

mailq doesn't show anything pertaining to the confirmation email.

> Normally you would see log messages for outgoing confirmations in
> /opt/mailman/mm/var/logs/smtp.log.  You might see errors in
> mailman.log if Mailman core is requesting the confirmations.  If
> Postorius is requesting the confirmations, I think it would probably
> be in mailmanweb.log (Django has its own mail-sending facility,
> those don't go through Mailman core).

I assume Postorius is requesting the confirmations as this happens when I try
to login to mailmanweb, the smtp logs don't show anything about the 
confirmation email
being sent.

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)

> 
> --
> GNU Mailman consultant (installation, migration, customization)
> Sirius Open Source    https://www.siriusopensource.com/
> Software systems consulting in Europe, North America, and Japan
_______________________________________________
Mailman-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at: 
https://lists.mailman3.org/archives/list/[email protected]/message/6RVBCAC5BGKTY7WXE5CKOMZHFV26IO3C/

This message sent to [email protected]

Reply via email to