Re: [Mailman-Users] Finding list user in redacted FBL reports

[David Josephson]

Wouldn't it be simple enough just to use rot13, or the senders name 
without the domain?


On 8/7/2019 5:20 PM, Carl Zwanzig wrote:

On 8/7/2019 1:17 PM, Scott Neader wrote:

I need a way to put some clue about the recipient into the footer, when
personalization is enabled.  I've seen some past solutions where admins
were successful in adding some type of hash or encoded version of the
recipient's email address into the footer, but the steps to get that done
were not shared.  Open to other ideas.


See-
https://wiki.list.org/DOC/What%20variables%20can%20I%20use%20in%20the%20headers%20and%20footers%20added%20to%20messages%20by%20Mailman%3F 



I regularly get email from a list with the footer (redacted)
===
UUU mailing list
u...@domain.org
http://listsmgt.DOMAIN.org/mailman/listinfo/UUU
Sent to Carl Zwanzig at zb...@sonic.net
All posts to the UUU mailing list are copyright the individual senders.
===


z!

--
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 not found' after kernel upgrade

[David Josephson]

Never mind. Beware of yum-update. I have mailman in /usr/local, and yum update 
installed a new copy in /usr/lib, and helpfully updated the script in 
/etc/smrsh to point to the new one. &*&*(#^!!

On Aug 19, 2016, at 2:29 PM, David Josephson wrote:

> We have been running Mailman 2.1.18-1 for a long time, on a Centos 7 system 
> with sendmail. We do a yum update every few months. Coincident with the last 
> one, which included a kernel update to 3.10, mailman stopped working, posts 
> are bounced back with this message:
> 
>- The following addresses had permanent fatal errors -
> "|/etc/smrsh/mailman post ampex"
> (reason: 1)
> (expanded from: <am...@lena.recordist.com>)
> 
>- Transcript of session follows ---
--
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 not found' after kernel upgrade

[David Josephson]

We have been running Mailman 2.1.18-1 for a long time, on a Centos 7 
system with sendmail. We do a yum update every few months. Coincident 
with the last one, which included a kernel update to 3.10, mailman 
stopped working, posts are bounced back with this message:


- The following addresses had permanent fatal errors -
"|/etc/smrsh/mailman post ampex"
 (reason: 1)
 (expanded from: )

- Transcript of session follows -
post script, list not found: ampex
554 5.3.0 unknown mailer error 1

Mailman log says the same thing,

Aug 18 05:46:09 2016 post(1452): post script, list not found: ampex

Maillog says

Aug 19 13:29:43 lena sendmail[10931]: u7JKTgkW010930: 
to="|/etc/smrsh/mailman post ampex", ctladdr= 
(8/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=32792, 
dsn=5.3.0, stat=unknown mailer error 1


Qrunner is running, sendmail is working normally. SELinux is disabled. 
There is nothing but default in mm_cfg.py, which hasn't changed since 2015.


The yum update can't be rolled back because of the kernel upgrade.

I noticed that the symbolic link in /etc/smrsh was touched about the 
same time as the update.


Clues?
--
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] ERROR in 2.1.5

[David Josephson]

On 10/31/13 6:01 PM, Janice Boothe wrote:

When I try to log into the admin page for my list (recently upgraded to 
MM2.1.5) I get the following...


Bug in Mailman version 2.1.15
We're sorry, we hit a bug!
Please inform the webmaster for this site


I got this error once in an upgrade, it was a file permissions issue. 
Did you run check_perms?


--
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] SMTP problem after recovering from disk full, clues?

[David Josephson]

A very old and well-used list has been fine for years on this box, 
running Mailman 2.1.10 on Red Hat 7.2. The disk got full and everything 
crashed. I was able to clear out a couple GB of space and get all 
services running again, but now mailman will not send any messages, 
either to the list admins or to members. Just before it died completely, 
admins got a We're sorry, we hit a bug email.


Incoming spam is properly discarded and logged in /logs/vette. Incoming 
posts show up in /logs/post showing 250 failures (there are 698 members 
on the list). The web interface seems to be functioning properly.


/logs/smtp-failure shows
Low level smtp error: (-2, 'Name or service not known'), msgid: ...
and then

May 19 22:02:15 2013 (16851) Low level smtp error: please run connect() 
first, msgid: ...


and then listings of each of the addresses where delivery was attempted, 
each with delivery to xx@yy failed with code -1: (-2, 'Name or service 
not known')


Nothing has changed with /etc/smrsh or sendmail, I can send and receive 
mail with mutt just fine.


When I reinstalled mailman and sent it a test post, I got the group 
mismatch error reminder in the returned mail message that I needed to 
run configure with --with-mail-gid=mail, which I did, now test messages 
to lists don't bounce back to the sender, they just don't get out of the 
server.


Following some of the FAQs I've looked with dumpdb and find no obviously 
corrupt .pck files. I moved ~mailman/lists and ~mailman/archives off 
somewhere else, reinstalled the same version, brought those directories 
back to ~mailman, and get the same behavior.


What am I missing?

--
David Josephson
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] SMTP problem after recovering from disk full, clues?

[David Josephson]

On 05/20/2013 05:20 AM, Richard Shetron wrote:

I've noticed that if mailman is stopped/crashes/system reboot/etc. and
there is anything in mailman/qfiles/maildir/cur that stuff seems to just
hang in mailman until you stop mailman, clear this directory, and then
restart mailman.  May not be your problem but try checking it.



I am looking for this kind of bug, as it's an old version of Mailman, 
but there is no maildir here, as Mark mentioned, and all of qfiles was 
generated new when I rebuilt Mailman.


Also check_db and check_perms show no errors.

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] SMTP problem after recovering from disk full, clues?

[David Josephson]

Yes... but nothing changed on the server in /etc ... it worked fine a 
couple of days ago, then there was a disk full, now it doesn't. Nothing 
has changed in /etc for several months, and regular mail client works.



On 05/19/2013 10:45 PM, David Josephson wrote:


/logs/smtp-failure shows
Low level smtp error: (-2, 'Name or service not known'), msgid: ...
and then



This issue can have several different underlying causes including things
like permissions on /etc/hosts and /etc/resolv.conf. See the FAQs at
http://wiki.list.org/x/-IA9 and http://wiki.list.org/x/AoE9 and some
posts linked therefrom for various tests and debugging techniques you
can use to help find the cause.



--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] SMTP problem after recovering from disk full, clues?

[David Josephson]

On 5/20/2013 11:12 AM, Mark Sapiro wrote:

On 05/20/2013 11:05 AM, David Josephson wrote:

Yes... but nothing changed on the server in /etc ... it worked fine a
couple of days ago, then there was a disk full, now it doesn't. Nothing
has changed in /etc for several months, and regular mail client works.


Yes, but read the FAQs and do some of the tests outlined therein and in
list posts linked therefrom to help you figure out what the problem is.


Thank you. /etc/hosts contained a line

127.0.0.1 localhost.localdomain

Previously that was enough for Mailman. Adding 'localhost' on that line 
fixed the problem. What would have changed to cause this?

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] All members treated as nonmembers redux

[David Josephson]

We had a list (MM 2.1.5 under sendmail) suddenly stop working, with logs
showing that all incoming messages (from members and nonmembers alike)
were being discarded. Configs had been set to discard without copying to
the list admin, and it is a relatively low volume list, so it wasn't
noticed for a while. During troubleshooting we re-enabled
forward_auto_discards and the moderator approval page for each incoming
post showed post by nonmember to members-only list *and* poster is a
member of ... list.  Following up on an earlier answer to this sort of
problem, we commented out the SENDER_HEADERS = ('from') line in
mm_cfg.py and this fixed the problem. Question is, how did this break in
the first place? And why did it apply to only one list? Other lists, and
new lists created since then, work fine. There is mention of being able
to modify member checking on a per-list basis but I was not able to find
where to do this.

There was a server reboot (for other reasons) at about the same time
this problem appeared.

During this debugging process we also upgraded from 2.1.5 to 2.1.6,
could this have been a default of the 2.1.6 install, and the real
problem was something else?

Thanks ...

David Josephson

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp