[Mailman-Users] Mailman subscribe confirmation

[John]

Hello,

We've encountered a weird issue with mailman 2. We're using mailman 2.1.39, 
running on a straight RHEL 9 server.

When someone subscribes to a mailing list, they receive an email that says, 
among other things:


Or visit this web page:


http:///mailman/confirm//9e2fccef2ac047bb3d67e602e7fb695a277afe43


Normally, clicking on this link would confirm the subscription. In our case, it 
prompts for the string again, and keeps doing so - it seems that mailman 
doesn't recognize the string as being valid.

Using one of the other confirmation methods, such as just replying to the 
message, works correctly. The new subscriber is confirmed successfully.

The same issue occurs for unsubscribe requests.

The What steps are required for subscription? option is set to Confirm.

Can anyone suggest how to fix this?

Thanks.

::Jack



--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@jab.org

[Mailman-Users] Read-only File System

[John]

Hello,

Several days ago, I posted a message to his list concerning our installation of 
Mailman 2, and a weird problem that caused messages posted to a list to fail, 
as /usr/local/mailman/qfiles/in/ was behaving like it was read-only.

First off, thanks to everyone who replied with suggestions.

While we haven't determined what was causing this issue, we did devise a 
work-around of sorts. I'm posting it here in case someone else encounters the 
same issue.

The problem that we encountered was that mailman / python regarded 
/usr/local/mailman/qfiles and all the directories under it to be read-only. 
They're not - anything else that wants to create a file therein can do so.

This was how we fixed it:


  1.
Stop mailman if it's running.
  2.
cd /usr/local/mailman .
  3.
cp -R qfiles /qfiles . (I suspect there are more appropriate places to copy the 
directory to, such as /var - this worked for us and we stopped messing with it.)
  4.
mv qfiles qfiles.dist - just in case you ever figure out the real cause and 
want to reverse all this.
  5.
ln -s /qfiles qfiles . (That is, create a symbolic link to the /qfiles 
directory, or wherever you decided to put it.)
  6.
Start mailman

Mailman proved to have no problem writing to the relocated qfiles directory, 
and everything magically started working.

Hope this saves someone from banging their head against a wall, as we very 
nearly wound up doing.

::Jack



--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@jab.org

[Mailman-Users] Re: Mailman subscribe confirmation

[Bill Cole]

On 2024-07-05 at 11:59:54 UTC-0400 (Fri, 5 Jul 2024 15:59:54 +)
John 
is rumored to have said:


Hello,

We've encountered a weird issue with mailman 2. We're using mailman 
2.1.39, running on a straight RHEL 9 server.


When someone subscribes to a mailing list, they receive an email that 
says, among other things:



Or visit this web page:


http:///mailman/confirm//9e2fccef2ac047bb3d67e602e7fb695a277afe43


Normally, clicking on this link would confirm the subscription. In our 
case, it prompts for the string again, and keeps doing so - it seems 
that mailman doesn't recognize the string as being valid.


One thing to check is that URL. If your webserver always redirects http 
to https but Mailman thinks its URL starts with http:// you will have 
problems like this. The solution is switch Mailman to use the https URL.









Using one of the other confirmation methods, such as just replying to 
the message, works correctly. The new subscriber is confirmed 
successfully.


The same issue occurs for unsubscribe requests.

The What steps are required for subscription? option is set to 
Confirm.


Can anyone suggest how to fix this?

Thanks.

::Jack



--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: 
https://www.mail-archive.com/mailman-users@python.org/

https://mail.python.org/archives/list/mailman-users@python.org/
Member address: mailmanu-20190...@billmail.scconsult.com



--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo@toad.social and many *@billmail.scconsult.com 
addresses)

Not Currently Available For Hire
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@jab.org

[Mailman-Users] Re: Read-only File System

[Dmitri Maziuk]

On 7/5/24 08:53, John wrote:
...

Mailman proved to have no problem writing to the relocated qfiles directory, 
and everything magically started working.


Did you try lsattr on the original files/dir?

Just curious,
Dima
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@mail-archive.com

[Mailman-Users] Re: Read-only File System

[John]

I didn't... but I tried it now, as I kept the original qfiles directory under 
another name.

It said:

--e--- qfiles.dist/commands
qfiles.dist/commands:
--e--- qfiles.dist/shunt
qfiles.dist/shunt:
--e--- qfiles.dist/in
qfiles.dist/in:
--e--- qfiles.dist/bounces
qfiles.dist/bounces:
--e--- qfiles.dist/virgin
qfiles.dist/virgin:
--e--- qfiles.dist/archive
qfiles.dist/archive:
--e--- qfiles.dist/retry
qfiles.dist/retry:
--e--- qfiles.dist/out
qfiles.dist/out:
--e--- qfiles.dist/news


::Jack



From: Dmitri Maziuk 
Sent: 05 July 2024 16:53
To: mailman-users@python.org 
Subject: [Mailman-Users] Re: Read-only File System

On 7/5/24 08:53, John wrote:
...
> Mailman proved to have no problem writing to the relocated qfiles directory, 
> and everything magically started working.

Did you try lsattr on the original files/dir?

Just curious,
Dima
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: j_p_waterho...@hotmail.com
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@mail-archive.com

[Mailman-Users] Re: Mailman subscribe confirmation

[Mark Sapiro]

On 7/5/24 09:45, Bill Cole wrote:


One thing to check is that URL. If your webserver always redirects http 
to https but Mailman thinks its URL starts with http:// you will have 
problems like this. The solution is switch Mailman to use the https URL.



And to do that, set

DEFAULT_URL_PATTERN = 'https:///mailman/'

(substituting for  of course) in mm_cfg.py and then fun 
fix_url, see https://wiki.list.org/x/4030616


--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@jab.org