Hello list.
I'm receiving a lot of fake Subscription Requests and spend time to
discard them.
1. how can I "lock" lists not to receive requests except administrator's
mass subscription?
2. how can I mass discard those request from console?
Thank you in advance,
Nikos.
I want all mails sent to the list to come from the list's email address...
But, in this case, if the user forgets to sign their name at the
bottom of their mail body, effectively the mail to the list is
anonymous...!
Is there a way to add the user name (or email address) to the top of
each mail so that the mails have the name of the sender, while the
mail itself comes from the list address?
I have looked high and low for an answer, but noone seems to have the solution.
Thank you!
Mal
Hi Folks,
A couple of days ago, over on the MAILOP mailinglist, there was a long
thread titled 'Mailman confirmation email denial of service'. This
detailed some of the problems we've all seen with Mailman subscription
spam. The Mailman team has addressed a lot of these problems with
ReCAPTCHA support and additional configuration options. Arguably the
best solution has been the ReCAPTCHA integration. BUT, a lot of people
don't like the Google tie-ins that come with ReCAPTCHA.
Recently, a kind person submitted a patch [1] to Mailman for hCAPTCHA an
alternative to ReCAPTCHA. In the discussion of that patch, Mark has
stated that he is not interested in any more features for Mailman 2.x.
I think that is fine, Mark has given decades of this time to Mailman and
I think it's perfectly natural for him to want to move on. He deserves
a lot of credit for Mailman's success, both the 2.x and 3.x branches.
So, I have volunteered to spearhead an effort to add one or two more
people to the Mailman Coders group[2] in order to vet and approve new
features that continue the long tradition of providing value to Mailman
2.x. Who's with me on this?
1. https://code.launchpad.net/~jks/mailman/hcaptcha/+merge/389691
2. https://launchpad.net/~mailman-coders/+members#active
Since Centos 7 is way behind on mailman rpm (2.1.15 is the only
available rpm) and mailman is currently at 2.1.34 I need to do a manual
update. While I know how to install software, I am concerned that just
doing a manual install from the tarball will mess up current settings,
lists and members. Does anyone have experience doing this that can
advise about pitfalls or has a cookbook document to do a safe update? TIA.
Hi,
I received the following error this morning. So I rerun configure again with the following command: ./configure --with-cgi-id=apache --prefix=/var/mailman. I'm still getting the same error. Is there any place that I can look for so that I can debug this problem better? Perhaps, looking at the config history file or something. Any other places that I can check the cause of this error?
"Mailman CGI error!!!
The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog:
Group mismatch error. Mailman expected the CGI
wrapper script to be executed as group "nobody", but
the system's web server executed the CGI script as
group "apache". Try tweaking the web server to run the
script as group "nobody", or re-run configure,
providing the command line option `--with-cgi-gid=apache'."
Thanks
Mary
Hi,
I would like to unsubscribe that list but it seems that Your MX which
hosting mailman-users(a)pythong.org is not Tor friendly.
Im getting confirmation from Your host, that my unsubscribe e-mail has
been rejected - because it looks like spam. Also I`m not able to do it
using website provided in Your E-mail footer.
IP of my server is blacklisted by primitive BL pyzor.org - because its
part of the tor network.
Please remove by address from Your list and be more TOR friendly if
possible.
Cheers
Konrad
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
We run a list of our mailman listserver that our public school sysadmins use to share info. The problem is - a lot of them have become Google schools, and Google has a problem with list servers.
Each post winds up going to multiple Google mail domains, and they bounce:
stat=Deferred: 451-4.3.0 Multiple destination domains per transaction is unsupported.
meaning the emails are queued, sometimes for quite a while, as the system sends each domain, one attempt (and one mess of deferrals) at a time.
Is there a setting I can change or add that would allow mailman to kind of bundle each domain, open a thread, and send one-thread-per-domain or one-domain-per-thread to alleviate the issue?
We are a bit behind, using Mailman version: 2.1.20
--
Jeff
Good morning.
Today, when I tried to access Mailman, I obtained the following error:
---------------------------------------------------
Bug in Mailman version <undetermined>
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.
----------------------------------------------
I have checked the logs and they have no information.
I have checked mailman status and it's active and also have checked the permissions and they're right.
It still doesn't work and I have no idea of what to do.
Can you help me please? Thank you.
--
Iván Molina Pastor.
C/Perú, 5-1, Edificio FORUM II, of. 3.9
Polígono . Ind. Oeste
30820 - Alcantarilla (Murcia)
Telf: +34 968 351 364
INFORMACIÓN SOBRE PROTECCIÓN DE DATOS
Sistemas y Control del Mediterráneo SL como Responsable del Tratamiento, con domicilio C/ Perú, nº 5- Edif. Forum II, 3ª planta oficina 9. P.I.Oeste- 30820 Alcantarilla-Murcia. Telf. 968351364 Mail: info(a)syscomed.es CIF. B73503914. Le informa que trata sus datos para la finalidad de gestionar relación comercial, con la base jurídica de nuestra relación comercial. Sus datos se conservarán todo el tiempo que dure nuestra relación, o se puedan derivar responsabilidades de la prestación de servicios. No se realizan cesiones, excepto por obligación legal. Para ejercer sus derechos de acceso, rectificación, supresión, portabilidad de sus datos, limitación u oposición al tratamiento de sus datos, puede hacerlo dirigiéndose a Sistemas y Control del Mediterráneo SL en la dirección arriba indicada, adjuntando documento que acredite su identidad, o interponer reclamación ante la Autoridad de Control. Más info: www.syscomed.es
I am maintaining a list on mailman 2.1.18 on a server I have no control
(actually it is some 1000's km from here). The list is absolutely closed,
reserved to a committee with a small membership which is updated, if any,
every severl years.
In the last days the list is receiving subscription requests from odd
addresses, apparently in couples. When I found two of them yesterday, I
rejected them with a notice "list usage reserved ....". Today I found a
mail announcing two further requests, and when I entered the
administrative interface found two more.
I would like to close completely the list from subscription requests (so
that they can be inserted only by the administrators).
I thought to set ban_list ^.*@.*
Is there any other better option ?
Will the ban_list interfere with existing subscriptions ?
(sent in Bcc to the other list maintainers)
--
Lucio Chiappetti - INAF/IASF - via Corti 12 - I-20133 Milano (Italy)
For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html
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 fast the disk is. This server is typically more than 90% idle at any time. Maybe a few bursts of activity on large lists every now and then.
I have three questions:
First, If I run the prune_arch command to remove archives older than a year, is this going to take minutes, hours or days to complete? In one post Mark Sapiro states that prune_arch locks the list while updating the LISTNAME.mbox so other processes won’t be updating concurrently. Then the list is again locked by the bin/arch process while the HTML archive is being regenerated. If this list is used on an hourly basis and the list is “locked” this could be problematic for us.
Second, Our disk space is getting low and that is why we are cleaning up the archives. Is the prune_arch command going to be temporarily generating more files and taking up more space in order to process the list archives? If so I’ll have to make sure we have enough disk space to run prune_arch.
I would like to schedule the prune_arch command as a cron job to run against several lists. I have looked at prune_arch before and I found some earlier posts that detailed how to prune the archives and there were more instructions that just running the prune_arch command. I cannot locate those old posts now. I should have bookmarked them. Is this all I need to do, just run prune_arch against the list and slap it in cron?
Thank you for any info you can provide.
—
Andy
