Hi - I have searched FAQ and archives to find an answer. Hoping you can
help.
I have a new list (with previously imported addresses) for announcements
only, and wish these announcements to be received immediately.
I set the defaults to allow non-digest and to not allow digest.
I wish to send out announcements in html, and so wish to make the
default for new subscribers be MIME. While I see a setting under Digest
Options (MIME_is_Default_Digest), I don't see any equivalent option
under Non-Digest Options... and new subscribers continue to come in as
plain text.
QUESTIONS:
In order to avoid having to manually change this option for each
existing subscriber, is there a way to force all existing subscribers to
receive MIME in Non-Digest mode?
If not, is there a way to force all NEW subscribers to be enrolled with
MIME as their default?
Also, is there a way to "lock" the MIME switch on, so that users who try
to change their option to plain text will be prevented from doing so?
Thanks -
Steve
Recently, my Mailman list users who use either a HotMail or MSN.COM email address have not received any messages. Mailman does not record a "bounce" from these email addresses, but they do not receive any of the list traffic. When trying to send a message to a Mailman list, the user gets the following error message:
"This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed."
And it lists the Mailman list email address. However, Mailman does not receive a bounce message. (My server is not listed with SpamHaus.org, or any of the other blacklists, so it should not be a spam filter sort of thing).
One user requested help from MSN, and they responded with:
"You are experiencing this issue because your .Net Passport <user's email address here> Profile (which is extensively used for authentication purposes) is corrupted (not updated). In order to resolve this issue, I would suggest you to Update your .NET passport profile."
They follow that with instructions to go to their MSN .NET Passport profile and re-type all the information by hand (not by cut and paste). Then a 15-step procedure is given to delete all cookies, history and temporary internet files and re-set the disk cache (space for files) to 10MB. They believe that will solve the problem but alas, it has not for the 4 users I have with MSN or HotMail email addresses.
Anyone else run into this and resolved it? I didn't see anything in the archives. If any of you have users with MSN or HotMail addresses, be advised they probably will not be able to receive emails, but you will not get "bounce" messages. They only way they will know is if they try to post to a Mailman list.
Hi List
I have a (bit aged) Redhat 9 box (Pentium II/512Mb RAM) running Mailman
2.1.6 with Postfix. Its only has to run a single moderated mailing list
sending out one email every day to around 20,000 subscribers.
Sending out the emails is not problem - it works great. The major
problem is logging in to approve the email. It (Apache/2.0.40) is so
slow that it usually times out with a 500 error after you try and
login.
Is there a way of speeding up the web interface?
Can I approve postings from the command line?
There is a large archive as they have been running this for around 3
years. Will it speed up if we trash part of the archive. If so how can I
trash archived data that is (say) over a year old?
There was a thread on this problem, but it was not really resolved, and
that user had 450,000 subscribers.
Any help appreciated.
Jon Harris
Hello Folks,
I recently setup a mailman server with ver 2.1.6, and I am liking it so far.
Since I am not with the IT Team of my organization, I am working around
some mailman problems and this is where I need some ideas.
I setup a few mail lists (including default mailman list) in
name.comdomain, and worked with my IT folks to redirect <maillist>@
name.com to my mail server <mailist>@mine.name.com
I do get a few <maillist-name>-bounce(a)name.com emails, and I would like to
re-direct all these emails to mailman(a)name.com (or mailman(a)mine.name.com)
Does someone have ideas how to accomplish this?
I do not administer the company's mail servers.
Folks here are not open to the list.name.com domain idea, for legacy
reasons.
I have a bunch of /etc/aliases entries for each of my mail lists on
mine.name.com server.
Is there a way I can use these alaises to re-firect <maillist-bounce>@
name.com to mailman(a)name.com
Any help / ideas are appreciated.
Thanks!
Tom
Hello
One of my users' messages are always sent out to list members with a
blank body.
I have tried unsubscribing him and resubscribing him. Same result.
Most other members are posting fine (though some never bother!).
What could be causing this and how can I run diagnostics to trace the
problem? Or, even better, how can I fix it?
I am running Mailman v 2.1.7. I am not allowed to upgrade to 2.1.8 as
the installation is provided by a third party (CPanel) via my web host.
Any ideas?
Many thanks
Nigel
Dear List -
I recently have changed mail servers and my attempt at moving Mailman
appears to have only partially succeeded.
Currently:
check_perms comes back fine - Good.
cron is running the news_port command every 5 minutes (good cron check)
-Good.
The web interface works fine - all list look great - Good.
Mail sent to a list appears in a qfile - Good.
Qrunner is running - Good.
Mailmanctrl is running - Good.
Nothing is being sent to Postfix - Bad!!!
Qfile In directory purged just in case, still nothing.
System:
Gentoo 2.6.13 running 2.6.13-gentoo.r3 kernel, 64-bit, on an AMD64 3000.
Postfix - but nothing fancy - no virtual domains, etc.
Mailman 2.1.5-r3 build via emerge into the standard location
Help!!! <with a smile>
Kevin
hi.
i have searched the faq and asked google but haven't found anything for
my problem (so forgive me if i missed something obvious):
my basic problem is, that i want to forward mails from one mailing list
to another (on both lists only subscribers can post):
the setting is as follows: there is an "announce"-list and a
"users"-list; mails going to the "announce"-list should also go to the
"users"-list, so people don't have to subscribe to both lists
the subscribers to both lists overlap, but there are a lot of users
subscribed to only one of them.
so my first attempt was, to just subscribe "users" to the "announce"
list, but as soon as somebody who is subscribed to "announce" but NOT to
"users" posts to the announce-list, the mail is held for approval in the
"users" list.
this is rather inconvenient.
so my second thought was to auto-accept postings to the "users" list
which has a special header-field (i thought that the "List-ID"-field
would just be ok for my purposes).
unfortunately i found that this wasn't possible (i am running debian and
tried both 2.1.5-8sarge2 (which is basically 2.1.5 with some
cross-site-scripting security issues fixed) and 2.1.8)
the only header-field i found which could be used for auto-accepting is
the the "Approved: <moderator-password>".
so i did a quick hack to handle this at the MTA-level
<sidenote>
i didn't want to patch mailman itself, because this is only a rather
long-term solution: wait until the patch gets accepted upstream; then
wait until the upstream version is in debian (and with the debian way of
releasing this will take years until it is in the stable branch which i
prefer for my servers); in the meantime i could either run the newest
mailman release (from source) or patch each and every security update of
the debian-package.
</sidenote>
basically now my working setting is like this (using mailman, exim4,
procmail)
"users" is subscribed to "announce".
mails for "users" are not directly delivered to the mailman-wrapper by
the MTA but instead it is first piped through procmail.
if any mail directed to "users" appears to come from "announce" (based
on the "List-ID" header field) i add another header "Approved: <mod-pw>"
with formail, before it gets delivered to the mailman-wrapper for "users".
of course this is not very secure (but not much less secure then
accepting mails based on the "From:" field)
however, since this was a bit of work and somewhat hackish (though only
configuration and no patching was involved) my question is: is there as
simpler way to acchieve this? would an option for each mailing list to
auto-accept mails with a special header (perferrably a regex) make sense
(feature-request)?
or - if my setup is of some use for others - should i post a short howto
somewhere (where)?
mfg.asd.r
IOhannes
Mark,
If we want to change both host IP address and hostname, what is the correct way to do it. We are running Mailman 2.1.5.
Thanks for your help!,
Mardin
-------------- Original message ----------------------
From: Mark Sapiro <msapiro(a)value.net>
> mardin(a)comcast.net wrote:
> >
> >By the way, is it normal not find any hostnames in the mm_cfg.py file?
>
> Yes, if Mailman was configured with the correct names so that the
> assignments in Defaults.py are correct.
>
> In this case, they would only be needed in add_virtualhost() lines in
> mm_cfg.py to add additional virtual hosts.
>
> --
> Mark Sapiro <msapiro(a)value.net> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
>
I run a rather interesting mailman setup with a very large number of lists
that have a lot of traffic.
This has lead to a couple issues mostly tied to storing all the data in
pickle files. If I could replace
the pickle interface with something that stores to a SQL database I could
load balance the service, and
stick the web interface and cron jobs a box dedicated to that purpose. My
question is:
does anyone know of a plugin replacement to cpickle that will store data in
a database (not as a blob), and
has anyone created any sort of schema for storing list data in a database?
I figured I would ask before recreating the wheel.
thanks,
--
--Matt
Hi ALL,
I set the personalization option to Full for a list so the mail would be
sent to the user address and not to the list main address. It kinda work.
But the main list address is still shown in the CC: field. Is there any way
to avoid this behavior ?
--
Fabiano de Carvalho Breves
fabiano.breves(a)gmail.com
