Re: [Mailman-Users] add_members
Mark,
Bingo!
The script from the sourceforge site works fine. Here are the
diffs between that version and the version that Apple is providing. Note the
change of address of Foundation and the ill-fated option in the Apple-supplied
version to disable mail for the new subscriber. ( is official version, is
Apple's version).
A bit of nosing around on the sourceforge site shows that the address was
changed on the main cvs branch from version 2.16 to version 2.17 on 8/17/05.
The copyright notice on both 2.17 and Apple's version are both 1998-2003.
None of the versions 2003 and later has Apple's changes, as you also noted.
So Apple's version does, indeed, appear to be an Apple hack gone awry.
I suppose it could be fixed by extracting the address before sending
the member to setDeliveryStatus, but I'll refrain from that.
Thank you for the sourceforge reference. It will simplify my scripts.
Allan
The differences:
17c17
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
USA.
---
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
54a55,58
--enable-mail=y|n
-e y|n
Enable user mail deilvery options.
79a84
from Mailman import MemberAdaptor
127c132
def addall(mlist, members, digest, ack, outfp):
---
def addall(mlist, members, digest, ack, outfp, enable):
137a143,146
if enable == 1:
mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED)
else:
mlist.setDeliveryStatus(member, MemberAdaptor.BYADMIN)
146a156,160
if enable == 1:
mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED)
else:
mlist.setDeliveryStatus(member, MemberAdaptor.BYADMIN)
149d162
153c166
'a:n:r:d:w:h',
---
'a:n:r:e:d:w:h',
154a168
'enable-mail=',
168a183
enable_mail = 1
184a200,206
elif opt in ('-e', '--enable-mail'):
if arg.lower()[0] == 'y':
enable_mail = 1
elif arg.lower()[0] == 'n':
enable_mail = 0
else:
usage(1, _('Bad argument to -3/--enable-mail: %(arg)s'))
235c257
addall(mlist, nmembers, 0, send_welcome_msg, s)
---
addall(mlist, nmembers, 0, send_welcome_msg, s, enable_mail)
238c260
addall(mlist, dmembers, 1, send_welcome_msg, s)
---
addall(mlist, dmembers, 1, send_welcome_msg, s, enable_mail)
256d277
At 22:20 -0800 2/27/06, Mark Sapiro wrote:
Allan Hansen wrote:
I'm starting with an empty list called Test and a file, Long,
with a subscriber (me) in long format, and another file, Short,
with a subscriber (me) in short format:
// Empty list
$/usr/share/mailman/bin/list_members -f Test
nothing
// The files Long and Short
$cat Long
Allan Hansen [EMAIL PROTECTED]
$cat Short
[EMAIL PROTECTED]
// Here's the traceback from add_members:
$add_members -r Long Test
Traceback (most recent call last):
File /usr/share/mailman/bin/add_members, line 277, in ?
main()
File /usr/share/mailman/bin/add_members, line 257, in main
addall(mlist, nmembers, 0, send_welcome_msg, s, enable_mail)
File /usr/share/mailman/bin/add_members, line 157, in addall
mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED)
File /usr/share/mailman/Mailman/OldStyleMemberships.py, line 338, in
setDeliveryStatus
self.__assertIsMember(member)
File /usr/share/mailman/Mailman/OldStyleMemberships.py, line 113, in
__assertIsMember
raise Errors.NotAMemberError, member
Mailman.Errors.NotAMemberError: Allan Hansen [EMAIL PROTECTED]
This is apparently some Apple modified add_members script. The line
numbers don't correlate with any distributed Mailman 2.1.x, and the
standard script does not call the setDeliveryStatus() method at all.
snip
// Now, let's try removing same. We have a problem:
$/usr/share/mailman/bin/remove_members -f Long Test
No such member: Allan Hansen [EMAIL PROTECTED]
Yes, I mentioned this previously. remove_members does not accept the
'long' format, but then if you're removing a member, you probably
don't care about the 'name'.
The above shows that 'add_members' and 'remove_members' don't understand
the long format that is readily accepted by 'sync_members' and output by
'list_members'.
Well, my add_members does. I think Apple broke yours. You might try
getting a recent add_members from
http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/bin/add_members,
and see if that works for you.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
_
| Allan Hansen, Ph.D. |
|P.O. Box 2423, Cypress, CA 90630, U.S.A. |
|
[Mailman-Users] Reg CallId in CRCX
Hi all, Can any of you tell me how to validate the below scenario? Ensure that the IUT sends CRCX including Callid which is unique within the list of call agents that control the same gateway. IUT in the above scenario is Call Agent(MGC). Kindly tell me the test procedure for the above scenario? Any help will be appreciated. Thanks in advance, Geetha. -- geetha [EMAIL PROTECTED] -- http://www.fastmail.fm - I mean, what is it about a decent email service? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] MGCP + Reg CallId in CRCX
Hi all, Can any of you tell me how to validate the below scenario? Ensure that the IUT sends CRCX including Callid which is unique within the list of call agents that control the same gateway. IUT in the above scenario is Call Agent(MGC). Kindly tell me the test procedure for the above scenario? Any help will be appreciated. Thanks in advance, Geetha. -- geetha [EMAIL PROTECTED] -- http://www.fastmail.fm - A no graphics, no pop-ups email service -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] MGCP + Reg CallId in CRCX
What make/model of MGC? Also, do you know that it is presently not unique? -Jim P. geetha wrote: Hi all, Can any of you tell me how to validate the below scenario? Ensure that the IUT sends CRCX including Callid which is unique within the list of call agents that control the same gateway. IUT in the above scenario is Call Agent(MGC). Kindly tell me the test procedure for the above scenario? Any help will be appreciated. Thanks in advance, Geetha. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Question about g-zipped mail archives - attachment folders/files?
I'm looking at messages posted to a mailman-driven open-source development email list (on mail.gnome.org/archives), and I've downloaded the g-zip archives I want. When I extract the files, I get one .txt file, and one or more attachment folders (with the suffix .txt.attachment00, .txt.attachment01, etc.) which, in turn, contain additional attachment files (with suffixes .txt.attachment00.attachment00, .txt.attachment00.attachment01, etc.). I don't think these are attachments in the usual sense of attachment in email programs. I don't think other file attachments are allowed on this list. It looks like the the first .txt document (at the root) contains all of the messages, but I was hoping someone could verify that for me. Have you ever dealt with this? Any help you could offer would be appreciated. Dave Yeats -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Question about g-zipped mail archives -attachment folders/files?
Dave Yeats wrote: I'm looking at messages posted to a mailman-driven open-source development email list (on mail.gnome.org/archives), and I've downloaded the g-zip archives I want. When I extract the files, I get one .txt file, and one or more attachment folders (with the suffix .txt.attachment00, .txt.attachment01, etc.) which, in turn, contain additional attachment files (with suffixes .txt.attachment00.attachment00, .txt.attachment00.attachment01, etc.). This is not standard mailman. In the distributed mailman, the monthly .gz files if any are just gzipped versions of the .txt files which in turn just contain flattened versions of the messages in the pipermail HTML archive. These messages also may contain plain text of the form -- next part -- An embedded and charset-unspecified text was scrubbed... Name: .txt Url: http://www.example.com/pipermail/list1/attachments/20060102/f04f72ba/attachment.txt -- next part -- but they don't contain the contents of that attachment.txt file. I don't think these are attachments in the usual sense of attachment in email programs. I don't think other file attachments are allowed on this list. It looks like the the first .txt document (at the root) contains all of the messages, but I was hoping someone could verify that for me. I looked at a couple of archives on mail.gnome.org and the ones I looked at only have one file in the -.txt.gz archive named -m.txt.attachment00 which appears to be just the normal -m.txt file except that the headers of the first message were missing and way more headers were 'kept' - perhaps all of them. Also, a .gz (gzipped) file does not contain a hierarchy of folders and files unless it is a gzip of a .tar or other archive. Where are these coming from in your case? This looks like some mail.gnome.org specific way of dealing with the plain text archive. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] add_members
Allan Hansen wrote:
So Apple's version does, indeed, appear to be an Apple hack gone awry.
I suppose it could be fixed by extracting the address before sending
the member to setDeliveryStatus, but I'll refrain from that.
Yes, but why? See below for fix, but the hack adds the --enabled option
to set the added members delivery status to enabled or disabled by
admin. If the member is truly added, delivery is already enabled, so
this is unnecessary. I suppose if you wanted to use this to add
members with delivery disabled, it might be useful. It can also be
used to set delivery status for existing members...
The differences:
snip
137a143,146
if enable == 1:
mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED)
else:
mlist.setDeliveryStatus(member, MemberAdaptor.BYADMIN)
146a156,160
if enable == 1:
mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED)
else:
mlist.setDeliveryStatus(member, MemberAdaptor.BYADMIN)
In all the setDeliveryStatus calls above, 'member' should be replaced by
'userdesc.address' to allow input with names.
snip
184a200,206
elif opt in ('-e', '--enable-mail'):
if arg.lower()[0] == 'y':
enable_mail = 1
elif arg.lower()[0] == 'n':
enable_mail = 0
else:
usage(1, _('Bad argument to -3/--enable-mail: %(arg)s'))
'-3' above should be '-e'.
And, I wonder if Apple really updated the translations to include that
message?
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Question about g-zipped mail archives -attachment folders/files?
Dave Yeats wrote: On 2/28/06, Mark Sapiro [EMAIL PROTECTED] wrote: Also, a .gz (gzipped) file does not contain a hierarchy of folders and files unless it is a gzip of a .tar or other archive. Where are these coming from in your case? I'm looking at http://mail.gnome.org/archives/evince-list/ This looks like some mail.gnome.org specific way of dealing with the plain text archive. Must be. I thought it was weird, too. I'll double-check that the child folders don't contain anything new, and go from there. Actually, I've looked at http://mail.gnome.org/archives/evince-list/2006-January.txt.gz, and I see the issue is with the way you are expanding the gzip file. If I expand the file with gunzip, I get 2006-January.txt = 98890 bytes. If I expand with Stuffit Deluxe with the create surrounding folder and further expansion options off, I get the same thing, but if I set those options on, I get a 2006-January.txt folder containing files 2006-January.txt.attachment00 = 1876 bytes 2006-January.txt.attachment01 = 277 bytes 2006-January.txt.attachment02 = 88537 bytes signature.asc = 188 bytes signature_1.asc = 188 bytes What is happening is Stuffit is parsing the email into separate messages. The answer is don't use Stuffit, or if you do, turn off the further expansion option. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] add_members
Mark Sapiro wrote: Allan Hansen wrote: So Apple's version does, indeed, appear to be an Apple hack gone awry. I suppose it could be fixed by extracting the address before sending the member to setDeliveryStatus, but I'll refrain from that. Yes, but why? Upon rereading my post, I see the above but why doesn't say what I meant. It appears that I'm saying but why refrain from fixing the hack? This is definitely not what I meant to say. I meant to say but why fix it?, just the opposite of how it comes out. I did indicate how you could fix it, but I also tried to say that I didn't see a real need for the botched option in the first place. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Integrating htdig
michael dunston said the following on 2/28/2006 2:31 AM: [EMAIL PROTECTED], 11:48 AM (-0800) Monday, February 27, 2006: 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? Not this is necessarily of much help, but I was in a similar situation recently and ended up giving up on htdig entirely and using swish-e instead. It wasn't as easy to set up (as htdig integration) but it works and seems much faster to use. I don't recall having to do anything special in this situation. I'm running 2.1.7 with htdig 3.2.0b6 ... I did customize my htdig setup, so that my logo, color scheme and such are used, and I put all that in the templates/en/htdig_conf.txt file. But I don't recall doing anything particularly special there. Best, --Glenn -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. ~Benjamin Franklin, Historical Review of Pennsylvania, 1759 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Set-up Instructions
Hi: Im using mailman for one of our mailing lists, but I have a hard time configuring it. If someone replies to the a mail that’s sent to the mailing list, it goes to everybody on the list, as if I sent a mail to the list. How can I stop that? I tried everything, but no luck! Thanks in Advance Sesiri -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 268.1.1/270 - Release Date: 2/27/2006 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Integrating htdig
Glenn Sieb said the following on 2/28/2006 12:50 PM: I don't recall having to do anything special in this situation. I'm running 2.1.7 with htdig 3.2.0b6 ... I did customize my htdig setup, so that my logo, color scheme and such are used, and I put all that in the templates/en/htdig_conf.txt file. But I don't recall doing anything particularly special there. In case anyone is interested, here are my html files (from $SHAREBASE/htdig/common/.) and my conf file (from $USRBASE/mailman/templates/en/.) Best, --Glenn -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. ~Benjamin Franklin, Historical Review of Pennsylvania, 1759 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Integrating htdig
Glenn Sieb said the following on 2/28/2006 1:13 PM: Glenn Sieb said the following on 2/28/2006 12:50 PM: I don't recall having to do anything special in this situation. I'm running 2.1.7 with htdig 3.2.0b6 ... I did customize my htdig setup, so that my logo, color scheme and such are used, and I put all that in the templates/en/htdig_conf.txt file. But I don't recall doing anything particularly special there. In case anyone is interested, here are my html files (from $SHAREBASE/htdig/common/.) and my conf file (from $USRBASE/mailman/templates/en/.) How about.. if anyone's interested I can email it backchannel LOL :) Best, --G. -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. ~Benjamin Franklin, Historical Review of Pennsylvania, 1759 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Set-up Instructions
Sesiri Pathirane wrote: If someone replies to the a mail that’s sent to the mailing list, it goes to everybody on the list, as if I sent a mail to the list. How can I stop that? I tried everything, but no luck! On the list's general options page you want first_strip_reply_to = No reply_goes_to_list = Poster Beyond that, it is up to the person doing the replying and his/her MUA. Normally, a 'reply-all' (as I'm doing here) will go to the original poster and the list because the list is a recipient of the original post, and a 'reply' will go to the poster only. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Set-up Instructions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sesiri Pathirane wrote: Im using mailman for one of our mailing lists, but I have a hard time configuring it. If someone replies to the a mail that’s sent to the mailing list, it goes to everybody on the list, as if I sent a mail to the list. How can I stop that? I tried everything, but no luck! Mark covered how you can change the reply to in his post. If the list is supposed to not allow anyone but you to post to it, then you'll want to have a look at the FAQ. Search for announce or one-way. In particular, see these entries: 3.11. How do I create a newsletter/announcement/one-way list? 3.34. How do I spoof-proof my one-way (announcements or newsletter) list? - -- ToddOpenPGP - KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp == Damn you all! -- Stewie Griffin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iG0EARECAC0FAkQEm6YmGGh0dHA6Ly93d3cucG9ib3guY29tL350bXovcGdwL3Rt ei5hc2MACgkQuv+09NZUB1rKxQCcChUBymsd1tL0IhVCyub7ufdSaJEAnR/hLylJ t5QTVdTfQ46O1mND3vOC =fEdZ -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailing List
Sesiri Pathirane wrote: Thanks for the Reply on the list. I had selected first_reply_to = no and reply_goes_to_list = poster. But when people reply to the list, it went to everybody on the list. I need to set it up where, if anyone replies to the list, it goes to the list admin. How do I do that? If you want all replies to go to the list owner and not to the original poster, set first_strip_reply_to = Yes reply_goes_to_list = Explicit address reply_to_address = [EMAIL PROTECTED] It seems like you may be trying to set up an announcement type list, in which case, you also probably want to moderate the members so they can't post to the list. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.011.htp for detailed information on setting up this kind of list. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] add_members
Thank you for clarifying, Mark. I do not yet have the knowledge to fix it, thus my comment. I do appreciate the fix, though, because a number of my subscribers do want to be subscribed inactive from a second address that they use for posts (and they don't want duplicates). So I'll use your version. Allan At 9:18 -0800 2/28/06, Mark Sapiro wrote: Mark Sapiro wrote: Allan Hansen wrote: So Apple's version does, indeed, appear to be an Apple hack gone awry. I suppose it could be fixed by extracting the address before sending the member to setDeliveryStatus, but I'll refrain from that. Yes, but why? Upon rereading my post, I see the above but why doesn't say what I meant. It appears that I'm saying but why refrain from fixing the hack? This is definitely not what I meant to say. I meant to say but why fix it?, just the opposite of how it comes out. I did indicate how you could fix it, but I also tried to say that I didn't see a real need for the botched option in the first place. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] add_members
Allan Hansen wrote: Thank you for clarifying, Mark. I do not yet have the knowledge to fix it, thus my comment. I do appreciate the fix, though, because a number of my subscribers do want to be subscribed inactive from a second address that they use for posts (and they don't want duplicates). So I'll use your version. End original message. - So why not add them to the list of approved posters? It's under accept_these_nonmembers on the Privacy options, Send filters page. That's what I do when somebody wants to be able to post from a non-subscribed address. It's clean and easy. Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] add_members
On 2/28/06, Dragon [EMAIL PROTECTED] wrote: Allan Hansen wrote: Thank you for clarifying, Mark. I do not yet have the knowledge to fix it, thus my comment. I do appreciate the fix, though, because a number of my subscribers do want to be subscribed inactive from a second address that they use for posts (and they don't want duplicates). So I'll use your version. End original message. - So why not add them to the list of approved posters? It's under accept_these_nonmembers on the Privacy options, Send filters page. That's what I do when somebody wants to be able to post from a non-subscribed address. It's clean and easy. By doing it that way, it's extra work for the list admin. When folks on my lists want to post for different accounts I give them instructions on how to sub that address and then postpone that subscription. it puts the onus on the onus on the user to make sure they post from legitimate accounts. -- Bryan Carbonnell - [EMAIL PROTECTED] Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting What a great ride! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] add_members
Bryan Carbonnell sent the message below at 11:29 2/28/2006: On 2/28/06, Dragon [EMAIL PROTECTED] wrote: Allan Hansen wrote: Thank you for clarifying, Mark. I do not yet have the knowledge to fix it, thus my comment. I do appreciate the fix, though, because a number of my subscribers do want to be subscribed inactive from a second address that they use for posts (and they don't want duplicates). So I'll use your version. End original message. - So why not add them to the list of approved posters? It's under accept_these_nonmembers on the Privacy options, Send filters page. That's what I do when somebody wants to be able to post from a non-subscribed address. It's clean and easy. By doing it that way, it's extra work for the list admin. When folks on my lists want to post for different accounts I give them instructions on how to sub that address and then postpone that subscription. it puts the onus on the onus on the user to make sure they post from legitimate accounts. End original message. - OK, I still don't understand the real issue here nor exactly how this would be setup. It sounds like more time will be expended setting this up than it would take to actually add a bunch of people to the non-member accept list. It takes me all of a minute to add somebody to that list and it is rare that I even get a request to do it. I can only see that becoming a real time issue on huge lists with lots of people who want to post from an alternate address. In my case, this is extremely unlikely to happen so I go with the simpler approach. Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] add_members
On 2/28/06, Dragon [EMAIL PROTECTED] wrote: OK, I still don't understand the real issue here nor exactly how this would be setup. It sounds like more time will be expended setting this up than it would take to actually add a bunch of people to the non-member accept list. It depends on who's time you consider more valuable. You the admin trying to take care of the lists, possibly the mailman install or even the actual server. It takes me all of a minute to add somebody to that list and it is rare that I even get a request to do it. I can only see that becoming a real time issue on huge lists with lots of people who want to post from an alternate address. In my case, this is extremely unlikely to happen so I go with the simpler approach. For me the issue is time. If someone wants to post from an alternate address, I have stock text that I copy paste into an e-mail and hit send. I can post the text of the e-mail later this evening if you'd like. It details the steps the user has to take to subscribe themselves from a second address and then postpone it. If I added them manually, then I would have to add them, change their address when it changes, and it does, and remove them when they no longer want to post from that address. I also then have to let the other admins know what is going on in case I get hit by a truck. Much easier to have the user do it themselves. I also believe there would be a performance hit on the server (just an assumption nothing I've ever tested) because of having to check the non-member accept list, especially if it gets large. I don't know if the performace hit is even an issue, but it's something to consider. I probably got about 3 or 4 requests a month when I first took over the admin of the lists, now it's down to 1 every few months, since most of the users now know how to do it themselves. I actually see unsubs and resubs from different addresses for the same user on a fairly regular basis, so I know that the requests would stay high for this kind of thing if I hadn't educated the users on how to do it themselves. Granted the lists I administer are populated by extremely tech savy users (MS Access developers list is the main one) so that probably doesn't hurt. Having said all that, your approach works well for you and mine works well for me. 2 different ways to accomplish the same goal. -- Bryan Carbonnell - [EMAIL PROTECTED] Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting What a great ride! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] admin email interface
I see docs for the email interface for members of a list (subscribe, unscubscribe, etc). Are there equivalents for the administration functions (add list, remove list, list admins, list lists, etc)? The goal is to integrate a 3rd party application to use Mailman without having to have a person physically create and administer the list through the web interface. --Tony __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Goodmail spells doom for mailing lists?
At 4:56 PM -0800 2006-02-23, Dave Crocker wrote: From what I can tell, the Goodmail technology does not work through a mailing list. From what I can tell, limited its application to transaction mail will keep this from being a problem. I worked at AOL for over two years, as the first Internet Mail Operations person they ever hired, and left as the Sr. Internet Mail Systems Administrator for AOL. I know how their marketing department works. On the one hand, you have an old creaky system that only ever kinda-semi-sorta-somewhat works on the best days, and costs a boatload of money, people, and time to maintain. On the other hand, you have a system where they get a share of the paid spam that goes through the system, via Goodmail -- a method that they have said will completely by-pass all anti-spam checks, and guarantees that the paid spammer in question will have unhindered access to your mailbox. Which one do you honestly think that they are going to choose? -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 LOPSA member since December 2005. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Goodmail spells doom for mailing lists?
At 9:08 AM -0500 2006-02-24, Jonathan Dill wrote: If you only have a few people on your mailing list, probably nothing, but if you cross a certain threshhold--I'm guessing either number of messages sent from you, or number of spam complaints--AOL just starts rejecting your e-mail, and you have to sign up for their Enhanced Whitelist service, which is apparently being phased out in favor of Goodmail. They have since claimed that they won't phase out the existing whitelist mechanism, but I worked at AOL for two years in the Internet Mail Operations group, and I know how their marketing department works. They may dilly-dally for a while, and keep the existing whitelist mechanism in place for a while, but the amount of money that they're going to get paid as their share of what Goodmail sends to their users as paid spam, that's just going to be too big of an attraction for them. So, bit-by-bit, I am convinced that they will disassemble the whitelist mechanism -- people will get reassigned, budgets will get cut, and it will wind up going the way of the Dodo bird. Sometime last year, AOL just started rejecting our e-mail, and I had to register them for the Enhanced Whitelist program so the e-mail would go to AOL subscribers. One thing that did do is that I started receiving e-mail from AOL every time someone reported the mailing as spam and then I would unsubscribe them from the list. People sign up for the list, confirm their subscription, and then turn around and complain about getting e-mail from us, and then when I take them off the list, they complain that they should not have been removed, I just don't get it. I got first-hand experience as to how stupid most AOL users are during the time I was working there. Believe me, you're interacting with the intelligent ones -- the really dumb ones can't figure out how to send or receive e-mail at all. Since Enhanced Whitelist is supposedly being phased out and we are already on that program, I am wondering if AOL will just start rejecting our e-mail again unless we sign up for Goodmail. Maybe not immediately, but in the long-run, if you want to get e-mail to an AOL recipient for any reason, you're going to have to pay them money -- one way or another. This is a potential cash cow that has been ignored for too long, and once the advertising and marketing vampires get their teeth into this, it's game over, man. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 LOPSA member since December 2005. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] KNOWN_USERS + SpamAssassin discarding lots of mail
I have in my mm_cfg.py :
KNOWN_SPAMMERS = [('X-Spam-Status', 'Yes')]
But for some reason this is discarding lots of mail. Is there some way I
can turn up the debugging so I can see why these messages are being
discarded? Where do these discarded messages go?
Thanks
--
Joel Heenan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Spam check and bounced email's body
(I do not found this problem on the archives)
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.
[EMAIL PROTECTED]
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] KNOWN_USERS + SpamAssassin discarding lots of mail
Joel Heenan wrote:
I have in my mm_cfg.py :
KNOWN_SPAMMERS = [('X-Spam-Status', 'Yes')]
But for some reason this is discarding lots of mail. Is there some way I
can turn up the debugging so I can see why these messages are being
discarded? Where do these discarded messages go?
The messages are being discarded because they have an
X-Spam-Status: Yes
(case insensitive) header. The Message-IDs are logged in the vette log
with the message 'Message discarded, msgid: %s' where %s is replaced
by the message-id or 'n/a' if there isn't one. There is no debugging
knob other than modifying the code. The discarded messages evaporate
without a trace.
If you really think this is resulting in messages being discarded that
shouldn't be, I suggest you remove the KNOWN_SPAMMERS entry from
mm_cfg.py and instead, put
^X-Spam-Status:\s*Yes
in header_filter_rules for some of the problem lists with action Hold.
That way you'll get to see the messages.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Spam check and bounced email's body
Oliver Schulze L.wrote: 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? I think we did the best we can with this last week in the thread you started at http://mail.python.org/pipermail/mailman-users/2006-February/049499.html. To answer your specific question, without modifying Mailman code or turning off admin_immed_notify, you can't. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Integrating htdig
At 3:14 PM -0500 2006-02-27, Jeff Donsbach wrote: Based on the lack of traffic to the mailman3-dev mailing list, is it a safe assumption that Mailman3 development is stalled? (Please, devs, don't take this as criticism. It is just a question). No, I wouldn't say it's stalled. Maybe the online stuff is temporarily paused for the moment, but there's a Python sprint going on right now and I think a lot of people have been involved in helping to get that going, and are participating quite heavily in that process -- part of the sprint may be to do work on Mailman, among other things. I would expect things to pick up again once the sprint is over. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 LOPSA member since December 2005. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Web interface to Mailman list (read, reply, post...)
At 3:27 PM -0800 2006-02-27, Tom Jennings wrote: I realize that MM doesn't contain such a thing, I was hoping someone would know of an external package that does this. I was hoping I was just being an idiot and overlooking an obvious package; that's the easiest thing to fix. Mailman was never intended to be a webmail system. It was never intended to be a web forum system. However, there are some patches floating around that you could use to integrate Mailman with a number of different web forum systems, if you have users that would prefer that method. Integrating with a webmail system would probably be a bit more work, since there's really not much on the Mailman side of things to be done -- it's mostly just setting up a webmail server and giving people a way to sign up for accounts, then giving them a way to use those accounts to send e-mail to the mailing lists you host -- which could just as easily be on a totally different machine. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 LOPSA member since December 2005. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] MGCP + Reg CallId in CRCX
Actually I am new to this MGCP protocol.I am reading RFC 3435 for the first time. I am framing test cases also parallely.So kindly clarify my doubt. Thanks, Geetha. On Tue, 28 Feb 2006 07:21:27 -0500, Jim Popovitch [EMAIL PROTECTED] said: What make/model of MGC? Also, do you know that it is presently not unique? -Jim P. geetha wrote: Hi all, Can any of you tell me how to validate the below scenario? Ensure that the IUT sends CRCX including Callid which is unique within the list of call agents that control the same gateway. IUT in the above scenario is Call Agent(MGC). Kindly tell me the test procedure for the above scenario? Any help will be appreciated. Thanks in advance, Geetha. -- geetha [EMAIL PROTECTED] -- http://www.fastmail.fm - Access all of your messages and folders wherever you are -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
