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
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.
Thanks!!
I understand the purpose of the confirmation, I just want the ability to turn it off. It is okay if users get unsubscribed from my list because of a spooked request.
-----Original Message-----
From: Mark Sapiro [mailto:msapiro@value.net]
Sent: Wednesday, July 27, 2005 11:52 AM
To: Sintz, James; mailman-users(a)python.org
Subject: Re: [Mailman-Users] unsubscribe without confirmation
Sintz, James wrote:
>Is there a way to enable unsubscribing without requiring user confirmation? Users are added to the list manually by an administrator, yet we do want to allow users the ability to unsubscribe using the listname-leave@ address.
E-mail unsub requests require confirmation to prevent spoofed requests
from succeeding. The user can avoid the confirmation by providing
his/her password with the e-mailed unsubscribe command, but this only
works if an unsubscribe command is mailed to the listname-request
address. Mail to the listname-leave or listname-unsubscribe address is
not parsed for commands and is treated as if it just contained a plain
'unsubscribe'.
Send mail with subject 'help' (w/o the quotes) to the listname-request
address for more info on the unsubscribe command.
--
Mark Sapiro <msapiro(a)value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
CONFIDENTIALITY NOTICE: The Ohio Public Employees Retirement System intends this e-mail message, and any attachments, to be used only by the person(s) or entity to which it is addressed. This message may contain confidential and/or legally privileged information. If the reader is not the intended recipient of this message or an employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that you are prohibited from printing, copying, storing, disseminating or distributing this communication. If you received this communication in error, please delete it from your computer and notify the sender by reply e-mail.
I've looked at the Whole Mailman FAQ and looked at archived message threads
back 5-6 months and have not see a discussion or resolution on the problem
I'm seeing with URL line breaks in my list archived messages.
Basically if I set Non-digest options/"Scrub attachments of regular delivery
message?" to No my archived messages, scrubber adds the non-test attachment
was scrubbed URL, URL's are ok full line and clickable. Messages from the
list have the attachment and life is good. The first example below.
If I set Non-digest options/"Scrub attachments of regular delivery message?"
to Yes my archived messages URL's have an extra = in the URL string at the
end of line one and a line break making the URL 2 lines and non-clickable.
The second example.
Please, if somebody has seen this problem, has a resolution, or if the FAQ
has the answer, let me know.
------------- next part --------------
A non-text attachment was scrubbed...
Name: Official notice Spam Filtering Implementation Update 09030.pdf
Type: application/octet-stream
Size: 76382 bytes
Desc: not available
Url :
<http://www.mn.us/pipermail/listname/attachments/20050901/4bb779ff/Officialn
oticeSpamFilteringUpdate09030-0001.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Official notice Spam Filtering Implementation Update 09030.pdf Type:
application/octet-stream Size: 76382 bytes
Desc: not available
Url : <http://www.mn.us/pipermail/listname/attachments/20050901/2d8=>
eb35e/OfficialnoticeSpamFilteringUpdate09030.pdf
-tw
-tw
We have migrated all mailing lists from Majordomo to Mailman (mailman-2.1.5-25.rhel3n on redhat
3.0 AS). We would like to hide those lists that are closed for subscription from the listinfo
page for 2 reasons: to keep the page short and to avoid subscription attempts. We would like to
keep them on the admin page for the list owners. Setting "advertised = 1" will hide the list from
both listinfo page and admin page.
We would like to set this up at the list level so we dont have to modify the global
configurations during upgrades. I have tried to modify web_page_url = listinfo/%(list_name)s
to something like web_page_url = listinfo/%( )s to blank out the listinfo url but could not
get the syntax right.
Am I on the right track? What are the other options?
Thanks.
Xiaoyan
Hello,
I thought this was working when we moved to Mailman 2.1.6b4
in June, (I could be wrong) but the monthly password reminder
is not working. I, and a colleague, have tried to manually
test the script for a single list but it is not working. The
script that runs out of mailman's cron is:
# 5 AM on the first of each month, mail out password reminders.
0 5 1 * * /usr/bin/python -S /usr1/mailman/mailman/cron/mailpasswds
I tried testing with:
$ pwd
/usr1/mailman/mailman/cron
$ runas -u mailman ./mailpasswds -l testlist
It just exits. Nothing in the mail or mailman logs.
Other details: Red Hat Enterprise Linux AS release 3
Any suggestions?
Darren
Old Dominion University
Hey All,
My apologies in advance if I'm directing this to the wrong location, but
I'm about out of ideas. I recently built a small PHP web form to allow
individuals to send email updates to our various mailman lists. Everything
works quite nicely for non-digest users, but when I tried to configure the
script for digest users, things started to get weird.
Initially, no matter how many emails I dispatched using the form, the
Mailman digest always listed a single topic. In the MIME digest it attached
a single message (the first message sent to the list) and in plaintext it
appended all the messages sent to the list but still listed as a single
message. The headers where all subsequent messages were to start seemed
pretty messed up. So I decided to play with the headers a bit and added the
line in the php:
$headers .= "X-Mailer: PHP/" . phpversion() . "\n";
After that change all digests calculated the number of messages correctly
and displayed the headers accurately. Unfortunately, though every thing
looks good in digest/plaintext, digest/MIME was acting up. When a MIME
digest was received in Outlook, the messages were not attached to the
digest. Yet when I sent to a gmail account they appeared below as forwarded
messages. Now if I forsake the php form and send MIME email from outlook to
the list Outlook correctly creates a multipart/alternative email and the
MIME/digest contains appropriate attachments for all messages.
Below I list the headers that I'm setting in php, the relevant sections of
the plaintext digest with incorrectly counted messages/topics and finally
the relevant sections of the plaintext digest with the correct message
count.
Thanks in advance to anyone who has any thoughts
php:
$boundary='--' . md5( uniqid("IsNealAGenius") );
$headers = "From: \"Home Office\" <" . $from. ">\n";
$headers .= "Mime-Version: 1.0\n";
$headers .= "Content-type: multipart/alternative;\n boundary=\"$boundary\"\n
X-Mailer: PHP/" . phpversion() . "\n";
$message="\nThis is a multi-part message in MIME format.\n";
$message.="\n\n--$boundary\n";
$message.="Content-Type: text/plain; charset=\"us-ascii\"\n";
$message.="Content-Transfer-Encoding: 8bit\n\n";
$mail_to = "test_list(a)here.com";
$message .= strip_tags($test);
$message .= "\n\n--$boundary\n";
$message .= "Content-Type: text/html; charset=\"us-ascii\"\n";
$message.="Content-Transfer-Encoding: 8bit\n\n";
$message .= $test;
mail ($mail_to,"test",$message,$headers);
......................................................................................
plaintext digest 1.
Today's Topics:
1. test (Home Office)
----------------------------------------------------------------------
Date: Wed, 21 Sep 2005 10:19:36 -0400 (EDT)
From: "Home Office" neal(a)here.com
To: test_list(a)here.com
Subject: [Test_list] test
Message-ID: 20050921141936.AF158524114(a)mail.here.com
Content-Type: multipart/alternative;
boundary="--274280a87c2f32840e53791334dfb49f"
MIME-Version: 1.0
Precedence: list
Message: 1
This is a multi-part message in MIME format.
----274280a87c2f32840e53791334dfb49f
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
<stripped HTML here.>
----274280a87c2f32840e53791334dfb49f
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 8bit
<Real HTML here>
----274280a87c2f32840e53791334dfb49f--
>From apache(a)here.com Wed Sep 21 10:19:51 2005
Return-Path: apache(a)here.com
X-Original-To: test_list(a)here.com
Delivered-To: test_list(a)here.com
Received: by mail.here.com <http://mail.here.com> (Postfix, from userid 48)
id 0952E52406B; Wed, 21 Sep 2005 10:19:51 -0400 (EDT)
To: test_list(a)here.com
From: "Home Office" neal(a)here.com
Mime-Version: 1.0
Content-type: multipart/alternative;
boundary="--921e4b971d970fe077e26dadad939251"
Message-Id: 20050921141951.0952E52406B(a)mail.here.com
Date: Wed, 21 Sep 2005 10:19:51 -0400 (EDT)
Subject: [Test_list] test
X-BeenThere: test_list(a)here.com
X-Mailman-Version: 2.1
Precedence: list
List-Id: Test list to work out bugs <test_list.here.com>
List-Unsubscribe:
<*http://www.here.com/mailman/listinfo/test_list*<http://www.here.com/mailman/listinfo/test_list>
>,
<*mailto:test_list-request@here.com?subject=unsubscribe*<test_list-request(a)here.com?subject=unsubscribe>
>
List-Archive: </heremail>
List-Post: <*mailto:test_list@here.com* <test_list(a)here.com>>
List-Help: <*mailto:test_list-request@here.com?subject=help*<test_list-request(a)here.com?subject=help>
>
List-Subscribe:
<*http://www.here.com/mailman/listinfo/test_list*<http://www.here.com/mailman/listinfo/test_list>
>,
<*mailto:test_list-request@here?subject=subscribe*<test_list-request@here?subject=subscribe>
>
This is a multi-part message in MIME format.
----921e4b971d970fe077e26dadad939251
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit .....
<Rest of message>
............................................................
plaintext digest #2:
Today's Topics:
1. test (Home Office)
2. test (Home Office)
3. test (Home Office)
----------------------------------------------------------------------
Date: Wed, 21 Sep 2005 09:56:42 -0400 (EDT)
From: "Home Office" neal(a)here.com
To: test_list(a)here.com
Subject: [Test_list] test
Message-ID: 20050921135642.7C15B52406B(a)mail.here.com
Content-Type: multipart/alternative;
boundary="--c9dff2da6d2e9942c846b891d664122e"
X-Mailer: PHP/4.3.2
MIME-Version: 1.0
Precedence: list
Message: 1
This is a multi-part message in MIME format.
----c9dff2da6d2e9942c846b891d664122e
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
<Plain text here>
----d9d51c58d8acd322402f930ba7754354
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 8bit
<HTML here>
----01f73f678c4ca55f470d0225d6131bb2
------------------------------
Date: Wed, 21 Sep 2005 13:28:37 -0400 (EDT)
From: "Home Office" neal(a)here.com
To: test_list(a)here.com
Subject: [Test_list] test
Message-ID: 20050921172837.6110952406B(a)mail.here.com
Content-Type: multipart/alternative;
boundary="--7cdc89be99811720df8db7a5ddb7bc0e"
X-Mailer: PHP/4.3.2
MIME-Version: 1.0
Precedence: list
Message: 2
This is a multi-part message in MIME format.
----7cdc89be99811720df8db7a5ddb7bc0e
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
<rest of message>
Hello, there!
I am using MailMain trough its web-based interface. I don't have access
to the server where its runs, because it's a third-party hosting company
which provides me the MailMan service.
I want to export the subscribers list in a format like this:
subscriber1(a)mydomain.com
subscriber2(a)mydomain.com
. . . . . . .
subscriber9(a)mydomain.com
I wasn't able to find the way to perform this operation, searching
deeply into the options tree.
Is it possible to obtain this kind of list?
T.I.A.
--
Arlequín _o)
amahoro_AT_adinet_DOT_com_DOT_uy / \\
http://counter.li.org/ _(___V
Linux Registered User #207262
