[Mailman-Users] text/plain flowed wrapping

2010-11-30 Thread Steve Foster

HI Folks,

I'm trying to track down where a spurious ! is being injected into a 
number of lines in a text/plain message that is being wrapped at about 990 
chars.


The ! doesn't appear in the copy in the archive, just the email that is 
sent out. I've been lookin in the code in pythonlib/email and 
pythonlib/smtplib but can't see anything glaring. The only mention of 
RFC3676 is in Handler/Scrubber which appears to be the relevant RFC.


Anythoughts?

Cheers

Steve

For example (all chars converted to 'a' due to sensitivity of original):

aa aaa aa aa aaa aaa, aaa  aa  aa    
aaa   aa 2007/08 aa aaa aaa a, aa a aaa  aaa. 
aaa  a aa a aa aaa  aa  , a 
aaa aaa a  aa  aa (aaa), a.a. 
  a aa aa aaa a aa aaa a  aa aa a 
aa-.  aa aaa a aa aaa  , a aaa aa aa  aa aaa 
aaa;  aa  aa aaa aa aa aaa  . 
 aaa aaa  aa    aaa aaa aa 'aaa ', 
aa aaa aaa aaa  a, aaa aa aaa a a  a 
a  a aaa aa a aa  aa  a aaa 
aaa  aaa aa a aaa  aaa 
a  -  a  aa  aa aaa a aaa 5- 
 a aa   aaa aaa aaa a, a aa aaa 
aa   (aaa).  aa aaa aa, aa was  a  
aaa aaa aaa aaa 'aaa' aa  (aaa  aaa aa 
aaa) a  aa aa aaa aa a  a aa aa aaa 
aaa.   a  aaa aaa aaa a aaa aaa a 
 aaa , aaa aa aaa  aa a,   aa aaa 
aa- a aaa.


becomes

aa aaa aa aa aaa aaa, aaa  aa  aa    
aaa   aa 2007/08 aa aaa aaa a, aa a aaa  aaa. 
aaa  a aa a aa aaa  aa  , a 
aaa aaa a  aa  aa (aaa), a.a. 
  a aa aa aaa a aa aaa a  aa aa a 
aa-.  aa aaa a aa aaa  , a aaa aa aa  aa aaa 
aaa;  aa  aa aaa aa aa aaa  . 
 aaa aaa  aa    aaa aaa aa 'aaa ', 
aa aaa aaa aaa  a, aaa aa aaa a a  a 
a  a aaa aa a aa  aa  a aaa 
aaa  aaa aa a aaa  aaa 
a  -  a  aa  aa aaa a aaa 5- 
 a aa   aaa aaa aaa a, a aa aaa 
aa   (aaa).  aa aaa aa, aa wa!
 s  a  aaa aaa aaa aaa 'aaa' aa  (aaa 
 aaa aa aaa) a  aa aa aaa aa a  a 
aa aa aaa aaa.   a  aaa aaa aaa a 
aaa aaa a  aaa , aaa aa aaa  aa a,   
aa aaa aa- a aaa.



--
Steve FosterEmail: s.p.fos...@leeds.ac.uk

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Django itegration

2010-11-30 Thread Tim

 Hi all,

Anybody done the django_mailman thing?

I'm sure the documentation could be a bit better.

Any help appreciated.
Tim
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] text/plain flowed wrapping

2010-11-30 Thread Ralf Hildebrandt
* Steve Foster s.p.fos...@leeds.ac.uk:
 HI Folks,
 
 I'm trying to track down where a spurious ! is being injected into
 a number of lines in a text/plain message that is being wrapped at
 about 990 chars.
 
 The ! doesn't appear in the copy in the archive, just the email
 that is sent out. I've been lookin in the code in pythonlib/email and
 pythonlib/smtplib but can't see anything glaring. The only mention of
 RFC3676 is in Handler/Scrubber which appears to be the relevant RFC.
 
 Anythoughts?

Sounds like an MTA issue. Have you checked that? Should be easy using
tcpdump or something along these lines.

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  ralf.hildebra...@charite.de | http://www.charite.de

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] text/plain flowed wrapping

2010-11-30 Thread Steve Foster

On Tue, 30 Nov 2010, Ralf Hildebrandt wrote:


Sounds like an MTA issue. Have you checked that? Should be easy using
tcpdump or something along these lines.


Already tested that one, put the message through a server with identical 
setup MTA (except no Mailman) and the message was flowed correctly without 
the '!'.


Cheers

Steve

--
Steve FosterEmail: s.p.fos...@leeds.ac.uk
Unix team   Phone: 0113 343 7225
Information Systems ServicesFax:   0113 343 5411
University of Leeds
Leeds LS2 9JT

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] text/plain flowed wrapping

2010-11-30 Thread Ralf Hildebrandt
* Steve Foster s.p.fos...@leeds.ac.uk:
 On Tue, 30 Nov 2010, Ralf Hildebrandt wrote:
 
 Sounds like an MTA issue. Have you checked that? Should be easy using
 tcpdump or something along these lines.
 
 Already tested that one, put the message through a server with
 identical setup MTA (except no Mailman) and the message was flowed
 correctly without the '!'.

Because 990 Characters is usually the line length limit of an MTA, so
I guessed some MAT would truncate (truncate or just insert the !?)
the message...

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  ralf.hildebra...@charite.de | http://www.charite.de

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] text/plain flowed wrapping

2010-11-30 Thread Mark Sapiro
On 11/30/2010 7:44 AM, Ralf Hildebrandt wrote:
 * Steve Foster s.p.fos...@leeds.ac.uk:
 HI Folks,

 I'm trying to track down where a spurious ! is being injected into
 a number of lines in a text/plain message that is being wrapped at
 about 990 chars.

 The ! doesn't appear in the copy in the archive, just the email
 that is sent out. I've been lookin in the code in pythonlib/email and
 pythonlib/smtplib but can't see anything glaring. The only mention of
 RFC3676 is in Handler/Scrubber which appears to be the relevant RFC.

 Anythoughts?
 
 Sounds like an MTA issue. Have you checked that? Should be easy using
 tcpdump or something along these lines.
 

It could be an MTA issue, but it seems to me more likely to be an MUA
issue. The reason I think it is not as likely to be an MTA is if the
original is Format=flowed, it would have no long lines so there would
be no reason for an MTA to do anything to the message in transmission.

It is clearly not a Mailman/Python issue, at least with the versions in
use by this list, since the OP as delivered to me from the list and
viewed with Thunderbird did not show any spurious ! or line break in
the before example text.

-- 
Mark Sapiro m...@msapiro.netThe 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
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] text/plain flowed wrapping

2010-11-30 Thread Steve Foster

On Tue, 30 Nov 2010, Mark Sapiro wrote:


On 11/30/2010 7:44 AM, Ralf Hildebrandt wrote:

Sounds like an MTA issue. Have you checked that? Should be easy using
tcpdump or something along these lines.



It could be an MTA issue, but it seems to me more likely to be an MUA
issue. The reason I think it is not as likely to be an MTA is if the
original is Format=flowed, it would have no long lines so there would
be no reason for an MTA to do anything to the message in transmission.


Just been looking at this in more detail, the message is being sent with 
the headers:


Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

The encoding is maintained through the Mailman queues and handlers. At 
some point between it leaving Mailman and coming out the other end of the 
MTA (sendmail) the encoding gets mangled.


I'll dig a bit more deeply in the MTA and see if its playing silly 
beggers.


Cheers

Steve

--
Steve FosterEmail: s.p.fos...@leeds.ac.uk
Unix team   Phone: 0113 343 7225
Information Systems ServicesFax:   0113 343 5411
University of Leeds
Leeds LS2 9JT

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Django itegration

2010-11-30 Thread Chris Tandiono

On Mon, 29 Nov 2010 09:01:15 -0800, Tim w...@govanhillbaths.com wrote:


  Hi all,

Anybody done the django_mailman thing?

I'm sure the documentation could be a bit better.

Any help appreciated.
Tim


Not personally. However, if you add Mailman to your Python path, in your  
Django views you can just do things like from Mailman import MailList or  
from Mailman import Utils, which might be a better choice depending on  
what you want to do.


--
Chris
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Mailman - trouble creating a second list at an existing virtual host

2010-11-30 Thread Dean Suhr
snipped

 [...]
 Will I always have to manually post entries into virtual-mailman or is that
 supposed to happen somewhere along the way?  Is there a terminal command
 line I missed or could have run in addition to cause this to happen
 automatically?
 
 
On 11/29/10 6:28 PM, Mark Sapiro m...@msapiro.net wrote:
 It should happen automatically. I suspect it didn't in your case
 because of certain case-sensitivities which are really bugs. If you
 make all your domain names in mm_cfg.py, i.e. DEFAULT_URL_HOST,
 DEFAULT_EMAIL_HOST, additional domains in add_virtualhost() and
 domains in POSTFIX_STYLE_VIRTUAL_DOMAINS, all lower case and use all
 lower case in -u options to newlist or fix_url. Everything should work.
 
 The underlying bug is that domains in add_virtualhost() directives are
 lower-cased by Mailman but are matched case-sensitively to
 POSTFIX_STYLE_VIRTUAL_DOMAINS so if the POSTFIX_STYLE_VIRTUAL_DOMAINS
 domains are mixed or upper case, they don't match.
 
 If you make everything lower case and run fix_url with a lower case -u
 domain and then run genaliases, you should be OK.
 
 Note that manually editing virtual-mailman is unsafe because if
 genaliases is ever run, your changes will be lost.

Thanks again Mark.

Yes, I contributed to the problem because I like to use MLDfamily (mixed
case) in the user viewable emails and tend to follow that behind the scenes.

Right now I have manually entered the aliases into virtual-mailman. You
indicated this could be a problem with the next run of genaliases.

The original list and the new one are both at lists.MLDfamily.org. (note
CAPS).

I ran genaliases and the list remained intact with entries updated in
virtual-mailman.  Should I stand down and assume my rickety path to
functionality will hold up - or should I delete the list and start over?

If I start over I would not want to upset the apple cart on the original
list at lists.MLDfamily.org so I would use that mixed case virtual host for
the re-creation of the new list.

I promise if I ever add any new virtual domains everything will be lower
case!

Thanks, Dean

-- 
Dean Suhr
President
MLD Foundation
21345 Miles Drive
West Linn, OR  97068-2878   USA

1+503-656-4808  or 1-800-617-8387

Complete MLD information at: www.MLDfoundation.org

Celebrating our tenth year of serving families!

Please watch this awareness video and pass it along:
http://mldfoundation.org/awareness-video.html



--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Mailman - trouble creating a second list at anexisting virtual host

2010-11-30 Thread Mark Sapiro
Dean Suhr wrote:

Yes, I contributed to the problem because I like to use MLDfamily (mixed
case) in the user viewable emails and tend to follow that behind the scenes.

Right now I have manually entered the aliases into virtual-mailman. You
indicated this could be a problem with the next run of genaliases.


Yes, because genaliases will remove all entries from aliases and
virtual-mailman and then rebuild aliases for all lists and
virtual-mailman for only those lists whose host_name is found in
POSTFIX_STYLE_VIRTUAL_DOMAINS.

The above is the key here. If your domains are mixed case in
add_virtualhost() and POSTFIX_STYLE_VIRTUAL_DOMAINS, creating the list
and possibly running fix_url will produce a list with its host_name
attribute lower cased which will not match
POSTFIX_STYLE_VIRTUAL_DOMAINS and thus will not create virtual-mailman
entries.

If however you then manually change host_name on the list admin General
Options page (or via config_list) to match the case of the domain in
POSTFIX_STYLE_VIRTUAL_DOMAINS and run genaliases, that will create the
virtual-mailman entries.

The original list and the new one are both at lists.MLDfamily.org. (note
CAPS).

I ran genaliases and the list remained intact with entries updated in
virtual-mailman.  Should I stand down and assume my rickety path to
functionality will hold up - or should I delete the list and start over?


Presumably, you did what I suggest above, i.e., change the case of the
list's host_name before running genaliases.


-- 
Mark Sapiro m...@msapiro.netThe 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
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org