Re: [Mailman-Users] DMARC and Reply-To lines with from_is_list munging.

On 05/12/2014 01:25 AM, Stephen J. Turnbull wrote: > > How about multipart/alternative: > > message header > multipart/alternative > > part header > message/rfc822# original message in all its glory > > part header > Interesting idea, but I thi

Re: [Mailman-Users] Who authored the message?

On 05/12/2014 08:45 PM, Dave Nathanson wrote: > > I saw a message today sent to a list named "AlmostEverybody". The message > author did not properly configure their MUA (Verizon webmail) with their > proper name, so the only identifier is their email address. Which is of > course now deleted a

[Mailman-Users] Who authored the message?

Since DEMARC we don't know who is authoring list messages anymore. I saw a message today sent to a list named "AlmostEverybody". The message author did not properly configure their MUA (Verizon webmail) with their proper name, so the only identifier is their email address. Which is of course no

Re: [Mailman-Users] Logging fail?

On 05/12/2014 05:51 PM, Mark J Bradakis wrote: > > My turn to apologize, I should have specified that the logs contained > nothing related to > that specific message, and not implied they were completely empty. Please note that when I ask what's in logs, I don't want a filtered response. Granted

Re: [Mailman-Users] Saving list subscribers from a backup

On Mon, 2014-05-12 at 16:14 -0400, Bernie Cosell wrote: > in the face of zillions of bounce/unsubscribes thanks to the DMARC mess, > what I'd like to do is get the sysadmin to snapshot the list members > from, say, a week ago. I ought to also point out that using config.db or config.pck will onl

Re: [Mailman-Users] Logging fail?

Mark Sapiro wrote: What's in Mailman's qrunner log? Nothing. There can't be "Nothing" in the qrunner log unless you never started mailmnanctl or you're looking at the wrong log? My turn to apologize, I should have specified that the logs contained nothing related to that specific mes

Re: [Mailman-Users] MM 2.1.18-1 question

On 05/12/2014 07:59 AM, Lindsay Haisley wrote: > My understanding is that MM 2.1.18-1 corrects a python version > incompatibility in MM 2.1.18 and nothing more. I did sneak in one additional change to fix , but it's very minor. See the bug for deta

Re: [Mailman-Users] Logging fail?

On 05/12/2014 01:40 AM, Mark J Bradakis wrote: > Mark Sapiro wrote: > >> Is incomingRunner running? OutgoingRunner? > > Like I said, the runners are running. I apologize for my skepticism, but many people will see a list of qrunner processes and assume that *all* are running. >> What's in Mai

Re: [Mailman-Users] Saving list subscribers from a backup

On 05/12/2014 01:14 PM, Bernie Cosell wrote: > in the face of zillions of bounce/unsubscribes thanks to the DMARC mess, > what I'd like to do is get the sysadmin to snapshot the list members > from, say, a week ago. Then when we get things cleaned up I can > 'restore' the list as it was. I don

Re: [Mailman-Users] Saving list subscribers from a backup

On Mon, 2014-05-12 at 16:14 -0400, Bernie Cosell wrote: > in the face of zillions of bounce/unsubscribes thanks to the DMARC mess, > what I'd like to do is get the sysadmin to snapshot the list members > from, say, a week ago. Then when we get things cleaned up I can > 'restore' the list as it

Re: [Mailman-Users] (postfix &) Results of testing posts to yahoogroups from AOL

On 05/11/2014 09:18 PM, Peter Shute wrote: > > I should also note that in the footer of each message there is a mailto: link > that sets up a reply to the original sender. I've never noticed it before, > although it's always been there, and I assume this can't be broken by any > changes they've

Re: [Mailman-Users] (postfix &) Results of testing posts to yahoogroups from AOL

On 05/11/2014 09:09 PM, Peter Shute wrote: > > I haven't tried to check what headers they've used to confuse Outlook like > this. See the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B.

Re: [Mailman-Users] MM-2.1.15: Small bug regarding the "request forgery check"

On Wed, May 7, 2014 at 4:18 PM, Mark Sapiro wrote: > > And what generates that URL? Do you have a local mod for this? I don't > see where in the admin UI such a URL is generated or recognized. hmmm -- now that you mention it... maybe it's coming from one of the patches I did around the MySQL Me

[Mailman-Users] Saving list subscribers from a backup

in the face of zillions of bounce/unsubscribes thanks to the DMARC mess, what I'd like to do is get the sysadmin to snapshot the list members from, say, a week ago. Then when we get things cleaned up I can 'restore' the list as it was. I don't know how to do it and I tried googling and only f

[Mailman-Users] MM 2.1.18-1 question

My understanding is that MM 2.1.18-1 corrects a python version incompatibility in MM 2.1.18 and nothing more. My MM server is running python 2.7.3 and I've had no problems with MM 2.1.18. Are there any compelling reasons for me to upgrade? I have a patch collection which would need to be re-appl