[Mailman-Users] Re: Admin Requests Time Out

[Dennis Putnam]

On 4/24/2024 6:22 PM, Mark Sapiro wrote:

On 4/24/24 08:36, Dennis Putnam wrote:

On 4/23/2024 2:31 PM, Mark Sapiro wrote:


Look in the logs of your web server.

Look at the source of the admindb page you are trying to submit. In 
particular you are looking for a FORM tag like

```

```
Does that URL look correct? If not see lines 67-95 at 
https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Defaults.py.in



Hi Mark,

It looks right to me. This is all I see:

192.168.0.196 - - [24/Apr/2024:11:30:03 -0400] "GET 
/mailman/admindb/cufsalumni HTTP/1.1" 200 2091
192.168.0.196 - - [24/Apr/2024:11:30:03 -0400] "GET /favicon.ico 
HTTP/1.1" 200 5882
192.168.0.196 - - [24/Apr/2024:11:30:05 -0400] "POST 
/mailman/admindb/cufsalumni HTTP/1.1" 200 6964





Your POST gets a 200 status. If it doesn't update it's most likely 
because the URL is http and is being redirected to https and losing 
the POST data. See https://wiki.list.org/x/4030602 - you need to 
ensure the scheme in DEFAULT_URL_PATTERN is https, not http.


Although that said, I don't know why that would cause a timeout.

Again, look at the source of the admindb page in your web browser. 
Look for

```

```
If the scheme is http, the above applies and you need to set
```
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
```
in mm_cfg.py


Hi Mark,

I figured out the issue and the URL is basically correct. The bottom 
line is that an AT router is blocking my IP for some reason. How to 
fix it is another problem as I don't expect AT to do anything about 
it. Not sure when this started.


Anyway, here is the issue. I don't have a static IP address so I am 
using dyndns-ip.com. Most of the links on the admin page uses just 
'dap002' as the URL host which uses only the LAN. However, the submit 
and a couple of other links use dyndns-ip.com in the URL which sends it 
out over the WAN. I never had a problem with that until now. It has been 
eons since I've configured mailman so I've pretty much forgotten 
what/how I did it. I guess for the admin pages only, I need to make all 
the links just dap002 since I only access them on the LAN. The public 
pages still need to use dyndns-ip.com in the URL. Is there a way to do that?


Even if AT fixes the problem it would still be better if all the admin 
stuff is done only on the LAN.


Thanks.


OpenPGP_signature.asc
Description: OpenPGP digital signature
--
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: Admin Requests Time Out

[Dennis Putnam]

On 4/23/2024 2:31 PM, Mark Sapiro wrote:

On 4/23/24 06:55, Dennis Putnam wrote:
I am trying to submit an admin request (rejecting an email) but when 
I click "submit" it times out. I don't see anything in the log file 
(maybe I need to look somewhere else). Restarting the service does 
not help nor does rebooting the system. The status appears to me to 
be correct:


Look in the logs of your web server.

Look at the source of the admindb page you are trying to submit. In 
particular you are looking for a FORM tag like

```

```
Does that URL look correct? If not see lines 67-95 at 
https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Defaults.py.in



Hi Mark,

It looks right to me. This is all I see:

192.168.0.196 - - [24/Apr/2024:11:30:03 -0400] "GET 
/mailman/admindb/cufsalumni HTTP/1.1" 200 2091
192.168.0.196 - - [24/Apr/2024:11:30:03 -0400] "GET /favicon.ico 
HTTP/1.1" 200 5882
192.168.0.196 - - [24/Apr/2024:11:30:05 -0400] "POST 
/mailman/admindb/cufsalumni HTTP/1.1" 200 6964


Is it possible the database is not responding? But if that were the case 
I wouldn't get the administrative request page, right?


OpenPGP_signature.asc
Description: OpenPGP digital signature
--
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] Admin Requests Time Out

[Dennis Putnam]

I am trying to submit an admin request (rejecting an email) but when I 
click "submit" it times out. I don't see anything in the log file (maybe 
I need to look somewhere else). Restarting the service does not help nor 
does rebooting the system. The status appears to me to be correct:


$ sudo service mailman status
Redirecting to /bin/systemctl status mailman.service
● mailman.service - GNU Mailing List Manager
   Loaded: loaded (/usr/lib/systemd/system/mailman.service; enabled; 
vendor preset: disabled)

   Active: active (running) since Thu 2024-04-18 12:21:44 EDT; 4 days ago
  Process: 1143 ExecStart=/usr/lib/mailman/bin/mailmanctl -s start 
(code=exited, status=0/SUCCESS)
  Process: 1126 ExecStartPre=/bin/chmod 660 /var/log/mailman/error 
(code=exited, status=0/SUCCESS)
  Process: 1123 ExecStartPre=/bin/chown mailman:mailman 
/var/log/mailman/error (code=exited, status=

0/SUCCESS)
  Process: 1119 ExecStartPre=/bin/touch /var/log/mailman/error 
(code=exited, status=0/SUCCESS)
  Process: 1097 ExecStartPre=/usr/bin/install -m644 -o root -g root 
/usr/lib/mailman/cron/crontab.in

 /etc/cron.d/mailman (code=exited, status=0/SUCCESS)
  Process: 830 ExecStartPre=/usr/lib/mailman/bin/mailman-update-cfg 
(code=exited, status=0/SUCCESS)

 Main PID: 1842 (mailmanctl)
    Tasks: 9
   CGroup: /system.slice/mailman.service
   ├─1842 /usr/bin/python2 /usr/lib/mailman/bin/mailmanctl -s start
   ├─1892 /usr/bin/python2 /usr/lib/mailman/bin/qrunner 
--runner=ArchRunner:0:1 -s
   ├─1893 /usr/bin/python2 /usr/lib/mailman/bin/qrunner 
--runner=BounceRunner:0:1 -s
   ├─1894 /usr/bin/python2 /usr/lib/mailman/bin/qrunner 
--runner=CommandRunner:0:1 -s
   ├─1895 /usr/bin/python2 /usr/lib/mailman/bin/qrunner 
--runner=IncomingRunner:0:1 -s
   ├─1896 /usr/bin/python2 /usr/lib/mailman/bin/qrunner 
--runner=NewsRunner:0:1 -s
   ├─1897 /usr/bin/python2 /usr/lib/mailman/bin/qrunner 
--runner=OutgoingRunner:0:1 -s
   ├─1898 /usr/bin/python2 /usr/lib/mailman/bin/qrunner 
--runner=VirginRunner:0:1 -s
   └─1899 /usr/bin/python2 /usr/lib/mailman/bin/qrunner 
--runner=RetryRunner:0:1 -s


Apr 18 11:21:19 dap002 systemd[1]: Starting GNU Mailing List Manager...
Apr 18 12:21:44 dap002 mailmanctl[1143]: Starting Mailman's master qrunner.
Apr 18 12:21:44 dap002 systemd[1]: Started GNU Mailing List Manager.


How do I find out what is going on? Any help would be appreciated.


OpenPGP_signature.asc
Description: OpenPGP digital signature
--
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: Administrator Membership List

[Dennis Putnam]

That did it. Thanks.

On 11/10/2022 1:29 PM, Mark Sapiro wrote:

On 11/10/22 08:33, Dennis Putnam wrote:
Is there a way to get the entire membership list on a page like 
before? I don't have a large number of subscribers and going through 
them alphabetically is a royal pain.


Like before what?

Set General Options -> admin_member_chunksize to a number greater than 
the number of members.






OpenPGP_signature
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Administrator Membership List

[Dennis Putnam]

Is there a way to get the entire membership list on a page like before? 
I don't have a large number of subscribers and going through them 
alphabetically is a royal pain.


OpenPGP_signature
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: crontab Problem

[Dennis Putnam]

Hi Mark,

What would cause the entire crontab to disappear? Would a system update 
that modifies cron do something with non-root crontabs? I guess that is 
a question for the CentOS folks.


On 3/22/2022 3:00 PM, Mark Sapiro wrote:

On 3/22/22 11:47, Dennis Putnam wrote:
For some reason the crontab for mailman is gone. When I try run 
crontab for mailman on crontab.in there is no error but when I run 
'crontab -l -u mailman' it says there is no crontab. Can someone tell 
me how to fix this? TIA.


Are you running crontab as the mailman user?
```
crontab -u mailman path/to/crontab.in
```
or
```
sudo -u mailman crontab path/to/crontab.in
```




OpenPGP_signature
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: crontab Problem

[Dennis Putnam]

Hi Mark,

Doh, my bad. I have 2 sudo's installed and was using the wrong one. I 
have to use /bin/sudo to get the standard one. Thanks for jogging my memory.


On 3/22/2022 3:11 PM, Mark Sapiro wrote:

On 3/22/22 12:00, Mark Sapiro wrote:

On 3/22/22 11:47, Dennis Putnam wrote:
For some reason the crontab for mailman is gone. When I try run 
crontab for mailman on crontab.in there is no error but when I run 
'crontab -l -u mailman' it says there is no crontab. Can someone 
tell me how to fix this? TIA.


Are you running crontab as the mailman user?
```
crontab -u mailman path/to/crontab.in
```
or
```
sudo -u mailman crontab path/to/crontab.in
```



Also, if you ran this for another user, you clobbered that user's 
crontab and you need to remove the mailman crontab from that user and 
restore the original if any.






OpenPGP_signature
Description: OpenPGP digital signature
--
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/

[Mailman-Users] crontab Problem

[Dennis Putnam]

For some reason the crontab for mailman is gone. When I try run crontab 
for mailman on crontab.in there is no error but when I run 'crontab -l 
-u mailman' it says there is no crontab. Can someone tell me how to fix 
this? TIA.


OpenPGP_signature
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: mailman user problem

[Dennis Putnam]

I am still struggling with this. I tried to add a shell for mailman in 
/etc/passwd. I am now able to su to mailman but I'm not sure that is the 
way it is supposed to be. I am doing this so I can manually run 
'fetchmail' with the -v option. However, I now get a permissions error 
when fetchmail tries to create its pid file. It is in /usr/lib/mailman' 
and runs as user mailman. I am now confused by the permissions of that 
directory.


drwxr-xr-x. 13 root mailman 4096 Mar 22 05:09 ../mailman

 Is that correct? When I run perms_check it seems to think so. Is is 
safe to give group mailman r/w access to that directory? Is that 
something that changed from previous versions? I'm running 2.1.15-30.


On 3/20/2022 5:35 AM, Dennis Putnam wrote:
I don't know what happened but mailman is no longer working (CentOS 
7). I don't think it is mailman per se but I don't know where else to 
turn for help. I am feeding mailman using fetchmail from gmail.com 
which has been working fine for eons. For some reason fetchmail no 
longer works as I get this error:


Old UID list from pop.gmail.com: 

After considerable research I THINK I have traced the problem to the 
mailman account since fetchmail runs as mailman via cron. It appears 
that the crontab for mailman is gone and I cannot 'su - mailman' to 
run 'crontab' on 'crontab.in'. Although isn't that supposed to happen 
automatically? Nor can I run fetchmail as mailman. I get the error:


This account is currently not available.

The passwd file entry is:

 mailman:x:41:41:GNU Mailing List Manager:/usr/lib/mailman:/sbin/nologin

I think it has always been that way but I'm not sure since 
'/sbin/nologin' means there is no shell and is why I am getting that 
error. I don't, at this point, see how it could have ever worked. In 
any case I need some help figuring out why mailman is getting that error.


FWIW, if I run 'passwd -S mailman', I get this:

mailman NP 2022-03-19 -1 -1 -1 -1 (Empty password.)

TIA





OpenPGP_signature
Description: OpenPGP digital signature
--
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/

[Mailman-Users] mailman user problem

[Dennis Putnam]

I don't know what happened but mailman is no longer working (CentOS 7). 
I don't think it is mailman per se but I don't know where else to turn 
for help. I am feeding mailman using fetchmail from gmail.com which has 
been working fine for eons. For some reason fetchmail no longer works as 
I get this error:


Old UID list from pop.gmail.com: 

After considerable research I THINK I have traced the problem to the 
mailman account since fetchmail runs as mailman via cron. It appears 
that the crontab for mailman is gone and I cannot 'su - mailman' to run 
'crontab' on 'crontab.in'. Although isn't that supposed to happen 
automatically? Nor can I run fetchmail as mailman. I get the error:


This account is currently not available.

The passwd file entry is:

 mailman:x:41:41:GNU Mailing List Manager:/usr/lib/mailman:/sbin/nologin

I think it has always been that way but I'm not sure since 
'/sbin/nologin' means there is no shell and is why I am getting that 
error. I don't, at this point, see how it could have ever worked. In any 
case I need some help figuring out why mailman is getting that error.


FWIW, if I run 'passwd -S mailman', I get this:

mailman NP 2022-03-19 -1 -1 -1 -1 (Empty password.)

TIA



OpenPGP_signature
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: OpenPGP and S/MIME aware Mailman

[Dennis Putnam]

Hi Sam,

On 2/14/2021 11:26 AM, Sam Kuper wrote:

On Sun, Feb 14, 2021 at 10:58:01AM -0500, Dennis Putnam wrote:

I'm looking to decrypt incoming email from subscribers and encrypt
outgoing to each. The threat model is to not have any email into or
out of the mailing list to be intercepted/monitored.

The two sentences imply different requirements.

Even if you satisfy the requirements in the first sentence, any attacker
on the wire will be able to capture ("monitor") the emails; and the
headers will be in plain-text (including the Subject header, sender, and
recipients), even if the body and attachments are encrypted:
https://ssd.eff.org/en/module/why-metadata-matters

Also, if the attacker has compromised the CA, then they will potentially
be able to decrypt S/MIME messages (but not OpenPGP messages, if the
encryption and key generation were well-implemented[1]).

If you really want to satisfy the requirements in the second sentence,
then you might want to look at DIME (aka Darkmail), mixers, or
alternatives to email:

- https://en.wikipedia.org/wiki/Dark_Mail_Alliance

- https://en.wikipedia.org/wiki/Mix_networks

- https://en.wikipedia.org/wiki/Anonymous_remailers

- https://en.wikipedia.org/wiki/Tutanota

- https://en.wikipedia.org/wiki/ProtonMail

- https://en.wikipedia.org/wiki/Category:Internet_privacy_software

[1] At least, not unless affordable quantum computing is available to
the attacker.  If it is, then you would also need to use a
quantum-resistant cipher.  Unfortunately, doing that is still very
inconvenient to do using GnuPG or similar.

Thanks for the info. It is not the headers that I care about but rather 
the email content. I also would not care about S/MIME as all my 
subscribers will be GPG. I thought that was essentially the obsolete 
code did. I was considering taking that plug-in and modifying it to at 
least work with GPG and mailman 2.1.36.


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
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/

[Mailman-Users] Re: OpenPGP and S/MIME aware Mailman

[Dennis Putnam]

Hi Sam,

On 2/13/2021 3:18 PM, Sam Kuper wrote:

On Fri, Feb 12, 2021 at 10:11:20AM -0500, Dennis Putnam wrote:

If I need a secure mailman list, is there another alternative?

You may want to give some thought to, and to then specify in a follow-up
in this thread, what you mean by "secure" in this context.

For example, you might want security properties such as:

- Every message sent to the list can be authenticated by its recipients.

- Every message sent to the list is robustly encrypted to prevent its
   being readable by non-members.

- For the property/ies above to be immune to rogue CAs.

- Some combination of the above.

It may be helpful to ask yourself: what is your threat model?

Also, which key distribution mechanisms are available to you?  (For
instance: are the list members able to meet in person for key exchange?)

I'm looking to decrypt incoming email from subscribers and encrypt 
outgoing to each. The threat model is to not have any email into or out 
of the mailing list to be intercepted/monitored.


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
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/

[Mailman-Users] Re: OpenPGP and S/MIME aware Mailman

[Dennis Putnam]

Hi Christian,

On 2/12/2021 5:01 AM, Mailman-admin wrote:

Hello

Am 11.02.21 um 19:24 schrieb Dennis Putnam:

Does anyone have any experience with this that can provide a review
and/or advice? TIA.

http://non-gnu.uvt.nl/mailman-pgp-smime/


1) From the site itself:
"Beware! This code has not been touched since 2010-09. Therefore, it's
mainly obsolete.

DO NOT USE THIS CODE"

2) In my experience the main problem is not to decrypt and encrypt
emails, it is to get the public keys of your users and keep your private
keys valid.

For a public encrypted mailing list server you need an S/MIME
certificate *and* an PGP certificate for each list.
That is, because you usually can not restrict users to one method or the
other, and they are not compatible.
Especially S/MIME certificates expire after some time (yearly, or up to
5 years).
Your PGP certificates should expire too, for security reasons.
You need to keep them both up to date with overlapping new certificates.
And you need to distribute their public keys to your users.

Then you need to know the preferred encryption method of each user plus
their public keys.
Those will change too, therefore you need some mechanism to get the
current one and keep them in sync.
And make sure, to never use expired ones.


Kind regards,
Christian Mack

Thanks for that info. None of it sounds insurmountable other than the 
code itself. If I need a secure mailman list, is there another alternative?


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
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/

[Mailman-Users] OpenPGP and S/MIME aware Mailman

[Dennis Putnam]

Does anyone have any experience with this that can provide a review 
and/or advice? TIA.


http://non-gnu.uvt.nl/mailman-pgp-smime/

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
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/

[Mailman-Users] Re: From Format

[Dennis Putnam]

On 11/26/2020 12:22 PM, Mark Sapiro wrote:

On 11/26/20 9:11 AM, Dennis Putnam wrote:

That option (from_is_list) is already set to Munge from.


And what exactly does the From: header in mail from the RHEL list look like?


Hi Mark,

This is the actual header. Sorry but I guess I did not look at the 
header itself until now.


*From:* Rushtalk  on behalf of Dennis Putnam 
via Rushtalk 


This must be a Thunderbird issue as the From displayed is this:

Open discussion of current events *

I think this is an address book feature in TB. Again, sorry.


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
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/

[Mailman-Users] Re: From Format

[Dennis Putnam]

On 11/26/2020 12:03 PM, Mark Sapiro wrote:

On 11/26/20 7:31 AM, Dennis Putnam wrote:

I have mailman 2.1.34 running on both RHEL 7 and CentOS 7. When mail
arrives from CentOS 7 the from header reads:

{sender's name} via {list name} 

I don't know what I did to get that format. When mail arrives from RHEL
7 the from header has just some text. I'd like the RHEL 7 from header to
be the same but I cannot find how to do that. Can someone point me in
the right direction? TIA.


If you want this for all messages, set General Options -> from_is_list
to Munge From.

If you want it only for messages from domains that publish DMARC
policies, set General Options -> from_is_list to No and set Privacy
options... -> Sender filters -> dmarc_moderation_action to Munge From
and set dmarc_quarantine_moderation_action and
dmarc_none_moderation_action as desired.


Hi Mark,

Happy Thanksgiving.

That option (from_is_list) is already set to Munge from.

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
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/

[Mailman-Users] From Format

[Dennis Putnam]

I have mailman 2.1.34 running on both RHEL 7 and CentOS 7. When mail 
arrives from CentOS 7 the from header reads:


{sender's name} via {list name} 

I don't know what I did to get that format. When mail arrives from RHEL 
7 the from header has just some text. I'd like the RHEL 7 from header to 
be the same but I cannot find how to do that. Can someone point me in 
the right direction? TIA.


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
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/

[Mailman-Users] Re: Group Mismatch Error

[Dennis Putnam]

On 10/25/2020 11:48 AM, Mark Sapiro wrote:
> On 10/25/20 7:37 AM, Dennis Putnam wrote:
>
>> This is still a bit confusing. I need to state that 'fetchmail' is
>> involved here. I don't know how it interfaces but I have the
>> 'postmaster' parameter in 'fetchmailrc' set to 'mailman'. This was not
>> an issue with the previous version of mailman so I did not change it.
>> That I had to use 'nobody' when installing the new version was different
>> than the old version. I really don't know what else that would effect.
>
> Whatever the cause, the /usr/lib/mailman/mail/mailman wrapper is being
> invoked by group mailman so you need to start over with `configure` and
> `make install` with the --with-mail-gid=mailman option to configure and
> not with --with-mail-gid=nobody.
>
>
>> Yes, I ran 'check_perms' and it set it back.
>
> Good. Leave it that way.
>
>
>
>> This is where I'm a bit confused. That aliases file is owned by
>> mailman:mailman.
> Actually, it's the aliases.db file that counts and only the owner,
> unless the invoking user:group comes from fetchmail.
>
>> I don't know what configure file you are talking about.
> I'm talking about the configure command you use to configure Mailman.
>
>
>> If you are referring to rebuilding mailman and the
>> 'configure' command, that was where this started. I don't know if you
>> recall the emails from back when I was installing 2.1.34. If I set that
>> to 'mailman' rather than 'nobody', mailman will not start.
>
> Are you referring to the thread at
> <https://mail.python.org/archives/list/mailman-users@python.org/thread/NR7ACRKU552EJYGXNLUVUVB47HF2N3QD/>?
> If so, I don't have time at the moment to look in detail, but the issue
> seemed to be permissions and only changing the --with-mail-gid option
> from mailman to nobody would not have affected this at all.
>
Hi Mark,

Yes that is what I was referring to. I have this sorted out now but I
don't understand it completely. There are actually 2 servers involved
here. The one you helped with originally  (and on which that article was
based) was RHEL 7 and that is where I used 'nobody' to get it working.
This one is CentOS 7 which I thought was the same but obviously it is
slightly different. So I did indeed change it to 'mailman' and now it
works. Thanks again.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Group Mismatch Error

[Dennis Putnam]

On 10/24/2020 6:57 PM, Mark Sapiro wrote:
> On 10/24/20 3:10 PM, Dennis Putnam wrote:
>> I am getting this error:
>>
>>  (expanded from ):
>> Command died with status 2: "/usr/lib/mailman/mail/mailman post
>> cufsalumni". Command output: Group mismatch error.  Mailman expected the
>> mail wrapper script to be executed as group "nobody", but the system's 
>> mail
>> server executed the mail script as group "mailman".  Try tweaking the 
>> mail
>> server to run the script as group "nobody", or re-run configure,  
>> providing
>> the command line option `--with-mail-gid=mailman'.
>>
>> When I upgraded to this version of Mailman (2.1.34) I specified the 
>> configure options per the article (https://wiki.list.org/x/17892071) for 
>> RHEL. The group for '/usr/lib/mailman/mail/mailman' is indeed 'nobody'. What 
>> is this error trying to tell me. It is not clear what wrapper it is talking 
>> about since the group on the indicated script is correct.
Hi Mark,

Thanks for the reply. See embedded comments.

>
> That's not what the error is saying. See the FAQ at
> <https://wiki.list.org/x/4030645> for the detail.
>
> `Mailman expected the mail wrapper script to be executed as group
> "nobody"` is because you configured --with-mail-gid=nobody and that says
> you expect your MTA to invoke the /usr/lib/mailman/mail/mailman wrapper
> as group `nobody`, but in fact it invoked it as group mailman.
This is still a bit confusing. I need to state that 'fetchmail' is
involved here. I don't know how it interfaces but I have the
'postmaster' parameter in 'fetchmailrc' set to 'mailman'. This was not
an issue with the previous version of mailman so I did not change it.
That I had to use 'nobody' when installing the new version was different
than the old version. I really don't know what else that would effect.
>
> There are two things going on here. The actual group of the
> /usr/lib/mailman/mail/mailman wrapper should not be `nobody`. it should
> be SETGID and group `mailman`. check_perms should tell you that. All the
> wrappers /usr/lib/mailman/mail/mailman and /usr/lib/mailman/cgi-bin/*
> shoulkd be SETGID and group `mailman` so they actually execute as
> effective group `mailman`.
Yes, I ran 'check_perms' and it set it back.
>
> The second thing is I'm guessing your MTA is Postfix and you have
> Mailman/Postfix integration so your Mailman aliases are in
> /var/lib/mailman/data/aliases. If this is the case, Postfix executes the
> pipe for the alias with the user/group set to the user and primary group
> of the owner of the .db file in which it found the alias. See the
> `DELIVERY RIGHTS` section at <http://www.postfix.org/local.8.html>. This
> means if /var/lib/mailman/data/aliases.db is owned by `mailman`, Postfix
> will invoke the wrapper as group `mailman` and you should configure
> --with-mail-gid=mailman
This is where I'm a bit confused. That aliases file is owned by
mailman:mailman. I don't know what configure file you are talking about.
That is not a postfix parameter as far as I know in either main.cf or
master.cf. If you are referring to rebuilding mailman and the
'configure' command, that was where this started. I don't know if you
recall the emails from back when I was installing 2.1.34. If I set that
to 'mailman' rather than 'nobody', mailman will not start.
>
>
> --
> 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/



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Group Mismatch Error

[Dennis Putnam]

I am getting this error:

 (expanded from ):
Command died with status 2: "/usr/lib/mailman/mail/mailman post
cufsalumni". Command output: Group mismatch error.  Mailman expected the
mail wrapper script to be executed as group "nobody", but the system's mail
server executed the mail script as group "mailman".  Try tweaking the mail
server to run the script as group "nobody", or re-run configure,  providing
the command line option `--with-mail-gid=mailman'.

When I upgraded to this version of Mailman (2.1.34) I specified the configure 
options per the article (https://wiki.list.org/x/17892071) for RHEL. The group 
for '/usr/lib/mailman/mail/mailman' is indeed 'nobody'. What is this error 
trying to tell me. It is not clear what wrapper it is talking about since the 
group on the indicated script is correct.




signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Archive Issue

[Dennis Putnam]

On 9/17/2020 8:15 PM, Mark Sapiro wrote:
> On 9/17/20 4:49 PM, Dennis Putnam wrote:
>>  
>> I'll give that a try tomorrow. In the meantime I discovered something
>> that may or may not be relevant. Apparently the last saved archive was
>> in Feb 2020. That was when I did a 'yum update' to version 2.1.15 to
>> resolve the DMARC problem. I am betting that the RHEL version did
>> something to cause this problem. It is too much of a coincidence to
>> think otherwise.
>
> I really doubt that. Is my conjecture correct that you are working on a
> test system copied from a production system? If so, is the contents of
> /var/lib/mailman/archives/public on the production system symlinks or
> entire file hierarchies. I suspect the former and that the full file
> hierarchies in /var/lib/mailman/archives/public only exist in the backups.
>
Hi Mark,

You are correct. However, the test system was cloned with just a
hostname change. The original production system, from which the test
system was cloned, has the same problem.

I followed your instructions and it worked on the test system. What is
really odd, to me, is that now the archives after Feb 2020 are showing
up. Anyway, it looks like we are good to go. Thanks yet again.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Archive Issue

[Dennis Putnam]

On 9/17/2020 5:34 PM, Mark Sapiro wrote:
> On 9/17/20 11:50 AM, Dennis Putnam wrote:
>> Hit a bug page. Note this is the production server running 2.1.15 but
>> the test server running 2.1.34 got the same thing. This is the error log:
>>
>> Sep 17 12:37:13 2020 admin(24458):
>> 
>> admin(24458): [- Mailman Version: 2.1.15 -]
>> admin(24458): [- Traceback --]
>> admin(24458): Traceback (most recent call last):
>> admin(24458):   File "/usr/lib/mailman/scripts/driver", line 112, in
>> run_main
>> admin(24458): main()
>> admin(24458):   File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 227,
>> in main
>> admin(24458): mlist.Save()
>> admin(24458):   File "/usr/lib/mailman/Mailman/MailList.py", line 582,
>> in Save
>> admin(24458): self.CheckHTMLArchiveDir()
>> admin(24458):   File "/usr/lib/mailman/Mailman/Archiver/Archiver.py",
>> line 236, in CheckHTMLArchiveDir
>> admin(24458): breaklink(pubdir)
>> admin(24458):   File "/usr/lib/mailman/Mailman/Archiver/Archiver.py",
>> line 56, in breaklink
>> admin(24458): os.unlink(link)
>> admin(24458): OSError: [Errno 21] Is a directory:
> I thought that might happen, but I didn't confirm it. Oh well ...
>
> Do this:
>
> rm -rf /var/lib/mailman/archives/public/*
>
> Then Toggle the archive_private setting in the web admin UI for both lists.
>
> The background on what caused this in the first place is you apparently
> copied your production Mailman installation to a test environment, but
> whatever process you used to do the copy, copied the targets of the
> symlinks in /var/lib/mailman/archives/public/ instead of copying the
> symlinks as symlinks.
>
> This is what causes the issue with public archives no longer being
> updated. They actually are updated in
> /var/lib/mailman/archives/private/, but the pipermail URLs point to the
> old, static archive now copied to /var/lib/mailman/archives/public/.
>
> We've seen this multiple times in backup/restore scenarios and moving
> installations to another server.
>
> The bottom line is when backing up, always ensure you copy symlinks as
> symlinks and not their targets. For rsync, this is -l/--links (included
> as part of -a/--archive). For cp, it's -d or -P/--no-dereference or
> -a/--archive.
>
Hi Mark,
 
I'll give that a try tomorrow. In the meantime I discovered something
that may or may not be relevant. Apparently the last saved archive was
in Feb 2020. That was when I did a 'yum update' to version 2.1.15 to
resolve the DMARC problem. I am betting that the RHEL version did
something to cause this problem. It is too much of a coincidence to
think otherwise.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Archive Issue

[Dennis Putnam]

On 9/17/2020 2:57 PM, Dmitri Maziuk wrote:
> On 9/17/2020 1:50 PM, Dennis Putnam wrote:
>
>> admin(24458): OSError: [Errno 21] Is a directory:
>> '/var/lib/mailman/archives/public/rushtalk'
>
> ICBW but files in public/ should be symlinks to subdirs in private/
> i.e. public/rushtalk should be a symlink to private/rushtalk and not a
> directory.
>
> Dima
I know. That is what Mark is trying to help me fix. Public contains all
the archives rather than private so creating a symlink will destroy the
archives.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Archive Issue

[Dennis Putnam]

On 9/17/2020 1:06 PM, Mark Sapiro wrote:
> OK. First make a backup of /var/lib/mailman/archives/public/ just in
> case, although it appears that
> /var/lib/mailman/archives/private/rushtalk is more up to date. Then go
> to the web admin UI for both the mailman and rushtalk lists and set
> Archiving Options -> archive_private to private and then set it back to
> public.
>
> That should fix it.
>
> The story is all updates are done in /var/lib/mailman/archives/private,
> and /var/lib/mailman/archives/public should contain only symlinks to
> /var/lib/mailman/archives/private. Since
> /var/lib/mailman/archives/public contains archives rather than symlinks,
> those archives are static as of whatever created them and are never updated.
Hit a bug page. Note this is the production server running 2.1.15 but
the test server running 2.1.34 got the same thing. This is the error log:

Sep 17 12:37:13 2020 admin(24458):

admin(24458): [- Mailman Version: 2.1.15 -]
admin(24458): [- Traceback --]
admin(24458): Traceback (most recent call last):
admin(24458):   File "/usr/lib/mailman/scripts/driver", line 112, in
run_main
admin(24458): main()
admin(24458):   File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 227,
in main
admin(24458): mlist.Save()
admin(24458):   File "/usr/lib/mailman/Mailman/MailList.py", line 582,
in Save
admin(24458): self.CheckHTMLArchiveDir()
admin(24458):   File "/usr/lib/mailman/Mailman/Archiver/Archiver.py",
line 236, in CheckHTMLArchiveDir
admin(24458): breaklink(pubdir)
admin(24458):   File "/usr/lib/mailman/Mailman/Archiver/Archiver.py",
line 56, in breaklink
admin(24458): os.unlink(link)
admin(24458): OSError: [Errno 21] Is a directory:
'/var/lib/mailman/archives/public/rushtalk'
admin(24458): [- Python Information -]
admin(24458): sys.version =   2.7.5 (default, Jun 11 2019, 14:33:56)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]
admin(24458): sys.executable  =   /usr/bin/python
admin(24458): sys.prefix  =   /usr
admin(24458): sys.exec_prefix =   /usr
admin(24458): sys.path    =   ['/usr/lib/mailman/pythonlib',
'/usr/lib/mailman', '/usr/lib/mailman/scripts', '/usr/lib/mailman',
'/usr/lib64/python27.zip', '/usr/lib64/python2.7/',
'/usr/lib64/python2.7/plat-linux2', '/usr/lib64/python2.7/lib-tk',
'/usr/lib64/python2.7/lib-old', '/usr/lib64/python2.7/lib-dynload',
'/usr/lib/python2.7/site-packages']
admin(24458): sys.platform    =   linux2
admin(24458): [- Environment Variables -]
admin(24458):   HTTP_COOKIE:
rushtalk+admin=28020069a4ac635f73280031666237653866353739613765303565326633653266646330663738613838333931383633386635
admin(24458):   CONTEXT_DOCUMENT_ROOT: /usr/lib/mailman/cgi-bin/
admin(24458):   SERVER_SOFTWARE: Apache/2.4.6 (Red Hat Enterprise Linux)
OpenSSL/1.0.2k-fips
admin(24458):   CONTEXT_PREFIX: /mailman/
admin(24458):   SERVER_SIGNATURE:
admin(24458):   REQUEST_METHOD: GET
admin(24458):   PATH_INFO: /rushtalk/archive
admin(24458):   SERVER_PROTOCOL: HTTP/1.1
admin(24458):   QUERY_STRING:
admin(24458):   HTTP_USER_AGENT: Mozilla/5.0 (Windows NT 6.1; Win64;
x64; rv:80.0) Gecko/20100101 Firefox/80.0
admin(24458):   HTTP_CONNECTION: keep-alive
admin(24458):   HTTP_REFERER: http://galene.csd.net/mailman/admin/rushtalk
admin(24458):   SERVER_NAME: galene.csd.net
admin(24458):   REMOTE_ADDR: 162.230.29.192
admin(24458):   PATH_TRANSLATED: /var/www/html/rushtalk/archive
admin(24458):   SERVER_PORT: 80
admin(24458):   SERVER_ADDR: 204.181.152.21
admin(24458):   DOCUMENT_ROOT: /var/www/html
admin(24458):   PYTHONPATH: /usr/lib/mailman
admin(24458):   SCRIPT_FILENAME: /usr/lib/mailman/cgi-bin/admin
admin(24458):   SERVER_ADMIN: root@localhost
admin(24458):   HTTP_DNT: 1
admin(24458):   HTTP_HOST: galene.csd.net
admin(24458):   SCRIPT_NAME: /mailman/admin
admin(24458):   HTTP_UPGRADE_INSECURE_REQUESTS: 1
admin(24458):   REQUEST_URI: /mailman/admin/rushtalk/archive
admin(24458):   HTTP_ACCEPT:
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
admin(24458):   GATEWAY_INTERFACE: CGI/1.1
admin(24458):   REMOTE_PORT: 61998
admin(24458):   HTTP_ACCEPT_LANGUAGE: en-US,en;q=0.5
admin(24458):   REQUEST_SCHEME: http
admin(24458):   HTTP_ACCEPT_ENCODING: gzip, deflate
admin(24458):   UNIQUE_ID: X2Os2dJmdT9yDBIgbsvt@gk
>
> Note that if you go to the private archive URL at
> http://example.com/mailman/private/rushtalk or wherever it it, you
> should see your recent messages.
>
> I'll be out for a few hours, so if you need more, it'll have to wait.
>
I can wait. Thanks.



signature.asc
Description: OpenPGP digital signature
--
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: 

[Mailman-Users] Re: Archive Issue

[Dennis Putnam]

On 9/17/2020 12:29 PM, Mark Sapiro wrote:
> On 9/17/20 9:06 AM, Dennis Putnam wrote:
>
> Before doing anything, show me the results of
> ls -la /var/lib/mailman/archives/public/
# ls -la /var/lib/mailman/archives/public/
total 44
drwxrwsr-x.   4 root mailman    37 Jul 31  2019 .
drwxrwsr-x.   4 root mailman    35 Jul 31  2019 ..
drwxrwsr-x.   2 root mailman    24 Feb 16  2020 mailman
drwxrwsr-x. 302 root mailman 28672 Feb 16  2020 rushtalk
>
> and
>
> ls -la /var/lib/mailman/archives/private/
# ls -la /var/lib/mailman/archives/private/
total 44
drwxrws---.   6 apache  mailman    78 Jul 31  2019 .
drwxrwsr-x.   4 root    mailman    35 Jul 31  2019 ..
drwxrwsr-x.   2 mailman mailman    24 Feb 16  2020 mailman
drwxrwsr-x.   2 mailman mailman 6 Feb 16  2020 mailman.mbox
drwxrwsr-x. 309 mailman mailman 28672 Sep  1 09:38 rushtalk
drwxrwsr-x.   2 mailman mailman    27 Feb 16  2020 rushtalk.mbox
>
> First you need to do something like
>
> rsync -a /var/lib/mailman/archives/public/
> /var/lib/mailman/archives/private/
>
> to copy the entire structure from /var/lib/mailman/archives/public/ to
> /var/lib/mailman/archives/private/.
>
> Alternatively, assuming your
> /var/lib/mailman/archives/private/.mbox/.mbox files
> are good and contain all the messages except recent tests, you could
> just do something like
> ```
> for list in `bin/list_lists --bare`; do
> bin/arch --wipe $list
> done
>
> to rebuild the archives from the .mbox files, but if any of the .mbox
> files go back before Mailman 2.1, they should first be checked with
> bin/cleanarch for unescaped 'From ' lines in message bodies and fixed first.
>
> This part I don't understand. What does
>
> ls -la /var/lib/mailman/archives/private/*.mbox
>
> show?
# ls -la /var/lib/mailman/archives/private/*.mbox
/var/lib/mailman/archives/private/mailman.mbox:
total 0
drwxrwsr-x. 2 mailman mailman  6 Feb 16  2020 .
drwxrws---. 6 apache  mailman 78 Jul 31  2019 ..

/var/lib/mailman/archives/private/rushtalk.mbox:
total 1093228
drwxrwsr-x. 2 mailman mailman 27 Feb 16  2020 .
drwxrws---. 6 apache  mailman 78 Jul 31  2019 ..
-rw-rw-r--. 1 mailman mailman 1119459801 Sep 17 09:38 rushtalk.mbox

That is weird. That mbox seems to be updating but nothing shows up on
the archives web page after Feb 2020.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Archive Issue

[Dennis Putnam]

On 9/17/2020 11:40 AM, Mark Sapiro wrote:
>
> What makes you think messages aren't being archived?
Because when I look at it via the web, the emails I sent as a test are
not there. There is no September 2020 link and the date on the mbox file
is old (Feb 2020).
>
> Is your archive public? If so, is
> /var/lib/mailman/archives/public/ a symlink to
> /var/lib/mailman/archives/private/, or is it an entire archive
> structure. The latter can occur in some backup-restore scenarios and
> results in a public (pipermail URL) archive that is never updated
> because only/var/lib/mailman/archives/private/ is actually
> updated.
There are no sym links. Private looks like just place holders as there
is no data there nor any archives. It looks like everything is in
public. The ownership is root:mailman and the group has R/O permissions.
Only root has write. I'm assuming that is correct, otherwise check_perms
would fix it.
>
> /var/lib/mailman/archives/public/ must be a symlink to
> /var/lib/mailman/archives/private/. If that's the issue, you
> can fix it manually, or I think just setting Archiving Options ->
> archive_private to private and then back to public in the web admin UI
> will fix it.
Looks like it is backwards. This must be the problem but how it got this
way I have no clue. Since the real data is in public, doing either would
mess it up, right?
>
> Eailier I asked "Is
> /var/lib/mailman/archives/private/.mbox/.mbox being
> updated?" and you answered "No. Those files are owned by
> mailman:mailman." which doesn't answer the question.
The no applied to your question. I included the other information in
case it you asked.
>
> Are new messages being appended to the
> /var/lib/mailman/archives/private/.mbox/.mbox files?
No




signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Archive Issue

[Dennis Putnam]

On 9/17/2020 10:43 AM, Mark Sapiro wrote:
>
> Is ArchRunner running? Are there entries in /var/spool/mailman/archive/?
Looks like it:

● mailman.service - GNU Mailing List Manager
   Loaded: loaded (/usr/lib/systemd/system/mailman.service; disabled;
vendor preset: disabled)
   Active: active (running) since Thu 2020-09-17 07:39:59 MDT; 1h 10min ago
  Process: 28178 ExecStart=/usr/lib/mailman/bin/mailmanctl -s start
(code=exited, status=0/SUCCESS)
  Process: 28175 ExecStartPre=/bin/chmod 660 /var/log/mailman/error
(code=exited, status=0/SUCCESS)
  Process: 28172 ExecStartPre=/bin/chown mailman:mailman
/var/log/mailman/error (code=exited, status=0/SUCCESS)
  Process: 28169 ExecStartPre=/bin/touch /var/log/mailman/error
(code=exited, status=0/SUCCESS)
  Process: 28165 ExecStartPre=/usr/bin/install -m644 -o root -g root
/usr/lib/mailman/cron/crontab.in /etc/cron.d/mailman (code=exited,
status=0/SUCCESS)
  Process: 28162 ExecStartPre=/usr/lib/mailman/bin/mailman-update-cfg
(code=exited, status=0/SUCCESS)
 Main PID: 28180 (mailmanctl)
    Tasks: 9
   CGroup: /system.slice/mailman.service
   ├─28180 /bin/python /usr/lib/mailman/bin/mailmanctl -s start
   ├─28189 /bin/python /usr/lib/mailman/bin/qrunner
--runner=ArchRunner:0:1 -s
   ├─28190 /bin/python /usr/lib/mailman/bin/qrunner
--runner=BounceRunner:0:1 -s
   ├─28191 /bin/python /usr/lib/mailman/bin/qrunner
--runner=CommandRunner:0:1 -s
   ├─28192 /bin/python /usr/lib/mailman/bin/qrunner
--runner=IncomingRunner:0:1 -s
   ├─28193 /bin/python /usr/lib/mailman/bin/qrunner
--runner=NewsRunner:0:1 -s
   ├─28194 /bin/python /usr/lib/mailman/bin/qrunner
--runner=OutgoingRunner:0:1 -s
   ├─28195 /bin/python /usr/lib/mailman/bin/qrunner
--runner=VirginRunner:0:1 -s
   └─28196 /bin/python /usr/lib/mailman/bin/qrunner
--runner=RetryRunner:0:1 -s

Sep 17 07:39:59 harmonia.csd.net systemd[1]: Starting GNU Mailing List
Manager...
Sep 17 07:39:59 harmonia.csd.net mailmanctl[28178]: Starting Mailman's
master qrunner.
Sep 17 07:39:59 harmonia.csd.net systemd[1]: Started GNU Mailing List
Manager.

>
> This looks OK. The ownership is irrelevant as long as the group is
> 'mailman' and /var/log/mailman/ itself is group mailman and SETGID.
> (Those owned by apache were created by a web action.)
>
> I'm assuming that the 'error' log has nothing relevant, but it is being
> written so no archiving exceptions have been logged which makes me think
> ArchRunner isn't running. What's in the 'qrunner' log?
>
Error doesn't have anything recent. As for the qrunner log, I don't see
anything interesting (just my restart of MM):

Sep 17 07:39:41 2020 (21351) VirginRunner qrunner caught SIGTERM.  Stopping.
Sep 17 07:39:41 2020 (21351) VirginRunner qrunner exiting.
Sep 17 07:39:41 2020 (21350) OutgoingRunner qrunner caught SIGTERM. 
Stopping.
Sep 17 07:39:41 2020 (21349) NewsRunner qrunner caught SIGTERM.  Stopping.
Sep 17 07:39:41 2020 (21349) NewsRunner qrunner exiting.
Sep 17 07:39:41 2020 (21350) OutgoingRunner qrunner exiting.
Sep 17 07:39:41 2020 (21346) BounceRunner qrunner caught SIGTERM.  Stopping.
Sep 17 07:39:41 2020 (21346) BounceRunner qrunner exiting.
Sep 17 07:39:41 2020 (21348) IncomingRunner qrunner caught SIGTERM. 
Stopping.
Sep 17 07:39:41 2020 (21348) IncomingRunner qrunner exiting.
Sep 17 07:39:41 2020 (21345) ArchRunner qrunner caught SIGTERM.  Stopping.
Sep 17 07:39:41 2020 (21345) ArchRunner qrunner exiting.
Sep 17 07:39:41 2020 (21336) Master watcher caught SIGTERM.  Exiting.
Sep 17 07:39:41 2020 (21347) CommandRunner qrunner caught SIGTERM. 
Stopping.
Sep 17 07:39:41 2020 (21347) CommandRunner qrunner exiting.
Sep 17 07:39:41 2020 (21352) RetryRunner qrunner caught SIGTERM.  Stopping.
Sep 17 07:39:41 2020 (21352) RetryRunner qrunner exiting.
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21346, sig: None, sts: 15, class: BounceRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21351, sig: None, sts: 15, class: VirginRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master watcher caught SIGTERM.  Exiting.
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21349, sig: 15, sts: None, class: NewsRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21350, sig: 15, sts: None, class: OutgoingRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21352, sig: 15, sts: None, class: RetryRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21347, sig: 15, sts: None, class: CommandRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21345, sig: 15, sts: None, class: ArchRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21348, sig: 15, sts: None, class: IncomingRunner, slice: 1/1)
Sep 17 07:40:00 2020 (28189) 

[Mailman-Users] Re: Archive Issue

[Dennis Putnam]

On 9/17/2020 9:59 AM, Mark Sapiro wrote:
> On 9/17/20 6:49 AM, Dennis Putnam wrote:
>> For some reason, messages are not being archived. I see no error in the
>> logs and check_perms says no problems found. Any suggestions on how to
>> get archive working? Thanks.
>
> Is /var/lib/mailman/archives/private/.mbox/.mbox
> being updated?
No. Those files are owned by mailman:mailman.
>
> Are any logs being written? What are mode and user:group on
> /var/log/mailman/?
Yes, some logs are being written but most of the files are old and
empty. The files for today are the test emails I sent. The ownership of
log files varies:

-rw-rw-r--. 1 mailman mailman 0 Sep 13 19:13 bounce
-rw-rw-r--. 1 mailman mailman 0 Aug 16 03:43 bounce-20200823
-rw-rw-r--. 1 mailman mailman 0 Aug 23 03:40 bounce-20200830
-rw-rw-r--. 1 mailman mailman 0 Aug 30 03:13 bounce-20200906
-rw-rw-r--. 1 mailman mailman 0 Sep  6 03:33 bounce-20200913
-rw-rw. 1 mailman mailman   275 Sep 17 07:39 error
-rw-rw. 1 mailman mailman 0 Aug 16 03:43 error-20200823
-rw-rw. 1 mailman mailman 0 Aug 23 03:40 error-20200830
-rw-rw. 1 mailman mailman   692 Sep  5 07:15 error-20200906
-rw-rw. 1 mailman mailman 0 Sep  6 03:33 error-20200913
-rw-rw-r--. 1 apache  mailman   639 Sep  5 07:15 mischief
-rw-rw-r--. 1 mailman mailman   409 Sep 17 07:50 post
-rw-rw-r--. 1 mailman mailman 10939 Aug 22 23:23 post-20200823
-rw-rw-r--. 1 mailman mailman  2546 Aug 29 20:39 post-20200830
-rw-rw-r--. 1 mailman mailman  6108 Sep  5 10:29 post-20200906
-rw-rw-r--. 1 mailman mailman  5840 Sep 12 18:00 post-20200913
-rw-rw-r--. 1 mailman mailman  6048 Sep 17 07:40 qrunner
-rw-rw-r--. 1 mailman mailman   738 Aug 16 03:43 qrunner-20200823
-rw-rw-r--. 1 mailman mailman   738 Aug 23 03:40 qrunner-20200830
-rw-rw-r--. 1 mailman mailman   738 Aug 30 03:13 qrunner-20200906
-rw-rw-r--. 1 mailman mailman   738 Sep  6 03:33 qrunner-20200913
-rw-rw-r--. 1 mailman mailman   284 Sep 17 07:50 smtp
-rw-rw-r--. 1 mailman mailman  8875 Aug 22 23:23 smtp-20200823
-rw-rw-r--. 1 mailman mailman  1804 Aug 29 20:39 smtp-20200830
-rw-rw-r--. 1 mailman mailman  4854 Sep  5 10:29 smtp-20200906
-rw-rw-r--. 1 mailman mailman  4715 Sep 12 18:00 smtp-20200913
-rw-rw-r--. 1 mailman mailman 0 Sep 13 19:13 smtp-failure
-rw-rw-r--. 1 mailman mailman 0 Aug 16 03:43 smtp-failure-20200823
-rw-rw-r--. 1 mailman mailman 0 Aug 23 03:40 smtp-failure-20200830
-rw-rw-r--. 1 mailman mailman 0 Aug 30 03:13 smtp-failure-20200906
-rw-rw-r--. 1 mailman mailman 0 Sep  6 03:33 smtp-failure-20200913
-rw-rw-r--. 1 apache  mailman 0 Sep 13 19:13 subscribe
-rw-rw-r--. 1 apache  mailman 0 Aug 16 03:43 subscribe-20200823
-rw-rw-r--. 1 apache  mailman 0 Aug 23 03:40 subscribe-20200830
-rw-rw-r--. 1 apache  mailman 0 Aug 30 03:13 subscribe-20200906
-rw-rw-r--. 1 apache  mailman 0 Sep  6 03:33 subscribe-20200913
-rw-rw-r--. 1 mailman mailman 0 Sep 13 19:13 vette
-rw-rw-r--. 1 mailman mailman 0 Aug 16 03:43 vette-20200823
-rw-rw-r--. 1 mailman mailman 0 Aug 23 03:40 vette-20200830
-rw-rw-r--. 1 mailman mailman 0 Aug 30 03:13 vette-20200906
-rw-rw-r--. 1 mailman mailman 0 Sep  6 03:33 vette-20200913





signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

[Dennis Putnam]

On 9/17/2020 9:46 AM, Mark Sapiro wrote:
> On 9/17/20 1:47 AM, Dennis Putnam wrote:
>> That worked perfectly. Thanks. This is the configure command I used:
>>
>> *./configure --prefix=/usr/lib/mailman --with-username=mailman
>> --with-groupname=mailman --with-cgi-gid=apache --with-mail-gid=mailman
>> --with-pid-dir=/var/run/mailman/ --with-config-dir=/etc/mailman/
>> --with-lock-dir=/var/lock/mailman/ --with-queue-dir=/var/spool/mailman/
>> --with-log-dir=/var/log/mailman/ --with-var-prefix=/var/lib/mailman/*
>>
>> Also, I don't know if it was necessary but I did run autoconf after. I
>> don't know if it actually did anything.
>
> Thanks for the feedback. Running autoconf is not needed with the patch
> in the FAQ article, as that patches configure as well as configure.in,
> but it doesn't hurt as it won't actually change the patched configure.
>
> I've made an additional update to <https://wiki.list.org/x/17892071> to
> include the other configure options you used.
>
>
Hi Mark,

Looks good to me. Thanks.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Archive Issue

[Dennis Putnam]

For some reason, messages are not being archived. I see no error in the
logs and check_perms says no problems found. Any suggestions on how to
get archive working? Thanks.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

[Dennis Putnam]

On 9/17/2020 4:47 AM, Dennis Putnam wrote:
> On 9/16/2020 4:33 PM, Mark Sapiro wrote:
>> I have created a work in progress FAQ at
>> <https://wiki.list.org/x/17892071>. This contains an updated patch that
>> applies cleanly to the head of the lp:mailman branch and also patches
>> configure so the `autoconf` step is not required. It also contains a
>> brief summary of steps to upgrade.
>>
>> If you try it, I'd appreciate feedback.
> Hi Mark,
>
> That worked perfectly. Thanks. This is the configure command I used:
>
> *./configure --prefix=/usr/lib/mailman --with-username=mailman
> --with-groupname=mailman --with-cgi-gid=apache --with-mail-gid=mailman
> --with-pid-dir=/var/run/mailman/ --with-config-dir=/etc/mailman/
> --with-lock-dir=/var/lock/mailman/
> --with-queue-dir=/var/spool/mailman/ --with-log-dir=/var/log/mailman/
> --with-var-prefix=/var/lib/mailman/*
>
> Also, I don't know if it was necessary but I did run autoconf after. I
> don't know if it actually did anything.
Hi Mark,

I didn't have it quite right. I got this postfix error:

Sep 17 07:30:46 harmonia postfix/local[22654]: A6FE22B14:
to=, relay=local, delay=0.15,
delays=0.09/0.04/0/0.02, dsn=5.3.0, status=bounced (Command died with
status 2: "/usr/lib/mailman/mail/mailman post rushtalk". Command output:
Group mismatch error.  Mailman expected the mail wrapper script to be
executed as group "mailman", but the system's mail server executed the
mail script as group "nobody".  Try tweaking the mail server to run the
script as group "mailman", or re-run configure,  providing the command
line option `--with-mail-gid=nobody'. )

I assumed, for lack of anything better, '*--with-mail-gid=mailman'*. 
Obviously I should have used '*--with-mail-gid=nobody*'. The
documentation was lacking on what that parameter should be. I suggest
you add this to your document.


signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

[Dennis Putnam]

On 9/16/2020 4:33 PM, Mark Sapiro wrote:
> I have created a work in progress FAQ at
> . This contains an updated patch that
> applies cleanly to the head of the lp:mailman branch and also patches
> configure so the `autoconf` step is not required. It also contains a
> brief summary of steps to upgrade.
>
> If you try it, I'd appreciate feedback.
Hi Mark,

That worked perfectly. Thanks. This is the configure command I used:

*./configure --prefix=/usr/lib/mailman --with-username=mailman
--with-groupname=mailman --with-cgi-gid=apache --with-mail-gid=mailman
--with-pid-dir=/var/run/mailman/ --with-config-dir=/etc/mailman/
--with-lock-dir=/var/lock/mailman/ --with-queue-dir=/var/spool/mailman/
--with-log-dir=/var/log/mailman/ --with-var-prefix=/var/lib/mailman/*

Also, I don't know if it was necessary but I did run autoconf after. I
don't know if it actually did anything.


signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

[Dennis Putnam]

Hi Mark,

On to the next layer of the onion. After the install I get this:

#./check_perms -f
WARNING: directory does not exist: @PID_DIR@
WARNING: directory does not exist: @CONFIG_DIR@
WARNING: directory does not exist: @LOCK_DIR@
WARNING: directory does not exist: @QUEUE_DIR@
WARNING: directory does not exist: @LOG_DIR@
Warning: Private archive directory is other-executable (o+x).
 This could allow other users on your system to read private
archives.
 If you're on a shared multiuser system, you should consult the
 installation manual on how to fix this.
No problems found

Although it says no problems found I am concerned about the warnings
(except the last). I seem to be back, more or less, to where I started.
Interestingly the 'execstartpre' uses the hard coded path and the
startup script uses the symbolic path which is one of the warnings.

● mailman.service - GNU Mailing List Manager
   Loaded: loaded (/usr/lib/systemd/system/mailman.service; disabled;
vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2020-09-16 11:55:31 MDT;
3min 49s ago
  Process: 3303 ExecStart=/usr/lib/mailman/bin/mailmanctl -s start
(code=exited, status=1/FAILURE)
  Process: 3300 ExecStartPre=/bin/chmod 660 */var/log/mailman/error*
(code=exited, status=0/SUCCESS)
  Process: 3297 ExecStartPre=/bin/chown mailman:mailman
/var/log/mailman/error (code=exited, status=0/SUCCESS)
  Process: 3294 ExecStartPre=/bin/touch /var/log/mailman/error
(code=exited, status=0/SUCCESS)
  Process: 3289 ExecStartPre=/usr/bin/install -m644 -o root -g root
/usr/lib/mailman/cron/crontab.in /etc/cron.d/mailman (code=exited,
status=0/SUCCESS)
  Process: 3286 ExecStartPre=/usr/lib/mailman/bin/mailman-update-cfg
(code=exited, status=0/SUCCESS)

Sep 16 11:55:31 harmonia.csd.net mailmanctl[3303]: File
"/usr/lib64/python2.7/codecs.py", line 881, in open
Sep 16 11:55:31 harmonia.csd.net mailmanctl[3303]: file =
__builtin__.open(filename, mode, buffering)
Sep 16 11:55:31 harmonia.csd.net mailmanctl[3303]: IOError: [Errno 13]
Permission denied: '*@LOG_DIR@/error*'
Sep 16 11:55:31 harmonia.csd.net mailmanctl[3303]: Original log message:
Sep 16 11:55:31 harmonia.csd.net mailmanctl[3303]: [Errno 13] Permission
denied: '@LOG_DIR@/error'
Sep 16 11:55:31 harmonia.csd.net mailmanctl[3303]: Sep 16 11:55:31 2020
(3303) Site list is missing: mailman
Sep 16 11:55:31 harmonia.csd.net systemd[1]: mailman.service: control
process exited, code=exited status=1
Sep 16 11:55:31 harmonia.csd.net systemd[1]: Failed to start GNU Mailing
List Manager.
Sep 16 11:55:31 harmonia.csd.net systemd[1]: Unit mailman.service
entered failed state.
Sep 16 11:55:31 harmonia.csd.net systemd[1]: mailman.service failed.

I am guessing I can't just overwrite the 2.1.15 version with this
version using 'make install'. The upgrade is more complicated, right? I
have to uninstall the old version, install the new version then migrate
the data into the new version.




signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

[Dennis Putnam]

On 9/15/2020 3:06 PM, Mark Sapiro wrote:
>
> If you are in the directory that you unpacked the Mailman 2.1.34 tarball
> into, do
>
> patch -p1 < /path/to/mailman-FHS.patch
>
>
Hi Mark,

I guess there is still something wrong:

# patch -p1 <../mailman-FHS.patch
patching file bin/check_perms
Hunk #1 succeeded at 183 with fuzz 1 (offset 19 lines).
patching file configure.in
Hunk #1 succeeded at 321 (offset 141 lines).
Hunk #2 succeeded at 348 with fuzz 2 (offset 141 lines).
Hunk #3 succeeded at 821 (offset 147 lines).
patching file Mailman/Defaults.py.in
Hunk #1 succeeded at 1751 (offset 553 lines).
Hunk #2 succeeded at 1766 (offset 553 lines).
Hunk #3 succeeded at 1780 (offset 553 lines).
patching file Mailman/MTA/Postfix.py
Hunk #1 FAILED at 32.
1 out of 1 hunk FAILED -- saving rejects to file Mailman/MTA/Postfix.py.rej
patching file Makefile.in
patching file misc/mailman.in
Hunk #1 FAILED at 24.
1 out of 1 hunk FAILED -- saving rejects to file misc/mailman.in.rej
patching file misc/Makefile.in
Hunk #1 succeeded at 27 (offset 1 line).
Hunk #2 succeeded at 94 with fuzz 1 (offset 4 lines).

# cat Postfix.py.rej
--- Mailman/MTA/Postfix.py    2003-03-31 16:49:43.0 -0500
+++ Mailman/MTA/Postfix.py    2004-10-08 16:02:20.0 -0400
@@ -32,8 +32,8 @@
 from Mailman.Logging.Syslog import syslog
 
 LOCKFILE = os.path.join(mm_cfg.LOCK_DIR, 'creator')
-ALIASFILE = os.path.join(mm_cfg.DATA_DIR, 'aliases')
-VIRTFILE = os.path.join(mm_cfg.DATA_DIR, 'virtual-mailman')
+ALIASFILE = os.path.join(mm_cfg.CONFIG_DIR, 'aliases')
+VIRTFILE = os.path.join(mm_cfg.CONFIG_DIR, 'virtual-mailman')
 
 try:
 True, False





signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

[Dennis Putnam]

On 9/15/2020 1:13 PM, Mark Sapiro wrote:
> On 9/15/20 9:02 AM, Dennis Putnam wrote:
>> Thanks again. I thought if I was already at 2.1.15 the patch was not
>> necessary. However, reading the article it is not clear to me when/where
>> to run that patch. Does it get run after the install or before running
>> ./config?
>
> It needs to be applied before running configure as it patches configure.
>
>
Hi Mark,

I guess I don't know how to use patch. Better documentation would be
helpful.

# patch --verbose -i ../mailman-FHS.patch

Hmm...  Looks like a unified diff to me...
can't find file to patch at input line 5
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--
|Only in mailman-2.1.5.FHS: autom4te.cache
|diff -r -u mailman-2.1.5.orig/bin/check_perms
mailman-2.1.5.FHS/bin/check_perms
|--- mailman-2.1.5.orig/bin/check_perms    2003-03-31 15:07:55.0
-0500
|+++ mailman-2.1.5.FHS/bin/check_perms    2004-10-08 16:05:09.0
-0400
--
File to patch:

Before I screw it up, is it wanting to patch the file listed in the diff
command (i.e. check_perms)? I also assume I need to use -u.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

[Dennis Putnam]

On 9/15/2020 10:26 AM, Mark Sapiro wrote:
> On 9/15/20 6:56 AM, Dennis Putnam wrote:
>> Thanks for the reply. Your article is not much help as I am already at
>> 2.1.15 so the paths are already correct. I turned off SELinux to see if
>> that helps but there is another issue after the reboot. I'll let you
>> know when I get the machine back online. That may fix the permission
>> problem but probably not the missing site list.
>
> The point is that without applying the patch attached to the post linked
> from the article, running configure and make install as you did will not
> install things according to the RHEL FHS layout.
>
> At a minimum, you need to configure with the options
> `--prefix=/usr/lib/mailman --with-var-prefix=/var/lib/mailman`, but
> there are other things changed in configure itself by the patch to get
> things installed in the proper places.
>
>
Hi Mark,

Thanks again. I thought if I was already at 2.1.15 the patch was not
necessary. However, reading the article it is not clear to me when/where
to run that patch. Does it get run after the install or before running
./config?



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

[Dennis Putnam]

On 9/14/2020 9:11 PM, Mark Sapiro wrote:
> On 9/14/20 9:59 AM, Dennis Putnam wrote:
>> On 8/29/2020 2:11 PM, Dennis Putnam wrote:
>>> Since Centos 7 is way behind on mailman rpm (2.1.15 is the only
>>> available rpm) and mailman is currently at 2.1.34 I need to do a manual
>>> update. While I know how to install software, I am concerned that just
>>> doing a manual install from the tarball will mess up current settings,
>>> lists and members. Does anyone have experience doing this that can
>>> advise about pitfalls or has a cookbook document to do a safe update? TIA.
>>>
>> After additional attempts and some research I am stuck upgrading mailman
>> 2.1.5 to 2.1.34 and get the same results I had reported here earlier. I
>> followed these instructions:
>>
>> https://wiki.list.org/DOC/How%20do%20I%20upgrade%20a%20Debian/Ubuntu%20Mailman%20package%20from%20source.
>
> This FAQ (note period is part of URL) is not relevant.
>
> The relevant FAQ is https://wiki.list.org/x/8486953> which references
> the post at
> <https://mail.python.org/pipermail/mailman-developers/2004-October/017343.html>
> (also now at
> <https://mail.python.org/archives/list/mailman-develop...@python.org/message/TNSLSSV7KSJGXHZE5RWVCOPHZR5SMAVG/>
> which contains a patch which enables Mailman to install in the
> RHEL/Centos way.
>
> (more below)
>
>> And made, what I thought were, the appropriate changes to the configure
>> parameters:
>>
>> ./configure --prefix=/usr/lib/mailman --with-username=mailman
>> --with-groupname=mailman --with-cgi-gid=apache --with-mail-gid=mailman
>>
>> If anyone sees anything wrong please point it out. Anyway, after doing
>> the make and install, I start mailman and get this status:
>>
>> ● mailman.service - GNU Mailing List Manager
>>    Loaded: loaded (/usr/lib/systemd/system/mailman.service; disabled;
>> vendor preset: disabled)
>>    Active: failed (Result: exit-code) since Mon 2020-09-14 10:31:12 MDT;
>> 20min ago
>>   Process: 20030 ExecStart=/usr/lib/mailman/bin/mailmanctl -s start
>> (code=exited, status=1/FAILURE)
>>   Process: 20028 ExecStartPre=/bin/chmod 660 /var/log/mailman/error
>> (code=exited, status=0/SUCCESS)
>>   Process: 20024 ExecStartPre=/bin/chown mailman:mailman
>> /var/log/mailman/error (code=exited, status=0/SUCCESS)
>>   Process: 20021 ExecStartPre=/bin/touch /var/log/mailman/error
>> (code=exited, status=0/SUCCESS)
>>   Process: 20018 ExecStartPre=/usr/bin/install -m644 -o root -g root
>> /usr/lib/mailman/cron/crontab.in /etc/cron.d/mailman (code=exited,
>> status=0/SUCCESS)
>>   Process: 20014 ExecStartPre=/usr/lib/mailman/bin/mailman-update-cfg
>> (code=exited, status=0/SUCCESS)
>>
>> Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: File
>> "/usr/lib64/python2.7/codecs.py", line 881, in open
>> Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: file =
>> __builtin__.open(filename, mode, buffering)
>> Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: IOError: [Errno 13]
>> Permission denied: '/usr/lib/mailman/logs/error'
>> Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: Original log message:
>> Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: [Errno 13]
>> Permission denied: '/usr/lib/mailman/logs/error'
>> Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: Sep 14 10:31:12 2020
>> (20030) Site list is missing: mailman
>> Sep 14 10:31:12 harmonia.csd.net systemd[1]: mailman.service: control
>> process exited, code=exited status=1
>> Sep 14 10:31:12 harmonia.csd.net systemd[1]: Failed to start GNU Mailing
>> List Manager.
>> Sep 14 10:31:12 harmonia.csd.net systemd[1]: Unit mailman.service
>> entered failed state.
>> Sep 14 10:31:12 harmonia.csd.net systemd[1]: mailman.service failed.
>>
>> I don't understand the permissions denied error.
>
> I suspect this is a SELinux issue. That's what the RHEL FHS patch is
> for. Is SELinux enabled? If yoiu disable it does Mailman start?
>
>
>
Hi Mark,

Thanks for the reply. Your article is not much help as I am already at
2.1.15 so the paths are already correct. I turned off SELinux to see if
that helps but there is another issue after the reboot. I'll let you
know when I get the machine back online. That may fix the permission
problem but probably not the missing site list.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

[Dennis Putnam]

On 8/29/2020 2:11 PM, Dennis Putnam wrote:
> Since Centos 7 is way behind on mailman rpm (2.1.15 is the only
> available rpm) and mailman is currently at 2.1.34 I need to do a manual
> update. While I know how to install software, I am concerned that just
> doing a manual install from the tarball will mess up current settings,
> lists and members. Does anyone have experience doing this that can
> advise about pitfalls or has a cookbook document to do a safe update? TIA.
>
After additional attempts and some research I am stuck upgrading mailman
2.1.5 to 2.1.34 and get the same results I had reported here earlier. I
followed these instructions:

https://wiki.list.org/DOC/How%20do%20I%20upgrade%20a%20Debian/Ubuntu%20Mailman%20package%20from%20source.

And made, what I thought were, the appropriate changes to the configure
parameters:

./configure --prefix=/usr/lib/mailman --with-username=mailman
--with-groupname=mailman --with-cgi-gid=apache --with-mail-gid=mailman

If anyone sees anything wrong please point it out. Anyway, after doing
the make and install, I start mailman and get this status:

● mailman.service - GNU Mailing List Manager
   Loaded: loaded (/usr/lib/systemd/system/mailman.service; disabled;
vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2020-09-14 10:31:12 MDT;
20min ago
  Process: 20030 ExecStart=/usr/lib/mailman/bin/mailmanctl -s start
(code=exited, status=1/FAILURE)
  Process: 20028 ExecStartPre=/bin/chmod 660 /var/log/mailman/error
(code=exited, status=0/SUCCESS)
  Process: 20024 ExecStartPre=/bin/chown mailman:mailman
/var/log/mailman/error (code=exited, status=0/SUCCESS)
  Process: 20021 ExecStartPre=/bin/touch /var/log/mailman/error
(code=exited, status=0/SUCCESS)
  Process: 20018 ExecStartPre=/usr/bin/install -m644 -o root -g root
/usr/lib/mailman/cron/crontab.in /etc/cron.d/mailman (code=exited,
status=0/SUCCESS)
  Process: 20014 ExecStartPre=/usr/lib/mailman/bin/mailman-update-cfg
(code=exited, status=0/SUCCESS)

Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: File
"/usr/lib64/python2.7/codecs.py", line 881, in open
Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: file =
__builtin__.open(filename, mode, buffering)
Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: IOError: [Errno 13]
Permission denied: '/usr/lib/mailman/logs/error'
Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: Original log message:
Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: [Errno 13]
Permission denied: '/usr/lib/mailman/logs/error'
Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: Sep 14 10:31:12 2020
(20030) Site list is missing: mailman
Sep 14 10:31:12 harmonia.csd.net systemd[1]: mailman.service: control
process exited, code=exited status=1
Sep 14 10:31:12 harmonia.csd.net systemd[1]: Failed to start GNU Mailing
List Manager.
Sep 14 10:31:12 harmonia.csd.net systemd[1]: Unit mailman.service
entered failed state.
Sep 14 10:31:12 harmonia.csd.net systemd[1]: mailman.service failed.

I don't understand the permissions denied error. Unfortunately it does
not tell me what process is trying to open it. The directory is rw by
mailman:mailman. In addition, the error that site list is missing
'mailman' is also confusing. Does the upgrade overwrite something that
makes the existing lists disappear? The instructions say nothing about
running anything else to make the lists known to the new version. I am
guessing I need to do something with 'withlist' but I don't know what.
Finally, I am concerned that the working 2.1.15 version has no
'mm_cfg.py' while the new version has a file with only comments. Perhaps
this is OK if I'm using all defaults. I need someone to nursemaid me
through this upgrade. TIA.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Filer From: no-reply

[Dennis Putnam]

On 9/11/2020 11:52 AM, Mark Sapiro wrote:
> On 9/11/20 6:44 AM, Dennis Putnam wrote:
>
>> Thanks. So far it is looking good but I made one small change:
>>
>> ^from:\s*(>
>> I hope I did it right.
>
> What you did is OK. It will match
>
> From: Jane Doe 
>
> but a simpler way to do that is
>
> ^from:\s*(
> and to also match
>
> From: nore...@example.com
>
> make it
>
> ^from:\s*(
>
Thanks Mark. Clever. Now that I see it, I should have been able to
figure that out myself. Regex is not my forte.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Manual Update on Centos 7

[Dennis Putnam]

Hi Tom,

I ran the following sequence of commands as best I could interpret them
for CentOS:

./configure --prefix=/usr/lib/mailman --with-username=mailman
--with-groupname=mailman --with-cgi-gid=apache --with-mail-gid=mailman
make
service mailman stop
make install
service mailman start
/usr/lib/mailman/bin/check_perms -f

After all that with no errors, when I try to start mailman I get this:

 mailman.service - GNU Mailing List Manager
   Loaded: loaded (/usr/lib/systemd/system/mailman.service; disabled;
vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2020-09-11 08:39:55 MDT;
6s ago
  Process: 21345 ExecStart=/usr/lib/mailman/bin/mailmanctl -s start
(code=exited, status=1/FAILURE)
  Process: 21342 ExecStartPre=/bin/chmod 660 /var/log/mailman/error
(code=exited, status=0/SUCCESS)
  Process: 21339 ExecStartPre=/bin/chown mailman:mailman
/var/log/mailman/error (code=exited, status=0/SUCCESS)
  Process: 21336 ExecStartPre=/bin/touch /var/log/mailman/error
(code=exited, status=0/SUCCESS)
  Process: 21333 ExecStartPre=/usr/bin/install -m644 -o root -g root
/usr/lib/mailman/cron/crontab.in /etc/cron.d/mailman (code=exited,
status=0/SUCCESS)
  Process: 21329 ExecStartPre=/usr/lib/mailman/bin/mailman-update-cfg
(code=exited, status=0/SUCCESS)

Sep 11 08:39:55 harmonia.csd.net mailmanctl[21345]: File
"/usr/lib64/python2.7/codecs.py", line 881, in open
Sep 11 08:39:55 harmonia.csd.net mailmanctl[21345]: file =
__builtin__.open(filename, mode, buffering)
Sep 11 08:39:55 harmonia.csd.net mailmanctl[21345]: IOError: [Errno 13]
Permission denied: '/usr/lib/mailman/logs/error'
Sep 11 08:39:55 harmonia.csd.net mailmanctl[21345]: Original log message:
Sep 11 08:39:55 harmonia.csd.net mailmanctl[21345]: [Errno 13]
Permission denied: '/usr/lib/mailman/logs/error'
Sep 11 08:39:55 harmonia.csd.net mailmanctl[21345]: Sep 11 08:39:55 2020
(21345) Site list is missing: mailman
Sep 11 08:39:55 harmonia.csd.net systemd[1]: mailman.service: control
process exited, code=exited status=1
Sep 11 08:39:55 harmonia.csd.net systemd[1]: Failed to start GNU Mailing
List Manager.
Sep 11 08:39:55 harmonia.csd.net systemd[1]: Unit mailman.service
entered failed state.
Sep 11 08:39:55 harmonia.csd.net systemd[1]: mailman.service failed.

If I look at that file, it is missing. The directory seems correct:

drwxrwsr-x.  2 mailman mailman   19 Sep 11 08:39 logs

I should note that the first time I built/installed it, I had the wrong
prefix directory (/var/lib/mailman) taken from the Ubuntu instructions.
I also was not sure what to use for the other parameters but on CentOS
everything is owned by user mailman:mailman. The 2.15 installation had
that directory (/var/lib/mailman) but it was used by mailman for
something else. So I don't know if by doing that, it messed things up
beyond repair. If so I can reclone my production machine to this test
machine and try again. Please advise. Thanks.

On 8/29/2020 5:18 PM, Tom Coradeschi wrote:
> I found the info here to be of good use on ubuntu. Hopefully centos is 
> similar enough that it’s useful to you.
>
> https://wiki.list.org/DOC/5%20Downloading%20and%20installing%20Mailman
>
> —
> Tom Coradeschi
> tjc...@icloud.com
>
>
>> On 29 Aug 2020, at 2:11 PM, Dennis Putnam  wrote:
>>
>> Since Centos 7 is way behind on mailman rpm (2.1.15 is the only
>> available rpm) and mailman is currently at 2.1.34 I need to do a manual
>> update. While I know how to install software, I am concerned that just
>> doing a manual install from the tarball will mess up current settings,
>> lists and members. Does anyone have experience doing this that can
>> advise about pitfalls or has a cookbook document to do a safe update? TIA.
>>
>> --
>> 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/







signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Filer From: no-reply

[Dennis Putnam]

On 9/10/2020 4:52 PM, Mark Sapiro wrote:
> On 9/10/20 12:13 PM, Dennis Putnam wrote:
>>> From:\s.*no-reply
>>>
>> Thanks again for the reply. Unfortunately that doesn't work either.
> Try this in header_filter_rules
>
> ^from:\s*(
> These are case insensitive. The 'From:\s.*no-reply' pattern is too
> liberal. It will for example match
>
> Subject: a message from: someone with a no-reply address
>
> You need the initial ^ to ensure you're matching the From: header and
> not just any header with 'from: ' in it. My suggestion will match things
> like:
>
> From: no-re...@example.com
> From: 
> From: Jane Doe 
>
> and it won't match
>
> From: juno-re...@example.com
> From: no-reply...@example.com
>
>
Thanks. So far it is looking good but I made one small change:

^from:\s*(

signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Filer From: no-reply

[Dennis Putnam]

On 9/10/2020 2:56 PM, Richard Damon wrote:
> On 9/10/20 2:37 PM, Dennis Putnam wrote:
>> On 9/10/2020 2:01 PM, Richard Damon wrote:
>>> On 9/10/20 12:47 PM, Dennis Putnam wrote:
>>>> I am getting email from entities with From: no-reply headers. Is there a
>>>> way to filter those and just dump them in the bit bucket rather than go
>>>> through bounce processing? TIA.
>>>>
>>> If you can write a regex for them, you could put it into Privacy / Spam
>>> Filters with result discard. Might want to test with Hold to see if you
>>> get false positives with your regex first.
>>>
>> Thanks for the reply. I'm not a regex expert so I am struggling with
>> this a bit. I can get this much to work:
>>
>> (?i)no-reply@
>>
>> However, I have to make sure this occurs in the 'From' header and that
>> is the part I don't know how to add. Does the filter parse the entire
>> raw message? It appears there is some character I cannot seem to catch
>> after the 'From:'.
>>
>> This does not work:
>>
>> From:\s.?(?i)no-reply
> \s.? says a space followed by 0 or 1 occurance of any character.
>
> I would use something like:
>
> From:\s.*no-reply
>
Thanks again for the reply. Unfortunately that doesn't work either.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Re: Filer From: no-reply

[Dennis Putnam]

On 9/10/2020 2:01 PM, Richard Damon wrote:
> On 9/10/20 12:47 PM, Dennis Putnam wrote:
>> I am getting email from entities with From: no-reply headers. Is there a
>> way to filter those and just dump them in the bit bucket rather than go
>> through bounce processing? TIA.
>>
> If you can write a regex for them, you could put it into Privacy / Spam
> Filters with result discard. Might want to test with Hold to see if you
> get false positives with your regex first.
>
Thanks for the reply. I'm not a regex expert so I am struggling with
this a bit. I can get this much to work:

(?i)no-reply@

However, I have to make sure this occurs in the 'From' header and that
is the part I don't know how to add. Does the filter parse the entire
raw message? It appears there is some character I cannot seem to catch
after the 'From:'.

This does not work:

From:\s.?(?i)no-reply



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Filer From: no-reply

[Dennis Putnam]

I am getting email from entities with From: no-reply headers. Is there a
way to filter those and just dump them in the bit bucket rather than go
through bounce processing? TIA.



signature.asc
Description: OpenPGP digital signature
--
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/

[Mailman-Users] Manual Update on Centos 7

[Dennis Putnam]

Since Centos 7 is way behind on mailman rpm (2.1.15 is the only
available rpm) and mailman is currently at 2.1.34 I need to do a manual
update. While I know how to install software, I am concerned that just
doing a manual install from the tarball will mess up current settings,
lists and members. Does anyone have experience doing this that can
advise about pitfalls or has a cookbook document to do a safe update? TIA.



signature.asc
Description: OpenPGP digital signature
--
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/

Re: [Mailman-Users] Handling Munged From Addresses

[Dennis Putnam]

On 2/27/2020 1:38 PM, Mark Sapiro wrote:
> On 2/27/20 10:17 AM, Dennis Putnam wrote:
>> Thanks for the reply. I am not seeing that. The From: looks like this:
>>
>> From: Rushtalk Discussion List via Rushtalk 
>
> That must be a RedHat thing having to do with their backport of DMARC
> mitigations. If you don't like it, install from source.
>
>
>> In "General Options" for that list I set the item "Replace the From:
>> header address with the list's posting address to mitigate issues
>> stemming from the original From: domain's DMARC or similar policies."
>> with "Munge From." Did I set the wrong thing?

>
> That will apply From: munging to all posts. I have no idea what the
> RedHat package does, but if in Privacy options... -> Sender filters you
> have dmarc_moderation_action and dmarc_quarantine_moderation_action set
> General Options -> from_is_list to No and set dmarc_moderation_action to
> Munge From and dmarc_quarantine_moderation_action to Yes and if you have
> it, dmarc_none_moderation_action to No.
>
> This will apply From: munging only to those messages From: a domain that
> publishes DMARC policy = reject or quarantine.
>
>
Hi Mark,

I didn't realize that there were OS dependencies in the DMARC
mitigation. I thought it was all within the mailman code.

In any case I'll look through those options and see what they do in
RHEL. Thanks.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Handling Munged From Addresses

[Dennis Putnam]

On 2/27/2020 1:23 PM, Mark Sapiro wrote:
> On 2/27/20 10:05 AM, Jim Popovitch via Mailman-Users wrote:
>> I've been wondering if we should change that to something like this:
>>
>>  From: Jane Doe (jane@domain.tld) via Listname
>> 
>
> We specifically do not do that because it is said that multiple email
> addresses in From: trigger spam filters.
>

From: Jane Doe (jane.doe at domain.tld) via Listname





signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Handling Munged From Addresses

[Dennis Putnam]

On 2/27/2020 12:58 PM, Mark Sapiro wrote:
> On 2/27/20 7:22 AM, Dennis Putnam wrote:
>> I think this may have been addressed but I can't find it. Now that I am
>> munging the from address to mitigate DMARC, recipients can no longer
>> tell who the message is from. What are other folks doing to handle that?
>> Other than having list members add their own signature? Thanks.
>
> The From: header in the munged message contains the sender's display
> name as in
>
> From: Jane Doe via ListName 
>
> and depending on list settings the original From: is in either Reply-To:
> or Cc:.
>
> If this is not sufficient, perhaps the recipients can use smarter email
> clients ;)
>
> Also, if you are Munging the From: on all messages via the from_is_list
> setting, it is better to use dmarc_moderation_action for this so only
> those From: headers that need it are munged. The only reason to use
> from_is_list is if those users whose domains publish DMARC reject or
> quarantine policy feel they are singled out and treated as second class
> users.
>
>
Hi Mark,

Thanks for the reply. I am not seeing that. The From: looks like this:

From: Rushtalk Discussion List via Rushtalk 

In "General Options" for that list I set the item "Replace the From:
header address with the list's posting address to mitigate issues
stemming from the original From: domain's DMARC or similar policies."
with "Munge From." Did I set the wrong thing?


signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Possible Backup Issue

[Dennis Putnam]

On 2/27/2020 12:47 PM, Mark Sapiro wrote:
> On 2/27/20 6:27 AM, Dennis Putnam wrote:
>> It has not happened in 2 days however, there are no files in any of
>> those directories. Does that not imply the backups are not working? Is
>> that handled by a cronjob?
>
> This has nothing to do with backups per se. The error messages are
> somewhat different.
>
>> Feb 25 12:02:06 2020 (14100) Uncaught runner exception: [Errno 2] No
>> such file or directory
> The above actually goes with a set below (pid 14100).
>
>
>> Feb 25 12:02:06 2020 (5133) Uncaught runner exception: [Errno 2] No such
>> file or directory:
>> '/var/spool/mailman/out/1582657325.390982+504a3666a91ef8722e1af700669bf0190e00417d.pck'
>> Feb 25 12:02:06 2020 (5133) Traceback (most recent call last):
>>   File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop
>> msg, msgdata = self._switchboard.dequeue(filebase)
>>   File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 154, in dequeue
>> fp = open(filename)
>> IOError: [Errno 2] No such file or directory:
>> '/var/spool/mailman/out/1582657325.390982+504a3666a91ef8722e1af700669bf0190e00417d.pck'
>
> The above says OutgoingRunner has listed its queue and is now trying to
> retrieve the indicated .pck file from the queue, but it is gone. The
> only way this can happen is if another instance of OutgoingRunner has
> retrieved the message in the mean time.
>
>
>> Feb 25 12:02:06 2020 (5133) Skipping and preserving unparseable message:
>> 1582657325.390982+504a3666a91ef8722e1af700669bf0190e00417d
> This goes with the above, but is spurious. The missing file exception is
> assumed to be an unparseable message, but it's not.
>
>
>> Feb 25 12:02:06 2020 (14100) Traceback (most recent call last):
>>   File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop
>> msg, msgdata = self._switchboard.dequeue(filebase)
>>   File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 158, in dequeue
>> os.rename(filename, backfile)
>> OSError: [Errno 2] No such file or directory
>>
>> Feb 25 12:02:06 2020 (14100) Skipping and preserving unparseable
>> message: 1582657325.390982+30007f7a3ce65a426ba60c1ab46d996c33d2bb9a
>
> Here again, we are trying to retrieve a queued message that another
> instance has already retrieved.
>
> The rest of the messages are similar.
>
> As best as I can tell, this is all due to the issue discussed at
> <https://wiki.list.org/x/4030715>. If the server has been rebooted since
> this happened, that would have fixed it.
>
>
Hi Mark,

Thanks. I'll just keep an eye on it to see if it recurs.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Handling Munged From Addresses

[Dennis Putnam]

I think this may have been addressed but I can't find it. Now that I am
munging the from address to mitigate DMARC, recipients can no longer
tell who the message is from. What are other folks doing to handle that?
Other than having list members add their own signature? Thanks.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Possible Backup Issue

[Dennis Putnam]

On 2/26/2020 9:14 PM, Mark Sapiro wrote:
> On 2/26/20 8:18 AM, Dennis Putnam wrote:
>> mailman   5129  5125  0 Feb24 ?    00:00:16 /usr/bin/python
>> /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
>>
>> I think that means there is only 1 process.
>
> Yes, but maybe that wasn't the case at the time of those messages. Are
> the errors continuing? Also, I indicated BounceRunner as I was looking
> at the last messages you posted. There are also ones involving
> OutgoingRunner and VirginRunner
>
> Also, there should be files in /var/spool/mailman/bad/ which you may be
> able to examine with Mailman's dumpdb which are the unparseable message(s).
>
>
Hi Mark,

It has not happened in 2 days however, there are no files in any of
those directories. Does that not imply the backups are not working? Is
that handled by a cronjob?



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Possible Backup Issue

[Dennis Putnam]

On 2/26/2020 11:09 AM, Mark Sapiro wrote:
> On 2/26/20 6:56 AM, Dennis Putnam wrote:
>> I'm not sure why I am getting these errors but it seems to be associated
>> with backups. Is there a backup cronjob that didn't run, fail or is
>> something else wrong? The directories do exist but not the indicated pck
>> files. TIA
>
> I haven't looked at this in full detail, but is there more than one
> BounceRunner running processing the same slice. What does
>
> ps -fwwA|grep BounceRunner
>
> give? If there is more than one process showing
> "--runner=BounceRunner:0:1" see the article at
> <https://wiki.list.org/x/4030715> for advice on completely stopping
> Mailman and starting only one instance.
>

mailman   5129  5125  0 Feb24 ?    00:00:16 /usr/bin/python
/usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s

I think that means there is only 1 process.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Possible Backup Issue

[Dennis Putnam]

I'm not sure why I am getting these errors but it seems to be associated
with backups. Is there a backup cronjob that didn't run, fail or is
something else wrong? The directories do exist but not the indicated pck
files. TIA

Feb 25 12:02:06 2020 (14100) Uncaught runner exception: [Errno 2] No
such file or directory
Feb 25 12:02:06 2020 (5133) Uncaught runner exception: [Errno 2] No such
file or directory:
'/var/spool/mailman/out/1582657325.390982+504a3666a91ef8722e1af700669bf0190e00417d.pck'
Feb 25 12:02:06 2020 (5133) Traceback (most recent call last):
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop
    msg, msgdata = self._switchboard.dequeue(filebase)
  File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 154, in dequeue
    fp = open(filename)
IOError: [Errno 2] No such file or directory:
'/var/spool/mailman/out/1582657325.390982+504a3666a91ef8722e1af700669bf0190e00417d.pck'

Feb 25 12:02:06 2020 (5133) Skipping and preserving unparseable message:
1582657325.390982+504a3666a91ef8722e1af700669bf0190e00417d
Feb 25 12:02:06 2020 (14100) Traceback (most recent call last):
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop
    msg, msgdata = self._switchboard.dequeue(filebase)
  File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 158, in dequeue
    os.rename(filename, backfile)
OSError: [Errno 2] No such file or directory

Feb 25 12:02:06 2020 (14100) Skipping and preserving unparseable
message: 1582657325.390982+30007f7a3ce65a426ba60c1ab46d996c33d2bb9a
Feb 25 12:02:06 2020 (14102) Failed to unlink/preserve backup file:
/var/spool/mailman/out/1582657325.390982+504a3666a91ef8722e1af700669bf0190e00417d.bak
Feb 25 12:02:07 2020 (5128) Failed to unlink/preserve backup file:
/var/spool/mailman/archive/1582657325.390982+30007f7a3ce65a426ba60c1ab46d996c33d2bb9a.bak
Feb 25 12:07:35 2020 (5134) Uncaught runner exception: [Errno 2] No such
file or directory:
'/var/spool/mailman/virgin/1582657654.150712+53c19a1ee899509786cc9beb40990d4c631f65d4.pck'
Feb 25 12:07:35 2020 (5134) Traceback (most recent call last):
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop
    msg, msgdata = self._switchboard.dequeue(filebase)
  File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 154, in dequeue
    fp = open(filename)
IOError: [Errno 2] No such file or directory:
'/var/spool/mailman/virgin/1582657654.150712+53c19a1ee899509786cc9beb40990d4c631f65d4.pck'

Feb 25 12:07:35 2020 (5134) Skipping and preserving unparseable message:
1582657654.150712+53c19a1ee899509786cc9beb40990d4c631f65d4
Feb 25 12:07:35 2020 (14098) Failed to unlink/preserve backup file:
/var/spool/mailman/virgin/1582657654.150712+53c19a1ee899509786cc9beb40990d4c631f65d4.bak
Feb 25 12:29:07 2020 (14099) Uncaught runner exception: [Errno 2] No
such file or directory
Feb 25 12:29:07 2020 (14099) Traceback (most recent call last):
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop
    msg, msgdata = self._switchboard.dequeue(filebase)
  File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 158, in dequeue
    os.rename(filename, backfile)
OSError: [Errno 2] No such file or directory

Feb 25 12:29:07 2020 (14099) Skipping and preserving unparseable
message: 1582658947.082654+30ee2b8943fe331a15218871760c1c8d3a5d8a90
Feb 25 12:29:07 2020 (5131) Failed to unlink/preserve backup file:
/var/spool/mailman/in/1582658947.082654+30ee2b8943fe331a15218871760c1c8d3a5d8a90.bak
Feb 25 13:04:00 2020 (14099) Uncaught runner exception: [Errno 2] No
such file or directory
Feb 25 13:04:00 2020 (14099) Traceback (most recent call last):
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop
    msg, msgdata = self._switchboard.dequeue(filebase)
  File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 158, in dequeue
    os.rename(filename, backfile)
OSError: [Errno 2] No such file or directory

Feb 25 13:04:00 2020 (14099) Skipping and preserving unparseable
message: 1582661039.25433+fcd57e8ec68cce26d6ec44748d97987a885b8f3c
Feb 25 13:04:00 2020 (5131) Failed to unlink/preserve backup file:
/var/spool/mailman/in/1582661039.25433+fcd57e8ec68cce26d6ec44748d97987a885b8f3c.bak
Feb 25 13:04:01 2020 (14104) Uncaught runner exception: [Errno 2] No
such file or directory:
'/var/spool/mailman/bounces/1582661040.887134+c53e72b90df57867b3447d0e85584d819d2f14b4.pck'
Feb 25 13:04:01 2020 (14104) Traceback (most recent call last):
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop
    msg, msgdata = self._switchboard.dequeue(filebase)
  File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 154, in dequeue
    fp = open(filename)
IOError: [Errno 2] No such file or directory:
'/var/spool/mailman/bounces/1582661040.887134+c53e72b90df57867b3447d0e85584d819d2f14b4.pck'

Feb 25 13:04:01 2020 (14104) Skipping and preserving unparseable
message: 1582661040.887134+c53e72b90df57867b3447d0e85584d819d2f14b4
Feb 25 13:04:01 2020 (5129) Failed to 

Re: [Mailman-Users] Archives Permission Denied

[Dennis Putnam]

On 2/25/2020 5:11 PM, Mark Sapiro wrote:
> On 2/25/20 10:25 AM, Dennis Putnam wrote:
>
>> So shouldn't 'check_perms -f' have fixed that?
>
> check_perms is not perfect. See below for more.
>
>
>> This is a server used strictly for mailman. There are only 2 users with
>> access so I am not worried about the caveat in that article. It looks
>> like you are giving me options and I am not sure what to do now?
>
> Either way works, but in your case, I would ensure
> /var/lib/mailman/archives/private is group mailman and mode is 2771.
> With this setting, check_perms will say
>
>> Warning: Private archive directory is other-executable (o+x).
>>  This could allow other users on your system to read private 
>> archives.
>>  If you're on a shared multiuser system, you should consult the
>>  installation manual on how to fix this.
> which you can ignore. The reason I suggest this is so you don't need to
> be concerned about the owner of /var/lib/mailman/archives/private
>
>
Got it. Thanks Mark.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Archives Permission Denied

[Dennis Putnam]

On 2/25/2020 12:12 PM, Mark Sapiro wrote:
> On 2/25/20 6:34 AM, Brian Carpenter wrote:
>> On 2/25/20 5:49 AM, Dennis Putnam wrote:
>>> IOError: [Errno 13] Permission denied:
>>> '/var/lib/mailman/archives/private/rushtalk/2020-February.txt'
>>>
>>>   I ran check_perms and it found no issues. However, when I look at the
>>> ownership of the archives I get this:
>>>
>>> -rw-r--r--.    1 root mailman   72404 Feb 16 14:26 2020-February.txt
>>>
>>> Shouldn't either the owner be mailman or permissions be -rw-rw-r--? TIA.
> ...
>> From what I am seeing with my own servers, the permissions should be 664.
>>
> That's true, but more importantly, /var/lib/mailman/ should be 2775 and
> group mailman as should all the sub-directories  archives, data, lists,
> locks, logs, qfiles and spam. /var/lib/mailman/archives/private is
> tricky. it should be group mailman and either 2771 or owned by the web
> server user and 2770. See
> <https://www.list.org/mailman-install/node9.html> for more on this.
>
So shouldn't 'check_perms -f' have fixed that?

This is a server used strictly for mailman. There are only 2 users with
access so I am not worried about the caveat in that article. It looks
like you are giving me options and I am not sure what to do now?



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Membership List Include Legend Link Wrong

[Dennis Putnam]

On 2/25/2020 9:37 AM, Brian Carpenter wrote:
> On 2/25/20 5:36 AM, Dennis Putnam wrote:
>> The link to include legend on the membership management page is:
>>
>> http://localhost.localdomain/mailman/admin/rushtalk/members/list?legend=yes
>>
>>
>> Why is that not defaulting to the real host and how do I fix it? TIA.
>
> Have you tried running:
>
> /mailman_installation_directory/bin/withlist -l -r fix_url listname -u
> listdomain
>
> for the list to see if that fixes the issue?
>
Yes, I did that once when I first start the migration but I must have
made some inadvertent changes at some point. I ran it again and it
worked. Thanks.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Archives Permission Denied

[Dennis Putnam]

I am in the process of migrating mailman to a new server. It seems to
have been done correctly but mailman is unable to write to the archive
files.

IOError: [Errno 13] Permission denied:
'/var/lib/mailman/archives/private/rushtalk/2020-February.txt'

 I ran check_perms and it found no issues. However, when I look at the
ownership of the archives I get this:

-rw-r--r--.    1 root mailman   72404 Feb 16 14:26 2020-February.txt

Shouldn't either the owner be mailman or permissions be -rw-rw-r--? TIA.





signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Membership List Include Legend Link Wrong

[Dennis Putnam]

The link to include legend on the membership management page is:

http://localhost.localdomain/mailman/admin/rushtalk/members/list?legend=yes

Why is that not defaulting to the real host and how do I fix it? TIA.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Server Configuration 2.1.12

[Dennis Putnam]

I have mailman 2.1.12 installed on RHEL 7 (that is the latest version
available in the RHEL 7 repository). When I try to access the mailman
web pages (apache 2.4) I get the error:

[Mon Feb 17 03:43:04.099892 2020] [authz_core:error] [pid 30156] [client
162.230.29.192:49655] AH01630: client denied by server configuration:
/usr/lib/mailman/cgi-bin/listinfo

Here is my mailman.conf file:

#
#  httpd configuration settings for use with mailman.
#

ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/

    AllowOverride None
    Options ExecCGI
    Order allow,deny
    Allow from all



Alias /pipermail/ /usr/lib/mailman/archives/public/

    Options Indexes MultiViews FollowSymLinks
    AllowOverride None
    Order allow,deny
    Allow from all


# Uncomment the following line, replacing www.example.com with your server's
# name, to redirect queries to /mailman to the listinfo page (recommended).

RedirectMatch ^/$ http://galene.csd.net/mailman/listinfo/rushtalk

Since it looks correct to me, perhaps some new eyes can see what I am
missing. TIA.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman 2.1.18 for RHEL 5

[Dennis Putnam]

On 2/16/2020 11:45 PM, Stephen J. Turnbull wrote:
> Dennis Putnam writes:
>
>  > Since migrating to mailman 3 on the latest RHEL is going to take some
>  > time, I need an interim solution to DMARC mitigation. I understand
>  > version 2.1.18
>
> Why 2.1.18?  Do you have that already installed?  It's already pretty
> old, and many of the fixes still being made are security-related.
It turns out that the only version available for RHEL 7 is 2.1.12.
However, the mailman documentation indicates that also has DMARC
mitigation. Anyway, I am giving it a try. Seems silly that RHEL
repositories are so far behind the curve.
>
>  > will do what I need, at least until I can finish the
>  > migration. However, I have been unable to find a repository or rpm
>  > for that version for RHEL 5. Can someone help me out with that?
>
> The Red Hat or Fedora lists would be a much better place to ask.
> We're not likely to know, and we can't provide much support except
> generic comments since we're generally not using packaged versions of
> Mailman, even for testing.  We just don't have the time.
>
> Steve




signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] mailman 2.1.18 for RHEL 5

[Dennis Putnam]

Since migrating to mailman 3 on the latest RHEL is going to take some
time, I need an interim solution to DMARC mitigation. I understand
version 2.1.18 will do what I need, at least until I can finish the
migration. However, I have been unable to find a repository or rpm for
that version for RHEL 5. Can someone help me out with that?



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Server Migration

[Dennis Putnam]

Hi Mark,

I guess there needs to be a caveat in the documentation indicating
different distros will need different commands. This project is turning
into a nightmare since I know nothing about django and they way mailman
3 is installed is radically different. Hyperkitty was installed but when
I run the command it fails.

# django-admin hyperkitty_import -l rusht...@csdco.com rushtalk.mbox
No Django settings specified.
Unknown command: 'hyperkitty_import'
Type 'django-admin help' for usage.

The last line being of no use.

I'm also struggling with the web UI which is what prompted my other
email about where the icons are stored. It almost seems like the web UI
is just a radically different and does not use Apache in the same way
any more.

On 2/14/2020 11:37 AM, Mark Sapiro wrote:
> On 2/14/20 7:09 AM, Dennis Putnam wrote:
>> Hi Mark,
>>
>> Just a little confusing with respect to the documentation which says:
>>
>> python manage.py hyperkitty_import -l foo-l...@example.com 
>> $var_prefix/archives/private/foo-list.mbox/foo-list.mbo
>>
>>
>> So the documentation should say for some installations:
>>
>> django-admin hyperkitty_import -l foo-l...@example.com 
>> $var_prefix/archives/private/foo-list.mbox/foo-list.mbox
>>
>> Is that right?
>
> It is correct that in some installations the command to invoke Django
> may be django-admin. Whether our documentation should cover every
> possible packaging decision made by a packager or installer is a
> separate issue. My opinion is the people who do this
> packaging/installation should provide supplemental documentation where
> appropriate.
>
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Server Migration

[Dennis Putnam]

Hi Mark,

Another issue with these servers. The admin says 'pip3' was used to
install mailman. I thought 'pip' was a python installer. Unfortunately I
cannot find where it put the stuff. So the documentation that specifies
$prefix is of no use since I don't know what that is. This is RHEL so
does anyone know where things wind up? Specifically I'm looking for all
the icons to copy to my httpd directory. TIA

On 2/13/2020 3:40 PM, Mark Sapiro wrote:
> On 2/13/20 11:36 AM, Dennis Putnam wrote:
>> Hi Mark,
>>
>> Sorry for being a PITA but I can't find manage.py. Indeed I can't find
>> any mailman files other than in /opt/mailman which has no /bin.
>> Apparently version 3 uses different directories than what I've been
>> using (/usr/lib/Mailman and /var/lib/mailman).
> It's probably not called manage.py in your installation. In a 'default'
> Django install, manage.py is the name of the Django administratitve
> command. In your case, it could be called django-admin or something else
> depending on how Postorius/HyperKitty were installed.
>
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Server Migration

[Dennis Putnam]

Hi Mark,

Just a little confusing with respect to the documentation which says:

python manage.py hyperkitty_import -l foo-l...@example.com 
$var_prefix/archives/private/foo-list.mbox/foo-list.mbo


So the documentation should say for some installations:

django-admin hyperkitty_import -l foo-l...@example.com 
$var_prefix/archives/private/foo-list.mbox/foo-list.mbox

Is that right?

On 2/13/2020 3:40 PM, Mark Sapiro wrote:
> On 2/13/20 11:36 AM, Dennis Putnam wrote:
>> Hi Mark,
>>
>> Sorry for being a PITA but I can't find manage.py. Indeed I can't find
>> any mailman files other than in /opt/mailman which has no /bin.
>> Apparently version 3 uses different directories than what I've been
>> using (/usr/lib/Mailman and /var/lib/mailman).
>
> It's probably not called manage.py in your installation. In a 'default'
> Django install, manage.py is the name of the Django administratitve
> command. In your case, it could be called django-admin or something else
> depending on how Postorius/HyperKitty were installed.
>
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Server Migration

[Dennis Putnam]

Hi Mark,

Sorry for being a PITA but I can't find manage.py. Indeed I can't find
any mailman files other than in /opt/mailman which has no /bin.
Apparently version 3 uses different directories than what I've been
using (/usr/lib/Mailman and /var/lib/mailman).



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Server Migration

[Dennis Putnam]

Hi Mark,

For some reason the first 'create' didn't work even though it said
successful. The 2nd on did and the import worked.

On 2/13/2020 12:09 PM, Mark Sapiro wrote:
> On 2/13/20 8:40 AM, Dennis Putnam wrote:
>> Hi Mark,
>>
>> I'm stuck on the 2nd step.
>>
>> I did:
>>
>> mailman create rusht...@csdco.com
>>
>> Got no errors.
> Good.
>> I'm on the new server, copied the pickle file from the old server to the
>> current directory and used the command:
>>
>> mailman import21 rusht...@csdco.com config.pck
>>
>> I get: Error: No such list: rusht...@csdco.com
>>
>> Apparently I don't know what to use for the LISTSPEC. The specified
>> address is how we send messages to the list. I also tried the FQDN and
>> got the same error.
>
> It should work with either rusht...@csdco.com or rushtalk.csdco.com. Are
> you sure you didn't spell it differently on the create? What does
>
> mailman lists
>
> give?
>
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Server Migration

[Dennis Putnam]

Hi Mark,

I'm stuck on the 2nd step.

I did:

mailman create rusht...@csdco.com

Got no errors.

I'm on the new server, copied the pickle file from the old server to the
current directory and used the command:

mailman import21 rusht...@csdco.com config.pck

I get: Error: No such list: rusht...@csdco.com

Apparently I don't know what to use for the LISTSPEC. The specified
address is how we send messages to the list. I also tried the FQDN and
got the same error.

On 2/13/2020 11:14 AM, Mark Sapiro wrote:
> On 2/13/20 3:17 AM, Dennis Putnam wrote:
>> Hi Mark,
>>
>> I've been thrown into this so I am unfamiliar with these servers (not my
>> own that I usually deal with). Anyway, as I unravel things I'm working
>> with, I see that I am really running version 2.1.9. As I understand it,
>> the DMARC mitigation was not added until 2.1.18. So I think using
>> import21 should work, right?
>
> Yes, import21 will work with a 2.1.9 config.pck. And yes, there are no
> DMARC mitigations in that version.
>
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Server Migration

[Dennis Putnam]

Hi Mark,

I've been thrown into this so I am unfamiliar with these servers (not my
own that I usually deal with). Anyway, as I unravel things I'm working
with, I see that I am really running version 2.1.9. As I understand it,
the DMARC mitigation was not added until 2.1.18. So I think using
import21 should work, right?

On 2/12/2020 12:51 PM, Mark Sapiro wrote:
> On 2/12/20 9:06 AM, Dennis Putnam wrote:
>> Hi Mark,
>>
>> We finally got the networking folks to cooperate so DNS is the way we
>> will go. I don't know if it makes any difference but the version was a
>> typo, we are at 2.0.x.
> If you really mean your current Mailman is 2.0.x, trying to import to MM
> 3 with `mailman import21` will likely result in a mess. See the
> UPGRADING FROM 2.0.x to 2.1 section at
> <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/UPGRADING>
>
>> Please see embedded comments.
>>
>>> Import the Mailman 2.1 config.pck with `mailman import21`
>> Easy enough assuming I copy config.pck to the new server to run the command.
> Yes.
>
>
>>> Import the Mailman 2.1 archives/private/xxx.mbox/zzz.mbox mailbox with
>>> the Django Admin hyperkitty_import command.
>> I'm not familiar with that. I am guessing, similar to config.pck, I copy
>> that directory to the new server then run that command on that
>> directory. I'll have to install Django.
>
> The Mailman 2.1 archives/private/xxx.mbox/zzz.mbox mailbox is a file,
> not a directory. It is the cumulative mailbox containing all the 'zzz'
> list's archived messages.
>
> A complete Mailman 3 installation will include Postorius and HyperKitty
> and Django to support them. Postorius is the web management UI for
> Mailman. HyperKitty is the archiver. If you don't have that installed,
> there's nothing to import the archives to.
>
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Server Migration

[Dennis Putnam]

Hi Mark,

We finally got the networking folks to cooperate so DNS is the way we
will go. I don't know if it makes any difference but the version was a
typo, we are at 2.0.x.

Please see embedded comments.

On 2/12/2020 11:42 AM, Mark Sapiro wrote:
> On 2/12/20 6:06 AM, Dennis Putnam wrote:
>> Hi Mark,
>>
>> Those are the ones I have been reading. I guess what I need to do is a
>> little more complicated than I posted. The old server is running v 2.1
>> and we are running into DEMARC issues. Since we need to upgrade anyway
>> we have upgraded a new server to the latest RHEL version and mailman
>> 3.3. Once we migrate the lists to the new server we just want the users
>> to message the same email addresses as before which is why I questioned
>> those instructions. Since we don't have access to change DNS it seems
>> the easiest thing to do is change their hostnames and IP addresses. If
>> there is a better way I am interested.
>
> All the instructions/advice for moving lists are about moving from one
> Mailman 2.1 installation to another. Migrating lists from Mailman 2.1 to
> Mailman 3 is totally different. For that, you need a working Mailman 3
> installation. You migrate Mailman 2.1 lists roughly as follows:
>
> Create the Mailman 3 list with `mailman create`
No problem there.
> Import the Mailman 2.1 config.pck with `mailman import21`
Easy enough assuming I copy config.pck to the new server to run the command.
> Import the Mailman 2.1 archives/private/xxx.mbox/zzz.mbox mailbox with
> the Django Admin hyperkitty_import command.
I'm not familiar with that. I am guessing, similar to config.pck, I copy
that directory to the new server then run that command on that
directory. I'll have to install Django.
>
> I'm a bit confused about the rest of what you want to do. First, I don't
> know what your DMARC issues might be with your current lists, but if
> your Mailman 2.1 installation is relatively recent, there is essentially
> no difference in DMARC mitigations between that and Mailman 3.3.
>
> Then, your OP said you wanted users to be able to mail to the list at
> listn...@oldserver.domain.com. If you don't control DNS, you apparently
> can't make the MX for oldserver.domain.com point to the new server, so
> the only way to accomplish this would be to maintain the old server and
> create aliases there (or change the existing Mailman aliases) to send
> all the mail to listname(-*)@oldserver.domain.com to the corresponding
> listname(-*)@newserver.domain.com address and also make
> listn...@oldserver.domain.com an acceptable alias of
> thelistn...@newserver.domain.com list.
>
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Server Migration

[Dennis Putnam]

Hi Mark,

Those are the ones I have been reading. I guess what I need to do is a
little more complicated than I posted. The old server is running v 2.1
and we are running into DEMARC issues. Since we need to upgrade anyway
we have upgraded a new server to the latest RHEL version and mailman
3.3. Once we migrate the lists to the new server we just want the users
to message the same email addresses as before which is why I questioned
those instructions. Since we don't have access to change DNS it seems
the easiest thing to do is change their hostnames and IP addresses. If
there is a better way I am interested.

On 2/11/2020 3:51 PM, Mark Sapiro wrote:
> On 2/11/20 11:42 AM, Dennis Putnam wrote:
>> I've been reading up on migrating to a new server but I'm not sure I am
>> reading the right instructions. It seems that copying the lists to the
>> new server is one thing but it appears that the end result means the
>> users will have to use a new list server. That is, if users were
>> emailing listn...@oldserver.domain.com they will now have to email
>> listn...@newserver.domain.com. That is not what I want. After migrating
>> to the new server I want users to still email
>> listn...@oldserver.domain.com. I expect to simply rename the new server
>> to the old hostname and change its IP address. Can someone point me to
>> some documentation that does that type migration? TIA.
>
> This is dead simple.
>
> Have you seen <https://wiki.list.org/x/4030682>, in particular, the two
> archived posts linked from the first paragraph.
>
> In any case, there are details depending on things like whether you want
> to upgrade/change configurations, but I will assume that this is just a
> matter of replacing a server and not changing Mailman.
>
> In that case, you just rsync almost all of Mailman to the new server.
> What I did when I did this last December is:
>
>> rsync -a --exclude /locks /var/lib/mailman/ 
>> r...@new.example.com:/var/lib/mailman
>> rsync -a --exclude *pid --exclude /locks /opt/mailman/mm/var/ 
>> r...@new.example.com:/opt/mailman/mm/var
> Depending on your installation, you may have only one directory for
> $prefix and $var_prefix. You may also have stuff in /etc/mailman.
>
> You also have to copy Mailman's crontab and the relevant web server and
> mail server configuration.
>
> You need to set TTL a day or so in advance on your DNS records that
> point to the old IP to a very short time, 300 seconds maybe even less if
> you can.
>
> Then you stop the services on the old server, change DNS to point to the
> dew IP, do the final rsyncs, and start the services on the new server,
> and you're done.
>
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Server Migration

[Dennis Putnam]

Hi Robert,

Thanks for the reply. I have no access to DNS which is why the old
server needs to be shutdown and the new server renamed the same as the
old server and the IP address changed to match. I have root access to
the mailman server. I'll reply to Mark's message with more detail.

On 2/11/2020 3:50 PM, Robert Heller wrote:
> At Tue, 11 Feb 2020 14:42:15 -0500 Dennis Putnam  wrote:
>
>>
>>
>> Content-Language: en-US
>>
>> I've been reading up on migrating to a new server but I'm not sure I am
>> reading the right instructions. It seems that copying the lists to the
>> new server is one thing but it appears that the end result means the
>> users will have to use a new list server. That is, if users were
>> emailing listn...@oldserver.domain.com they will now have to email
>> listn...@newserver.domain.com. That is not what I want. After migrating
>> to the new server I want users to still email
>> listn...@oldserver.domain.com. I expect to simply rename the new server
>> to the old hostname and change its IP address. Can someone point me to
>> some documentation that does that type migration? TIA.
> You don't "name" (or rename) the server.  You update the DNS server to use 
> the 
> new server's IP address for the old hostname.  How you update the DNS server 
> greatly depends on exactly what sort of access you have to the DNS server.
>
> It also depends on what level of access you have to the server(s).  Are these 
> VPSs? Physical server boxes?  Are you just swapping physical hardware?  If 
> you 
> are swapping *physical hardware*, then you could, once the files are copied 
> and everything is working (eg you have tested things as 
> newserver.domain.com), 
> you could shutdown the original oldserver.domain.com, and then reconfigure 
> newserver.domain.com's IP address to be what oldserver.domain.com was.  In 
> that case, there is no need to mess with the DNS server. (You might need to 
> mess with a DHCP server, depending on how IP addresses are set up.)
>
> In order to point you in the right direction, you need to tell us more...
>
>> Content-Description: OpenPGP digital signature
>>
>> -BEGIN PGP SIGNATURE-
>>
>> iF0EARECAB0WIQTebsbo9TQsIuOkbg/9+JZipna1VAUCXkMDmAAKCRD9+JZipna1
>> VGajAKDxxI26C50i0+eKII1m8vtNZeuBowCdEXAqTWrPLMx742cnqMIdBBfKYc4=
>> =5/6h
>> -END PGP SIGNATURE-
>>
>> MIME-Version: 1.0
>>
>> --
>> Mailman-Users mailing list Mailman-Users@python.org
>> https://mail.python.org/mailman/listinfo/mailman-users
>> Mailman FAQ: http://wiki.list.org/x/AgA3
>> Security Policy: http://wiki.list.org/x/QIA9
>> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
>> Unsubscribe: 
>> https://mail.python.org/mailman/options/mailman-users/heller%40deepsoft.com
>>
>> 




signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Server Migration

[Dennis Putnam]

I've been reading up on migrating to a new server but I'm not sure I am
reading the right instructions. It seems that copying the lists to the
new server is one thing but it appears that the end result means the
users will have to use a new list server. That is, if users were
emailing listn...@oldserver.domain.com they will now have to email
listn...@newserver.domain.com. That is not what I want. After migrating
to the new server I want users to still email
listn...@oldserver.domain.com. I expect to simply rename the new server
to the old hostname and change its IP address. Can someone point me to
some documentation that does that type migration? TIA.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] From Address for 'mailpasswds'

[Dennis Putnam]

Thanks. That is what I need to override. How do I do that?

On 6/7/2019 4:25 AM, mailman-admin wrote:
> Am 05.06.19 um 20:18 schrieb Dennis Putnam:
>> Hi Mark,
>>
>> After looking at this a bit I have a question. Are the strings 'owner',
>> 'request' and 'bounces' appended to the list name?
>>
>> list1-owner@domain
>> list1-request@domain
>> list1-bounces@domain
>>
> yes.
>
>
> Kind regards,
> Christian Mack
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net
>




signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] From Address for 'mailpasswds'

[Dennis Putnam]

Hi Mark,

After looking at this a bit I have a question. Are the strings 'owner',
'request' and 'bounces' appended to the list name?

list1-owner@domain
list1-request@domain
list1-bounces@domain

On 6/5/2019 1:21 PM, Mark Sapiro wrote:
> On 6/5/19 8:55 AM, Dennis Putnam wrote:
>> I am trying to send a monthly reminder using 'mailman
>> /usr/lib/mailman/cron/mailpasswds'. However, the messages bounce due to
>> an invalid from address. How can I change the script to use a valid from
>> address? Thanks.
>
> Why is the From: invalid? it is the site list -owner address and the
> envelope is from the site list -bounces address. These should be
> deliverable addresses. There is a potential issue with virtual domains
> in that the domain of these addresses can be the virtual host domain and
> the address may not be valid in that domain.
>
> We currently add the site list address in each virtual domain in
> POSTFIX_STYLE_VIRTUAL_DOMAINS to the generated virtual-mailman file, but
> we don't add the -owner and -bounces addresses. I'll fix that. See
> <https://bugs.launchpad.net/mailman/+bug/1831777>.
>
> As far as changing these addresses is concerned, at lines 197-199 in the
> script you'll see
>
> siteowner = Utils.get_site_email(host, 'owner')
> sitereq = Utils.get_site_email(host, 'request')
> sitebounce = Utils.get_site_email(host, 'bounces')
>
> You could replace host in these lines with the literal host name which
> is valid for the site list in quotes like 'example.com'.
>
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] From Address for 'mailpasswds'

[Dennis Putnam]

Hi Mark,

I am using U-Verse which means the domain and from address of my Linux
server are fake. I tried setting up translation in Postfix (generic) but
it does not seem to work for this particular address. I'll try your
suggestion. Thanks.

On 6/5/2019 1:21 PM, Mark Sapiro wrote:
> On 6/5/19 8:55 AM, Dennis Putnam wrote:
>> I am trying to send a monthly reminder using 'mailman
>> /usr/lib/mailman/cron/mailpasswds'. However, the messages bounce due to
>> an invalid from address. How can I change the script to use a valid from
>> address? Thanks.
>
> Why is the From: invalid? it is the site list -owner address and the
> envelope is from the site list -bounces address. These should be
> deliverable addresses. There is a potential issue with virtual domains
> in that the domain of these addresses can be the virtual host domain and
> the address may not be valid in that domain.
>
> We currently add the site list address in each virtual domain in
> POSTFIX_STYLE_VIRTUAL_DOMAINS to the generated virtual-mailman file, but
> we don't add the -owner and -bounces addresses. I'll fix that. See
> <https://bugs.launchpad.net/mailman/+bug/1831777>.
>
> As far as changing these addresses is concerned, at lines 197-199 in the
> script you'll see
>
> siteowner = Utils.get_site_email(host, 'owner')
> sitereq = Utils.get_site_email(host, 'request')
> sitebounce = Utils.get_site_email(host, 'bounces')
>
> You could replace host in these lines with the literal host name which
> is valid for the site list in quotes like 'example.com'.
>
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] From Address for 'mailpasswds'

[Dennis Putnam]

I am trying to send a monthly reminder using 'mailman
/usr/lib/mailman/cron/mailpasswds'. However, the messages bounce due to
an invalid from address. How can I change the script to use a valid from
address? Thanks.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Ban Any AOL Users

[Dennis Putnam]

On 10/5/2018 2:40 PM, Mark Sapiro wrote:
> On 10/05/2018 11:23 AM, Dennis Putnam wrote:
>> I am not much on regexp but I want to prevent any AOL user from
>> subscribing. The examples in the FAQ are all overly complex for what I
>> want to do. Can someone show me the syntax to ban all AOL addresses? TIA.
>
> There are lots of regexps that will work, but
>
> ^.*[@.]aol\.com$
>
> will ban any address that ends with '@aol.com' or '.aol.com', i.e. any
> address in the aol.com domain or a sub-domain thereof.
>
>
Hi Mark,

Thanks. That is what I needed.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Ban Any AOL Users

[Dennis Putnam]

On 10/5/2018 3:35 PM, Robert Heller wrote:
> At Fri, 5 Oct 2018 14:23:59 -0400 Dennis Putnam  wrote:
>
>>
>> From: Dennis Putnam 
>> To: Mailman Users 
>> Message-ID: <0d662c43-c5ea-02c1-2b36-e11cf49e9...@bellsouth.net>
>> Subject: Ban Any AOL Users
>>
>> Content-Language: en-US
>>
>> I am not much on regexp but I want to prevent any AOL user from
>> subscribing. The examples in the FAQ are all overly complex for what I
>> want to do. Can someone show me the syntax to ban all AOL addresses? TIA.
> AOL was bought out by Yahoo and Yahoo merged (?) with Verizon. (Also, AOL way
> back when bought out netscape.) Right now, Yahoo handles @aol.com,
> @netscape.net, @yahoo.com, and @verizon.net. So if you want to avoid AOL DMARC
> issues, you really want to avoid Yahoo DMARC issues, so you need to ban 
> @aol.com, @netscape.net, @yahoo.com, and @verizon.net (at least).
Thanks for the reply. I am aware of all that but I have a totally
different reason for wanting to ban just the aol.com domain. In any case
you forgot to include the regexp I asked about.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Ban Any AOL Users

[Dennis Putnam]

I am not much on regexp but I want to prevent any AOL user from
subscribing. The examples in the FAQ are all overly complex for what I
want to do. Can someone show me the syntax to ban all AOL addresses? TIA.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Using REST API

[Dennis Putnam]

On 9/26/2018 12:23 PM, Mark Sapiro wrote:
> On September 26, 2018 10:14:06 AM CDT, Dennis Putnam  
> wrote:
>> Thanks for the reply. I saw that page but it didn't seem to answer what
>> I was looking for so I thought I needed to look elsewhere. I guess I am
>> missing something basic. I don't see where I specify from which list I
>> want to retrieve members?
>
> Scroll down to "We can also get just the members of a single mailing list."
>
>
Hi Mark,

Sheesh! How did I miss that? Sorry.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Using REST API

[Dennis Putnam]

On 9/26/2018 10:25 AM, Mark Sapiro wrote:
> On 9/26/18 6:33 AM, Dennis Putnam wrote:
>> I am reading through the REST API documentation and cannot find a way to
>> obtain a list of all the email addresses to a specific list. Can someone
>> point me to the proper page? TIA.
>
> <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/membership.html#subscribers>
>
> Also note that the focus of this list is Mailman 2.1. The corresponding
> list for Mailman 3 is mailman-us...@mailman3.org
> <https://lists.mailman3.org/mailman3/lists/mailman-us...@mailman3.org/>.
>

Hi Mark,

Thanks for the reply. I saw that page but it didn't seem to answer what
I was looking for so I thought I needed to look elsewhere. I guess I am
missing something basic. I don't see where I specify from which list I
want to retrieve members?



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Using REST API

[Dennis Putnam]

I am reading through the REST API documentation and cannot find a way to
obtain a list of all the email addresses to a specific list. Can someone
point me to the proper page? TIA.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman qrunner: [abrt] full crash report

[Dennis Putnam]

Hi Mark,

Thanks for the reply.

You are correct, there is nothing in the error log and this is all that
is in the qrunner log at that time:

Oct 20 06:43:20 2016 (3826) Master qrunner detected subprocess exit
(pid: 3842, sig: 6, sts: None, class: VirginRunner, slice: 1/1) [restarting]
Oct 20 06:43:21 2016 (30064) VirginRunner qrunner started.

For that particular day mailman was idle so there was no mailman log.
There was no list activity. That would seem to support your suggestion
that this is not a mailman problem but rather mailman is a victim of
some OS or external issue. Odd however, that it is always mailman that
is effected and yes, the dumps seem to be similar, although I did not
try to do a diff on any of them (that probably wouldn't mean much anyway).

On 10/31/2016 12:43 PM, Mark Sapiro wrote:
> On 10/31/2016 05:43 AM, Dennis Putnam wrote:
>> I have been getting these crash reports occasionally. Does this look
>> like a mailman problem or is mailman falling victim to some OS (Centos
>> 7) or other issue? TIA.
>>
>>
>> time: Thu 20 Oct 2016 06:43:20 AM EDT
>>
>> cmdline:/usr/bin/python /usr/lib/mailman/bin/qrunner 
>> --runner=VirginRunner:0:1 -s
>
> The crash is in VirginRunner, but it is at a very low level within
> Python itself.
>
> Is there anything in Mailman's logs. There probably won't be anything in
> the 'error' log specific to this event because the runner itself
> crashed, but there should be something in the qrunner log about the
> death and restart (and after the 10th time, it won't restart so you'd
> need to restart Mailman).
>
> Also, is it always VirginRunner and is the "core_backtrace:" always similar?
>
> VirginRunner processes Mailman generated notices. There should be
> messages in Mailman's logs and the system mail log which will indicate
> what kind of notice Mailman was trying to send.
>
> Also when VirginRunner dies, there will be a *.bak file left in the
> virgin queue and when the runner restarts, this file will be recovered
> and reprocessed, so there should be log messages (e.g. in Mailman's
> 'smtp' log) about that.
>
> In any case, this seems more of a Python or OS issue than Mailman per se.
>
>
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net




signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman qrunner: [abrt] full crash report

[Dennis Putnam]

I have been getting these crash reports occasionally. Does this look
like a mailman problem or is mailman falling victim to some OS (Centos
7) or other issue? TIA.










time: Thu 20 Oct 2016 06:43:20 AM EDT

cmdline:/usr/bin/python /usr/lib/mailman/bin/qrunner 
--runner=VirginRunner:0:1 -s
uid:41 (mailman)
abrt_version:   2.1.11
event_log:  
executable: /usr/bin/python2.7
global_pid: 3842
hostname:   dap002
kernel: 3.10.0-327.36.2.el7.x86_64
last_occurrence: 1477879758
pid:3842
pkg_arch:   x86_64
pkg_epoch:  3
pkg_name:   mailman
pkg_release:21.el7_1
pkg_version:2.1.15
pwd:/usr/lib/mailman
runlevel:   N 3
username:   mailman

cgroup:
:10:perf_event:/
:9:cpuset:/
:8:freezer:/
:7:blkio:/
:6:devices:/
:5:cpuacct,cpu:/
:4:memory:/
:3:hugetlb:/
:2:net_cls:/
:1:name=systemd:/system.slice/mailman.service

core_backtrace:
:{   "signal": 6
:,   "executable": "/usr/bin/python2.7"
:,   "stacktrace":
:  [ {   "crash_thread": true
:,   "frames":
:  [ {   "address": 140714112447991
:,   "build_id": "53c0918c85fa9cc08d2b57e76467631ab07554ae"
:,   "build_id_offset": 218615
:,   "function_name": "raise"
:,   "file_name": "/lib64/libc.so.6"
:}
:  , {   "address": 140714112453864
:,   "build_id": "53c0918c85fa9cc08d2b57e76467631ab07554ae"
:,   "build_id_offset": 224488
:,   "function_name": "abort"
:,   "file_name": "/lib64/libc.so.6"
:}
:  , {   "address": 140714126793150
:,   "build_id": "e0629f287ee1197290386973b9c5bd0576c35ee4"
:,   "build_id_offset": 1034686
:,   "file_name": "/lib64/libpython2.7.so.1.0"
:}
:  , {   "address": 140714126210812
:,   "build_id": "e0629f287ee1197290386973b9c5bd0576c35ee4"
:,   "build_id_offset": 452348
:,   "function_name": "PyFrame_New"
:,   "file_name": "/lib64/libpython2.7.so.1.0"
:}
:  , {   "address": 140714126678028
:,   "build_id": "e0629f287ee1197290386973b9c5bd0576c35ee4"
:,   "build_id_offset": 919564
:,   "function_name": "PyEval_EvalFrameEx"
:,   "file_name": "/lib64/libpython2.7.so.1.0"
:}
:  , {   "address": 140714126678112
:,   "build_id": "e0629f287ee1197290386973b9c5bd0576c35ee4"
:,   "build_id_offset": 919648
:,   "function_name": "PyEval_EvalFrameEx"
:,   "file_name": "/lib64/libpython2.7.so.1.0"
:}
:  , {   "address": 140714126678112
:,   "build_id": "e0629f287ee1197290386973b9c5bd0576c35ee4"
:,   "build_id_offset": 919648
:,   "function_name": "PyEval_EvalFrameEx"
:,   "file_name": "/lib64/libpython2.7.so.1.0"
:}
:  , {   "address": 140714126684349
:,   "build_id": "e0629f287ee1197290386973b9c5bd0576c35ee4"
:,   "build_id_offset": 925885
:,   "function_name": "PyEval_EvalCodeEx"
:,   "file_name": "/lib64/libpython2.7.so.1.0"
:}
:  , {   "address": 140714126684610
:,   "build_id": "e0629f287ee1197290386973b9c5bd0576c35ee4"
:,   "build_id_offset": 926146
:,   "function_name": "PyEval_EvalCode"
:,   "file_name": "/lib64/libpython2.7.so.1.0"
:}
:  , {   "address": 140714126788095
:,   "build_id": "e0629f287ee1197290386973b9c5bd0576c35ee4"
:,   "build_id_offset": 1029631
:,   "function_name": "run_mod"
:,   "file_name": "/lib64/libpython2.7.so.1.0"
:}
:  , {   "address": 140714126792638
:,   "build_id": "e0629f287ee1197290386973b9c5bd0576c35ee4"
:,   "build_id_offset": 1034174
:,   "function_name": "PyRun_FileExFlags"
:,   "file_name": "/lib64/libpython2.7.so.1.0"
:}
:  , {   "address": 140714126797385
:,   "build_id": "e0629f287ee1197290386973b9c5bd0576c35ee4"
:,   "build_id_offset": 1038921
:,   "function_name": "PyRun_SimpleFileExFlags"
:,   "file_name": "/lib64/libpython2.7.so.1.0"
:}
:  , {   "address": 140714126867359
:,   "build_id": "e0629f287ee1197290386973b9c5bd0576c35ee4"
:,   "build_id_offset": 1108895
:,   "function_name": "Py_Main"
:,   "file_name": 

Re: [Mailman-Users] Reply-To-List Header

[Dennis Putnam]

On 1/10/2016 6:34 PM, Mark Sapiro wrote:
> On 01/10/2016 03:07 PM, Dennis Putnam wrote:
>> Google is back up. I guess I was wrong in my original assessment. The
>> headers are indeed there including List-Post. The reply to list button
>> is displayed (I don't know why I sometimes don't get that but I will
>> have to look closer next time it happens). Anyway, I now see the
>> problem, but I don't know how/where to fix it. The address in the
>> List-Post is wrong. I can see how to turn it off/on in the documentation
>> but not how to customize it?
>
> It is the list posting address, i.e. listname@host_name, the same as the
> address in "To post a message to all the list members, send email to
> ..." on the list's listinfo page.
>
> If the local part in the List-Post: header is not the list name,
> something is seriously wrong, but I don't know what. If the domain is
> not what you think it should be, the list's host_name (on the General
> Options page) is wrong. You can change it there, although that may
> indicate issues with add_virtualhost and DEFAULT_*_HOST in mm_cfg.py.
>
> As I said before, if you sometimes don't see it, it might be because you
> are looking at a reply sent to you directly (To: or Cc:) and not from
> the list.
>
>
Got it. I guess the "Preferred Hostname" in the settings is somewhat of
a misnomer. It is really the preferred email hostname.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Reply-To-List Header

[Dennis Putnam]

On 1/14/2016 1:38 PM, Mark Sapiro wrote:
> On 01/14/2016 04:02 AM, Dennis Putnam wrote:
>> Got it. I guess the "Preferred Hostname" in the settings is somewhat of
>> a misnomer. It is really the preferred email hostname.
>
> Where are you seeing "Preferred Hostname"?
>
> Mailman's General Options page says
>
> Host name this list prefers for email.
> (Details for host_name)
>   
> which seems clear enough. I can't find the regexp 'preferred.?host' case
> insensitively anywhere in the GNU Mailman distribution.
>
>
Sorry, I guess I should not have put it in quotes. That title is not at
all clear to me that it means the domain name (not host name) for
replying email. I had that set to my email domain (bellsouth.net).
Changing it to the reply email domain (gmail.com) worked. I tried the
host name 'pop.gmail.com' and that did not.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Reply-To-List Header

[Dennis Putnam]

On 1/9/2016 4:43 PM, Mark Sapiro wrote:
> On 01/09/2016 01:10 PM, Dennis Putnam wrote:
>> Thanks for the reply. Those options are and apparently always have been
>> on. But none of those headers show up. I wonder if an SMTP server
>> somewhere along the way is stripping them out for some reason.
>
> Are there other Mailman headers such as X-BeenThere: and
> X-Mailman-Version: in the messages?
>
> Do you have any local modifications to Mailman/Handlers/CookHeaders.py?
>
> How do messages get from Mailman to you?
>
>
Thanks for the reply. Unfortunately I don't recall but I don't think so.
I am currently unable to test it to see as imap.gmail.com seems to be
down and has been for a while. The messages go from mailman on my
Postfix server to JetMail, to the subscriber's ISP (AT in my case).



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Reply-To-List Header

[Dennis Putnam]

On 1/10/2016 1:57 PM, Mark Sapiro wrote:
> On 01/10/2016 06:29 AM, Dennis Putnam wrote:
>> On 1/9/2016 4:43 PM, Mark Sapiro wrote:
>>> Are there other Mailman headers such as X-BeenThere: and
>>> X-Mailman-Version: in the messages?
>>>
>>> Do you have any local modifications to Mailman/Handlers/CookHeaders.py?
>>>
>>> How do messages get from Mailman to you?
>>>
>>>
>> Thanks for the reply. Unfortunately I don't recall but I don't think so.
>> I am currently unable to test it to see as imap.gmail.com seems to be
>> down and has been for a while.
>
> I use imap.googlemail.com for my gmail imap server, but that won't make
> any difference. I've just tested, and it appears that gmail/googlemail
> is now forcing SSL. I.e., neither imap.gmail.com nor imap.googlemail.com
> is answering port 143 connects, but both work with SSL on port 993.
>
>
>> The messages go from mailman on my
>> Postfix server to JetMail, to the subscriber's ISP (AT in my case).
>
> The next time you receive a post from the list in question, view the
> source (More -> View Source in Thunderbird). If you don't see the List-*
> headers, copy ALL of the headers and post them here. You can munge any
> personal info if you like.
>
>
Google is back up. I guess I was wrong in my original assessment. The
headers are indeed there including List-Post. The reply to list button
is displayed (I don't know why I sometimes don't get that but I will
have to look closer next time it happens). Anyway, I now see the
problem, but I don't know how/where to fix it. The address in the
List-Post is wrong. I can see how to turn it off/on in the documentation
but not how to customize it?



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Reply-To-List Header

[Dennis Putnam]

On some mailman lists I receive messages in which Thunderbird displays a
"Reply to List" button. However, on my own lists that does not happen.
What header is TB relying on to get that and what setting do I need to
change my mailman for that to happen? TIA.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Reply-To-List Header

[Dennis Putnam]

On 1/9/2016 1:36 PM, Mark Sapiro wrote:
> On 01/09/2016 06:14 AM, Dennis Putnam wrote:
>> On some mailman lists I receive messages in which Thunderbird displays a
>> "Reply to List" button. However, on my own lists that does not happen.
>> What header is TB relying on to get that and what setting do I need to
>> change my mailman for that to happen? TIA.
>
> Thunderbird and many other MUAs rely on the RFC 2369 List-Post: header
> for "reply to list". There are six RFC 2369 List-* headers; List-Id:,
> List-Unsubscribe:, List-Archive:, List-Post:, List-Help: and
> List-Subscribe:. Mailman's adding of these headers is controlled by the
> lists General Options include_rfc2369_headers and
> include_list_post_header settings.
>
> If include_rfc2369_headers is No, none of these headers will be added.
> If include_rfc2369_headers is Yes, List-Post: will be added only if
> include_list_post_header is Yes, List-Archive will be added only if the
> list is archiving and the other four will be added.
>
> So to ensure posts received from the list have a List-Post header, both
> include_rfc2369_headers and include_list_post_header must be Yes.
>
> Also note that if your "Avoid duplicate copies of messages?" setting on
> a list is Yes and you are directly addressed in a reply, the copy you
> receive doesn't come from the list and won't have any Mailman headers.
>
>
Thanks for the reply. Those options are and apparently always have been
on. But none of those headers show up. I wonder if an SMTP server
somewhere along the way is stripping them out for some reason.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] list-owner getting spammed

[Dennis Putnam]

On 9/30/2015 1:25 PM, Stephen J. Turnbull wrote:
> Dennis Putnam writes:
>
>  > Thanks for the reply. I am using fetchmail to retrieve each
>  > mailbox. I am familiar with spamassassin but I don't think I can
>  > integrate that with fetchmail. I'm not sure what I could use.
>
> Hi, Dennis -- I use fetchmail (for personal mail), but fetchmail
> normally delivers to a local MDA/LDA/MTA.  Specifically, it can
> deliver using an SMTP protocol, or it can deliver over a pipe using
> the --mda option.  So I invoke "fetchmail --mda maildrop" (maildrop is
> an MDA developed by the Courier MTA/IMAP project, I think).  I don't
> currently use maildrop's filtering capabilities, but I would suppose
> that to access Spamassassin I would use the "xfilter" capability of
> Maildrop.  I've also used procmail, but the fetchmail docs recommend
> maildrop, so you might want to use that program.
>
> You might also find that maildrop's built-in filtering is sufficient
> to your purposes.  The advantage of SpamAssassin is that
> "crowd-sources" information about past spam -- if you were lucky, you
> update the SA rule set and automatically get protection from the most
> recent spam.
>
> Steve
>
Hi Steve,

Thanks, I'll look into it.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] list-owner getting spammed

[Dennis Putnam]

Hi Jason,

Thanks for the reply. I am using fetchmail to retrieve each mailbox. I
am familiar with spamassassin but I don't think I can integrate that
with fetchmail. I'm not sure what I could use.

On 9/30/2015 3:00 AM, Jayson Smith wrote:
> Hi,
>
> I was having this happen, but in my case there was a very easy way to
> get rid of it. Whoever set up that spam mailing list made a very big
> mistake. They chose to send their spam to the owner address *and* the
> address for posting to the list! Normally there is absolutely no valid
> reason for sending the same message to those two particular
> recipients, so I installed Milter-Greylist and set it up to block
> those messages at the SMTP level. Hasn't stopped the spammers, but at
> least my system doesn't have to process the spam.
>
> If something like this is going on in your case, that might be an
> option. If not, and if the spam has nothing in common, as far as I
> know there's nothing Mailman can do in this situation, you'll need to
> employ spam filtering before Mailman sees the mail.
>
> Jayson
>
> On 9/29/2015 7:32 AM, Dennis Putnam wrote:
>> The list-owner of one of my lists is getting spammed. Is there an easy
>> way to block that? TIA.
>>
>>
>>
>> --
>> Mailman-Users mailing list Mailman-Users@python.org
>> https://mail.python.org/mailman/listinfo/mailman-users
>> Mailman FAQ: http://wiki.list.org/x/AgA3
>> Security Policy: http://wiki.list.org/x/QIA9
>> Searchable Archives:
>> http://www.mail-archive.com/mailman-users%40python.org/
>> Unsubscribe:
>> https://mail.python.org/mailman/options/mailman-users/jaybird%40bluegrasspals.com
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives:
> http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe:
> https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net
>




signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] list-owner getting spammed

[Dennis Putnam]

The list-owner of one of my lists is getting spammed. Is there an easy
way to block that? TIA.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Fwd: [Mailman] Cron mailman@dap002 /usr/lib/mailman/bin/withlist -r get_bounce_info cufsalumni|mail -s cufsalumni List Bounce Report d...@bellsouth.net

[Dennis Putnam]

I get this traceback when I do bounce processing via cron (see subject
line). Is this something I need to worry about? It seems to be working
in spite of this error. Although perhaps it is only partially working
and I am just unaware of what part has failed.


 Forwarded Message 
Subject:[Mailman] Cron mailman@dap002 /usr/lib/mailman/bin/withlist
-r get_bounce_info cufsalumni|mail -s cufsalumni List Bounce Report
d...@bellsouth.net
Date:   Mon, 1 Jun 2015 00:00:02 -0400 (EDT)
From:   (Cron Daemon) d...@bellsouth.net
Reply-To:   d...@bellsouth.net
To: d...@bellsouth.net



Importing get_bounce_info...
Traceback (most recent call last):
  File /usr/lib/mailman/bin/withlist, line 302, in module
main()
  File /usr/lib/mailman/bin/withlist, line 270, in main
__import__(module)
ImportError: No module named get_bounce_info
Null message body; hope that's ok
___
Mailman mailing list
mail...@bellsouth.net
https://dap002.dyndns-ip.com/mailman/listinfo/mailman





signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Fwd: [Mailman] Cron mailman@dap002 /usr/lib/mailman/bin/withlist -r get_bounce_info cufsalumni|mail -s cufsalumni List Bounce Report d...@bellsouth.net

[Dennis Putnam]

On 6/1/2015 11:24 AM, Mark Sapiro wrote:
 On 06/01/2015 04:49 AM, Dennis Putnam wrote:
 I get this traceback when I do bounce processing via cron (see subject
 line). Is this something I need to worry about? It seems to be working
 in spite of this error. Although perhaps it is only partially working
 and I am just unaware of what part has failed.

 I don't know what you mean by seems to be working, but this traceback

 ...
 Importing get_bounce_info...
 Traceback (most recent call last):
   File /usr/lib/mailman/bin/withlist, line 302, in module
 main()
   File /usr/lib/mailman/bin/withlist, line 270, in main
 __import__(module)
 ImportError: No module named get_bounce_info
 says you haven't obtained the get_bounce_info.py script from
 https://www.msapiro.net/scripts/get_bounce_info.py or
 http://fog.ccsf.edu/~msapiro/scripts/get_bounce_info.py and saved it
 as /usr/lib/mailman/bin/get_bounce_info.py



Hi Mark,

Thanks for the reply. I mean, I get the expected output generated by my
cron job. Or at least I get some of it.

Somehow I missed that step. I guess when I migrated to CentOS 7, I
expected it to be part of the install and really didn't look at the
issue until now. I was busy putting out too many other fires introduced
by the upgrade.


signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Importing from 2.1.12-18.el6 to 2.1.15-17.el7

[Dennis Putnam]

On 5/15/2015 3:28 PM, Dean Collins wrote:
 This is Mailman 2.1.15-17, qmail, CentOS 7.

 I've got a new server and set up a test list, say, myl...@mydomain.com.

 Subscribers include m...@mydomain.com (the same domain the list is on) and
 various addresses from other domains/servers (a couple of servers I run,
 plus Gmail and ATT.)

 Mail sent to myl...@mydomain.com from any subscriber gets archived -- and
 distributed to m...@mydomain.com. But none of the other subscribers receive
 the list mail.

 Non-list, regular mail works fine. Using m...@mydomain.com I can send to
 anyone (and they receive it) and receive from anyone.

 I know less about mail than just about anything else in the world, so any
 suggestions as to what might be wrong would be appreciated. Thanks!

 Dean


What outgoing SMTP server are you trying to use? If smtp.att.yahoo.com
your problem is in the postfix config, not mailman. ATT is so heavily
restricted it is nearly impossible to set up. I use MailJet as my
outgoing server for mailman instead.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman on CentOs

[Dennis Putnam]

Hi Danil,

Sorry, I thought that was the version you were looking for. The version
from the CentOS 6 repos was older but maybe they upgraded it since I
migrated about 2 months ago.

On 5/11/2015 2:58 PM, Danil Smirnov wrote:
 2015-05-08 14:01 GMT+03:00 Dennis Putnam d...@bellsouth.net:
 If you are going to install a fresh CentOS why are you not using the
 latest version (7)? That will solve all your problems because the CentOS
 7 repos have the later version of mailman.
 Hi Dennis!

 Could you be more specific?
 I don't see last Mailman version on my newly installed Centos 7 box -
 just 2.1.15 one.
 What repo do you use?

 Many thanks in advance,
 Danil
 --
 Mailman-Users mailing list Mailman-Users@python.org
 https://mail.python.org/mailman/listinfo/mailman-users
 Mailman FAQ: http://wiki.list.org/x/AgA3
 Security Policy: http://wiki.list.org/x/QIA9
 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
 Unsubscribe: 
 https://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net





signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman on CentOs

[Dennis Putnam]

On 5/7/2015 9:26 PM, Eric Lamer wrote:
 I will reinstall a brand new CentOs 6.5 then install Mailman, should I 
 install directly version 2.1.20 or should I use yum first then upgrade?







 EricLamer
 CEO
 Phoenix Secure Inc.
  514-914-5599
   514-800-2556
  e...@phoenixsecure.com







 -Original Message-
 From: Mailman-Users 
 [mailto:mailman-users-bounces+eric=phoenixsecure@python.org] On Behalf Of 
 Mark Sapiro
 Sent: Thursday, May 7, 2015 9:24 PM
 To: mailman-users@python.org
 Subject: Re: [Mailman-Users] Mailman on CentOs

 On 05/07/2015 06:01 PM, Eric Lamer wrote:
 I tried to upgrade to version 2.1.20 or 2.1.18 and I have a lot of problems, 
 io error etc.

 We'd be happy to help if you post tracebacks or mailman error log messages.

 Lot's of i/o error issues are permissions, and Mailman's bin/check_perms -f 
 run as root will fix most of them.

 --
 Mark Sapiro m...@msapiro.netThe highway is for gamblers,
 San Francisco Bay Area, Californiabetter use your sense - B. Dylan

If you are going to install a fresh CentOS why are you not using the
latest version (7)? That will solve all your problems because the CentOS
7 repos have the later version of mailman.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] [SPAM] - Re: Mailman on CentOs - Sender is forged (SPF Fail)

[Dennis Putnam]

On 5/8/2015 11:32 AM, Eric Lamer wrote:
 Hi,

Is it normal that /var/www/html/mailman does not exist?


 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] 
 
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [- Mailman 
 Version: 2.1.20 -]
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [- Traceback 
 --]
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] Traceback (most 
 recent call last):
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70]   File 
 /usr/lib/mailman/scripts/driver, line 85, in run_main
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] immediate=1)
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70]   File 
 /usr/lib/mailman/Mailman/Logging/StampedLogger.py, line 52, in __init__
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] 
 Logger.__init__(self, category, nofail, immediate)
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70]   File 
 /usr/lib/mailman/Mailman/Logging/Logger.py, line 50, in __init__
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] self.__get_f()
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70]   File 
 /usr/lib/mailman/Mailman/Logging/Logger.py, line 68, in __get_f
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] 1)
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70]   File 
 /usr/lib64/python2.6/codecs.py, line 881, in open
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] file = 
 __builtin__.open(filename, mode, buffering)
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] IOError: [Errno 13] 
 Permission denied: '/var/lib/mailman/logs/error'





 EricLamer
 CEO
 Phoenix Secure Inc.
  514-914-5599
   514-800-2556
  e...@phoenixsecure.com






 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [- Python 
 Information -]
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.version = 
 2.6.6 (r266:84292, Jan 22 2014, 09:42:36)
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [GCC 4.4.7 20120313 
 (Red Hat 4.4.7-4)]
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.executable  = 
 /usr/bin/python
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.prefix  = 
 /usr
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.exec_prefix = 
 /usr
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.path= 
 ['/usr/lib/mailman/pythonlib', '/usr/lib/mailman', 
 '/usr/lib/mailman/scripts', '/usr/lib/mailman', '/usr/lib64/python26.zip', 
 '/usr/lib64/python2.6/', '/usr/lib64/python2.6/plat-linux2', 
 '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', 
 '/usr/lib64/python2.6/lib-dynload', '/usr/lib/python2.6/site-packages']
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.platform= 
 linux2
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [- Environment 
 Variables -]
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_COOKIE: 
 mailman+admin=2802006945c14a557328006531623265363133383561616563316138343762663435616335306536333632376633393265
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_SOFTWARE: 
 Apache/2.2.15 (CentOS)
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSCRIPT_NAME: 
 /mailman/listinfo
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_SIGNATURE: 
 addressApache/2.2.15 (CentOS) Server at list.sipro.com Port 80/address
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70]
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tREQUEST_METHOD: GET
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tPATH_INFO: /mailman
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_PROTOCOL: 
 HTTP/1.1
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tQUERY_STRING:
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_USER_AGENT: 
 Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like 
 Gecko) Chrome/42.0.2311.135 Safari/537.36
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_CONNECTION: 
 keep-alive
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_NAME: 
 list.sipro.com
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tREMOTE_ADDR: 
 192.168.2.2
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tPATH_TRANSLATED: 
 /var/www/html/mailman
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_PORT: 80
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_ADDR: 
 172.16.4.225
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tDOCUMENT_ROOT: 
 /var/www/html
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tPYTHONPATH: 
 /usr/lib/mailman
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSCRIPT_FILENAME: 
 /usr/lib/mailman/cgi-bin/listinfo
 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_ADMIN: 
 

Re: [Mailman-Users] Admin Requests Not Working

[Dennis Putnam]

On 2/5/2015 12:40 AM, Mark Sapiro wrote:
 On 02/04/2015 05:25 AM, Dennis Putnam wrote:
 Well, I thought the requests had disappeared but I was wrong. I'm not
 sure why they seemed to be gone other than operator error. In any case I
 searched through the logs and found nothing except this:

 192.168.0.102 - - [02/Feb/2015:15:51:30 -0500] POST
 /mailman/admindb/mailman HTTP/1.1 302 222 - Mozilla/5.0 (Windows NT
 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0

 Which is perfectly normal. I guess I need to turn on some kind of debug
 to see what this thing is doing. Thanks.

 When you go to the admindb page for the list, look at the exact URL of
 the page in the address bar. Then depending on what you actually do,
 i.e. accept/reject/discard message(s) from the summary page or go to a
 detail link and accept/reject/discard message(s) from there, look at the
 exact URL of any other pages in the address bar and also look at the
 source of all the pages you visit for the URLs in action= elements in
 form tags and the URLs in links you visit.

 Do all these have the exact same host name (relative actions/links are
 the same host as that of the URL of the page and are OK) and scheme? You
 are looking for anything different, i.e. a different host or scheme
 (http vs. https).

 One common way this occurs is the form action on an https page is an
 http url which gets redirected by the web server to https. The redirect
 loses the POST data. This is covered in the FAQ at
 http://wiki.list.org/x/4030602 but you may have missed it.

 If you need more than that, you'll have to add debug logging to
 Mailman/Cgi/admindb.py such as

 after

 def main():
 global ssort - you may not have this line
 # Figure out which list is being requested
 parts = Utils.GetPathPieces()


 add

 for p in parts:
 syslog('debug', 'Part from Utils.GetPathPieces(): %s', p)

 and after

 # Make sure the user is authorized to see this page.
 cgidata = cgi.FieldStorage(keep_blank_values=1)


 add

 for k, v in cgidata.items():
 syslog('debug', 'cgidata: %s: %s', k, v)

 This will write entries to a 'debug' log in Mailman's logs/ directory
 (or /var/log/mailman/debug in RHEL/CentOS) and you can then see if the
 script is actually getting the things it should be getting.


Hi Mark,

They all look consistent to me.

https://server/mailman/admindb/...

I will try your debug sometime this weekend. Thanks.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org