thanks again, Mark, for your detailed answer.
On 3/15/22 17:21, Mark Sapiro wrote:
See https://gitlab.com/mailman/mailman/-/issues/901
You can add something like
Alternatively, you can confirm by going to the URL https://$domain/mailman3/lists/$list_id/confirm/?token=$token
hmm. the list-url (e.g. where you can subscribe to the list) for my instance looks like https://$domain/postorius/lists/$list_id/ (that is: it spells "postorius" rather than "mailman3"). so i guess the URL should be https://$domain/postorius/lists/$list_id/confirm/?token=$token, which unfortunately returns 404.
also, my postorius/urls.py does not contain an url-pattern for "confirm", unlike the current one as found on <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/urls.py#L83>
so i guess this was not possible yet with postorius 1.2.4
to the list:user:action:subscribe template. Note that
$domainmay not be appropriate here because it is the email domain which may not be the web domain.also: the confirmation mail says that the subject must be kept intact. however, i noticed that the actual "From" address of the confirmation mail already contains the token.
The current template https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/li... doesn't say that.
yes. the *current* template. but not the template that came with mailman3 3.2.1
finally: what else is required to approve the confirmation? will the sender's email-address be taken into account? (e.g. if they subscribed "foo+mylist@example.com" but send the confirmation-reply from "foo@example.com", will that still work?
Yes. Only the token is required.
cool thanks. together with the not-yet-expired tokens, i think i can create some ad-hoc web-service that translates URLs to confirmation replies.
mfd IOhannes