Re: [Mailman-Users] line returns missing
Michael: I'm jumping into this thread midstream, but this comment caught my eye... Some supposedly full-featured MUAs, Outlook Exchange, have been victims. Some of those (so called) full-features MUA's specifically merge lines together when they shouldn't be ... and it's not even related to Mailman. This has caused me untold problems when it's not noticed. A few months ago one of our QA people sent me a few commands intended to replicate a problem ... but Exchange, in it's infinite wisdom, (arbitrarily) wrapped two the lines into one ... which caused the commands to fail. Outlook does, however, inform the user when it's removed extra line breaks ... and you can click on the message to restore them. The message is very easy to miss. david -- IBM i on Power -- For when you can't afford to be out of business -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Complaining Outlook users
Stephen J. Turnbull wrote: To be honest, that's exactly what on behalf of means, anyway, so I don't understand why there's a problem here unless Outlook defaults to reply-to-Sender rather than reply-to-From. I've never used Outlook. I have no personal knowledge of this, but my impression is thae following: Mailman sends a post From: [EMAIL PROTECTED] with Sender: [EMAIL PROTECTED] Outlook displays the message as From: [EMAIL PROTECTED] on behalf of [EMAIL PROTECTED] This is wrong. It would be more accurate if Outlook displayed Sender: [EMAIL PROTECTED] on behalf of [EMAIL PROTECTED] but I don't know if that would make much difference to the user. Also, it seems from what I see, that at least some Outlook clients do reply_to_Sender rather than reply-to-From which is a problem. Another problem is that some users get confused by bounces and think it means something is wrong. [EMAIL PROTECTED] might be more acceptable. -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Periods in user email addresses rejected
I just got mailman up and running with Postfix and everything has been working perfectly except when someone tries to subscribe to the list that has a period in the user portion of the address. For example: [EMAIL PROTECTED] It gets rejected as an invalid email address by the web interface. First, is this a setting somewhere that can be changed? I've searched through the administrative settings and can't seem to find it. I've also looked through the FAQs and can't find any reference to this issue. I've tried Google, to no avail. I would imagine that I'm not the first to pose this question... Second, if there isn't an actual setting for this, please point me in the direction of the source file responsible for the (what I assume is an) email address regex so I can change this behavior. Thank you, Jay Deiman -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Periods in user email addresses rejected
Jay Deiman writes: I just got mailman up and running with Postfix and everything has been working perfectly except when someone tries to subscribe to the list that has a period in the user portion of the address. For example: [EMAIL PROTECTED] It gets rejected as an invalid email address by the web interface. I've never heard of this before. Just checking, but are you sure that these mailboxes don't have periods in their display names rather than (or as well as) their addresses? That is, although Stephen Turnbull [EMAIL PROTECTED] is a valid mailbox according to RFC 2822, Stephen J. Turnbull [EMAIL PROTECTED] is not, and must be quoted Stephen J. Turnbull [EMAIL PROTECTED] (I don't think Mailman checks for this, but given that AFAICT from the source, Mailman should not behave the way you describe, it's a guess.) First, is this a setting somewhere that can be changed? No. I would assume that the design is to allow anything that RFC 2822 does. As far as I can tell, what you are seeing is a MMHostileAddress as defined in Mailman/Errors.py, and the characters checked for are in _badchars and _specials in Mailman/Utils.py. However, '.' isn't in there AFAICS, in a recently updated bzr checkout of 2.1. What version of Mailman are you using? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
