in a new setup I have a problem with the would-be subscriber sending to
list-request and the /var/log/mailman/subscribe file shows the request
at an appropriate place with the correct info and status "pending"
The user has not received a verification email. Where should I look to
see what has happened? I've checked the mailman administration page for
that list and see no pending admin tasks. Mailman 2.1.16 on a ubuntu
Reporter to Mahatma Ghandi after his tour of east London
"What do you think of western civilization, Mr. Ghandi?"
Ghandi - "I think it would be an excellent idea!"
Running Mailman 2.1.12 on CentOS 6.8. We have a regular-delivery subscriber who is somehow receiving both regular and digest delivery for the same list. She only wants regular delivery. Here’s what we’ve checked so far:
* Looked at Mailman’s web interface. Confirmed user is listed there as a non-digest, plain text subscriber
* Double-checked by running the # list_members –r <listname> command. Reran with the –d option. Output matched results above.
* Several people at her office are subscribers. Asked user if she receives mail on behalf of any current/former coworkers. She said no.
* In case user misunderstood what “digest” means, asked her to forward us a copy of a recent delivery. Sure enough, it’s the digest.
* Restarted Mailman via # sudo /etc/init.d/mailman restart
* Manually unsubscribed user via remove_members and re-added her for regular delivery
* Checked /var/log/mailman to see if anything useful there. Didn’t find anything relevant to the problem.
It’s very possible I’ve overlooked something basic.
Would be nice to see “under the hood” how Mailman is handling the user’s subscription. Am guessing there’s a way but am a fairly newbie sysadmin and am not familiar enough with Mailman to know.
Any suggestions on how to pin down and solve the problem? Thanks in advance for your time and advice.
I'm administrator/moderator of several Mailman mailing lists through my hosting
One of the lists MBRS(a)OptimistClubOfStAndrews.org
<mailto:MBRS@OptimistClubOfStAndrews.org> is bouncing to addresses with
sc.rr.com and earthlink.com domains.
I've deleted and rebuilt the list at least once, more I think. The bounces
How can I fix the problem?
Donald R Keating
I have a single moderation notification for a message that was sent to the default mailman alias.
I clicked on the “Delete” radio button and hit “Submit all data”.
The page refreshes but the moderation notification is still there.
1. How do I fix the situation where the notification isn’t removed (presumably by deleting the notification)?
2. How do I delete the notification?
Thank you, Caesar.
On Wed, Dec 7, 2016 at 3:09 PM, Adam Goldberg <adam(a)agp-llc.com> wrote:
> I use SES with Mailman. Just turn "munge from addresses" on, works fine.
> The only address/domain you have to have verified is the -bounce address
> Adam Goldberg
> 202-507-9900 <(202)%20507-9900>
> On Wed, Dec 7, 2016 at 3:07 PM -0500, "Leon" <best.sum(a)gmail.com> wrote:
> Hi, This problem is not caused by mailman, but I still want to give it a
> shot here. I'm hosting a mailing list on top of mailman. Emails are
> supposed to be sent out by AWS ses. However, ses requires that sender
> address must be verified, which leads to a problem that emails sent by
> subscribers to mailing list cannot be sent to other subcirbers, since their
> addresses are not verified. And it is impossible to verified every
> subscriber. Are there smtp service providers allowing unverified email
> address to send out emails, or do I have other solutions?
> Mailman-Users mailing list Mailman-Users(a)python.org
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/
> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/
On 12/05/2016 06:12 PM, vince(a)vheuser.com wrote:
> Nope. Clueless. -- Pure gambling.
> So how do I block "subscribe spam".
> Currently I am being inundated-- one every 4 minutes..
> Any suggestions appreciated.
First, back out any changes you made from
SUBSCRIBE_FORM_SECRET = "some secret unique to your site"
(replacing "some secret unique to your site" with your own secret
string) in mm_cfg.py.
This may or may not help much. The bots that have been attacking the
python.org lists from time to time have figured out to GET the form
first and delay before submitting it. The best we can do is use the
GLOBAL_BAN_LIST feature implemented in 2.1.21, and without that put
patterns in every list's ban_list.
The latest one only lasted for a few days. the last few were blocked
with patterns like
They tend to be a constant user name at gmail.com with all combinations
of interspersed dots (which gmail ignores).
There is a script at <https://www.msapiro.net/scripts/add_banned.py>
that can be used to add a pattern to all list's ban_list and a script at
<https://www.msapiro.net/scripts/erase> that can be used to remove all
the pending subs, etc. for a pattern.
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
Trying to stop subscribe spam following Mark's instructions here:
When activated, I get this html on the listinfo page:
"Bug in Mailman version 2.1.18
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited, but
the webmaster can find this information in the Mailman error logs."
And this is in the error log:
admin(31878): File "/var/lib/mailman/scripts/driver", line 117, in
admin(31878): File "/var/lib/mailman/Mailman/Cgi/listinfo.py", line 65, in
admin(31878): list_listinfo(mlist, language)
admin(31878): File "/var/lib/mailman/Mailman/Cgi/listinfo.py", line 198,
admin(31878): mlist.internal_name() +
admin(31878): TypeError: unsupported operand type(s) for +: 'bool' and 'str'
admin(31878): [----- Python Information -----]
admin(31878): sys.version = 2.7.9 (default, Mar 1 2015, 18:22:53)
admin(31878): sys.executable = /usr/bin/python
admin(31878): sys.prefix = /usr
admin(31878): sys.exec_prefix = /usr
admin(31878): sys.path = ['/var/lib/mailman/pythonlib',
'/var/lib/mailman', '/usr/lib/mailman/scripts', '/var/lib/mailman',
admin(31878): sys.platform = linux2
admin(31878): [----- Environment Variables -----]
admin(31878): HTTP_REFERER: http://lists.[redacted].com/
admin(31878): CONTEXT_DOCUMENT_ROOT: /usr/lib/cgi-bin/mailman/listinfo
admin(31878): SERVER_SOFTWARE: Apache/2.4.10 (Debian)
admin(31878): CONTEXT_PREFIX: /listinfo
admin(31878): SERVER_SIGNATURE: <address>Apache/2.4.10 (Debian) Server at
lists.[redacted].com Port 80</address>
admin(31878): REQUEST_METHOD: GET
admin(31878): PATH_INFO: /action-list
admin(31878): SERVER_PROTOCOL: HTTP/1.1
admin(31878): HTTP_USER_AGENT: Mozilla/5.0 (Windows NT 5.1; rv:50.0)
admin(31878): HTTP_CONNECTION: keep-alive
admin(31878): SERVER_NAME: lists.[redacted].com
admin(31878): REMOTE_ADDR: [redacted]
admin(31878): SERVER_PORT: 80
admin(31878): SERVER_ADDR: [redacted]
admin(31878): DOCUMENT_ROOT: /home/[redacted]/www/lists
admin(31878): PYTHONPATH: /var/lib/mailman
admin(31878): SCRIPT_FILENAME: /usr/lib/cgi-bin/mailman/listinfo
admin(31878): SERVER_ADMIN: [no address given]
admin(31878): HTTP_DNT: 1
admin(31878): HTTP_HOST: lists.[redacted].com
admin(31878): SCRIPT_NAME: /listinfo
admin(31878): HTTP_UPGRADE_INSECURE_REQUESTS: 1
admin(31878): HTTP_CACHE_CONTROL: max-age=0
admin(31878): REQUEST_URI: /listinfo/action-list
admin(31878): GATEWAY_INTERFACE: CGI/1.1
admin(31878): REMOTE_PORT: 1515
admin(31878): HTTP_ACCEPT_LANGUAGE: en-US,en;q=0.5
admin(31878): REQUEST_SCHEME: http
admin(31878): HTTP_ACCEPT_ENCODING: gzip, deflate
I am new to Python
I don't know how to verify whether the config change "mlist.hash_subscribe =
True" actually happened.
Is there a hash code in the listinfo page? Where is that?
Anyone know what is wrong?
I’m in Education and recently moved mailman to a linux box. Now when I send a message to the list serve, I don’t receive the email and don’t know that it was sent. Is this correctable?
I would appreciate any help on this issue.