Using Mailman v 2.1.4 I keep getting the following error.
Nov 30 19:19:07 2004 admin(29952):
/var/mailman/pythonlib/japanese/c/euc_jp.py:3: RuntimeWarning: Python C API
version mismatch for module _japanese_codecs: This Python has API version 1011,
module _japanese_codecs has version 1012.
In ver 2.1.4 I want to prevent subscription confirmation via the web.
Subscribing via the web is fine, but not confirmation. Allowing this lets
people/IPs black listed at server level in postfix to go around my spam
/security system.
Any help appreciated.
Tim
At 03:33 AM 11/21/2004, Jim Tittsler wrote:
On Sat, Nov 20, 2004 at 02:03:13PM +, Robin Becker wrote:
I see this question asked, but haven't seen a reply. Is there any way to
change the response message that non-members receive when rejection is
the chosen action?
They receive the
Go to your lists admin page.
At the bottom there is an option that says Should messages from this mailing
list include the RFC 2369 (i.e. List-*) headers?
Select No
Press the submit your changes button.
You may want to do the same with the List-Post: header option as well.
Tim
At 09:54 AM
I am wondering what action if any is taken by Mailman v2.1.x when a password reminder
bounces. Is it tracked anywhere? Will the bouncing address eventually be removed
from the lists it is a member of?
Tim
--
Mailman-Users mailing list
Since upgrading to Mailman 2.1.4 from v2.0.8 I have been getting the below errors in
the log whenever a non-member tries to access a non existing account. They are also
presented with the we've hit a bug screen which also displays the below information.
Is there some process that I can run to
I am wondering what action if any is taken by Mailman v2.1.x when a password reminder
bounces. Is it tracked anywhere? Will the bouncing address eventually be removed
from the lists it is a member of?
Tim
--
Mailman-Users mailing list
We have about 600 list running on a RH Linux box with Postfix and Mailman 2.1.4.
Since we have upgraded to the new version from v2.0.8 we have no been able to
successfully send a monthly membership reminder to our entire membership. It has
bombed at various points during the run. Below is
I have recently implemented VERP on a test basis. I have found that valid addresses
(namely mine and a few others) now bounce when VERP delivery is enabled.
Since I know that my address is valid and that I have not had problems prior to
enabling or after disabling VERP, I'm going to make the
I tried to implement VERP so I could take advantage of the bounce tracking but postfix
rejects the returned bounces as an unknown address. Does anyone here know how to set
up Postfix with VERP? I read the VERP info on the Postfix site but it doesn't SEEM to
apply to the way Mailman says it
At 11:38 PM 7/22/2004, Mark Sapiro wrote:
Toby Reiter wrote:
set
VERP_CONFIRMATIONS = Yes
in mm_cfg.py.
Read about it in Defaults.py
I would also like to implement this but all that I have read says VERP requires
cooperation from the MTA. I am using the latest ver of Postfix. What do I have
At 02:23 PM 7/21/2004, Alexander Storman wrote:
Hi All,
We are having issues with email being spoofed from M$ viruses that have
managed to get most of our company email addresses.
Viruses are getting through since they are spoofed as addresses that have
unmoderated approval to send to the list.
Is there a way in 2.1 to set subscriptions on administrative hold via the command line?
AOL is blocking my server again (even though I have filled out their white list form)
and I want to put all AOL subscriptions on hold so my queue isn't filling up with
thousands of retries.
Tim
I am the site admin for a server running Mailman v 2.1.5 on a Linux
box. We have about 600 lists running and site wide out of the over 40,000
subscribers we have several thousand AOL subscribers.
As you probably know, AOL (in it's infinite wisdom) has given it's users
the ability to black
14 matches
Mail list logo
