[Mailman-Developers] [ mailman-Bugs-660675 ] special characters in realnames

Bugs item #660675, was opened at 2003-01-01 15:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660675&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/

[Mailman-Developers] 2.1 bug?

I'm still running rc1, but.. Got this traceback in my mailbox this morning from the mailpasswd message. Does this also imply anyone beyond this didn't get a password mailed? Any chance of finding out what address caused this? Traceback (most recent call last): File "/usr/local/mailman/cron/ma

[Mailman-Developers] email comparison bug?

One of my users got two notices for her two lists at one domain, instead of one notice with two password/URLs. One of the lists has her address all lower case, and the other is capped like this: [EMAIL PROTECTED] They're exactly the same otherwise. Is this a bug in 2.1's comparison function that

[Mailman-Developers] [ mailman-Bugs-660733 ] bin/arch traceback

Bugs item #660733, was opened at 2003-01-01 12:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to:

Re: [Mailman-Developers] email comparison bug?

I've also discovered that bin/find_member lists addresses as separate people, like this: [EMAIL PROTECTED] found in: List 1 [EMAIL PROTECTED] found in: List 2 List 3 The user options page won't let me change <[EMAIL PROTECTED]> to <[EMAIL PROTECTED]>. It says "You are already u

Re: [Mailman-Developers] email comparison bug?

At 12:12 -0500 1/1/2003, Stonewall Ballard wrote: >One of my users got two notices for her two lists at one domain, instead of >one notice with two password/URLs. > >One of the lists has her address all lower case, and the other is capped >like this: [EMAIL PROTECTED] > >They're exactly the same ot

Re: [Mailman-Developers] email comparison bug?

On 1/1/03 12:47 PM, "John W Baxter" <[EMAIL PROTECTED]> wrote: > I don't know how Mailman can be expected to know which domains treat > address local parts caselessly (hint: almost all) and which treat them > casefully (hint: the RFCs still allow it). > > Since *can* be a different account than

[Mailman-Developers] [ mailman-Bugs-660733 ] bin/arch traceback

Bugs item #660733, was opened at 2003-01-01 12:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to:

Re: [Mailman-Developers] 2.1 bug?

> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes: CVR> I'm still running rc1, but.. CVR> Got this traceback in my mailbox this morning from the CVR> mailpasswd message. Does this also imply anyone beyond this CVR> didn't get a password mailed? I'm sure it does.

Re: [Mailman-Developers] email comparison bug?

> "SB" == Stonewall Ballard <[EMAIL PROTECTED]> writes: SB> One of my users got two notices for her two lists at one SB> domain, instead of one notice with two password/URLs. SB> One of the lists has her address all lower case, and the other SB> is capped like this: [EMAIL PR

Re: [Mailman-Developers] email comparison bug?

> "SB" == Stonewall Ballard <[EMAIL PROTECTED]> writes: SB> One of my users got two notices for her two lists at one SB> domain, instead of one notice with two password/URLs. SB> One of the lists has her address all lower case, and the other SB> is capped like this: [EMAIL PR

Re: [Mailman-Developers] email comparison bug?

> "SB" == Stonewall Ballard <[EMAIL PROTECTED]> writes: SB> One of the lists has her address all lower case, and the other SB> is capped like this: [EMAIL PROTECTED] Sorry for the frenetic responses... Here's the comment in mailpasswds: # BAW: we group by cpaddress

[Mailman-Developers] more on that password crash.

I think I found it. Turns out a couple of things weren't compiling right on MacOS X (the japanese and chinese language additions). that turns out to be a minor bug in how MacOS X ships a python config file. More details here: (maybe t

Re: [Mailman-Developers] email comparison bug?

> "SB" == Stonewall Ballard <[EMAIL PROTECTED]> writes: SB> I've also discovered that bin/find_member lists addresses as SB> separate people, like this: | [EMAIL PROTECTED] found in: | List 1 | [EMAIL PROTECTED] found in: | List 2 | List 3 This

[Mailman-Developers] Fwd: bin/rmlist too bold removing entries from postfix aliases file

I just realized this conversation occured on the mailman-users list while it would be more appropriately discussed on the developers' list. -- Jon Parise ([EMAIL PROTECTED]) :: http://www.csh.rit.edu/~jon/ --- Begin Message --- On Wed, Jan 01, 2003 at 07:14:41PM -0500, Todd wrote: > I was tes

Re: [Mailman-Developers] email comparison bug?

> "JWB" == John W Baxter <[EMAIL PROTECTED]> writes: JWB> Since *can* be a different account than is JWB> , I think we're stuck, even though it almost never JWB> is. When there is a sitewide database of Mailman JWB> users...we'll STILL be stuck, I fear, although the GUI migh

Re: [Mailman-Developers] more on that password crash.

> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes: CVR> I think I found it. Turns out a couple of things weren't CVR> compiling right on MacOS X (the japanese and chinese language CVR> additions). that turns out to be a minor bug in how MacOS X CVR> ships a python config

Re: [Mailman-Developers] Fwd: bin/rmlist too bold removing entries from postfix aliases file

> "JP" == Jon Parise <[EMAIL PROTECTED]> writes: JP> I just realized this conversation occured on the mailman-users JP> list while it would be more appropriately discussed on the JP> developers' list. Jon, your patch was perfect. It's been applied. Thanks. -Barry _

Re: [Mailman-Developers] more on that password crash.

On Wednesday, January 1, 2003, at 10:05 PM, Barry A. Warsaw wrote: I posted a follow up in the forum linked off your blog. It looks liek a from-source build of Python 2.2.2 doesn't have this problem, so it's only Apple's Python distro that seems to be affected. I've no idea how that gets buil