Re: [Mailman-Users] Saving attachments
At 3:41 PM -0700 2005-09-15, Elvis Fernandes wrote: I notice that when you save the attachments, they are saved with a different name than the name of the original attachment on the email. Is there a way that the attachment can be made to save as the same name as on the email? This sounds like a problem with your mail program. I don't think we can help you with that. -- 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 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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] endless reposting problem
Wow, Some of my clients had their office auto-responder switch on, and their replies ended up running an endless loop through the system so everyone else got 10-15 copies each before I had a chance to turn it off. I thought only a member of the list could post to the list, in this case all moderated so I would have to approve all posts anyway. If the list is not a member of itself, how can it keep posting the same mail to and from itself in a continuous loop? Is there something else I need to configure to stop this happening? Gil -- 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] Private archive for list
Darren G Pifer wrote: I have been trying to get to the private archives of a list but when I click on the URL http://list.odu.edu/private/telephone_logs/ I get nothing on the page. I have been able to access other archives of private lists but for some reason I am not seeing any for this list. I have thought about trying this bin/arch --wipe list-name but I don't want to remove the archives. Is there anything I check for or another script to run to find out if a file is corrupt? Just to be sure, I checked that this list does have a mbox in the archives/private/telephone_logs directory. Are you sure archiving is enabled for this list? Is there a global mailbox file at archives/private/telephone_logs.mbox/telephone_logs.mbox or just the archives/private/telephone_logs.mbox/ directory without the file? If the archives/private/telephone_logs.mbox/telephone_logs.mbox file exists and contains the past posts to the list, then bin/arch --wipe list-name should build archives. If the .mbox file is there and the HTML archives are not being created, there is probably a permissions issue. -- 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] Mailman with MHonArc
Elvis Fernandes wrote: Is there a simple way to delete off the old mail lists. I not not need to archive any data from these old lists. bin/rmlist --archives listname -- 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
[Mailman-Users] attachments in archives have wrong extensions
Hello, When users send email to any of my lists with attachments, they go through fine. But when someone tries to go back and get an attachment from one of the archives, they almost always find that the link to the attachment has a bad extension, and the web browser doesn't know what to do with it. If you do a save as and rename it with the proper extension, the attachments seem to be intact and ok. But most users don't know to do this, an it is causing us problems. Any solution to this? Here is an example of a file that was posted as MyFile.zip: -- next part -- A non-text attachment was scrubbed... Name: IFQSysFlights.zip Type: application/x-zip-compressed Size: 206816 bytes Desc: not available Url : http://my.mailman.server/mailman/private/testlist/attachments/20050916/132776cc/MyFile-0001.bin When the list members recieve the email, the attachment is correct (MyFile.zip), but the archive has a *.bin extension. Thanks for any info, DW -- 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] attachments in archives have wrong extensions
DW wrote: When users send email to any of my lists with attachments, they go through fine. But when someone tries to go back and get an attachment from one of the archives, they almost always find that the link to the attachment has a bad extension, and the web browser doesn't know what to do with it. If you do a save as and rename it with the proper extension, the attachments seem to be intact and ok. But most users don't know to do this, an it is causing us problems. Any solution to this? Here is an example of a file that was posted as MyFile.zip: -- next part -- A non-text attachment was scrubbed... Name: IFQSysFlights.zip Type: application/x-zip-compressed Size: 206816 bytes Desc: not available Url : http://my.mailman.server/mailman/private/testlist/attachments/20050916/132776cc/MyFile-0001.bin The scrubber makes the extension from the content-type (shown as Type: above). If this doesn't agree with the attachment's extension, the one 'guessed' from content-type is used. Here are comments from Scrubber.py # If the filename's extension doesn't match the type we guessed, # which one should we go with? For now, let's go with the one we # guessed so attachments can't lie about their type. The problem in your case is that application/x-zip-compressed is not a registered type (no 'x-' types are). See ftp://ftp.iana.org/assignments/media-types/ One possible solution is to use an MUA that will call a .zip file Content-Type: application/zip which is a registered type, but this probably is not a practical solution. Another possibility is to change the scrubber to use the file extension if any. -- 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] How to make attached jpg show in message body
Bill Morse wrote: Is there any way to make an image show in the body of a message to the list. When I attach an image in entourage, the image displays in the body of the message. When I attach an image to a list message, it only is listed in the attachments area. I think you are saying that if for example you send a post to a list with a Bcc: to yourself and then you view the received post and the Bcc: with the same MUA (e-mail client), the Bcc: shows the image inline and the received post does not. If this is correct, then Mailman has changed the MIME structure of the message in some way. Possibly this has to do with the addition of list headers and/or footers. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.039.htp -- 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] attachments in archives have wrong extensions
Mark Sapiro wrote: DW wrote: When users send email to any of my lists with attachments, they go through fine. But when someone tries to go back and get an attachment from one of the archives, they almost always find that the link to the attachment has a bad extension, and the web browser doesn't know what to do with it. If you do a save as and rename it with the proper extension, the attachments seem to be intact and ok. But most users don't know to do this, an it is causing us problems. Any solution to this? Here is an example of a file that was posted as MyFile.zip: -- next part -- A non-text attachment was scrubbed... Name: IFQSysFlights.zip Type: application/x-zip-compressed Size: 206816 bytes Desc: not available Url : http://my.mailman.server/mailman/private/testlist/attachments/20050916/132776cc/MyFile-0001.bin The scrubber makes the extension from the content-type (shown as Type: above). If this doesn't agree with the attachment's extension, the one 'guessed' from content-type is used. Here are comments from Scrubber.py # If the filename's extension doesn't match the type we guessed, # which one should we go with? For now, let's go with the one we # guessed so attachments can't lie about their type. The problem in your case is that application/x-zip-compressed is not a registered type (no 'x-' types are). See ftp://ftp.iana.org/assignments/media-types/ One possible solution is to use an MUA that will call a .zip file Content-Type: application/zip which is a registered type, but this probably is not a practical solution. Another possibility is to change the scrubber to use the file extension if any. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Cool, thanks! Thanks to your input, I was able to track down a solution: I searched Scrubber.py, and found some logic which said: if mm_cfg.SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION so I edited mm_cfg.py and put in the following line: SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = 1 then restarted mailman.sh I'm extension-happy now. -DW -- 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] mailman stopped working after upgrade
Daevid Vincent wrote: Well, exim hasn't changed since that date above, and the config hasn't changed for even longer, so I believe it *is* mailman and not exim: # ll total 80 drwxr-xr-x 2 root root 4096 Jun 26 12:45 . drwxr-xr-x 77 root root 4096 Sep 13 03:14 .. -rw-r--r-- 1 root root 775 Jul 7 00:57 auth_conf.sub -rw-r--r-- 1 root root 29452 Apr 29 13:54 exim.conf -rw-r--r-- 1 root root 25931 Jul 7 00:57 exim.conf.dist -rw-r--r-- 1 root root 8120 Jul 7 00:57 system_filter.exim Mailman WAS working just fine until September 7th, when I updated it. # ll /usr/local/mailman/mail/mailman -rwxr-sr-x 1 mailman mailman 7768 Sep 7 11:34 /usr/local/mailman/mail/mailman OK. It may well be Mailman. If so, the change is that prior to the update, the wrapper was expecting to be invoked as group 'mail' and now it is expecting to be invoked as group 'mailman', but you say you can't change configure to make the --with-mail-gid = 'mail' because Re-emerging doesn't let me change those .ebuild values. MD5 errors and such. So it would seem you have two choices: 1) change Exim so it does in fact invoke the wrapper as group mailman. or 2) find the src directory and change the line in src/Makefile that says MAIL_GROUP= mailman to MAIL_GROUP= mail and remake the wrapper. Of course, 2) will only avoid the problem until the next update. -- 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] Basic question of new list admin: how do i viewa list of subscri bers?
Brad Knowles wrote: To get the kind of information you want, you pretty much have to telnet or ssh in to the server and use the command-line interface. You're looking for the command list_members. While this is the preferred method, if you don't have sufficient access, you can script the web interface. See http://starship.python.net/crew/jwt/mailman/#throughtheweb for a script. -- 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] Lock files and withlist?
Adrian Wells wrote
customchange.py is located at the root installation directory of Mailman.
It contains:
# Python function to make custom changes
def customchange(m):
curlist = m.real_name
curlist = curlist.lower()
print 'Current list is: ' + curlist
if curlist.startswith('apples'):
print 'Starts with apples! Current host_name is: ' + m.host_name
print 'Changing hostname now...'
m.host_name = 'lists.newlistname.org'
m.Save()
This script is then run with withlist:
./withlist -a -l -r customchange
After preforming this, I noticed that the web interface for lists are not
accessible and that the locks directory contains at least two lock files
for every list.
This probably should be considered a bug in withlist or at least a
documentation deficiency. The problem is when running withlist with -l
and -a switches, only the last list is unlocked by withlist. Thus you
need to unlock the lists in your script. In your example you could do
this two ways
1) make sure you unlock every list, processed or not.
# Python function to make custom changes
def customchange(m):
curlist = m.real_name
curlist = curlist.lower()
print 'Current list is: ' + curlist
if curlist.startswith('apples'):
print 'Starts with apples! Current host_name is: ' +
m.host_name
print 'Changing hostname now...'
m.host_name = 'lists.newlistname.org'
m.Save()
m.Unlock()
2) run withlist with -a but without -l and only lock the lists you're
changing.
# Python function to make custom changes
def customchange(m):
curlist = m.real_name
curlist = curlist.lower()
print 'Current list is: ' + curlist
if curlist.startswith('apples'):
m.Lock()
print 'Starts with apples! Current host_name is: ' +
m.host_name
print 'Changing hostname now...'
m.host_name = 'lists.newlistname.org'
m.Save()
m.Unlock()
3) Safer still is like 2) with the addition of try: finally:
# Python function to make custom changes
def customchange(m):
curlist = m.real_name
curlist = curlist.lower()
print 'Current list is: ' + curlist
if curlist.startswith('apples'):
try:
m.Lock()
print 'Starts with apples! Current host_name is: ' +
m.host_name
print 'Changing hostname now...'
m.host_name = 'lists.newlistname.org'
m.Save()
finally:
m.Unlock()
--
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
[Mailman-Users] strange bounce message
A couple of people have sent replies to one of my lists today and several of the messages bounced like this: === THIS IS A WARNING MESSAGE ONLY YOU DO NOT NEED TO RESEND YOUR MESSAGE === A temporary error occured while delivering to the following address(es): pfenno at ncees.org: 454 TLS not available, must be connected via TCP I will continue trying to send the message until it is delivered or expires. They've replied without incident before. It looks like they have changed something on their end to require the message to be delivered TLS, which the server this message is attempting to deliver to does not support, and that there is nothing I can do...is that correct. What can I tell the sender to do to prevent this? Any pointers would be appreciated. I've been using mailman for a couple of years and haven't run into this before. -- Anne -- 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] Saving attachments
Elvis Fernandes wrote: I notice that when you save the attachments, they are saved with a different name than the name of the original attachment on the email. Is there a way that the attachment can be made to save as the same name as on the email? On Mailman 2.1.5 and earlier, no. On 2.1.6 see the Defaults.py and mm_cfg.py variables SCRUBBER_DONT_USE_ATTACHMENT_FILENAME and SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION. -- 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] strange bounce message
Anne Ramey wrote: A couple of people have sent replies to one of my lists today and several of the messages bounced like this: === THIS IS A WARNING MESSAGE ONLY YOU DO NOT NEED TO RESEND YOUR MESSAGE === A temporary error occured while delivering to the following address(es): pfenno at ncees.org: 454 TLS not available, must be connected via TCP I will continue trying to send the message until it is delivered or expires. They've replied without incident before. Are you saying the list is pfenno at ncees.org and replyers received that bounce instead of the reply going to the list? Are they all in the same domain? Did the bounces all come from the same MTA? which one? It looks like they have changed something on their end to require the message to be delivered TLS, which the server this message is attempting to deliver to does not support, and that there is nothing I can do...is that correct. Maybe. This may also be a temporary issue with your incoming MTA that may resolve before the messages expire and they may be ultimately delivered. What can I tell the sender to do to prevent this? Any pointers would be appreciated. I've been using mailman for a couple of years and haven't run into this before. Probably nothing, but it may depend on the answers to my first set of questions. If in fact something has changed at their end, they probably can't do anything about it unless they changed it in which case they should already know what to do about it. -- 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] strange bounce message
Anne Ramey wrote: A couple of people have sent replies to one of my lists today and several of the messages bounced like this: === THIS IS A WARNING MESSAGE ONLY YOU DO NOT NEED TO RESEND YOUR MESSAGE === A temporary error occured while delivering to the following address(es): pfenno at ncees.org: 454 TLS not available, must be connected via TCP I will continue trying to send the message until it is delivered or expires. They've replied without incident before. It looks like they have changed something on their end to require the message to be delivered TLS, which the server this message is attempting to deliver to does not support, and that there is nothing I can do...is that correct. What can I tell the sender to do to prevent this? Any pointers would be appreciated. I've been using mailman for a couple of years and haven't run into this before. This is an smtp mail server error which has nothing to do with mailman. It looks like the message is coming from their local smtp server and is saying that their smtp server can't reach your smtp server. If the people who are getting these bounce messages are all sending from different servers then the problem is with your smtp server. jc -- 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] Saving attachments
Mark, Thanks for yur response. I am using 2.1.6. However, i do not find mention of SCRUBBER_DONT_USE_ATTACHMENT_FILENAME and SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION in the Defaults.py and mm_cfg.py files. I also searched the mailman FAQ's and do not find any mention of these settings. Anyways, I tried this in mm_cfg.py SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = No And restarted mailman. I still am not able to save an email attachment with the same name as the attachment. Any ideas? Thanks Elvis On 9/16/05, Mark Sapiro [EMAIL PROTECTED] wrote: Elvis Fernandes wrote: I notice that when you save the attachments, they are saved with a different name than the name of the original attachment on the email. Is there a way that the attachment can be made to save as the same name as on the email? On Mailman 2.1.5 and earlier, no. On 2.1.6 see the Defaults.py and mm_cfg.py variables SCRUBBER_DONT_USE_ATTACHMENT_FILENAME and SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, California better 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] How to change all members to conceal address(hide on membership list page)
Bill Morse wrote: I have changed the new members default to hide- how do I change all the existing members to hide? If you have command line access, run $ bin/withlist -l listname Loading list listname (locked) The variable `m' is the listname MailList instance from Mailman import mm_cfg for member in m.getMembers(): ...m.setMemberOption(member, mm_cfg.ConcealSubscription, 1) ... m.Save() Unlocking (but not saving) list: listname Finalizing $ $ is the shell prompt. and ... are Python prompts. The 'empty' response to is Control-D. If you don't have command line access, see http://starship.python.net/crew/jwt/mailman/#throughtheweb for a script that uses the web interface to 'unhide' a list of members. changing 'conceal':0 to 'conceal':1 will make it 'hide' the list instead. The list of members must be in a file, but there is another script at the same location that can make this file. -- 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] Saving attachments
Elvis Fernandes wrote: I am using 2.1.6. However, i do not find mention of SCRUBBER_DONT_USE_ATTACHMENT_FILENAME and SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION in the Defaults.py and mm_cfg.py files. Are you sure you have 2.1.6? From the 2.1.6 Defaults.py # Mailman.Handlers.Scrubber uses attachment's filename as is. # If you don't like this (extremely long mime-encoded filename) then set # this True. SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False # Use of attachment filename extension per se is may be dangerous because # virus fakes it. You can set this True if you filter the attachment by # filename extension SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = False -- 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] strange bounce message
Anne Ramey wrote: Mark Sapiro wrote: Anne Ramey wrote: A couple of people have sent replies to one of my lists today and several of the messages bounced like this: === THIS IS A WARNING MESSAGE ONLY YOU DO NOT NEED TO RESEND YOUR MESSAGE === A temporary error occured while delivering to the following address(es): pfenno at ncees.org: 454 TLS not available, must be connected via TCP I will continue trying to send the message until it is delivered or expires. They've replied without incident before. Are you saying the list is pfenno at ncees.org and replyers received that bounce instead of the reply going to the list? They are telling me the reply when to all but 3 people on the list, who got this message. I'm confused. W replied to the list. The reply reached the list and was received by all but X, Y and Z who received the above message. Is this correct? Were X, Y and Z prior posters in the thread and mentioned in To: or Cc:? Are they all in the same domain? I think so, yes. Did the bounces all come from the same MTA? which one? I think they must have come from the ncees.org mta, but I don't see the corresponding messages in the logs. What was in the From: header of the above message? That specific message should only be sent to the sender of the post, W in this case. Is it possible that W received the three messages (or one message) mentioning X, Y and Z? snip If in fact something has changed at their end, they probably can't do anything about it unless they changed it in which case they should already know what to do about it. Not likely with this group. If their tech dept.s changed something, they may have no idea. I'm trying to figure out if it has to do with mailman's method of delivery or the sender's/replier's method of sending (in addition to trying to figure out what to tell them). That's what I was trying to say. If something changed at their end, they personally probably can't do anything about it unless they personally did the change. I'm still not sure what's going on, but I am guessing that what really happened is that W's reply was sent directly to X, Y and Z (via To: or Cc:) and your list didn't send to them at all and the 'delivery delay' notice(s) was sent to W and that the problem has nothing to do with your list and involves delivery of mail from W directly to X, Y and Z. We need more specific information about what was sent and how and who received these notices and their full contents and headers, not just the above excerpt, before we can know for sure. -- 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] strange bounce message
I'm looking at this again and I have more thoughts/questions. Mark Sapiro wrote: Anne Ramey wrote: Mark Sapiro wrote: Anne Ramey wrote: snip A temporary error occured while delivering to the following address(es): pfenno at ncees.org: 454 TLS not available, must be connected via TCP snip Are you saying the list is pfenno at ncees.org and replyers received that bounce instead of the reply going to the list? You didn't really answer. Is pfenno at ncees.org the list or perhaps a list member or? snip Did the bounces all come from the same MTA? which one? I think they must have come from the ncees.org mta, but I don't see the corresponding messages in the logs. I don't think so. The message appears to have originated from an MTA that was trying to deliver to [EMAIL PROTECTED] and was unable to establish an SMTP session. If there's anything in the logs at ncees.org it would only be a connection refusal. I think we still need more information. -- Mark Sapiro msapiro at value.net 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] Saving attachments
Hello, Yes I am using 2.1.6 and now I find these variables in Defaults.py. I updated the following in mm_cfg.py # Refer Defaults.py SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False # Refer Defaults.py SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = False And restarted mailman (/etc/init.d/mailman restart) I send a new email attachment, but still am unable to save the attachment with the same name. What am I missing? Thanks Elvis On 9/16/05, Mark Sapiro [EMAIL PROTECTED] wrote: Elvis Fernandes wrote: I am using 2.1.6. However, i do not find mention of SCRUBBER_DONT_USE_ATTACHMENT_FILENAME and SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION in the Defaults.py and mm_cfg.py files. Are you sure you have 2.1.6? From the 2.1.6 Defaults.py # Mailman.Handlers.Scrubber uses attachment's filename as is. # If you don't like this (extremely long mime-encoded filename) then set # this True. SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False # Use of attachment filename extension per se is may be dangerous because # virus fakes it. You can set this True if you filter the attachment by # filename extension SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = False -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, California better 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] attachments in archives have wrong extensions
I am battling a somewhat related problem. I am trying to get mailman to save the attachment with the same file name as attachment. So, what is the syntax for SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION Is it True/False or 1/0 I am using mailman 2.1.6 Thanks Elvis On 9/16/05, Mark Sapiro [EMAIL PROTECTED] wrote: DW wrote: I searched Scrubber.py, and found some logic which said: if mm_cfg.SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION I should have pointed you directly at this, but I'm glad you found it anyway. My excuse is it's new in 2.1.6 and I was looking at a 2.1.5 base. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, California better 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/elvisfern%40gmail.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- 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] Saving attachments
Elvis Fernandes wrote: Yes I am using 2.1.6 and now I find these variables in Defaults.py. I updated the following in mm_cfg.py # Refer Defaults.py SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False # Refer Defaults.py SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = False And restarted mailman (/etc/init.d/mailman restart) I send a new email attachment, but still am unable to save the attachment with the same name. I may not understand what you actually want. When you say you are unable to save the attachment with the same name., what exactly do you mean. Are you referring to the name that Mailman chooses for saving an attachment scrubbed from the archives and digest and perhaps from messages if you've configured that? If so, then SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False and SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True in mm_cfg.py should make this name close to the name of the attachment although leading dots and characters except alphanumerics, dash, underscore, and (non-leading)dot will be removed from the name. If this editing is the problem you have, you can't change it because the name must be made safe for use in a URL. If this is not your issue, then you'll have to be more specific about what you're doing and seeing. -- 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
[Mailman-Users] Mailman 2.1.2 and Python 2.4.1
Sorry, I haven't fully searched the FAQ and archives--I'm also guessing I wouldn't find the answer if I did. Does someone know without research whether Mailman 2.1.2 will run under Python 2.4.1. (Due to a disk failure, we're having to replace the build of a server, while mailman is running happily on the other machine. If we just let [most of] mailman get set up by our synchronization process, we'll end up with this combination of Mailman 2.1.2 and Python 2.4.1 on the restored machine.) Thanks. --John -- 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] Saving attachments
Hello, Let me try and explain what I want to accomplish. I send an email to the mailinglist with an attachment abc.xls. Then, I use Internet Explorer to browse this archived email (this was setup using mhonrac). When I get to the webpage, the attachment shows up as abc.xls on the email body. But, when I click on the attachment to save it, the save as name changes to .xls I would like to make the save as name abc.xls to have a consistent name. BTW, I just tried what you suggested in yur previous email, and that does not give this consistency that I am looking for. Thanks Elvis On 9/16/05, Mark Sapiro [EMAIL PROTECTED] wrote: Elvis Fernandes wrote: Yes I am using 2.1.6 and now I find these variables in Defaults.py. I updated the following in mm_cfg.py # Refer Defaults.py SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False # Refer Defaults.py SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = False And restarted mailman (/etc/init.d/mailman restart) I send a new email attachment, but still am unable to save the attachment with the same name. I may not understand what you actually want. When you say you are unable to save the attachment with the same name., what exactly do you mean. Are you referring to the name that Mailman chooses for saving an attachment scrubbed from the archives and digest and perhaps from messages if you've configured that? If so, then SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False and SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True in mm_cfg.py should make this name close to the name of the attachment although leading dots and characters except alphanumerics, dash, underscore, and (non-leading)dot will be removed from the name. If this editing is the problem you have, you can't change it because the name must be made safe for use in a URL. If this is not your issue, then you'll have to be more specific about what you're doing and seeing. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, California better 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] Saving attachments
Elvis Fernandes wrote: Let me try and explain what I want to accomplish. I send an email to the mailinglist with an attachment abc.xls. Then, I use Internet Explorer to browse this archived email (this was setup using mhonrac). When I get to the webpage, the attachment shows up as abc.xls on the email body. But, when I click on the attachment to save it, the save as name changes to .xls I would like to make the save as name abc.xls to have a consistent name. This is a MhonArc question and you'd be much more likely to get an answer from a MhonArc list. BTW, I just tried what you suggested in yur previous email, and that does not give this consistency that I am looking for. The settings I referred to earlier in this thread only affect file names for scrubbed attachments in digests and pipermail archives. -- 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] Saving attachments
Thanks for you replies. Best, Elvis On 9/16/05, Mark Sapiro [EMAIL PROTECTED] wrote: Elvis Fernandes wrote: Let me try and explain what I want to accomplish. I send an email to the mailinglist with an attachment abc.xls. Then, I use Internet Explorer to browse this archived email (this was setup using mhonrac). When I get to the webpage, the attachment shows up as abc.xls on the email body. But, when I click on the attachment to save it, the save as name changes to .xls I would like to make the save as name abc.xls to have a consistent name. This is a MhonArc question and you'd be much more likely to get an answer from a MhonArc list. BTW, I just tried what you suggested in yur previous email, and that does not give this consistency that I am looking for. The settings I referred to earlier in this thread only affect file names for scrubbed attachments in digests and pipermail archives. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, California better 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
[Mailman-Users] Email rejected with un-quoted From with a dot
On an old Debian Woody machine running mailmain 2.0.11 Mailman rejects mail with an un-quoted name part that includes a dot. From: Foo B. Baz [EMAIL PROTECTED] Mailmain then reports: post from foob.bar requires approval. While these work fine: From: Foo B. Bar [EMAIL PROTECTED] From: Foo Barr [EMAIL PROTECTED] I'm sure I've seen this mentioned someplace before but not having luck finding it now. Can anyone point me to info on this. It would be nice to get a patch until the machine can be upgraded to Sarge. Thanks. -- Bill Moseley [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
