-----Original Message----- From: Stephen J. Turnbull <steve@turnbull.jp> Sent: Thursday, August 28, 2025 12:27
Henry Hartley via Mailman-users writes:
- Are there particular headers that are causing the email to go to the Confirmation page instead of the Approval page? Or >>> are there particular headers we can add that will help with this?
No. That's entirely determined by the list's configuration. You cannot change that behavior via a user's subscription request whether by email or web. IIRC, the only overrides are either through the REST API, "mailman shell", or the "mass subscribe" page on the web. (I guess it's possible that the moderator can "pre confirm" at approval time, do you see such an option when you approve? I've never managed a "moderate" list so I don't know without groveling through the code.)
Do you really only have one list? Is it possible that the misbehaving list is not configured as you expect (ie, the list subscription policy is "confirm" or "confirm then moderate")? Unlikely, but if you haven't checked since the problem started, please confirm.
I have 50 lists and they all have the "Subscription Policy" set to Moderate. If I send an email (e.g. from my gmail account) to the LIST-join address, it goes into the Subscriptions Pending Approval list, as it should. But, when sent from Drupal it goes to the Subscriptions Pending User Confirmation list. That's the weirdness that I'm trying to untangle. Nevertheless, I will have one of our testers subscribe through Drupal to a list and confirm that the issue happens every time.
Are you sure that the members have not been approved by some moderator? I forget exactly how this works, but unless you use mass subscribe with the "pre confirm" option set, the user will have to confirm before they can receive mail.
The issue was reported by the moderator, who saw the email address in the wrong place. If the Subscription Policy is set to 'Confirm then Moderate' then ;First subscribers have to confirm, then a moderator needs to authorize.' Since it's set to 'Moderate' (only), then 'Moderators will have to authorize each subscription manually.'
- Is there any way for us to move an address from the Confirmation Pending page to confirmed on the backend > > > (preferably through the web interface, but on the server > > > itself, if necessary)?
Not that I know of, but what you can do is mass subscribe those addresses. I think that you'll still end up with them waiting for confirmation as described above. You can confirm them by accessing the database directly, but that's more fraught than I want to deal with at bedtime :-).
Until we figure this out, I've instructed the moderator to copy the address from the User Confirmation list and Mass Subscribe them and then remove them from the Confirmation List. It works but the moderators don't like it.
Authentication-Results: spf=fail (sender IP is 192.168.0.0) > smtp.mailfrom=SCHOOL.edu; dkim=none (message not signed) > header.d=none;dmarc=fail action=oreject > header.from=SCHOOL.edu;compauth=fail reason=000
This requires some care. DMARC is failing, and necessarily will fail. If SCHOOL.edu has a p=reject policy, this mail should not get to Mailman at all.
I'm pretty sure the outgoing mail from mailman is getting the right headers for DMARC but it definitely bears testing.
If the Drupal host is the Mailman host, then you could use the PHP script to talk to the REST API instead of using email. Cutting out the long list of middlemen, so to speak. (It would also be possible if they're different hosts, but the security precautions I would recommend are quite a bit more severe.)
Yes, Drupal and Mailman are on the same host. We definitely could rewrite our code to use the REST API, and in the long run, that would be good. But we brought this code over from government servers that were using Mailman2 and since it basically worked (except for this odd issue) we put that at a lower priority. But maybe we need to do that sooner rather than later.
-- Henry Hartley