[Mailman-Users] odd error with archive(?) and processing of mail cc'd to list with PDF attachement
Setup: Debian AMD64 (mixed testing/stable)
Exim 4.62 (exim-daemon-heavy)
Mailman 2.1.8 compiled from source, non-std debian policy install
Per domain independent installation of mailman in
/var/virtual/$domain/mailman/...
-
According to exim's logs a message sent out on 3/09/2006 was accepted,
delivered to two offsite recipients with a local list in an independent
mailman install for an exim virtual domain.
The message is plain text with a PDF attachment (letters, space and
underscores in filename), sender uses authenticated SMTP and our exim logs
are rather verbose in this regard. They show exim accepting the message,
delivering offsite but no delivery to Mailman. Additionally Mailman logs
only what what is included below for the same time period.
The critical issue was proving the message was sent [done] but a more
concerning issue is why it didn't reach Mailman at all.
Require_explicit_destination is OFF
Maximum_num_recipients is 50
Mail headers: TO: [EMAIL PROTECTED], [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
FROM: [EMAIL PROTECTED]
REPLY-TO: [EMAIL PROTECTED]
The logs below seem greek to me so any assistance in figuring out what they
mean would be appreciated.
(I promise I won't give the 3rd degree at to rationale - chuckles)
I'm afraid I don't know what I'm looking for otherwise FAQ Google would be
more useful. Other messages with PDF attachments go through fine to other
domains and with variations -- just not repeat tries of this same instance.
-
Here are the logs from /var/virtual/$domain/mailman/logs/error
[/var/virtual/$domain/mailman = MMHOME for brevity]
-
Sep 03 13:52:07 2006 qrunner(4093): File MMHOME/pythonlib/email/Utils.py,
line 337, in decode_params
Sep 03 13:52:07 2006 qrunner(4093): charset, language, value =
decode_rfc2231(EMPTYSTRING.join(value))
Sep 03 13:52:07 2006 qrunner(4093): File MMHOME/pythonlib/email/Utils.py,
line 284, in decode_rfc2231
Sep 03 13:52:07 2006 qrunner(4093): charset, language, s = parts
Sep 03 13:52:07 2006 qrunner(4093): ValueError : unpack list of wrong size
Sep 03 13:52:25 2006 qrunner(7888): Traceback (most recent call last):
Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/bin/qrunner, line 278, in?
Sep 03 13:52:25 2006 qrunner(7888): main()
Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/bin/qrunner, line 238, in main
Sep 03 13:52:25 2006 qrunner(7888): qrunner.run()
Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/Mailman/Queue/Runner.py,
line 70, in run
Sep 03 13:52:25 2006 qrunner(7888): filecnt = self._oneloop()
Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/Mailman/Queue/Runner.py,
line 99, in _oneloop
Sep 03 13:52:25 2006 qrunner(7888): msg, msgdata =
self._switchboard.dequeue(filebase)
Sep 03 13:52:25 2006 qrunner(7888): File
MMHOME/Mailman/Queue/Switchboard.py, line 151, in dequeue
Sep 03 13:52:25 2006 qrunner(7888): msg = email.message_from_string(msg,
Message.Message)
Sep 03 13:52:25 2006 qrunner(7888): File
MMHOME/pythonlib/email/__init__.py, line 51, in message_from_string
Sep 03 13:52:25 2006 qrunner(7888): return Parser(_class,
strict=strict).parsestr(s)
Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/pythonlib/email/Parser.py,
line 75, in parsestr
Sep 03 13:52:25 2006 qrunner(7888): return self.parse(StringIO(text),
headersonly=headersonly)
Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/pythonlib/email/Parser.py,
line 64, in parse
Sep 03 13:52:25 2006 qrunner(7888): self._parsebody(root, fp, firstbodyline)
Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/pythonlib/email/Parser.py,
line 240, in _parsebody
Sep 03 13:52:25 2006 qrunner(7888): msgobj = self.parsestr(part)
Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/pythonlib/email/Parser.py,
line 75, in parsestr
Sep 03 13:52:25 2006 qrunner(7888): return self.parse(StringIO(text),
headersonly=headersonly)
Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/pythonlib/email/Parser.py,
line 64, in parse
Sep 03 13:52:25 2006 qrunner(7888): self._parsebody(root, fp, firstbodyline)
Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/pythonlib/email/Parser.py,
line 146, in _parsebody
Sep 03 13:52:25 2006 qrunner(7888): boundary = container.get_boundary()
Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/pythonlib/email/Message.py,
line 762, in get_boundary
Sep 03 13:52:25 2006 qrunner(7888): boundary = self.get_param('boundary',
missing)
Sep 03 13:52:25 2006 qrunner(7888): FileMMHOME/pythonlib/email/Message.py,
line 616, in get_param
Sep 03 13:52:25 2006 qrunner(7888): for k, v in
self._get_params_preserve(failobj, header):
Sep 03 13:52:25 2006 qrunner(7888): File
MMHOME/pythonlib/email/Message.py, line 563, in _get_params_preserve
Sep 03 13:52:25 2006
Re: [Mailman-Users] odd error with archive(?) and processing of mail cc'd to list with PDF attachement
Bretton Vine said the following on 2006/09/13 09:28 AM: Sep 03 13:52:25 2006 qrunner(7888): charset, language, value = decode_rfc2231(EMPTYSTRING.join(value)) Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/pythonlib/email/Utils.py, line 284, in decode_rfc2231 http://rfc.net/rfc2231.html gives me an idea of possible problems but no solutions. -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | One of the penalties for refusing to participate in politics is that you end up being governed by your inferiors. - Plato -- 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] Problems with digests
Am Do, 7.09.2006, 15:57, schrieb Mário Filipe: Hello I have two problems with digests, and maybe you can help me: - on one mailing list some users complain that they don't get their own posts when they get the digest. I've tried this on a test list and i get my posts so my question is if there is any setting which i might have overlooked that would cause this? - I'm using debian testing and recently some lists fail to send the messages. I believe it is related to character-sets and maybe python, but maybe some of you have a better idea. This is what I get on the trace: Traceback (most recent call last): File /usr/lib/mailman/cron/senddigests, line 94, in ? main() File /usr/lib/mailman/cron/senddigests, line 86, in main mlist.send_digest_now() File /var/lib/mailman/Mailman/Digester.py, line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 142, in send_digests send_i18n_digests(mlist, mboxfp) File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 324, in send_i18n_digests msg = scrubber(mlist, msg) File /var/lib/mailman/Mailman/Handlers/Scrubber.py, line 393, in process replace_payload_by_text(msg, sep.join(text), charset) File /var/lib/mailman/Mailman/Handlers/Scrubber.py, line 175, in replace_payload_by_text msg.set_payload(text, charset) File email/Message.py, line 218, in set_payload File email/Message.py, line 242, in set_charset TypeError: iso-8859-1 Thanks -- Mário Filipe Same problem here :-| hjb :-? -- Hans-Juergen Beie [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
[Mailman-Users] Automatic creation of new lists
Hi, for our University I want to setup automatically mailinglists for each course and study year (some 10.000 mailing lists). I wonder, is something available for this aim? I could adapt newlist to make it non-interactive and script it with add_members, but probably some of you did this already or have a better idea? The setup that I have in mind/development is: - mailman on Debian Linux with exim4 - Setup a default config for new lists in mm_cfg.py (drop welcome message, setup one owner, ...) - From the database: create files with the listnames as filename and the email addresses as contents. - From these filenames: create new lists with a kind of adapted newlist??? - Run add_members for each list Who knows or has such adapted non-interactive newlist, or has a better idea alltogether? Thx -- Frederik Questier http://questier.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] Problems with digests
Am Mi, 13.09.2006, 12:58, schrieb Hans-Juergen Beie: Am Do, 7.09.2006, 15:57, schrieb Mário Filipe: Hello I have two problems with digests, and maybe you can help me: - on one mailing list some users complain that they don't get their own posts when they get the digest. I've tried this on a test list and i get my posts so my question is if there is any setting which i might have overlooked that would cause this? - I'm using debian testing and recently some lists fail to send the messages. I believe it is related to character-sets and maybe python, but maybe some of you have a better idea. This is what I get on the trace: Traceback (most recent call last): [...] TypeError: iso-8859-1 Thanks -- Mário Filipe Same problem here :-| hjb :-? According to http://groups.google.de/group/linux.debian.bugs.dist/browse_frm/thread/baf737656b6d5c1b/412f8d56338e22ad?lnk=gstq=Bug%23384016rnum=1#412f8d56338e22ad this is a bug in Python 2.4. (search for Bug#384016: I have this problem too, and it's caused by python 2.4. with google.groups.com if the above link doesn't work) The workaround given there seems to solve the problem temporarily. In short: Replace the first line in /usr/lib/mailman/cron/senddigests # ! /usr/bin/python by #! /usr/bin/python2.3 if you have a Python2.3 installed. As this problem appeared here (debian/etch, Mailman 2.1.8-2) after upgrading Python 2.3 to 2.4 this seems to be reasonable. hjb :-? -- 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] Problems with digests
In short: Replace the first line in /usr/lib/mailman/cron/senddigests # ! /usr/bin/python by #! /usr/bin/python2.3 if you have a Python2.3 installed. As this problem appeared here (debian/etch, Mailman 2.1.8-2) after upgrading Python 2.3 to 2.4 this seems to be reasonable. Hi, I want to clarify the situation. Is this specific to debian? Can you try these and check the email version? $ python Python 2.4.3 ... import email email.__version__ '3.0.1' ^D $ cd prefix/cron $ python Python 2.4.3 ... import paths import email email.__version__ '2.5.7' The email-3.0.x in Python 2.4 is not suitable for mailman. Mailman 2.1.8(or 9) works best with the email-2.5.7(or 8) which is the bug fix version of Python 2.3 library. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] Problems with digests
Tokio Kikuchi wrote: In short: Replace the first line in /usr/lib/mailman/cron/senddigests # ! /usr/bin/python by #! /usr/bin/python2.3 if you have a Python2.3 installed. As this problem appeared here (debian/etch, Mailman 2.1.8-2) after upgrading Python 2.3 to 2.4 this seems to be reasonable. Hi, I want to clarify the situation. Is this specific to debian? Can you try these and check the email version? $ python Python 2.4.3 ... import email email.__version__ '3.0.1' ^D $ cd prefix/cron $ python Python 2.4.3 ... import paths import email email.__version__ '2.5.7' The email-3.0.x in Python 2.4 is not suitable for mailman. Mailman 2.1.8(or 9) works best with the email-2.5.7(or 8) which is the bug fix version of Python 2.3 library. # python Python 2.4.3 (#2, Apr 25 2006, 07:14:33) [GCC 3.4.4 [FreeBSD] 20050518] on freebsd6 Type help, copyright, credits or license for more information. import email email.__version__ '3.0.1' # cd /usr/local/mailman/cron/ # python Python 2.4.3 (#2, Apr 25 2006, 07:14:33) [GCC 3.4.4 [FreeBSD] 20050518] on freebsd6 Type help, copyright, credits or license for more information. import paths import email email.__version__ '2.5.6' # uname -spr FreeBSD 6.1-STABLE i386 -- 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] RELEASED: Mailman 2.1.9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On behalf of the GNU Mailman development team, I'm please to announce GNU Mailman 2.1.9. This is primarily a security and bug fix release and it is highly recommended that all sites upgrade to this version. Mailman 2.1.9 also contains support for two new languages: Arabic and Vietnamese. Mailman is free software for managing email mailing lists and e- newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, including download links, please see: http://www.list.org http://mailman.sf.net http://www.gnu.org/software/mailman A more detailed change list is included below. Enjoy, - -Barry 2.1.9 (12-Sep-2006) Security - A malicious user could visit a specially crafted URI and inject an apparent log message into Mailman's error log which might induce an unsuspecting administrator to visit a phishing site. This has been blocked. Thanks to Moritz Naumann for its discovery. - Fixed denial of service attack which can be caused by some standards-breaking RFC 2231 formatted headers. CVE-2006-2941. - Several cross-site scripting issues have been fixed. Thanks to Moritz Naumann for their discovery. CVE-2006-3636 - Fixed an unexploitable format string vulnerability. Discovery and fix by Karl Chen. Analysis of non-exploitability by Martin 'Joey' Schulze. Also thanks go to Lionel Elie Mamane. CVE-2006-2191. Internationalization - New languages: Arabic, Vietnamese. Bug fixes and other patches - Fixed Decorate.py so that characters in message header/footer which are not in the character set of the list's language are ignored rather than causing shunted messages (1507248). - Switchboard.py - Closed very tiny holes at the upper ends of queue slices that could result in unprocessable queue entries. Improved FIFO processing when two queue entries have the same timestamp. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRQgPGnEjvBPtnXfVAQIVoQP/R2DffgpcPMzUrsef+ZEcYUeuQ1mOcol2 Z2+iQiHkCx6SP2B/NzOzqMQybvQAAe/TzJWzcfqDDoDDdF+vhJH+kkQIuRwHc5jd +TDF1NOUBegTyxQnoyCHVQddcVNMg9HTTkdwHuvE8MhP1gNuHEnefxf2wbf5+hRq h5/qlBiANn0= =VCTA -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
[Mailman-Users] Arquives sorting problems
Hello Some users of our mailing lists are complaining that when using the archives, sorted by date, some messages are skipped when using the Next message and Previous message links. For example: Message 1 Message 2 Message 3 Message 4 Message 5 Message 6 Message 7 Message 8 Message 9 Message 10 What they say is that going from message 1 to 10 will skip a few of the messages in between. I've tried recreating the archive but it didn't work. Does any one have a clue on what might be going on? Thank you -- Mário Filipe Serviço de Computação da Universidade de Évora [EMAIL PROTECTED] http://neptuno.sc.uevora.pt/~mjnf signature.asc Description: Esta é uma parte de mensagem assinada digitalmente -- 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] Automatic creation of new lists
Op Wednesday 13 September 2006 13:30, schreef Frederik Questier: Hi, for our University I want to setup automatically mailinglists for each course and study year (some 10.000 mailing lists). I wonder, is something available for this aim? I could adapt newlist to make it non-interactive and script it with add_members, but probably some of you did this already or have a better idea? The setup that I have in mind/development is: - mailman on Debian Linux with exim4 - Setup a default config for new lists in mm_cfg.py (drop welcome message, setup one owner, ...) - From the database: create files with the listnames as filename and the email addresses as contents. - From these filenames: create new lists with a kind of adapted newlist??? - Run add_members for each list Who knows or has such adapted non-interactive newlist, or has a better idea alltogether? OK, I found that newlist can be used non-interactively by supplying all it needs on the command line. Pretty sweet. I guess the above described setup is the best way to go? I'll publish a HOWTO for such automated setups when I'm ready. -- Frederik Questier http://questier.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
[Mailman-Users] Mailman upgrade
Can I go directly from Mailman 2.1.6 to Mailman 2.1.9 by doing the following ./configure make install -- 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] Virtual sites
How can I set mailman to use the MX record instead of localhost (or one static address) for sending mail? Thanks! Jay Vaagen Certified Technician Abadata Computer Corporation, Inc. mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Phone: 989 883 3411 Fax: 989 883 9313 -- 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] Problems with digests
Tokio Kikuchi said the following on 2006/09/13 02:45 PM:
Can you try these and check the email version?
snip
The email-3.0.x in Python 2.4 is not suitable for mailman. Mailman
2.1.8(or 9) works best with the email-2.5.7(or 8) which is the bug fix
version of Python 2.3 library.
Working under the assumption that this is related to the problem I posted
I've upgraded python and still get a problem with certain attachments going
to lists. Exim accepts the message, delivers to mailman and then mailman
chokes and fails to deliver to list members
Python 2.5c1 (r25c1:51305, Aug 19 2006, 21:01:01)
[GCC 4.1.2 20060814 (prerelease) (Debian 4.1.1-11)] on linux2
Type help, copyright, credits or license for more information.
import email
email.__version__
'4.0.1'
ctrl-D
# cd MMHOME/cron
# python
Python 2.5c1 (r25c1:51305, Aug 19 2006, 21:01:01)
[GCC 4.1.2 20060814 (prerelease) (Debian 4.1.1-11)] on linux2
Type help, copyright, credits or license for more information.
import paths
import email
email.__version__
'2.5.7'
What gives? What is odd is that some files with ' in the filename go to
the list while others don't. I've tried changing characterset in mail client
to no avail.
Apologies if I'm hijacking a thread, it's just I'm seen similar errors when
trying to post to a list with a PDF attachment ... not directly related to
senddigests at all (digests disabled)
I still get the following in the error log:
(edited for brevity)
---
qrunner(18178): File MMHOME/pythonlib/email/Parser.py, line 75, in parsestr
qrunner(18178): return self.parse(StringIO(text), headersonly=headersonly)
qrunner(18178): File MMHOME/pythonlib/email/Parser.py, line 64, in parse
qrunner(18178): self._parsebody(root, fp, firstbodyline)
qrunner(18178): File MMHOME/pythonlib/email/Parser.py, line 240, in _parsebody
qrunner(18178): msgobj = self.parsestr(part)
qrunner(18178): File MMHOME/pythonlib/email/Parser.py, line 75, in parsestr
qrunner(18178): return self.parse(StringIO(text), headersonly=headersonly)
qrunner(18178): File MMHOME/pythonlib/email/Parser.py, line 64, in parse
qrunner(18178): self._parsebody(root, fp, firstbodyline)
qrunner(18178): File MMHOME/pythonlib/email/Parser.py, line 146, in
_parsebody
qrunner(18178): boundary = container.get_boundary()
qrunner(18178): File MMHOME/pythonlib/email/Message.py, line 762, in
get_boundary
qrunner(18178): boundary = self.get_param('boundary', missing)
qrunner(18178): File MMHOME/pythonlib/email/Message.py, line 616, in
get_param
qrunner(18178): for k, v in self._get_params_preserve(failobj, header):
qrunner(18178): File MMHOME/pythonlib/email/Message.py, line 563, in
_get_params_preserve
qrunner(18178): params = Utils.decode_params(params)
qrunner(18178): File MMHOME/pythonlib/email/Utils.py, line 337, in
decode_params
qrunner(18178): charset, language, value =
decode_rfc2231(EMPTYSTRING.join(value))
qrunner(18178): File MMHOME/pythonlib/email/Utils.py, line 284, in
decode_rfc2231
qrunner(18178): charset, language, s = parts
--
| Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] |
| GPG: http://bretton.hivemind.net/bretton_vine.asc |
Insanity: doing the same thing over and over again and expecting different
results. - Albert Einstein
--
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 upgrade
On 9/13/06, Kory Wheatley [EMAIL PROTECTED] wrote: Can I go directly from Mailman 2.1.6 to Mailman 2.1.9 by doing the following ./configure make install Yes*. (You need to make sure you run ./configure with the same options you ran it with originally, otherwise you might end up with duplicate and/or incompatible code.) -- - Patrick Bogen -- 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] Alternative to Mailman
Hello, Looking at similar problems in the future...interesting to think about. We're looking at PHPlist, PHPList is all web-based, isn't it? Some clients may want to respond over email. DadaMail and other packages. We need to be able to send up to 100,000 at a shot, announce only, use MySQL Have you dbdump-ed a list pickle? Do you really want all that in MySQL? What for? and with html mail (or provide that as an option, which Mailman can't do), Uh, yes it can? Isn't that a setting in Outlook when you compose the message? In the best of worlds, I'd like to be able to maintain various fields on list members including name and source so, for example, we could decide to send an email to all list members from Source A and Source C, but not Source B, and if there are duplicates on lists A and B, of course send only one copy. Why not put all members on one big list, then put a customized filter that checked an external database that had all the rules. The filter goes into the python code. Maybe that's getting into the realm of campaign software. All of our list members are opt-in, but they come from various sources, so I'd like to be able to pick sources for each mailing and essentially build a list each time from various criteria. Keep those filters in the external database. If you pick a filter for a message, indicate filter name somewhere in the message, and then send, the custom code would ask the database for the list, or whether a member should get the message. Filter management would stay in the database. Also the identity management issues you raise. Don't want to jam all that into a mailing list manager. Just IMHO, -R -- 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] Alternative to Mailman
On Wed, Sep 13, 2006 at 11:59:04AM -0400, Kucera, Rich wrote: DadaMail and other packages. We need to be able to send up to 100,000 at a shot, announce only, use MySQL Have you dbdump-ed a list pickle? Do you really want all that in MySQL? What for? Share some of the information with other applications, eg: name, email, password. -- Alain Williams Parliament Hill Computers Ltd. Linux Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 http://www.phcomp.co.uk/ #include std_disclaimer.h -- 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] RELEASED: Mailman 2.1.9
Barry Warsaw said the following on 2006/09/13 04:00 PM: On behalf of the GNU Mailman development team, I'm please to announce GNU Mailman 2.1.9. This is primarily a security and bug fix release and it is highly recommended that all sites upgrade to this version. Excellent news, just one question before I upgrade (and hopefully fix some errors as per previous posts) -- and hopefully someone can answer here: Will the following patch apply to 2.1.9 source? [ 1220144 ] allow specifying another list in accept_these_nonmembers http://sourceforge.net/tracker/index.php?func=detailaid=1220144group_id=103atid=300103 regards -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | NP: http://www.sylviemarks.de/mp3/radiox060906sylviemarks.mp3 -- 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] Virtual sites
On 9/13/06, Jay Vaagen [EMAIL PROTECTED] wrote: How can I set mailman to use the MX record instead of localhost (or one static address) for sending mail? I've added FAQ 4.72 http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.072.htp as a simple answer for this. P.S., to the list, this is the first time I've added an FAQ entry. Please let me know if I did something wrong, or there's some way to be more clear. -- - Patrick Bogen -- 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] Alternative to Mailman
use MySQL What for? Share some of the information with other applications, eg: name, email, password. Well if you're talking strategic SQL access, either of these (*if only* they supported ODBC calling mechanisms) you could bolt it onto mailman and have at it: http://gadfly.sourceforge.net/ http://www.pythonweb.org/projects/snakesql/ You can still have at it in SQL without the calling mechanisms, but you're limited to command line that calls python script...maybe not so limited. SOAP could fix it so you could create an XML datasource bolted on the side of mailman. Then you could have at it from Excel etc. or from within real databases that supported some kind XML query. -R -- 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] Virtual sites
At 11:54 AM -0400 2006-09-13, Jay Vaagen wrote: How can I set mailman to use the MX record instead of localhost (or one static address) for sending mail? You don't. Mailman is not an MTA, so it knows nothing of MX records. Maybe you can tell us more about where you want to get, and then maybe we can tell you more about how you could get there. -- 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 Founding Individual Sponsor of LOPSA. 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] Virtual sites
Patrick Bogen wrote: On 9/13/06, Jay Vaagen [EMAIL PROTECTED] wrote: How can I set mailman to use the MX record instead of localhost (or one static address) for sending mail? I've added FAQ 4.72 http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.072.htp as a simple answer for this. The problem with this approach is that Mailman will still only use the single specified mail server, rather than processing a list of mailservers defined as MX records for a DNS domain. It would be a nice addition if Mailman allowed SMTPHOST to be set to either an explicit host or a domain to be queried. Sendmail accomplishes this in mailertable by using these two formats: explict: mx6.somedomain.com lookup: [somedomain.com] Using the lookup method causes Sendmail to query DNS for the current MX host(s) and then traverse the list until it finds one available. -Jim P. -- 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] Virtual sites
Jim Popovitch wrote: The problem with this approach is that Mailman will still only use the single specified mail server, rather than processing a list of mailservers defined as MX records for a DNS domain. If I have a domain name for which there are 3 MXs setup in a Round Robin configuration, wouldn't mailman be given a different IP each time? For example: ; zone file fragment @ IN MX 10 mail.example.com. mail IN A 192.168.0.4 IN A 192.168.0.5 IN A 192.168.0.6 If I tell mailman SMTPHOST='mail.example.com', in theory it should receive a different IP to connect to each time it queries that host name. UNLESS mailman is internally caching that information (to use again on subsequent runs.) -- W | It's not a bug - it's an undocumented feature. + Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130 IT Director / SysAdmin / Websmith . 800.441.3873 x130 Photo Craft Laboratories, Inc.. 3550 Arapahoe Ave. #6 http://www.pcraft.com . . .. Boulder, CO 80303, U.S.A. -- 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] Virtual sites
Ok, so after reading all this it becomes clear to me that this is not going to be an easy fix.. If I understand all this correctly, there's no current feature that will allow mailman to send mail from the correct virtual domain's hostname, and not localhost.. correct? Let's say I have these mailing lists: norwegians on the domain norway.com - 1.1.1.10 visitors on the domain sweden.com - 1.1.1.11 tourist on the domain denmark.com - 1.1.1.12 The hostname of the server running mailman is mailserver.europe.com - with IP 1.1.1.100 When someone posts to [EMAIL PROTECTED] I would like emails sent from that mailing list to originate from mail.norway.com ie. 1.1.1.10, not mailserver.europe.com or 1.1.1.100. When someone posts to [EMAIL PROTECTED] I would like emails sent from that mailing list to originate from mail.sweden.com ie. 1.1.1.11. The mail alias for those 3 domains would be mail. Any way to do this? How about passing the domain name for the list through to SMTPHOST when the email is sent and adding MAIL as the host name to make the FQDN...seeing as MAIL is a static naming scheme.?? Maybe that's not even possible...sounds good in theory... Thanks so much for your replies... :) Jay Vaagen Certified Technician Abadata Computer Corporation, Inc. [EMAIL PROTECTED] Phone: 989 883 3411 Fax: 989 883 9313 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Popovitch Sent: Wednesday, September 13, 2006 1:54 PM Cc: Mailman-Users@python.org Subject: Re: [Mailman-Users] Virtual sites Patrick Bogen wrote: On 9/13/06, Jay Vaagen [EMAIL PROTECTED] wrote: How can I set mailman to use the MX record instead of localhost (or one static address) for sending mail? I've added FAQ 4.72 http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.072.htp as a simple answer for this. The problem with this approach is that Mailman will still only use the single specified mail server, rather than processing a list of mailservers defined as MX records for a DNS domain. It would be a nice addition if Mailman allowed SMTPHOST to be set to either an explicit host or a domain to be queried. Sendmail accomplishes this in mailertable by using these two formats: explict: mx6.somedomain.com lookup: [somedomain.com] Using the lookup method causes Sendmail to query DNS for the current MX host(s) and then traverse the list until it finds one available. -Jim P. -- 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/jay%40abadata.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] Virtual sites
In a flurry of recycled electrons, Jay Vaagen wrote: If I understand all this correctly, there's no current feature that will allow mailman to send mail from the correct virtual domain's hostname, and not localhost.. correct? As I understand the current implimentation of virtual domains, much of the config is kept as site-wide, not domain- or list-wide, data. To do what you're talking about would require at least domain-wide config. Probably the easiest way to get the 'multiple' domains that you want is to run one instance of mailman for each domain. Yoy can then configure the smtphost for that specific domain. Perhaps virtual domains in 2.2 will have this feature, however you'll have to wait for 2.2 then :). z! -- 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] Virtual sites
Carl Zwanzig wrote: Probably the easiest way to get the 'multiple' domains that you want is to run one instance of mailman for each domain. Yoy can then configure the smtphost for that specific domain. And to second this part of Carl's e-mail, this is exactly what I'm doing on my end. I wanted to be able to have the same mailing list *name* exist across multiple virtual domains. Back in January 2003 I posted a question about this, and at the time, Barry Warsaw replied with the following: -- AMK Under MM2.0.x I created separate installations for AMK different virtual hosts. This allowed me to create the same AMK list name, on a different virtual host without having mailman AMK conflict. Now, with MM2.1, how should I continue to do this? MM2.1 doesn't lift this restriction, so your best bet is to continue your current approach. However, there /is/ a semi-supported extension mechanism that you might be able to use to share one installation to do it all. See the Mailman/Site.py file for details, although there's no guarantee this will give you enough of a hook. -Barry -- So far I haven't seen this change, and to be perfectly honest, I don't really expect it to either. I can't speak for everyone, but I think the number of people who have the same type of installation as me are fairly limited compared to everyone else who runs MM. But then, I could be wrong. MM does what it was designed to do. The fact that a few of us have quirky setups, I don't think is enough to go through a rewrite. :) Just my two cents. But to comment on Jay Vaagen's original post, I think separating the virtual domains across multiple MM installations might be the easier way to go. I have one server that's is specifically for MM, and it's hosting 7 different domains, each one with anywhere between 5 to 50 lists on each installation. -- Ash -- 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] Problems with digests
Hi, The email-3.0.x in Python 2.4 is not suitable for mailman. Mailman 2.1.8(or 9) works best with the email-2.5.7(or 8) which is the bug fix version of Python 2.3 library. I see. How can I fix that? I suspect the debian people have omitted the mailman-2.5.x package from their ports. File a bug report on their developers site. In the mean time, you can extract email-2.5.x from our official distribution and install into prefix/pythonlib directory. Or, you can edit cron/senddigests to use python2.3 as was suggested earlier. Cheers, -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] Problems with digests
Bretton Vine writes: What gives? What is odd is that some files with ' in the filename go to the list while others don't. I've tried changing characterset in mail client to no avail. This is a completely different issue IIRC. For reasons I don't think I've ever seen explained, the =?ISO-8859-1?Q?stuff%20goes%20here?= MIME word syntax (RFC 2047, I think?) is unsuitable for use in header parameters like file names. So RFC 2231 syntax was invented, which uses ' as a syntax delimiter the way MIME words use = and ?. Unfortunately, there is a bug (fixed in 2.1.9, again IIRC) in the way that Mailman's decode_rfc2231 function parses RFC 2231 syntax (basically, it doesn't expect the parameter value to contain any apostrophes other than those used for the purposes of RFC 2231). None of the above is necessarily accurate, but if you need more detail, feel free to wait for the authoritative version from Tokio, Barry, or Mark, or you can search the archives for rfc2231 (both mailman-users and mailman-developers, I think it was reported on the former and diagnosed on the latter). HTH Steve -- 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 Debian/Ubuntu Mailman Package
On 9/12/06 11:26 AM, Dragon [EMAIL PROTECTED] wrote: Version 2.1.5 is rather old. I believe there are some security issues that have been fixed since that release. IMO it is a good idea to use the latest version to preclude as many potential issues as possible. The security fixes are very likely backported by the major distributions. Beyond that, they don't tend to do version upgrades of components until their next major release. (This was a major nuisance a while back the Debian and Exim, as Debian had such a long wait for a major release that nearly everyone on the Exim-users list had forgotten how to drive the Exim version found in the stable Debian release.) Mailman 2.1.5 remains old, but if the distributions' updates are applied, the security fixes are likely close to current if not current. --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] Virtual sites
At 1:53 PM -0400 2006-09-13, Jim Popovitch wrote: The problem with this approach is that Mailman will still only use the single specified mail server, rather than processing a list of mailservers defined as MX records for a DNS domain. Mailman is a Mailing List Management system. It is not an MTA. It does not do the work of an MTA. It leave the MTA work to real MTAs that are designed to do that work. Looking up MX records is the job of an MTA, not an MLM. -- 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 Founding Individual Sponsor of LOPSA. 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] Virtual sites
At 2:57 PM -0400 2006-09-13, Jay Vaagen wrote: If I understand all this correctly, there's no current feature that will allow mailman to send mail from the correct virtual domain's hostname, and not localhost.. correct? Mailman is a Mailing List Management system, not an MTA. The kind of thing you're asking for would be within the purview of the MTA, and therefore Mailman would know nothing of it. Heck, I don't even know any MTAs that allow you to do this kind of thing, but it's more their line of work than Mailman -- we just dump our outgoing traffic on the MTA, and let it do the heavy lifting of actually handling the delivery to the respective remote ends. Any way to do this? Nope. I can't even imagine what kind of source code modifications would be required to achieve your goal. -- 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 Founding Individual Sponsor of LOPSA. 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] Virtual sites
On Wed, 2006-09-13 at 23:23 -0500, Brad Knowles wrote: At 1:53 PM -0400 2006-09-13, Jim Popovitch wrote: The problem with this approach is that Mailman will still only use the single specified mail server, rather than processing a list of mailservers defined as MX records for a DNS domain. Mailman is a Mailing List Management system. It is not an MTA. It does not do the work of an MTA. It leave the MTA work to real MTAs that are designed to do that work. Looking up MX records is the job of an MTA, not an MLM. Looking up MX records is also the job of an MUA, and Mailman is very much like an MUA, albeit on steroids. IMHO of course. -Jim P. -- 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] Virtual sites
At 12:51 AM -0400 2006-09-14, Jim Popovitch wrote: Looking up MX records is also the job of an MUA, and Mailman is very much like an MUA, albeit on steroids. IMHO of course. I don't know of an MUA on the planet that looks up MX records. Check your RFCs. Checking MX records is most definitely the purview of MTAs, since they're the ones expected to implement 2821 and to ensure the rules of 2822 are followed (and correct if not). -- 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 Founding Individual Sponsor of LOPSA. 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
