Re: [Mailman-Users] This should not have happened

2010-05-10 Thread Mark Sapiro
LuKreme wrote: >On 8-May-2010, at 15:38, Mark Sapiro wrote: >> >> 'Approved:(\s| )*Hon94Bar' > >how about > >Approved:([^<])*Password > >when searching the HTML portion? > >Or do you have to have the same search string for all portions? No, I don't have to use the same pattern for all parts, bu

Re: [Mailman-Users] This should not have happened

2010-05-09 Thread LuKreme
On 8-May-2010, at 15:38, Mark Sapiro wrote: > > 'Approved:(\s| )*Hon94Bar' how about Approved:([^<])*Password when searching the HTML portion? Or do you have to have the same search string for all portions? -- ALL WORK AND NO PLAY MAKES BART A DULL BOY ALL WORK AND NO PLAY MAKES BART A DULL

Re: [Mailman-Users] This should not have happened

2010-05-08 Thread Lindsay Haisley
On Sat, 2010-05-08 at 16:38 -0700, Mark Sapiro wrote: > I have never figured out how to do this in MSOE, and I haven't tried > with Apple Mail, and I don't know Evolution at all. For Evolution, one has to edit the per-account gconf key apps|evolution| eplugin|email_custom_header|customHeader. You

Re: [Mailman-Users] This should not have happened

2010-05-08 Thread Lindsay Haisley
On Sat, 2010-05-08 at 17:27 -0700, Mark Sapiro wrote: > which effectively gives clients free reign to ignore all but subject= > and body=, although I think most honor at least in-reply-to= and > references=. I don't know of any Internet services (except maybe Microsoft's implementation of HTTP/HT

Re: [Mailman-Users] This should not have happened

2010-05-08 Thread Mark Sapiro
On 5/8/2010 4:49 PM, Lindsay Haisley wrote: > On Sat, 2010-05-08 at 16:38 -0700, Mark Sapiro wrote: > >> One thing you could try is bookmarking a link like >> >> mailto:myl...@example.com?approved=password >> >> which should work, but those clients I've tried it with ignore it. > > Yep! I don'

Re: [Mailman-Users] This should not have happened

2010-05-08 Thread Lindsay Haisley
On Sat, 2010-05-08 at 16:38 -0700, Mark Sapiro wrote: > The patch will be in the 2.1 branch in Launchpad within a few days if > not sooner, but it is also attached to this mail as Approve.patch.txt. > It will be released in 2.1.14. Thanks!! > T-bird supports this. Go to Tools -> Options -> Advan

Re: [Mailman-Users] This should not have happened

2010-05-08 Thread Mark Sapiro
On 5/8/2010 3:11 PM, Lindsay Haisley wrote: > On Sat, 2010-05-08 at 14:38 -0700, Mark Sapiro wrote: >> I will modify the code to add \xA0 to make the pattern >> 'Approved:(\xA0|\s| )*Hon94Bar' in this case, which will work for >> this one and future ones like it, > > Where will this patch show up?

Re: [Mailman-Users] This should not have happened

2010-05-08 Thread Lindsay Haisley
On Sat, 2010-05-08 at 14:38 -0700, Mark Sapiro wrote: > I will modify the code to add \xA0 to make the pattern > 'Approved:(\xA0|\s| )*Hon94Bar' in this case, which will work for > this one and future ones like it, Where will this patch show up? Since I'm running the standard issue gentoo linux M

Re: [Mailman-Users] This should not have happened

2010-05-08 Thread Mark Sapiro
On 5/8/2010 1:05 PM, Lindsay Haisley wrote: > > The poster used an "Approved" pseudo-header. Mailman found the > pseudo-header in the text/plain part, removed it, and approved the post > for distribution. However in the text/html portion, the pseudo-header > was mucked up with markup and was app

[Mailman-Users] This should not have happened

2010-05-08 Thread Lindsay Haisley
I have a local Mailman (2.1.12) list hosting customer who sends out weekly HTML email from her business to her list from a couple of different computers. Normally this goes without a hitch, but today we had a problem. This particular HTML email sent to the list had a master MIME Content-Type of

[Mailman-Users] This should not have happened

2010-05-08 Thread Lindsay Haisley
I have a local Mailman (2.1.12) list hosting customer who sends out weekly HTML email from her business to her list from a couple of different computers. Normally this goes without a hitch, but today we had a problem. This particular HTML email sent to the list had a master MIME Content-Type of