Directly confirm a superuser's email?
Hi,
I installed Mailman3, created a Django superuser, tried to log into the GUI, and was told there was a confirmation email being sent out.
For some reason it was sent to "www-data@mailmans.domain", the postfix log says, not the configured email of "my-name@my.organisation", and ended in the bin since that user does not accept emails.
Is there a way to create a "pre-confirmed" superuser without that email being sent? Or to manually confirm it on the command line?
That would be quicker than brooding over the configuration files for another couple of hours.
Thanks in advance
Volkmar
Volkmar Grote writes:
I installed Mailman3, created a Django superuser, tried to log into the GUI, and was told there was a confirmation email being sent out.
For some reason it was sent to "www-data@mailmans.domain", the postfix log says, not the configured email of "my-name@my.organisation", and ended in the bin since that user does not accept emails.
I assume both of those addresses are placeholders, not literal addresses?
The normal way of creating the superuser account is the "mailmanweb creatsuperuser" command, which requires a username, an email address, and a password. (There are several aliases such as "djangoadmin" instead of "mailmanweb".) If you did that on a host dedicated to Mailman, I don't understand how the problem you observe can occur. Either you did something else or a more information about your system will be needed. The only thing I can think of offhand is a preexisting alias in your mailserver, but that seems unlikely too.
Is there a way to create a "pre-confirmed" superuser without that email being sent? Or to manually confirm it on the command line?
No, and no. If that address is incorrectly configured, we expect that most admins want to know it before the site goes live.
That would be quicker than brooding over the configuration files for another couple of hours.
The addresses in the configuration files are in principle unrelated to the identity of the Django superuser. They're not the source of this problem. (Of course it's likely that some or all of the config file addresses will be configured to be the same as the address of the Django superuser, but that's not what's causing your problem.)
Steve
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
Am 29.10.26 um 16:10 schrieb Stephen J. Turnbull:
Volkmar Grote writes:
I installed Mailman3, created a Django superuser, tried to log into the GUI, and was told there was a confirmation email being sent out.
For some reason it was sent to"www-data@mailmans.domain", the postfix log says, not the configured email of "my-name@my.organisation", and ended in the bin since that user does not accept emails.
I assume both of those addresses are placeholders, not literal addresses? Yes :-) The normal way of creating the superuser account is the "mailmanweb creatsuperuser" command, which requires a username, an email address, and a password. (There are several aliases such as "djangoadmin" instead of "mailmanweb".) If you did that on a host dedicated to Mailman, I don't understand how the problem you observe can occur. Either you did something else or a more information about your system will be needed. The only thing I can think of offhand is a preexisting alias in your mailserver, but that seems unlikely too.
After I removed some other issues, e.g. permissions of directories, it seems to fly now.
Is there a way to create a "pre-confirmed" superuser without that email being sent? Or to manually confirm it on the command line?
No, and no. If that address is incorrectly configured, we expect that most admins want to know it before the site goes live. OK, thanks, so there is no short cut available.
That would be quicker than brooding over the configuration files for another couple of hours.
The addresses in the configuration files are in principle unrelated to the identity of the Django superuser. They're not the source of this problem. (Of course it's likely that some or all of the config file addresses will be configured to be the same as the address of the Django superuser, but that's not what's causing your problem.)
Steve
With that out of the way now, the next problems are coming up, but that'll be another thread if I get stuck.
Volkmar
participants (2)
-
Stephen J. Turnbull -
Volkmar Grote