I moved my mailman list from an old Solaris server to the new Linux server.
I did a tarball of the "lists" directory and placed it in the mailman config
I do not have exim up and running yet. So, all I can do at the moment is
admin stuff. But, when I go to:
http://vidiot.net/mailman/listinfo it says that there are no public lists.
But, there are a few. Going to http://vidiot.net/mailman/listinfo/foolist
says that the list does not exit.
Besides copying over the lists file from old to new, what else is needed
for the admin tools to "see" the lists?
Thanks for any pointers.
e-mail: vidiot(a)vidiot.com | vidiot(a)vidiot.net /~\ The ASCII
6082066843(a)email.uscc.net (140 char limit) \ / Ribbon Campaign
Visit - URL: http://vidiot.com/ X Against
http://vidiot.net/ / \ HTML Email
"You're Sherlock Holmes, wear the damn hat!" - Watson to Sherlock
Sherlock - The Abominable Bride - 1/01/16
I upgraded our mail server to the Fedora 26 and mailman stopped working. Here
is the error that I get:
This is the mail system at host mail.eng.lsu.edu.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<test_l(a)eng.lsu.edu>: Command died with status 1:
"/usr/local/mailman/mail/mailman post test_l". Command output: Traceback
(most recent call last): File "/usr/local/mailman/scripts/post", line 69,
in <module> main() File "/usr/local/mailman/scripts/post", line 64,
in main tolist=1, _plaintext=1) File
"/usr/local/mailman/Mailman/Queue/Switchboard.py", line 136, in enqueue
fp = open(tmpfile, 'w') IOError: [Errno 30] Read-only file system:
If checked all of the ownership and permissions on that folder
(/usr/local/mailman/qfiles/in) both with the tool and manually and can't find
out of the ordinary.
Any ideas what may be causing this issue?
Chris Schwehm, Director
Office of Engineering Technology Services - 3324A Patrick F. Taylor Hall (CEBA)
Louisiana State University Internet: chris(a)rsip.lsu.edu
Baton Rouge, LA 70803 (225) 578-5262
WWW Home Page: http://www.rsip.lsu.edu/chris
I've been looking around and I'm not sure it exists but figured I would check here. I'm looking for a way to get a list's subscribe_policy from the command line.
We are syncing our lists with some user lists in our system but I only want to do this from mailman if 'require approval' or 'confirm and approve' are set. If anyone has any thoughts on how to verify this I'd appreciate the pointers.
I can't find the admistrator docs for Mailman 2.1.x (I am running 2.1.16). I
recently (today) got a Let's Encrypt SSL cert for my mailman site, but
some things are not working right. The forms are being populated with http://
actions and not https:// actions. What do I need to fix to correct that? I
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
in mm_cfg.py, but that is not helping.
Robert Heller -- 978-544-6933
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
heller(a)deepsoft.com -- Webhosting Services
Hi Mark & others,
Sorry for the delay in responding, and thanks for your generous offer of working with my webhost and/or cPanel to solve this. I passed that offer to my webhost, but it seems they have been able to sort it out with cPanel themselves. Here is the response from my webhost:
The issue with @mydomain.com was caused due to the setting "Discard the email while your server processes it at SMTP time with an error message" under cPanel>>Email>>Default Address. We've setup "Forward to Email Address" to catchall(a)mydomain.com<mailto:email@example.com>. As cPanel support explained, this indicates that all mail that is delivered, but does not have an address (like mailman-bounces@) on this server will be delivered to the default account - this can potentially pose the risk of the email account receiving email for accounts that do not exist, something commonly seen when a domain is being spoofed. Otherwise, it will be rejected with "No such user here".
They then provided some evidence from a log that the problem was fixed.
I then tested lists in all 7 domains, and they all sent subscribe/unsubscribe emails to me perfectly.
I then asked Jim Dory (who has participated in this thread) to setup a default address for his list, and it worked for him, too.
I’m confused by the wording of the above paragraph from the webhost, but maybe they mean that the server is configured to not allow emails to be sent out *from* addresses which can’t receive emails, and this is to help reduce outbound spam. (For years I’ve known that the webhost was fighting outbound spam by preventing email from being sent out from *domains* which I don’t have on that server, but maybe this even applies to the address level.) So, I guess when Mailman tries to send a subscribe/unsubscribe notification email out from mailman-bounces(a)mydomain.com<mailto:firstname.lastname@example.org> to the list owner address, maybe the server blocks it, since that mailman-bounces(a)mydomain.com<mailto:email@example.com> address doesn’t exist, as such. I tested this theory using a less overkill approach, by not using the "catchall" default address method, but just creating a forwarder (alias) for the address mailman-bounces(a)mydomain.com<mailto:firstname.lastname@example.org> which redirects its mail to one of my mailboxes (even to my catchall mailbox), and that seemed to work! I don't think this is to provide an address which will receive emails resulting from subscribes/unsubscribes (since I don't think that process sends anything *to* the mailman-bounces@... address), but just to satisfy the anti-spam requirements of the system that every sending address should be able to receive email, not just bounce it.
Any thoughts on this, Mark/others? Confused?
I can only imagine that the problems started recently due to some update to cPanel or other change by the webhost, because having looked through the history of my subscribe/unsubscribe email notifications, it looks as if the problems only started a few months ago, but I don’t think I’ve made relevant changes to those domains for years. (When I asked the webhost about this, they responded "Unfortunately, we cannot be sure about this. The cPanel representatives haven't mentioned about any recent changes to the Exim configuration.")
Anyway, here is a summary of my subscribe/unsubscribe notification problems that seem to have been resolved by setting the default addresses for my domains to my catchall address, instead of bouncing emails sent to non-existent addresses:
1. For some of my domains/lists I’d receive notifications as *attachments* to emails which have the subject “Bounce action notification” (as per my 1st post).
2. For some of my domains/lists I’d receive subscribe emails as *attachments*, but not receive anything for unsubscribes. (Might be the other way round sometimes.)
3. For some of my domains/lists I’d receive no subscribe or unsubscribe emails at all (as per my 3rd post).
On a server which hosts several mailman lists, a new list is exhibiting odd behavior for owner email addresses. There are two owners, and both are receiving post emails, but are also bouncing what I assume are administrative emails.
The smtp-failure log looks like:
Nov 01 09:37:09 2017 (1387) delivery to <scrubbed> failed with code 553: 5.1.8 <scrubbed>... Domain of sender address mailman-bounces@com does not exist
Note that the sender address is incorrect (default value?). Regular posting emails are delivered with the correct sender address (foo-bounces(a)domain.com).
Using config_list to inspect the non-working list against a working list produces only the expected differences.
Where should I look next?
On 11/01/2017 11:00 AM, Nick Wyman wrote:
> This is not cpanel. This is a virtual host running Ubuntu 14.04 and mailman 2.1.23.
> Things have been running smooth for 1+ year but seem to have been tripped up by spam to mailman(a)mydomain.com.
It's possible that it's the 'mailman' list that has the 'com' host name.
That might be it.
> Perhaps the "mailman" list is misconfigured?
> I don't have a mailman user account, the Ubuntu mailman setup created a "list" user. So I'm not sure how the above mail should be routed.
Yes, in Debian/Ubuntu the Mailman user is 'list'. The "site list" which
every Mailman 2.1 installation must have is normally named 'mailman' and
is 'mailman' in the Debian/Ubuntu package.
You can access the web UI for the 'mailman' list at the same URL you use
for other lists' admin UI but with 'mailman' as the list name. You can
set a site password for your installation via Mailman's bin/mmsitepass
and use that password to log in to the list.
Do that and check the host_name for that list. Also make sure the
'owner' address is good. Or you can do it with 'withlist'.
$ bin/withlist -l mailman
Loading list mailman (locked)
The variable `m' is the mailman MailList instance
Assuming that's the result, set it as in
>>> m.host_name = 'mydomain.com'
also look at
and set that if needed, and finally after making changes
>>> <- enter control-D here to exit
Unlocking (but not saving) list: mailman
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan