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
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
Greetings,
I cannot "Set everyone's moderation bit, including those members not
currently visible" to on, in the membership management section in any
list.
I have set
OWNERS_CAN_ENABLE_PERSONALIZATION = 1
In /Mailman/mm_cfgy.py
But still have the same problem.
Also I cannot set or unset digest for all users, any thing I overlooked?
This was happening before the changes made in the next issue explained
below.
In the last couple of days we had to reconfigure reverse mapping in DNS
for the server, and now the URLs that Mailman builds in the list admin
and info pages are pointing to the old host name, is there a way of
correcting this, without re-installing mailman from scratch?
Any pointers, clues will be greatly appreciated.
Thank you for your assistance.
Hi all,
I've just copied my mailman configs from one system to another, and
after reinstalling innd on a private news server, I'm now getting the
following in the logs:
Feb 26 23:50:02 2006 (2757) rgsouthern: [0..0]
Feb 26 23:50:02 2006 (2757) nothing new for list rgsouthern
Feb 26 23:50:02 2006 (2757) rgsouthern watermark: 12
Feb 26 23:50:02 2006 (2757) melbwireless: [0..0]
Feb 26 23:50:02 2006 (2757) nothing new for list melbwireless
Feb 26 23:50:02 2006 (2757) melbwireless watermark: 37
As the newsgroups were reset, the watermark is obviously incorrect.
Is there a way to reset this watermark so that the system starts
gating news correctly again?
--
Steven Haigh
Email: netwiz(a)crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9017 0597 - 0412 935 897
Hi,
I use spamassassin to filter spam. So I configured a rule in mailman
that detect
the string "{Spam}" in the subject of the email and then defer the email.
The problem is that mailman sent to owner of the list the email that is
spam with
the body of the email. So, spamassassin detects the body and mark the email
as spam, and mailman differ the mail sended to the owner.
My question is:
how can I configure mailman to not sent the body of the email in the
notification
to the owner of the list?
Many thanks
Oliver
--
Oliver Schulze L.
<oliver(a)samera.com.py>
I've removed sevaral list members, using the Mailman
Admin interface. However, they're still gettting my
mailings, and are threatening to complain to the spam
cops? I've double checked to confirm that these email
addresses are NOT in my membership list.
What's the deal?
ZB
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
I've spent a lot of time over the last few days trying to make htdig work
with my installation of mailman 2.1.5. I installed the patches and rebuilt
everything, set up the configuration, rebuilt my archives using arch and
everything seemed (mostly) fine until I tried to index the archive and do a
search.
The indexing problem I have is an htdig issue (segmentation fault while
running htfuzzy) so I won't go into that.
Even with that problem during the index process, I can use htsearch from
the command line and it gives me a valid search response. When I try to do
a search from the form on the archive index page, it bombs badly and just
gives me a useless error message (something like Search failed 12).
I noticed in the documentation that the 3.2 version of htdig is not
supported by the patches for using htdig with mailman. I've tried rolling
it back to version 3.1.6 but am having difficulty getting it to install so
it looks like for the moment I am stuck with 3.2
Is there any way to get this patch to work with the 3.2 version of htdig?
Is there any plan to support this in the future?
Dragon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
