I’m running mailman 2.x and I am getting ready to build a new server and
migrate my lists to 3.x. For those of you who have done this already, do you
have any recommended reading suggestions other than the official web page at
https://docs.mailman3.org/en/latest/migration.html
--
I have a list running on Mailman 2.1.26. For this list I want everybody
moderated except for people who’s email address is from a specific domain. Is
there a way to specify a domain that will bypass moderation? What I plan on
doing right now is to manually check or uncheck the “mod” checkbox
Using mailman 2.1.26. I have one particular list that has a 3G mbox file and
an 8G private archive directory. I was going to use prune_arch to remove any
archives over a year old. I think the archives go back over ten years. This
particular list server has two cpus (@2.5GHz) but not sure how
On Nov 19, 2019, at 9:39 AM, Andy Cravens wrote:
Mailman 2.1.26. I modified all our lists that did not have munge_from set for
DMARC compliance. I ran a few tests and was able to send and receive email
from my test list. Now I’m getting reports that large numbers of emails are
bouncing
Mailman 2.1.26. I modified all our lists that did not have munge_from set for
DMARC compliance. I ran a few tests and was able to send and receive email
from my test list. Now I’m getting reports that large numbers of emails are
bouncing and members are being unsubscribed. I had someone forw
Using mailman 2.1.26. I’m auditing the lists on my server for DMARC compliance
I’ve found several list configs that do not have the DMARC action set to
“munge_from.” It appears I need to edit all those list and fix that setting.
I’ve also noticed that in mm_cfg.py there is no setting for
REM
Using mailman 2.1.26. I have a list that is going to be retired and I need to
stop people from posting to the old list. However, I don’t want to delete the
list quite yet. Also, I need to auto-reply to any attempted posters that the
list is being replaced with a new list. I have a plan but w
Using mailman 2.1.26. When someone sends an unsubscribe email to a mailman
server, does that email get saved anywhere after it is processed?
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-
On Aug 18, 2017, at 8:36 AM, David Gibbs wrote:
On 8/17/17 3:47 PM, Andy Cravens wrote:
> I forgot to mention I’m also working on a modsecurity rule to look at
> all POSTs and reject if they contain an email address with a + sign.
I'm interested in both your recaptcha mod & mo
On Aug 19, 2017, at 8:27 AM, Steve Wehr wrote:
subscribe:Aug 18 00:41:10 2017 (22583) saintsofswing: deleted
dorrainescofi...@gmail.com; via the member options page
Steve, if this was done via the web interface the first thing I would do is get
the date/timestamp for the log entry “deleted
On 8/8/2017 12:22 PM, David Gibbs wrote:
> Anyone else noticing a distributed mass subscribe attack going on
> their lists?
>
> I've noticed a massive number of attempts a small subset of email
> addresses, with modifiers (address+modif...@example.com), going on.
>
> It appears the address is val
On 8/8/2017 12:22 PM, David Gibbs wrote:
> Anyone else noticing a distributed mass subscribe attack going on
> their lists?
>
> I've noticed a massive number of attempts a small subset of email
> addresses, with modifiers (address+modif...@example.com), going on.
>
> It appears the address is val
Currently running mailman 2.1.23 and would like to implement reCAPTCHA v2. The
only information I can find on this topic relates to reCAPTCHA v1 which google
no longer supports. I can’t even generate keys for v1 any more. Has anybody
successfully implemented reCAPTCHA v2 with mailman 2.1.X ?
We are running mailman 2.1.9 on Solaris 10. This afternoon we had a
strange problem that we have never seen before. The mailman aliases
file located at /opt/mailman/data/aliases was somehow truncated and
contained only a dozen of our 173 lists. Almost all of our list traffic
was rejected wit
Dragon wrote:
Andy Cravens wrote:
I'm running Mailman 2.1.9 on Solaris 10. Sometime this weekend we
had a mail loop which pounded our list server. The mail loop has
been fixed but there is a python process that is consuming an entire
cpu. Further inspection of this process re
I'm running Mailman 2.1.9 on Solaris 10. Sometime this weekend we had a
mail loop which pounded our list server. The mail loop has been fixed
but there is a python process that is consuming an entire cpu. Further
inspection of this process reveals:
qrunner --runner=ArchRunner:0:1 -s
I'm as
We are in the process of upgrading mailman and have to take some
intermediate steps to get there without affecting our customers. I'd
like to know if there is a way to configure mailman 1.0 so that any mail
sent by mailman would look like it came from [EMAIL PROTECTED]
instead of the current s
I'm looking for information on pros, cons and setup steps for taking
mailman off the mail server and setting it up on a dedicated mailman
list server. I looked through the entire FAQ and didn't see any info on
this. I've seen this information before but can't find it now.
--
Andy
---
Is there a way to manually delete held messages from a list's config.db
file? I periodically get held messages that will not delete because
they contain a sequence of characters that cause the discard function to
blow up. You know, the 'ol "We're sorry, we hit a bug!" error screen.
In the past I
We are currently running Mailman 1.0 and python 1.5.2
In prep for upgrading Mailman 1.0, I will be upgrading python from 1.5.2
to version 2.3.3. Will Mailman 1.0 continue to run after I upgrade
python to 2.3.3? Also, will Mailman 2.0.13 run OK under python 2.3.3?
The docs on the Mailman web sit
I'm going to be upgrading an old mailman 1.0 install to 2.x
In looking around at our old install I've discovered a lot of old que
files in .../mailman/data/ such as
1534 May 25 2001 mm_q.29687.1
1534 May 25 2001 mm_q.29683.1
1532 May 25 2001 mm_q.29660.1
1532 May 25 2001 mm_q.29656.1
1532 May
I have been given the task to upgrade our mail server which is running
Mailman 2.0.12
The existing server will be replaced with a completely rebuild box with
the latest versions of Mailman and Postfix. I have no previous
experience with Mailman so I have no idea how to move the current
Mailman c
22 matches
Mail list logo