I have debain 7.11 , mailman 2.1.5-1 i386
I have a few lists. All stopped archiving.
LISTNAME.mbox is not updateing
I have run chech_perms -f as root. /usr/lib/mailman permissions are OK, and
permissions of non-links ar OK.
I have also added w permission to all for directories.
Any suggestions ?
Our mailman server is on DMZ and a couple of month ago was changed to work https.
>From inside LAN we can access mailman.domain/mailman/listinfo/test and subscribe using browser interface.
>From outside LAN we get :
The site cannot be reached mailman.org refused to connect.
Any idea ?
Thank you for help
I’ve been googling a bit, but the only thing I can find is from back in 2010 (https://mail.python.org/pipermail/mailman-users/2010-May/069388.html) as to if it’s possible to configure a mailman list to “prevent” reply-all.
Basically, I support a lot of users that seem to not realize the difference between the two, or they just don’t care if everyone gets inundated with “thanks” and “congrats” responses. So I’m curious if there’s any way to make a mailman list not easily accommodate reply-all. I thought reply-to munging would work, but it doesn’t sound like it does. What I want is really what rpschwar wanted back then.
User A send message to list. List members get the mail, but it “appears” to be from User A and not from the list. So a Reply and Reply-all both do the same thing. To really reply-all, users would have to physically type in the mail list address into their To or CC fields.
Is this possible (short of re-educating our users about how “reply-all” really isn’t appropriate in most cases)?
TGIF Mailman Gurus,
My current Mailman 2.1.12 server is lists.washlaw.edu and is running on a RedHat vm. I need to move it onto a new server which already has a new instance of Mailman 2.1.22 also on a RedHat vm. I already ran the ./configure command to be the same setup as the OLD server. I have searched the discussion list archives on the steps and am not fully understanding what needs to be done. Below are the steps I do know I need to take but then I am at a loss.
1. Post Postfix, Apache and Mialman on OLD server and NEW servers
2. Tar up the lists and archives from the mailman directory and copy the tar files to the new server
a. tar xvfx /usr/local/mailman/lists
b. tar xvfz /usr/local/mailman/archives
3. Untar the lists and archives onto NEW server
a. tar -xvf lists.tgz
b. tar -xvf archives.tgz
c. Run from /usr/local/mailman/bin ./check_perms -f
4. Run newaliases
is it possible to subsrcibe a list to another list?
For example I have the lists scientists@domain, students@domain and
all@domain. I would like to subscribe the scientists and students lists
to all so that I can reach everyone with a single list.
I’m trying to start mailman on startup with ElCapitan.
I tried a plist in LaunchDaemons - that was working in the past with the command:
/usr/local/mailman/bin/mailmanctl -s start
this produces now the error:
Service only ran for 2 seconds. Pushing respawn out by 8 seconds
the error log says:
The master qrunner lock could not be acquired because it appears as if another
master qrunner is already running
So it starts, creates a lock as localhost … and then it tries to start again.
than I created a startup script as described here:
and it does … nothing
the only thing which works currently is starting it manually with sudo
and this is kind of inconvenient
I installed mailman manually without using macports or something like that.
I hope someone on the list can share some insight here.
I just gor a message from Mailman that a list subscription has been disabled because of too many bounces. This is quite okay, I think - but when I look at the Mailman management page, the user is still there as a subscribe. The only difference is the check mark and a "B" in the area "no message (reason)".
Of course, he does not receive any more messages, and the "B" probably means because messages have bounced. But why isn't he unsubscribed completely?
Thank you for clarifying.
Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland)
Hilfe fuer Strassenkinder in Ghana: http://www.chance-for-children.org
When moderating posts, I forwarded several to myself all at once, saw they
were fine, then went back and "accepted" them all at once. Just as I
clicked Submit, I saw that one was a new message I hadn't reviewed, and it
looked like spam. Too late; I clicked Submit.
Fortunately, this list is 100% digest-only with the exception of
mail-archive.com, and their spam filtering seems to have killed it there.
I loaded digest.mbox with mutt and deleted the offending message, so (I
believe) it won't be in the next digest. Is that all I have to do to wipe
this from my server? What else?
SO... I've digging further into Mailman code looking to further
improve problems with DMARC. I've noticed that Mailman "hold"
notifications (to:list-owner@) fail DMARC (if the mailing list domain
has a _dmarc RR) because of a simple code issue..... (not calling it a
bug at this point)
In Handlers/Hold.py, "held for moderation" notices to posters
correctly uses Message.UserNotification() to craft and send the poster
a notification. However, notification to list-owners (it really
should be list moderators...) also uses Message.UserNotification()
rather than Message.OwnerNotification(tomoderators=1).
Any thoughts on why?
So, all of my testing has so far been with email addresses that have their destination on the same system as the one, on which Mailman is running. I just tried a list that has all external destinations.
What log files should I look at to see, what might be going wrong?