Mailman 3 - Mailman-Users

Re: [Mailman-Users] [Fwd: Re: [Mailman-Users] NameError : recipients]
by Harald Meland 12 Feb '99

12 Feb '99

[Greg Stein] > Forwarding to the list. I'm just a bystander who can answer some > questions. Not all :-) Well, you're not alone, if that's any comfort :) > Scott A. McIntyre wrote: > > p.s. You don't happen to know why it would reject: > > > > From: "Scott A. McIntyre" <scott(a)whoi.edu> > > > > As a "non member posting" and only see "Scott A. McIntyre" and > > completely miss the email address? Ahem, I think you might have been led astray by your web browser here -- Mailman does "see" the entire "From:" header, but your web browser _displays_ it as > > From: "Scott A. McIntyre" due to "<" and ">" having special meaning in HTML (i.e. the mail address is interpreted as some unknown tag, hence ignored). I guess Mailman could do some s/</</-like stuff when generating the web pages, but this is not a "serious" bug. -- Harald

1 0

error with getpass module
by danilo lujambio 12 Feb '99

12 Feb '99

Sorry , but when I try to use mmsitepass I found : no module getpass I have been looking for in my Setup file for this modules , but I didn't find it. Can you help me (Sorry by my english) Thanks in advance

1 0

[Fwd: Re: [Mailman-Users] NameError : recipients]
by Greg Stein 11 Feb '99

11 Feb '99

Forwarding to the list. I'm just a bystander who can answer some questions. Not all :-) -g Scott A. McIntyre wrote: > > > This is a bug in Mailman 1.0b8. It has incorrect code for processing > > "Don't Receive Own Posts". Turn that off, and it should work okay. > > > > Postfix is a whole 'nother story... :-) > > Ironically, it worked as soon as I got the localhost in the access > control "ok" list -- and turned that option off....and now its just > fine! > > Thanks for the pointer! > > Scott > > p.s. You don't happen to know why it would reject: > > From: "Scott A. McIntyre" <scott(a)whoi.edu> > > As a "non member posting" and only see "Scott A. McIntyre" and > completely miss the email address? > > That is, the list is set so that only people on the list an send to it, > and scott(a)whoi.edu, this address I'm sending from, is indeed on the > list. However, when I post, it's held for administrative control and > the "Contents" seems only to list: > > From: "Scott A. McIntyre" > > Which implies that it's missing the email address. > > Familiar? > > thanks again. -- Greg Stein, http://www.lyra.org/

1 0

importing existing archives
by James Strickland 11 Feb '99

11 Feb '99

Hi. I've installed Mailman 1.0b7 and am pleased as punch (especially since it's written in Python, the best interpreted language ever :-) ) but I don't see how to import existing mail into an archive. I looked for documentation on this, I looked around the source a tiny bit, I looked at the crontab, I searched the archives for mailman-users, and I just don't see it. Presumably it's relatively simple - plunk down a mailbox file and run the indexing command. Does anyone know the magic incantation required? Also btw, does anyone know when Mailman 1.0 is likely to come out? Thanks in advance! -- James Strickland Perforce Software

1 0

Problems creating a list
by Pierce Cpl Wayne A 10 Feb '99

10 Feb '99

I just finished installing mailman on a RH 5.2 system with sendmail. I can create the test list without any problems. But when I try to create a list with capital letters, such as SNCO, it won't let me admin the list from the web interface. Any list with caps doesn't work, but if it's in complete lowercase it works fine however. Anyone know if this is a bug or just something I'm doing wrong? Also, I read in the archives that someone had an empty cgi-bin directory....so did I but I was able to give an absolute URL to view the pages. For example, (behind firewall) http://linux.miramar.usmc.mil/mailman/ gives me a forbidden error (403). But if I goto http://linux.miramar.usmc.mil/mailman/listinfo it loads fine. Not sure if you were having the same problem or not, but it only appeared to be the /mailman/ page the wasn't working here. For all those involved in the development, I'd like to say thanks. This looks like it's a really good piece of software (that will save me lots of headaches). Wayne Pierce -- "Binaries may die but source code lives forever."

2 1

Re: [Mailman-Users] Problems creating a list
by Harald Meland 10 Feb '99

10 Feb '99

[Christopher Lindsey] > > If this was done (properly) by design, I guess "newlist" should insist > > on all-lowercase list names, though. > > Just to be a pain, I'll add my $.00001 worth (advice comes cheap -- it would > be $.02 if I provided a solution). :-) > Anyhow, RFC 822 says that the localpart of an addr-spec is comprised of > either an atom or quoted-string. > > atom = 1+<any CHAR except specials, SPACE, and CTLs> > specials = ()<>@,;:\".[] > quoted-string = basically the same, but spaces allowed > if enclosed in quotes ... but this does not imply that Mailman _has_ to allow creation of Mailman lists with non-lowercased names. > That means that upper case is fine and dandy... So the best way to > probably handle this is to allow the list to be created with mixed cases > (or all upper), but then translate this internally to lowercase for all > functions using the list name. This way your passing the buck to the > MTA instead. I wasn't really talking about case trouble with the MTA (although the best MTA-independent fix for such problems would probably be for Mailman to insist on using lowercase-only aliases -- I know that e.g. Exim by default lowercases any localpart before looking it up in an alias file (although that behaviour can be configured)). I was talking about the inconsistent behaviour presently in Mailman -- "newlist" allows creation of mixed-case lists, while at least the "admin" cgi-bin script lowercases any list name it is given before trying to get the list object. Presently Mailman.MailList("test") could fail even if there is a Mailman.MailList("Test"). If we're willing to accept that some people have a legitimate need for mixed-case list names, your solution would be the Right Thing. The alternative solution of making all of Mailman case aware (i.e. treating "Test" and "test" as two separate lists) would be confusing to the vast majority of Mailman users. > Otherwise are you guaranteed that all addresses will be translated to lower > case when they come in? In general: No, you can't. However, if someone have set their MTA up to _not_ lowercase addresses before looking them up in the alias file, I'd say they deserve whatever they get when someone tries posting to a differently cased name of a list. They sure can't expect Mailman to put _every_ case permutation of all Mailman address in the alias file... > sendmail does this with any aliases, but what if a list is running > out of an account with '+' addressing instead (I know, it's a > stretch). As I said: If the MTA isn't doing "caseless" alias lookups, then all bets are off. > That said, I don't know why people insist on mixing case in their addresses. > It just confuses people... Exactly. But saying "Mailman doesn't support non-lowercased list names" might be a bit harsh, right? -- Harald

1 0

Re: [Mailman-Users] Problems creating a list
by J C Lawrence 10 Feb '99

10 Feb '99

On Wed, 10 Feb 1999 13:48:54 -0800 Greg Stein<gstein(a)lyra.org> wrote: > * Mailman's platform is Unix, AFAIK. I'm unaware of case-sensitive > mailers for Unix. Are you saying SGI boxes are case-sensitive with > their mailer? SGI's current IRIX offerings ship with a recent version of sendmail, which is default configured to be case insensitive. I am not aware of any currently shipping version of Unix which ships with an MUA configured to be case sensitive (I haven't checked recent versions of D-UX for instance). I am aware of older Unix offerings, such as Intergraph's CLIX (a SysV-ish *nix that ran on Fairchild CLIPPER based workstations) whose default MTA was configured to be case __sensitive__. I have no doubt that there are other older *nix'es similarly default configured. Additionally, Sendmail and co _can_ be configured to be case sensitive under any version of Unix/Linux/etc. Why a SysAdm might want to do so is a separate matter -- the fact remains that he can, he might, and he would not be in violation of any standard practice or RFC if he did so, and it is possible that he could have very good reasons for doing so even if I can't think of any now. Mailman needs to be able to work properly in such environments. -- J C Lawrence Internet: claw(a)kanga.nu (Contractor) Internet: coder(a)kanga.nu ---------(*) Internet: claw(a)under.engr.sgi.com ...Honorary Member of Clan McFud -- Teamer's Avenging Monolith...

1 0

Re: [Mailman-Users] Problems creating a list
by J C Lawrence 10 Feb '99

10 Feb '99

On Wed, 10 Feb 1999 12:09:58 -0600 (CST) Christopher Lindsey<lindsey(a)ncsa.uiuc.edu> wrote: > Anyhow, RFC 822 says that the localpart of an addr-spec is > comprised of either an atom or quoted-string. I don't have time to quote chapter and verse right now. However the local part (the user ID) can be case sensitive. It usually isn't, but it can be and on some unnamed platorms it is (I know CLIX's default sendmail installation was cese sensitive, but that's a long time ago). Automatically mutating the case of local parts, in whatever fashion, unless you are guaranteed that the local platform is case insensitive (we're not), is a Bad Idea. -- J C Lawrence Internet: claw(a)kanga.nu (Contractor) Internet: coder(a)kanga.nu ---------(*) Internet: claw(a)under.engr.sgi.com ...Honorary Member of Clan McFud -- Teamer's Avenging Monolith...

2 1

Re: [Mailman-Users] Hostname in mail headers
by Harald Meland 10 Feb '99

10 Feb '99

[Marcus C. Gottwald] > G'day! > > Greg Stein wrote (Mon 1999-Feb-08 02:37:17 -0800): > > > In the "General Options" administration screen, change the "host name > > this list prefers" option (near the bottom of the list) to whatever you > > would like it to be. You can also update the URL to use the appropriate > > virtual host. > > That is the setting which doesn't work, maybe I should have > explained a little more in detail. > > And this setting does not work although Mailman has been > told that he should always use the name I am trying to use > for this list. And Mailman does so when presenting HTML-pages > for example. Only when sending mails, it doesn't work. According to my copy of the b6 sources, the messages should be sent out with an envelope sender of <LISTNAME-admin@HOST> where you can find LISTNAME and HOST in a way similar to this: $ cd ~mailman $ python Python 1.5.1 (#1, Oct 9 1998, 15:23:54) [C] on sunos5 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam >>> from Mailman import MailList >>> list = MailList.MailList("LISTNAME") # This locks the list >>> list._internal_name 'LISTNAME' >>> list.host_name 'HOST' >>> list.Unlock() # Finished, remember to unlock Are you sure your problem isn't that your MTA is doing some address rewriting _after_ Mailman has passed the messages on to it? -- Harald

2 1

Re: [Mailman-Users] Problems creating a list
by Harald Meland 10 Feb '99

10 Feb '99

[Pierce Cpl Wayne A] > I just finished installing mailman on a RH 5.2 system with > sendmail. I can create the test list without any problems. But when I > try to create a list with capital letters, such as SNCO, it won't let me > admin the list from the web interface. I hope the lowercasing done by the "admin" CGI script has been done by design. Of all the details around valid mail addresses, issues regarding case of localparts are likely the seemingly most trivial thing that has caused the most trouble. If this was done (properly) by design, I guess "newlist" should insist on all-lowercase list names, though. > Also, I read in the archives that someone had an empty cgi-bin > directory....so did I but I was able to give an absolute URL to view the > pages. For example, (behind firewall) > http://linux.miramar.usmc.mil/mailman/ gives me a forbidden error > (403). This is as it should -- /mailman/ is merely a ScriptAlias, and not something that can be executed. The person with the empty cgi-bin directory indeed had _no_ files installed in ~mailman/cgi-bin/ (which is _not_ as it should be). -- Harald

2 1