Re: [Mailman-Users] HTML converted to attachment was:(no subject)
[EMAIL PROTECTED] wrote:
Unfortunately I am encountering problems with sending HTML email to the
mailing lists. Mailman seems to alter the email message and add the
original HTML email as an attachment.
I have content filtering switched off and the option 'convert text/html
to
text/plain' has been switched off as well.
Remove the message header and footer (msg_header and msg_footer on the
admin Non-digest options page. 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
Unfortunately this didn't help. I already configured in my mm_cfg.py to
remove the footer.
I've added my mm_cfg.py information at the bottom of this email.
Thanks for your help.
Brenno.
=== mm_cfg.py config ===
# -*- python -*-
# Copyright (C) 1998,1999,2000 by the Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307,
USA.
This is the module which takes your site-specific settings.
From a raw distribution it should be copied to mm_cfg.py. If you
already have an mm_cfg.py, be careful to add in only the new settings
you want. The complete set of distributed defaults, with annotation,
are in ./Defaults. In mm_cfg, override only those you want to
change, after the
from Defaults import *
line (see below).
Note that these are just default settings - many can be overridden via
the
admin and user interfaces on a per-list or per-user basis.
Note also that some of the settings are resolved against the active list
setting by using the value as a format string against the
list-instance-object's dictionary - see the distributed value of
DEFAULT_MSG_FOOTER for an example.
###
#Here's where we get the distributed defaults.#
from Defaults import *
##
# Put YOUR site-specific configuration below, in mm_cfg.py . #
# See Defaults.py for explanations of the values.#
#-
# The name of the list Mailman uses to send password reminders
# and similar. Don't change if you want mailman-owner to be
# a valid local part.
MAILMAN_SITE_LIST = 'mailman'
#-
# If you change these, you have to configure your http server
# accordingly (Alias and ScriptAlias directives in most httpds)
DEFAULT_URL_PATTERN = 'https://%s/generic/debuf9/cgi-bin/mailman/'
PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private'
IMAGE_LOGOS = '/images/mailman/'
#-
# Default domain for email addresses of newly created MLs
DEFAULT_EMAIL_HOST = 'lists.eu.bt.net'
#-
# Default host for web interface of newly created MLs
DEFAULT_URL_HOST = 'ncca-intra.eu.bt.net'
#-
# Required when setting any of its arguments.
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
#-
# The default language for this server.
DEFAULT_SERVER_LANGUAGE = 'en'
#-
# Iirc this was used in pre 2.1, leave it for now
USE_ENVELOPE_SENDER= 0 # Still used?
#-
# Unset send_reminders on newly created lists
DEFAULT_SEND_REMINDERS = 1
#-
# Uncomment this if you configured your MTA such that it
# automatically recognizes newly created lists.
# (see /usr/share/doc/mailman/README.{EXIM,...})
# MTA=None # Misnomer, suppresses alias output on newlist
#-
# Uncomment if you use Postfix virtual domains, but be sure to
# read /usr/share/doc/mailman/README.POSTFIX first.
# MTA='Postfix'
# Note - if you're looking for something that is imported from mm_cfg,
but you
# didn't find it above, it's probably in
/usr/lib/mailman/Mailman/Defaults.py.
#
# Custom archiving settings
#
DEFAULT_ARCHIVE = On
DEFAULT_ARCHIVE_PRIVATE = 1
ARCHIVE_TO_MBOX = 0
[Mailman-Users] Weird mailing list issues
I have a mailing list that will not accept a specific HTML message from a subscribing user. It will accept other messages but not this particular. I tested the message against a test list and the message posted just fine. So, I can probably conclude that there is something wrong with that particular list. Is that correct? Any ideas? Will rebuilding the archives help? Thanks, LDB -- 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 Typ x-zip-compressed being converted to bin
Hi All We are using Mailman 2.1.5 on RaQ550 Kernel 2.4.19C12_V-1. When we mail the list with an attached zip file the extension is changed to bin in the list archive. The list members receive a zip file with the correct extension. Is there a fix for this. Thanks in advance Michael Barnard [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] HTML converted to attachment
[EMAIL PROTECTED] wrote: Unfortunately I am encountering problems with sending HTML email to the mailing lists. Mailman seems to alter the email message and add the original HTML email as an attachment. I have content filtering switched off and the option 'convert text/html to text/plain' has been switched off as well. Remove the message header and footer (msg_header and msg_footer on the admin Non-digest options page. 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 Unfortunately this didn't help. I already configured in my mm_cfg.py to remove the footer. I've added my mm_cfg.py information at the bottom of this email. Thanks for your help. Brenno. I've had this problem before. It was because some email clients actually send the html as an attachment. They appear usually, as inline, because of how most mail clients are set up, but mailman treats it like the attachment it is. Outlook does this, or at least it used to (I haven't tried lately). I've used Thunderbird successfully. There are also tools out there that create html mails correctly specifically for sending to lists. -- Anne Ramey -- 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] HTML converted to attachment was:(no subject)
[EMAIL PROTECTED] wrote: Unfortunately this didn't help. I already configured in my mm_cfg.py to remove the footer. I've added my mm_cfg.py information at the bottom of this email. Thanks for your help. snip DEFAULT_MSG_HEADER = DEFAULT_MSG_FOOTER = Two things here. These only set defaults. The actual list msg_header and msg_footer are on the Non-digest options page in the admin interface for the list. More importantly, those settings specify a header and a footer consisting of a single blank space. This is very different from no header or footer. If you don't want Mailman to add anything to the message and thus, potentially alter the MIME structure of the message, the header and footer must be the null string. I.e., DEFAULT_MSG_HEADER = DEFAULT_MSG_FOOTER = Then go the the Non-digest options page and select and delete all text including stray white space in msg_header and msg_footer and 'Submit Your Changes'. I promise that if Content filtering-filter_content is No and if the Non-digest options, msg_header and msg_footer are truely empty with no white space and Non-digest options-scrub_nondigest is No, Mailman will not change the MIME structure of the non-digest messages it sends. -- 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] Weird mailing list issues
Lawrence Bowie wrote: I have a mailing list that will not accept a specific HTML message from a subscribing user. It will accept other messages but not this particular. I tested the message against a test list and the message posted just fine. So, I can probably conclude that there is something wrong with that particular list. Is that correct? I'm not sure without seeing the actual message as sent by the poster and the list settings. What happens to the post? If it is held, what is the reason? What is in Mailman's 'vette' log for this post? Any ideas? Will rebuilding the archives help? Rebuilding the archives will not help. -- 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 Typ x-zip-compressed being converted tobin
Michael Barnard wrote: We are using Mailman 2.1.5 on RaQ550 Kernel 2.4.19C12_V-1. When we mail the list with an attached zip file the extension is changed to bin in the list archive. The list members receive a zip file with the correct extension. In Mailman 2.1.5, if the attachment has a filename with an extension and if the extension is one of the extensions that maps to the Content-Type: according to the maps in your particular Python version, the filename extension is used. Otherwise, the extension is 'guessed' from the Content-Type. This should result in an extension of '.zip' for a content type of 'application/x-zip-compressed', but it may not depending on your Python version. In Mailman 2.1.6, a new mm_cfg.py setting SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION was added to force using the filename 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] Moving mailman to a new box
James, Mark Sapiro posted a very useful set of instructions about moving mailman lists around. The message is at: http://www.mail-archive.com/mailman-users@python.org/msg39615.html Here's the important part: ... Moving lists from one installation to another is generally fairly simple. A rough outline is 1) move the lists/listname/config.pck file. 2a) move the archives/private/listname/ directory 2b) move the archives/private/listname.mbox/listname.mbox file 3) run fix_url on the list (bin/withlist -l -r fix_url listname) 4) If desired because of absolute URLs on some archive pages or other reasons, rebuild archives with bin/arch --wipe listname If you are going to do step 4), you can skip step 2a) I hope this helps. Regards, Ricardo Patrick Bogen wrote: On 7/5/06, james edwards [EMAIL PROTECTED] wrote: I am moving our mailman server to a new box. On the old box I was running mailman-2.1.5.32.FC3 and on the new box mailman-2.1.5.1-34rhel4.3. What dirs and files do I need to copy over from the old to the new box to make mailman work ? FAQ 3.4 http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.004.htp should be helpful in this matter. If you have any questions or issues after reading that, feel free to ask. -- 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] List Using Old Membership List
I run Mailman 2.1.6 on a sun Cobalt RAQ 550 server. There are about 100 lists with memberships ranging from 50 to 350. On several occasions, several of the lists seem to have reverted to using membership lists from the past. People who had unsubscribed as much as two years ago, were suddenly subscribed again. Is this possible? If so, how does it happen, and how can it be prevented? finally, my UPS has gone bad, and is in the process of being replaced, so the server has had some ungraceful shutdowns recently. Would this cause problems with Mailman? Dave David Andrews and white cane Harry. -- 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] List Using Old Membership List
David Andrews wrote: I run Mailman 2.1.6 on a sun Cobalt RAQ 550 server. There are about 100 lists with memberships ranging from 50 to 350. On several occasions, several of the lists seem to have reverted to using membership lists from the past. People who had unsubscribed as much as two years ago, were suddenly subscribed again. It's hard to imagine how this could happen. Is this a 'stock' Mailman or do you have a custom member adaptor? If it is a custom member adaptor, I suppose anything can happen depending on the member adaptor and it's underlying storage scheme. If this is a 'stock' mailman, all the membership information is kept in the lists/listname/config.pck file with a one generation backup in lists/listname/config.pck.last, and the config.pck.last is very up to date representing the list's state just before it was last touched. One possibliity is if the installation was upgraded from a 2.0.x installation, there may be old, pre-upgrade config.db files repersenting the pre-upgrade list settings and membership. If the config.pck files somehow became unusable, Mailman could fall back to the config.db which would be way out of date. However, because of the way that config.pck/config.pck.last are updated/rotated, it's hard to see how both could become unusable at the same time. The message here though is that once a list has successfully upgraded/converted from config.db to config.pck files, the config.db files should be removed. Is this possible? If so, how does it happen, and how can it be prevented? See above. finally, my UPS has gone bad, and is in the process of being replaced, so the server has had some ungraceful shutdowns recently. Would this cause problems with Mailman? Maybe. Losing power during disk i/o can cause all kinds of corruption. -- 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] Moving mailman to a new box
On 7/7/06, Ricardo Scachetti Pereira [EMAIL PROTECTED] wrote: James, Mark Sapiro posted a very useful set of instructions about moving mailman lists around. The message is at: Thanks, everything went well. james -- 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
