[Mailman-Users] dmarc_moderation_action not working in 2.1.18
Hi, I've upgraded our Mailman installation to 2.1.18-1 recently and noticed that the "dmarc_moderation_action" is not working. We've setup a test list, and set the list to "Munge From" for "dmarc_moderation_action". Upon sending a test message in from either one of our Yahoo or AOL accounts the "From" field is being maintained as " usern...@yahoo.com" or "usern...@aol.com" respectively. The "vette" log is indicating that DMARC is being detected, and other logs also report DMARC's existence, however the "Munge From" action is NOT being taken. Any help or suggestions would be appreciated. *** I searched the archives prior to posting this message, and the topics related to "dmarc_moderation_action" did not seem to cover exactly or resolve my issue. If you require more info, please let me know. *** Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] dmarc_moderation_action not working in 2.1.18
Mark, When I set the option to "reject" it rejects properly as expected. But when it's set to "munge from" it sends it out as if "Accept" was chosen. Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com On Thu, Jun 12, 2014 at 11:46 AM, Mark Sapiro wrote: > On 06/12/2014 07:29 AM, Peter Knowles wrote: > > > > We've setup a test list, and set the list to "Munge From" for > > "dmarc_moderation_action". Upon sending a test message in from either one > > of our Yahoo or AOL accounts the "From" field is being maintained as " > > usern...@yahoo.com" or "usern...@aol.com" respectively. > > > > The "vette" log is indicating that DMARC is being detected, and other > logs > > also report DMARC's existence, however the "Munge From" action is NOT > being > > taken. > > > What happens if you set dmarc_moderation_action to Reject? > If the other logs are Mailman logs, what exactly do they report? > > Have you rearranged the handler pipeline, or do you have a custom > pipeline for this list that you didn't update to insert the new > WrapMessage handler. WrapMessage must be in the pipeline and should be > immediately before ToOutgoing, and CookHeaders must be after Moderate > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- > Mailman-Users mailing list Mailman-Users@python.org > https://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: > https://mail.python.org/mailman/options/mailman-users/pknowles%40tpnsolutions.com > -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] dmarc_moderation_action not working in 2.1.18
Mark, Inside mm_cfg.py, "GLOBAL_PIPELINE" has the following: SpamDetect Approve Replybot Moderate Hold MimeDel Scrubber Emergency Tagger CalcRecips AvoidDuplicates Cleanse CleanseDKIM CookieHeaders ToDigest ToArchive AfterDelivery Acknowledge ToOutgoing Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com On Thu, Jun 12, 2014 at 2:19 PM, Mark Sapiro wrote: > On 06/12/2014 01:41 PM, Peter Knowles wrote: > > > > When I set the option to "reject" it rejects properly as expected. But > > when it's set to "munge from" it sends it out as if "Accept" was chosen. > > > Then the problem almost certainly has to be the pipeline. There is a new > WrapMessage handler that must be in the pipeline. > > Do you have a GLOBAL_PIPELINE setting in mm_cfg.py? If so, look at the > setting in Defaults.py and make sure it contains the WrapMessage entry > in the right place. > > If not, try > > bin/withlist LISTNAME > > and then at the prompt enter m.pipeline. Does that return a value rather > than AttributeError? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] dmarc_moderation_action not working in 2.1.18
Mark, In Defaults.py "GLOBAL_PIPELINE" has the following: SpamDetect Approve Replybot Moderate Hold MimeDel Scrubber Emergency Tagger CalcRecips AvoidDuplicates CleanseDKIM CookieHeaders ToDigest ToArchive ToUsenet AfterDelivery Acknowledge WrapMessage ToOutgoing Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com On Thu, Jun 12, 2014 at 2:27 PM, Peter Knowles wrote: > Mark, > > Inside mm_cfg.py, "GLOBAL_PIPELINE" has the following: > > SpamDetect > Approve > Replybot > Moderate > Hold > MimeDel > Scrubber > Emergency > Tagger > CalcRecips > AvoidDuplicates > Cleanse > CleanseDKIM > CookieHeaders > ToDigest > ToArchive > AfterDelivery > Acknowledge > ToOutgoing > > Best Regards, > Peter Knowles > TPN Solutions > > Email: pknow...@tpnsolutions.com > Phone: 604-229-0715 > Skype: tpnsupport > Website: http://www.tpnsolutions.com > > > On Thu, Jun 12, 2014 at 2:19 PM, Mark Sapiro wrote: > >> On 06/12/2014 01:41 PM, Peter Knowles wrote: >> > >> > When I set the option to "reject" it rejects properly as expected. But >> > when it's set to "munge from" it sends it out as if "Accept" was chosen. >> >> >> Then the problem almost certainly has to be the pipeline. There is a new >> WrapMessage handler that must be in the pipeline. >> >> Do you have a GLOBAL_PIPELINE setting in mm_cfg.py? If so, look at the >> setting in Defaults.py and make sure it contains the WrapMessage entry >> in the right place. >> >> If not, try >> >> bin/withlist LISTNAME >> >> and then at the prompt enter m.pipeline. Does that return a value rather >> than AttributeError? >> >> -- >> Mark Sapiro The highway is for gamblers, >> San Francisco Bay Area, Californiabetter use your sense - B. Dylan >> > > -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Membership Management PHP UI
Hi, I'm attempting to re-create the "Membership Management" using PHP. More specifically, I want to be able to view, and modify all column data associated with each subscriber in the same way the default Mailman UI does (ex. Name, Email, MOD, Hide, Nomail, Ack, Not Metoo, NoDupes, Digest, Plain, Language) The purpose of this request is that I'm working on a PHP based admin UI which has company's look and feel, limits exposure to select options, add a few custom features, and potentially allows management of multiple lists from a single UI. Thanks in advance! Best Regards, Peter Knowles TPN Solutions -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Membership Management PHP UI
Mark, Preferably I'd like to transparently issue a command to Mailman backend script(s). That is, my PHP UI would make localized changes to queue (for scheduled changes) or directly via the "exec" (or similar) command (for real-time changes). Essentially, we want to be in a position eventually to completely cripple the admin UI shipped with Mailman. One of the problems that I face is, I'm not a Python developer, so if existing Mailman python scripts can manage the "read/write" functions in order to extract things and update things that'd be great. *** I'm already familiar with the "config_list" script which my "audit" script uses to maintain user/global config options we do not allow our users to maintain themselves. (that is, technically a user can override a setting we maintain currently, but within minutes the settings are reverted via our automated audit process. *** Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com On Mon, Jun 16, 2014 at 2:38 PM, Mark Sapiro wrote: > On 06/16/2014 02:01 PM, Peter Knowles wrote: > > Hi, > > > > I'm attempting to re-create the "Membership Management" using PHP. More > > specifically, I want to be able to view, and modify all column data > > associated with each subscriber in the same way the default Mailman UI > does > > (ex. Name, Email, MOD, Hide, Nomail, Ack, Not Metoo, NoDupes, Digest, > > Plain, Language) > > > Do you want to implement this capability with your own PHP pages or do > you want your PHP pages to GET the admin/listname/members page, parse it > and display the results in its own way, and POST changes back to the > Mailman web UI? > > I.e. do you want to work through the existing Mailman web UI or bypass it? > > If you want to work through the existing UI, see the FAQ at > <http://wiki.list.org/x/uIA9> which I'm sure will raise more questions. > > If you want to bypass it, you'll probably need to implement some helper > scripts (Python scripts using Mailman methods do do the work) to do the > actual data retrieval and updates, and invoke those from your PHP pages. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- > Mailman-Users mailing list Mailman-Users@python.org > https://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: > https://mail.python.org/mailman/options/mailman-users/pknowles%40tpnsolutions.com > -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Membership Management PHP UI
Mark, I'm also considering the use of the PEAR module Services_Mailman, which appears to interact with the Mailman default admin UI behind the scenes. This options may be feasible in the short term. Are you aware if this works with the current 2.x.x branch of Mailman without issue? Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com On Mon, Jun 16, 2014 at 2:50 PM, Peter Knowles wrote: > Mark, > > Preferably I'd like to transparently issue a command to Mailman backend > script(s). That is, my PHP UI would make localized changes to queue (for > scheduled changes) or directly via the "exec" (or similar) command (for > real-time changes). > > Essentially, we want to be in a position eventually to completely cripple > the admin UI shipped with Mailman. > > One of the problems that I face is, I'm not a Python developer, so if > existing Mailman python scripts can manage the "read/write" functions in > order to extract things and update things that'd be great. > > *** I'm already familiar with the "config_list" script which my "audit" > script uses to maintain user/global config options we do not allow our > users to maintain themselves. (that is, technically a user can override a > setting we maintain currently, but within minutes the settings are reverted > via our automated audit process. *** > > > Best Regards, > Peter Knowles > TPN Solutions > > Email: pknow...@tpnsolutions.com > Phone: 604-229-0715 > Skype: tpnsupport > Website: http://www.tpnsolutions.com > > > On Mon, Jun 16, 2014 at 2:38 PM, Mark Sapiro wrote: > >> On 06/16/2014 02:01 PM, Peter Knowles wrote: >> > Hi, >> > >> > I'm attempting to re-create the "Membership Management" using PHP. More >> > specifically, I want to be able to view, and modify all column data >> > associated with each subscriber in the same way the default Mailman UI >> does >> > (ex. Name, Email, MOD, Hide, Nomail, Ack, Not Metoo, NoDupes, Digest, >> > Plain, Language) >> >> >> Do you want to implement this capability with your own PHP pages or do >> you want your PHP pages to GET the admin/listname/members page, parse it >> and display the results in its own way, and POST changes back to the >> Mailman web UI? >> >> I.e. do you want to work through the existing Mailman web UI or bypass it? >> >> If you want to work through the existing UI, see the FAQ at >> <http://wiki.list.org/x/uIA9> which I'm sure will raise more questions. >> >> If you want to bypass it, you'll probably need to implement some helper >> scripts (Python scripts using Mailman methods do do the work) to do the >> actual data retrieval and updates, and invoke those from your PHP pages. >> >> -- >> Mark Sapiro The highway is for gamblers, >> San Francisco Bay Area, Californiabetter use your sense - B. Dylan >> -- >> Mailman-Users mailing list Mailman-Users@python.org >> https://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: >> https://mail.python.org/mailman/options/mailman-users/pknowles%40tpnsolutions.com >> > > -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Membership Management PHP UI
Lindsay, I didn't mean to come off as completely ignoring your suggestions. As for the temporary solution, yes this would require that the existing UI continue to be running in order to work, which as mentioned may be a "temporary" immediate solution while I work to gain the required knowledge. You had mentioned something about "withlist" being the script which may can do pretty much everything. Could this script be used for "updating" subscriber settings, and if so could you give an example? Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com On Mon, Jun 16, 2014 at 3:45 PM, Lindsay Haisley wrote: > On Mon, 2014-06-16 at 14:50 -0700, Peter Knowles wrote: > > Mark, > > > > Preferably I'd like to transparently issue a command to Mailman backend > > script(s). That is, my PHP UI would make localized changes to queue (for > > scheduled changes) or directly via the "exec" (or similar) command (for > > real-time changes). > > The ~mailman/bin/export.py script outputs full list information in XML > format. PHP has XML parsing capabilities which can probably pull the > information you want from the output. Alternatively, running > ~mailman/bin/dumpdb on the config.pck file for the list will provide you > with much the same information, albeit parsing the information may be > somewhat more difficult. > > This gives you read capabilities. Write capabilities are another > matter. > > > Essentially, we want to be in a position eventually to completely cripple > > the admin UI shipped with Mailman. > > Might this also disallow the use of the Services_Mailman PEAR module? > > > One of the problems that I face is, I'm not a Python developer, so if > > existing Mailman python scripts can manage the "read/write" functions in > > order to extract things and update things that'd be great. > > Peter, given the complexity of parsing the necessary information from > the output of existing scripts, and the limited options with the > existing scripts for inputting per-subscriber information, OR the > complexity of interacting with the membership web-UI, any time you spend > learning basic python scripting might well be a more effective use of > your development efforts. Python is perhaps the most syntactically > logical and easy to use of all the interpreted languages I've worked > with, which includes a good number of them, and scripting of list > membership management functions and I/O into a workable PHP-generated > web UI would be almost trivial given decent PHP and related web > development skills, once you have a basic understanding of the python > code required to read and write the atoms of information which make up > the subscriber database. It's not really all that complex, and you > don't have to become a python expert to do it. If you understand PHP > scripting and OO programming you're 2/3 of the way there. > > I know that Mark is the go-to guy on all things having to do with > Mailman code, but as far as integrating system administrative functions > into a web UI, I've had a lot of experience on my own hosting service, > so I'm not exactly shooting in the dark here. Been there, done that, > bought the T-shirt :) > > > *** I'm already familiar with the "config_list" script which my "audit" > > script uses to maintain user/global config options we do not allow our > > users to maintain themselves. (that is, technically a user can override a > > setting we maintain currently, but within minutes the settings are > reverted > > via our automated audit process. *** > > config_list doesn't handle per_subscriber settings. > > > On Mon, Jun 16, 2014 at 2:38 PM, Mark Sapiro wrote: > > > > > On 06/16/2014 02:01 PM, Peter Knowles wrote: > > > > Hi, > > > > > > > > I'm attempting to re-create the "Membership Management" using PHP. > More > > > > specifically, I want to be able to view, and modify all column data > > > > associated with each subscriber in the same way the default Mailman > UI > > > does > > > > (ex. Name, Email, MOD, Hide, Nomail, Ack, Not Metoo, NoDupes, Digest, > > > > Plain, Language) > > > > > > > > > Do you want to implement this capability with your own PHP pages or do > > > you want your PHP pages to GET the admin/listname/members page, parse > it > > > and display the results in its own way, and POST changes back to the > > > Mailman web UI? > >
[Mailman-Users] HTML messages being scrubbed...
Hi, Ever since I upgraded Mailman to address DMARC issues in April a number of archives have been having their HTML messages scrubbed. The result is that the archived message shows all these scrubbed notices instead of the actual message. What is causing this and how do I resolve this? *** is there a way to fix existing archives as well? *** Best Regards, Peter Knowles TPN Solutions E: pknow...@tpnsolutions.com P: 604-782-9342 W: http://www.tpnsolutions.com -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] mhonarc patch
Hi, Is anyone familiar with the "mhonarc" patch found at: http://www.openinfo.co.uk/mm/patches/mhonarc/ It seems when applied to 2.1.8, it cannot seem to patch "Mailboxes.py" and "Version.py". During the patching process, here is the error produced: Hunk #2 FAILED at 106. 1 out of 2 hunks FAILED -- saving rejects to file Mailman/Mailbox.py.rej Hunk #1 FAILED at 39. 1 out of 1 hunk FAILED -- saving rejects to file Mailman/Version.py.rej *** all other patching seems to work fine, and I've followed all instructions on the website to the best of my knowledge including changing the value of "DATA_FILE_VERSION" in the patch. Any help in making this patch work would be super, as I've got clients on my case about being able to use mhonarc once again. This patch was chosen specifically because we're also using the "htdig" patch by the same author. Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mhonarc patch
Mark, First off, to clarify, yes we're using version 2.1.18-1. Next, the "Version.py" issue has been resolved. I had forgotten to apply the "modinc" prerequisite patch. The only error that remains when applying the "mhonarc" patch is: Hulk #2 FAILED at 106. 1 out of 2 hulks FAILED -- saving rejects to file Mailman/Mailbox.py.rej *** Attached is a copy of "Mailbox.py.rej" *** Thanks in advance! Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com On Thu, Jul 17, 2014 at 7:53 PM, Mark Sapiro wrote: > > > > During the patching process, here is the error produced: > > > It would help if you actually provided the content of the .rej files. > > Also, Are you really patching 2.1.8 or did you mean 2.1.18? > > > > Hunk #2 FAILED at 106. > > 1 out of 2 hunks FAILED -- saving rejects to file Mailman/Mailbox.py.rej > > > The 2.1.7-0.1.patch file I'm looking at which is the patch also for > 2.1.8 is trying to replace > > mailbox.PortableUnixMailbox.__init__(self, fp, _archfactory(self)) > > with > > mailbox.UnixMailbox.__init__(self, fp, _archfactory(self)) > > and add a bunch of stuff following the definition of scrub. It looks OK > to me. Without seeing Mailman/Mailbox.py.rej and maybe > Mailman/Mailbox.py and/or Mailman/Mailbox.py.orig, I can't tell you what > the problem is. > > > > Hunk #1 FAILED at 39. > > 1 out of 1 hunk FAILED -- saving rejects to file Mailman/Version.py.rej > > > This is almost certainly because your existing Mailman/Version.py file > has Mailman/Version.py has DATA_FILE_VERSION = some number different > from what the patch expects. > > All you need to do is manually edit Mailman/Version.py and set > DATA_FILE_VERSION = a number bigger than what it currently is, perhaps > by appending '.1' to the existing number if it's an integer or > incrementing the number if it's a decimal. > > > > *** all other patching seems to work fine, and I've followed all > > instructions on the website to the best of my knowledge including > changing > > the value of "DATA_FILE_VERSION" in the patch. > > > Did you change the > > -DATA_FILE_VERSION = > > line to match what's currently in the file and the > > +DATA_FILE_VERSION = > > line to a larger number? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- > Mailman-Users mailing list Mailman-Users@python.org > https://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: > https://mail.python.org/mailman/options/mailman-users/pknowles%40tpnsolutions.com > -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mhonarc patch
Mark, So if I understand correctly, based on your patch, I apply things in the following order: 1. modinc.patch 2. mhonarc.patch 3. Mailbox.py.patch *** the latter patch addressing what the "mhonarc" patch didn't due to Mailman changes that were made post-patch release. *** Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com On Fri, Jul 18, 2014 at 10:26 AM, Mark Sapiro wrote: > On 07/18/2014 12:10 AM, Peter Knowles wrote: > > > > The only error that remains when applying the "mhonarc" patch is: > > > > Hulk #2 FAILED at 106. > > 1 out of 2 hulks FAILED -- saving rejects to file Mailman/Mailbox.py.rej > > > The problem with the patch is that the file it is based on ended at the > point where the last hunk was applied, and a new method was subsequently > added to Mailbox.py which wasn't taken into account in the patch. > > The attached Mailbox.py.patch should work with possible line number > shifts. It is intended to be applied to your previously patched > Mailbox.py with the first hunk of the patch already applied. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mhonarc patch
Mark, I hate to be a pest. 1. I saved your patch in "/usr/src" 2. I enter the folder "/usr/src/mailman-2.1.18-1" 3. I run "patch -p1 < ../Mailbox.py.patch" 4. The following message is presented: (Stripping trailing CRs from patch.) can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: - |--- Mailbox.py 2013-12-13 16:25:41.417368781 -0800 |--- Mailbox.py.new 2014-07-18 10:11:48.645854753 -0700 ----- File to patch: Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com On Fri, Jul 18, 2014 at 10:50 AM, Mark Sapiro wrote: > On 07/18/2014 10:40 AM, Peter Knowles wrote: > > > > So if I understand correctly, based on your patch, I apply things in the > > following order: > > > > 1. modinc.patch > > 2. mhonarc.patch > > 3. Mailbox.py.patch > > > > *** the latter patch addressing what the "mhonarc" patch didn't due to > > Mailman changes that were made post-patch release. *** > > > That is correct. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mhonarc patch
Mark, One last question, as I'm a bit of novice when it comes to the "patch" command. When I run the other patches, it'd report something like "Hunk #1 succeed at 12 (offset -1 lines).", compared to when I ran your patch (as directed above) it only spits out "patching file Mailman/Mailbox.py" with no indication whether it was successful or not. My question regarding this is, is this simply due to the way your patch was written, or does the "Hunk #X succeeded" message get generated by the "patch" program? Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com On Fri, Jul 18, 2014 at 11:12 AM, Mark Sapiro wrote: > On 07/18/2014 10:59 AM, Peter Knowles wrote: > > Mark, > > > > I hate to be a pest. > > > > 1. I saved your patch in "/usr/src" > > > > 2. I enter the folder "/usr/src/mailman-2.1.18-1" > > > > 3. I run "patch -p1 < ../Mailbox.py.patch" > > > > 4. The following message is presented: > > > > (Stripping trailing CRs from patch.) > > can't find file to patch at input line 3 > > Perhaps you used the wrong -p or --strip option? > > > It's partly my fault as I didn't have the same paths as the other > patches, but at steps 2 and 3 you need > > cd /usr/src/mailman-2.1.18-1/Mailman > patch -p0 < ../../Mailbox.py.patch > > Or you could just do > > patch Mailman/Mailbox.py < ../Mailbox.py.patch > in the /usr/src/mailman-2.1.18-1 directory. > > See 'man patch' > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman Stats
Hi, Does anyone know of any good statistics scripts that either can email detailed stats to list admins, or even offer stats from within the admin itself? We're using Mailman 2.1.18-1 Thanks in advance! Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Redacted Email Address in Feedback Loop
Hi, What is the best way to deal with feedback loop messages where the provider has redacted the email address of the party who filed the complaint? Does Mailman have any built in methods on dealing with this issue? At the moment we "force" a custom footer on all messages which includes the recipients email address, and the list they belong to, but recently a few ISPs have even been redacting data in that part of the message. Thanks in advance! Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Digest Volume Frequency
Hi, When I set the "Digest Volume Frequency" to "Weekly" is there a way set the day which messages are sent out (Sun, Mon, Tue, Wed, Thu, Fri, Sat)? I'm currently using Mailman 2.1.18-1 Best Regards, Peter Knowles TPN Solutions Email: pknow...@tpnsolutions.com Phone: 604-782-9342 Skype: tpnsupport Website: http://www.tpnsolutions.com -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Bounce Processing
Hi, We turned off bounce processing with the goal of NOT having subscribers removed in error (false positive) and instead use an internal auditing process to identify and deal with bad addresses. Recently I noticed that while bounce processing is turned OFF, subscriber addresses are still being disabled and "auto-unsubscribed" by Mailman. Would appreciate it if someone can shed some light on this topic... Have I misunderstood something or is something not working as it should be? Thanks in advance :-) Best Regards, Peter Knowles | TPN Solutions -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
