Mailman 3 June 1999 - Mailman-Users

Re: [Mailman-Users] Mailman, Exim -odqr, Python's `own' SMTP, etc.
by Harald Meland 15 Jun '99

15 Jun '99

[Ian Jackson] > So, what would be the canonical Python or Mailman way of doing this ? > Enclose the body of TrySMTPDelivery in a big `if' ? Move the body > into a new function and turn TrySMTPDelivery into a layer of > indirection ? Whatever suits your fancy :) > Is such a change likely to be accepted in any case, or will I have > to maintain a local version (which means I'll try for the patch with > the lowest changed-lines-count) ? If we're opening up for MTA-specific delivery mechanisms (which I personally am rather sceptical about), I think that the delivery mechanisms should be redesigned, to be easily subclassable or somesuch. Adding ever more `if' tests and layers of indirection is the way to go if you want to give another very well-known MLM a run for it's code-readability-"money" ;) -- but I don't think that's where we want Mailman to go. -- Harald

1 0

Re: [Mailman-Users] Multiple domains
by Harald Meland 15 Jun '99

15 Jun '99

[Lorenzo Cavassa] > Hi, > > i would like to run Mailman hosting several mailing lists with several domains. > An example: > > - two ml. : test(a)domain1.com, test(a)domain2.com > - the internal naming is: domain1.test and domain2.test > - i configure the MTA to accept test(a)domain1.com and test(a)domain2.com and to > route email for these ml. to domain1.test and to domain2.test > > How can i instruct MailMan to hide the internal naming in welcome > messages to subscribe users? Currently, this is hard. I'm hoping to be able to allow internal names with "@"s in them for post-1.0, so that the preferred email address and the internal name of a list are identical -- which seems to be the correct solution to problems like this. -- Harald

1 0

Re: [Mailman-Users] Newbie question
by Harald Meland 15 Jun '99

15 Jun '99

[Scott Kruger] > I just set up Mailman under Debian Linux using smail. I set up a > users mailing list but right now it is not working - obviously > because I have not set up the mail alias. Is this automated in any > way by mailman? It seems like such a nice package there must be > some way of having this automated. smail allows the creation of > lists just by putting a file with the email addresses in > /etc/smail/lists Is there an easy way of doing this? I think there used to be, and it was disabled for some reason or other (maybe it broke stuff on non-sendmail installations?) -- but that was before my time with Mailman. Thus, currently there is no such support. A suitably MTA-independent (well, with hooks for each supported MTA would be more likely :) mechanism to do this would be great to have, IMHO. Any takers? -- Harald

1 0

Re: [Mailman-Users] speaking of archiving ...
by Harald Meland 15 Jun '99

15 Jun '99

[Mitchell Marks] > Two of the lists I will be migrating to Mailman already have a > couple years of archives, built up by hypermail (on a different host > from where the slist mail management is running). Any suggestions > on how to integrate the old archives with the new ones that > Mailman+pipermail will be establishing? You can import mbox-format archives into pipermail with the $prefix/bin/arch script. -- Harald

1 0

Re: [Mailman-Users] Authentication/cookies question
by Harald Meland 15 Jun '99

15 Jun '99

[Matthew Darwin] > Is there any particular reason why there is no option (that I can > find) to configure the web interface to use basic authentication > instead of cookies? Just that no one has implemented such support yet. If anyone's willing to do that, I'm sure it'd be a nice feature to have. -- Harald

1 0

Re: [Mailman-Users] Problem with ALIASES
by Harald Meland 15 Jun '99

15 Jun '99

[Usuario para TESTE] > I Having some problem with mailman, i've followed the instructions and > installed 1.0rc1, but when i try to send an E-mail to the list i receive: RTFM, more specifically question #1 in the FAQ. -- Harald

1 0

Re: [Mailman-Users] Lack of RFC822 compliant date header
by Harald Meland 15 Jun '99

15 Jun '99

[Matthew Darwin] > So either mailman needs to deliver locally (via qmail-inject) or > generate RFC 822 Date: headers. I'll make Utils.DeliverToUser() add a Date: header when missing. > I also notice that pipermail is broken. My original message is archived > in two pieces: > > http://www.python.org/pipermail/mailman-users/1999-June/001436.html > http://www.python.org/pipermail/mailman-users/1999-June/001437.html Here's a quick fix for that one: Index: Archiver.py =================================================================== RCS file: /export/public/cvsroot/mailman/Mailman/Archiver/Archiver.py,v retrieving revision 1.11 diff -u -r1.11 Archiver.py --- Archiver.py 1999/02/28 00:27:32 1.11 +++ Archiver.py 1999/06/15 17:05:12 @@ -202,7 +202,11 @@ txt = txt + h if msg.body[0] != '\n': txt = txt + "\n" - txt = txt + msg.body + for line in string.split(msg.body, '\n'): + # Quote unprotected From_ lines appearing in body + if line and line[:5] == 'From ': + line = '>' + line + txt = txt + "%s\n" % line f = StringIO(txt) import HyperArch h = HyperArch.HyperArchive(self) -- Harald

1 0

Re: [Mailman-Users] Perhaps this is covered already ..
by Harald Meland 15 Jun '99

15 Jun '99

[Tor Houghton] > Thanks very much. Is there any way to have a "list" of base URL's? > It works as you say when I use the hostname, but it also has a CNAME > ('www') which most people tend to use. No, there are not any Mailman mechanisms to deal with this -- people accessing the web server by the "wrong" virtual interface will not get the same info as the ones accessing by the "right" one -- unless you turn off Mailman's virtual hosting support, of course. The virtual hosting support is controlled by the mm_cfg.VIRTUAL_HOST_OVERVIEW variable. Edit $prefix/Mailman/mm_cfg.py to change this. Or, you could have your web server issue redirects on access of mailman pages via one virtual interface to point the browser to the "right" one... -- Harald

2 1

Re: [Mailman-Users] Problem with ALIASES
by Harald Meland 15 Jun '99

15 Jun '99

As is apparent from the subject of the message I am now replying to, subject prefixing is broken in rc2 :( Here is the trivial patch (which was just checked into CVS): Index: MailList.py =================================================================== RCS file: /export/public/cvsroot/mailman/Mailman/MailList.py,v retrieving revision 1.125 diff -u -r1.125 MailList.py --- MailList.py 1999/06/13 07:19:20 1.125 +++ MailList.py 1999/06/15 11:43:27 @@ -1269,8 +1269,8 @@ prefix = self.subject_prefix if not subj: msg.SetHeader('Subject', '%s(no subject)' % prefix) - elif prefix and not re.match(re.escape(self.subject_prefix), - subj, re.I): + elif prefix and not re.search(re.escape(self.subject_prefix), + subj, re.I): msg.SetHeader('Subject', '%s%s' % (prefix, subj)) if self.anonymous_list: del msg['reply-to'] Sorry for not noticing this breakage in time, -- Harald

2 1

Perhaps this is covered already ..
by Tor Houghton 15 Jun '99

15 Jun '99

But why does the /mailman/admin link say "Welcome! [...] this is the collection of publicly-advertised mailman mailing lists on [...]" and then proceeds to list the publicly available lists (I have 4 lists on my server, where 1 is made non-public, so above link lists (correctly) 3 lists). When the link /mailman/listinfo says "Welcome! [...] There currently are no publicly-advertised [...] lists"?? I am assuming the latter link is wrong; since the admin page actually displays things correctly. I am running 1.0rc2. Regards, Tor Houghton.

2 2