Re: [Mailman-Users] Virtual sites
On Thu, 2006-09-14 at 00:34 -0500, Brad Knowles wrote: 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). OK, fair enough. Back to Mailman, why is checking MX records (or at least allowing specification of 2 or more SMTPHOSTS) a bad idea? It just seems to make good sense to me, considering failover, load balancing, resiliency, etc. -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 2:13 AM -0400 2006-09-14, Jim Popovitch wrote: OK, fair enough. Back to Mailman, why is checking MX records (or at least allowing specification of 2 or more SMTPHOSTS) a bad idea? It just seems to make good sense to me, considering failover, load balancing, resiliency, etc. There's nothing wrong in listing multiple IP addresses for the designated SMTPHOST. DNS round robin and the way the TCP protocol works should take care of the failover issues without any added complexity. If you wanted to put a Layer Four load-balancing switch in front of those mail servers, you could increase throughput and reliability even more. If you wanted to make that Layer Four load-balancing switch fault-tolerant with an active-active failover mate, that would be yet another additional improvement. However, speaking only for myself, Mailman does not need the added complexity of having to deal with looking up MX preferences, retrying DNS queries that are truncated because you tried to cram too many MXes into a UDP DNS packet, etc IMO, use the right tool for the right job. These are all problems that MTAs have to deal with today, and how well they handle them (or badly), I don't think that this is a wheel that we need -- or want -- to reinvent. Let the MTA do the job of the MTA, and let Mailman do the job of the MLM. Now, that said, in a true and proper virtual hosting/domain environment, I've been thinking about this a bit more, and I can see that some people might prefer that each virtual host/domain should have a separate SMTPHOST setting. The problem is that we don't have proper virtual hosting/domain handling within Mailman today, and I think it's generally a bad idea to retrofit one part of the overall solution without doing the rest. Let's take care of this problem at the right time, when we're implementing a full and proper virtual hosting/domain environment within Mailman, and not try to put that cart before the horse. -- 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] RELEASED: Mailman 2.1.9
Bretton Vine said the following on 2006/09/13 06:15 PM: 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 Confirmed: patch applies cleanly. In addition the move from 2.1.8 (separate installations per virtualhost) compiled and installed fine, inclusive of patch. -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | We must remember that a right lost to one is lost to all. - William Reece Smith, Jr. -- 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 9:42 AM +0100 2006-09-14, David Lee wrote: So I certainly wouldn't classify [EMAIL PROTECTED] and [EMAIL PROTECTED] (same name list) as 'quirky'. Rather as 'routine' for an ISP-like organisation offering multiple, logically independent domains. Mailman was never designed to be used in a hosted/ISP/virtual domain environment. It was originally designed to be run by individual list/site administrators on their own machine, where they have full privileged command-line access to the entire system. Running it in any other kind of environment is likely to expose areas where it does not perform so well. Just read all the FAQ entries pertaining to cPanel, Plesk, Apple, etc And I hereby match my +1 request with a +1 offer to help test and debug (so far as I reasonably can) any related beta code from the Mailman developers. We don't have a mailman-testers list. We have mailman-users and mailman-developers. If you're up to the task of discussing modifications to the Python source code, then you're welcome to subscribe to the mailman-developers list. I don't know where proper handling of full virtual domains is going to be implemented. I don't know if they're going to try to do that for Mailman 2.2, or if that's going to have to wait for Mailman3. But either way, it's going to be a little while before this is available. -- 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
[Mailman-Users] upgrading to mm2.1.9?
Has anyone upgraded to 2.1.9 successfully? I tried upgrading as follows:
./configure with same params as my release.
make install starts ok and ends ok but has one error:
Creating architecture independent directories...
chmod o-r /fs/mailman2/archives/private
for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \
do \
gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \
(cd ./$p ; umask 02 ; PYTHONPATH=/fs/mailman2/pythonlib
/usr/local/bin/pytho
n setup.py --quiet install --install-lib /fs/mailman2/pythonlib --install-pureli
b /fs/mailman2/pythonlib --install-data /fs/mailman2/pythonlib); \
done
File /fs/mailman2/pythonlib/email/_compat22.py, line 31
yield self
^
SyntaxError: invalid syntax
Then it updates the lists but with each one, it says:
Looks like you have a really recent CVS installation...
you're either one brave soul, or you already ran me
Finally, restarting sendmail, apache and mailman, if I try to login
from the webpage, I get a failure. Traceback shows:
Sep 14 11:48:44 2006 admin(1562):
admin(1562): [- Mailman Version: 2.1.9 -]
admin(1562): [- Traceback --]
admin(1562): Traceback (most recent call last):
admin(1562): File /fs/mailman2/scripts/driver, line 101, in run_main
admin(1562): main()
admin(1562): File /fs/mailman2/Mailman/Cgi/listinfo.py, line 61, in main
admin(1562): list_listinfo(mlist, language)
admin(1562): File /fs/mailman2/Mailman/Cgi/listinfo.py, line 176, in list_li
stinfo
admin(1562): replacements['mm-subscribe-box'] = mlist.FormatBox('email', s
ize=30)
admin(1562): File /fs/mailman2/Mailman/HTMLFormatter.py, line 336, in Format
Box
admin(1562): if isinstance(value, str):
Thank goodness for backups. Any ideas?
TIA
=-=-=-=-=-=-=-=-=-=- generated by /dev/dave -=-=-=-=-=-=-=-=-=-=-=-=
David SternUniversity of Maryland
Institute for Advanced Computer Studies
--
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] upgrading to mm2.1.9?
On Thu, 14 Sep 2006, Dave Stern wrote:
The last line of the tracedump was truncated in my initial message.
Here's the full text prior to the pythin (v2.1.2) and environment variables
admin(1562): [- Mailman Version: 2.1.9 -]
admin(1562): [- Traceback --]
admin(1562): Traceback (most recent call last):
admin(1562): File /fs/mailman2/scripts/driver, line 101, in run_main
admin(1562): main()
admin(1562): File /fs/mailman2/Mailman/Cgi/listinfo.py, line 61, in main
admin(1562): list_listinfo(mlist, language)
admin(1562): File /fs/mailman2/Mailman/Cgi/listinfo.py, line 176, in list_li
stinfo
admin(1562): replacements['mm-subscribe-box'] = mlist.FormatBox('email', s
ize=30)
admin(1562): File /fs/mailman2/Mailman/HTMLFormatter.py, line 336, in Format
Box
admin(1562): if isinstance(value, str):
admin(1562): TypeError: isinstance() arg 2 must be a class or type
TIA
=-=-=-=-=-=-=-=-=-=- generated by /dev/dave -=-=-=-=-=-=-=-=-=-=-=-=
David SternUniversity of Maryland
Institute for Advanced Computer Studies
--
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] archive emails are garbled
I have a noticed a problem with emails stored in the list archives if
they have been uuencoded. When HTML emails are distributed to all the
list members they just show the raw HTML code, so I used uuencode and it
fixed that, but when I take a look at the message in the archives it
looks mostly garbled. Here's an example:
begin 644 AgentCommissions.html
M/%$3T-465!%($A434P at 4%53$E#((M+R]7,T,O+T141!(5$U,(#0N,#$@
M5')A;G-I=EO;F%L+R]%3B(^#0H\:'1M;#X-CQH96%D/@T*/'1I=QE/D-I
M='EF;VYE($-O;6UIW-I;VX at 0F%N:SPO=ET;4^#0H\W1Y;4^#0H\(2TM
M#0IT9YL:71T;5T97AT(![(9O;G0M9F%M:6QY.B!!FEA;#L at 9F]N=US
M:7IE.B X'[EMAIL PROTECTED]:#$@( @( @( @( @R!F;VYT+69A;6EL3H at 07)I
M86P[(9O;G0MVEZ93H@,31P=!]#0IH,B @( @( @( @(![(9O;G0M
M9F%M:6QY.B!!FEA;#L at 9F]N=US:7IE.B Q,G!T('T-G1D+F)I9W1E'0@
M( @('L at 9F]N=UF86UI;'DZ($%R:6%L.R!F;VYT+7-IF4Z(#$T'[EMAIL PROTECTED]
Anyone know if there is a better way to deal with this?
--
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] upgrading to mm2.1.9?
Dave Stern wrote:
On Thu, 14 Sep 2006, Dave Stern wrote:
The last line of the tracedump was truncated in my initial message.
Here's the full text prior to the pythin (v2.1.2) and environment variables
admin(1562): [- Mailman Version: 2.1.9 -]
admin(1562): [- Traceback --]
admin(1562): Traceback (most recent call last):
admin(1562): File /fs/mailman2/scripts/driver, line 101, in run_main
admin(1562): main()
admin(1562): File /fs/mailman2/Mailman/Cgi/listinfo.py, line 61, in main
admin(1562): list_listinfo(mlist, language)
admin(1562): File /fs/mailman2/Mailman/Cgi/listinfo.py, line 176, in
list_li
stinfo
admin(1562): replacements['mm-subscribe-box'] = mlist.FormatBox('email',
s
ize=30)
admin(1562): File /fs/mailman2/Mailman/HTMLFormatter.py, line 336, in
Format
Box
admin(1562): if isinstance(value, str):
admin(1562): TypeError: isinstance() arg 2 must be a class or type
Ooops!
This statement in HTMLFormatter.py and a couple of similar 'isinstance'
calls in htmlformat.py are part of the security changes in Mailman
2.1.9. The problem is the use of str as the type argument requires
Python 2.3.
The quick and dirty fix in all three cases is to replace str with
types.StringType or with type(''). I.e.
HTMLFormatter - line 336 change
if isinstance(value, str):
to either
if isinstance(value, types.StringType):
or
if isinstance(value, type('')):
htmlformat.py - line 452 change
if isinstance(value, str):
to
if isinstance(value, types.StringType):
or
if isinstance(value, type('')):
htmlformat.py - line 465 change
if isinstance(text, str):
to
if isinstance(text, types.StringType):
or
if isinstance(text, type('')):
(or upgrade your Python :-) )
--
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] archive emails are garbled
Justin Zygmont wrote:
I have a noticed a problem with emails stored in the list archives if
they have been uuencoded. When HTML emails are distributed to all the
list members they just show the raw HTML code,
Messages as sent to message subscribers or messages in the archives?
You should be able to send HTML to individual subscribers if you don't
filter content or if you allow the appropriate MIME types in content
filtering. How such messages appear in archives depends on sitewide
archiving options set in mm_cfg.py.
so I used uuencode and it
fixed that, but when I take a look at the message in the archives it
looks mostly garbled. Here's an example:
begin 644 AgentCommissions.html
M/%$3T-465!%($A434P at 4%53$E#((M+R]7,T,O+T141!(5$U,(#0N,#$@
M5')A;G-I=EO;F%L+R]%3B(^#0H\:'1M;#X-CQH96%D/@T*/'1I=QE/D-I
M='EF;VYE($-O;6UIW-I;VX at 0F%N:SPO=ET;4^#0H\W1Y;4^#0H\(2TM
M#0IT9YL:71T;5T97AT(![(9O;G0M9F%M:6QY.B!!FEA;#L at 9F]N=US
M:7IE.B X'[EMAIL PROTECTED]:#$@( @( @( @( @R!F;VYT+69A;6EL3H at 07)I
M86P[(9O;G0MVEZ93H@,31P=!]#0IH,B @( @( @( @(![(9O;G0M
M9F%M:6QY.B!!FEA;#L at 9F]N=US:7IE.B Q,G!T('T-G1D+F)I9W1E'0@
M( @('L at 9F]N=UF86UI;'DZ($%R:6%L.R!F;VYT+7-IF4Z(#$T'[EMAIL PROTECTED]
This is not garbled. It is the uuencoded AgentCommissions.html file. A
uuencoded file is not human readable, but as far as mail agents are
concerned, it is plain text and will be archived in its raw form. Some
MUAs see a uuencoded file in an email and call it an 'attachment' and
render it as such, but this is non-standard. Also some MUAs when
composing will put uuencoded data in a separate MIME part with
Content-Transfer-Encoding: uuencode, x-uuencode, uue or x-uue, but
this to is non-standard.
Anyone know if there is a better way to deal with this?
You should be able to send HTML messages to your list members.
What Mailman version is this? What are your content filtering settings?
Can you provide a sample of a message as sent to Mailman and as
received from Mailman?
--
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] upgrading to mm2.1.9?
At 2:48 PM -0700 2006-09-14, Mark Sapiro wrote: This statement in HTMLFormatter.py and a couple of similar 'isinstance' calls in htmlformat.py are part of the security changes in Mailman 2.1.9. The problem is the use of str as the type argument requires Python 2.3. FAQ 5.8 has been updated. -- 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] upgrading to mm2.1.9?
Dave Stern wrote: make install starts ok and ends ok but has one error: Creating architecture independent directories... chmod o-r /fs/mailman2/archives/private for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \ do \ gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ (cd ./$p ; umask 02 ; PYTHONPATH=/fs/mailman2/pythonlib /usr/local/bin/pytho n setup.py --quiet install --install-lib /fs/mailman2/pythonlib --install-pureli b /fs/mailman2/pythonlib --install-data /fs/mailman2/pythonlib); \ done File /fs/mailman2/pythonlib/email/_compat22.py, line 31 yield self ^ SyntaxError: invalid syntax I don't know what happened to my first attempt to reply to this. Perhaps I sent it only to the OP (give 'em a vacation and you have to retrain them). Anyway, the above is OK. Your followup indicates you have Python 2.1.2. That's why the 'yield' fails. It requires Python 2.2, but in operation imports of _compat22 are wrapped in a try which falls back to importing _compat21 on a syntax exception. Then it updates the lists but with each one, it says: Looks like you have a really recent CVS installation... you're either one brave soul, or you already ran me This is OK too. It only means there were no config.pck format changes from Mailman 2.1.8 to 2.1.9. Finally, restarting sendmail, apache and mailman, if I try to login from the webpage, I get a failure. Traceback shows: Ooops! Answered in reply to your followup post. -- 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] trying (unsucessfully) to add contetn to the archvies TOC template
I am attempting to incorporate a search form into my archives by adding HTML to the following (v2.1.8) template files: templates/en/archtoc.html templates/en/archtocnombox.html but the archive TOC pages being created to not contain my additional HTML. (and even if I add the HTML manually, it gets erased the next time Mailman rewrites the archive TOC) The DEFAULT_SERVER_LANGUAGE parameter is 'en' so I thought those were the correct files to modify, but obviously I must be missing something here. Is there another place for the archive templates? Thanks in advance for any suggestions. -- -- Michael Dunston -- Music and Technology -- http://www.music.vt.edu/ -- Virginia Tech Department of Music -- -- -- -- -- -- -- -- -- -- -- -- -- 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] trying (unsucessfully) to add contetn to thearchvies TOC template
michael dunston wrote: I am attempting to incorporate a search form into my archives by adding HTML to the following (v2.1.8) template files: templates/en/archtoc.html templates/en/archtocnombox.html but the archive TOC pages being created to not contain my additional HTML. (and even if I add the HTML manually, it gets erased the next time Mailman rewrites the archive TOC) See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.048.htp. First, the templates/language/* templates should never be edited. Second, in your case it appears that a list specific, domain specific or site template is being used instead. This is all discussed in the above FAQ article. -- 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] Sendmail mailer in Python?
Am I missing something? Having recently installed Mailman 2.1.8, verified that it works, applied the exitstatus patch, again verified that it works, now I try to finish off the installation by automating the newaliases task for each newly created list by applying the patch, [ 644810 ] Sendmail mailer in Python, at http://sourceforge.net/tracker/index.php?func=detailaid=644810group_id=103atid=300103 I've read that it is no longer supported. I've searched far and wide for threads that pick up where it left off. Is there any way to ressurrect this thread of completely automating Mailman? Specifically, on my Linux (RHN 8.0, Sendmail 8.12, Python 2.4.3) ppsys's installation instructions fail when I try to patch sendmail's proto.m4. Should I just assume that on my version of Sendmail mailertable works and I can ignore his instruction to patch proto.m4? Or is there some bigger picture I'm missing with respect to using this Sendmail mailer in Python? Thanks in advance. -- 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
