Re: [Mailman-Users] Obscure addresses problem
At 7:06 PM -0700 2006-09-04, Jack Stone wrote: I looked at FAQ 4.4 and the method described there using an external archiving tool like MHonArc with Mailman methinks is a monster [...] It's not as clean as we would like, no. That is an area we are hoping to improve upon for future releases. [...] compared to my manner of cron-run scripts that updates my custom archives every 15 minutes to display the added messages. My need for a fix was minor IF I had just know where to look. Therein lies the key. I'm not sure what documentation you have or have not read, and which FAQ entries you have or have not seen, but the documentation should have made reference to the mm_cfg.py file and the fact that you should look through the Defaults.py file to see what options you may want to change, etc If you can tell us what parts of the documentation are not clear, we will try to get those fixed. Next, I'm just looking for a knob to drop the display of the archives in Mailman's web site and have members continue to use only the one they have been used to for several years -- and is not available for email harvesting. I'm not clear on what you're asking for. Could you elaborate? I still want to keep generating the mylist.txt because my scripts use that monthly file. Just don't want it to appear anywhere to the members or one that would join to mis-use it for spam lists. If you search the FAQ for archive, you might find some relevant information. Would be nicer, it seems if Mailman Xed out the email addresses as well rather than the present obscuring. That's another area of improvement that we have planned for future versions. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 Founding Individual Sponsor of LOPSA. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
Brad Knowles [EMAIL PROTECTED] wrote:At 7:06 PM -0700 2006-09-04, Jack Stone wrote: I looked at FAQ 4.4 and the method described there using an external archiving tool like MHonArc with Mailman methinks is a monster [...] It's not as clean as we would like, no. That is an area we are hoping to improve upon for future releases. JLS Needless for me to say, Mailman is a great system and everything cannot be done at once. Actually, I have found Mailman a lot easier to *install* than majordomo. MM worked right out of the box, but MJD can be a pain about permissions and configuring as matured as it is. I helped work up a separate installer script (including for vhosts) that made it much more of a breeze. [...] compared to my manner of cron-run scripts that updates my custom archives every 15 minutes to display the added messages. My need for a fix was minor IF I had just know where to look. Therein lies the key. I'm not sure what documentation you have or have not read, and which FAQ entries you have or have not seen, but the documentation should have made reference to the mm_cfg.py file and the fact that you should look through the Defaults.py file to see what options you may want to change, etc If you can tell us what parts of the documentation are not clear, we will try to get those fixed. JLS Actually, because of the time crunch, I just hadn't had time to read everything although I did quickly scan the FAQ and thoroughly man pages. I tested of course on a test list until I thought I had everything working to move over to a production list. My main concern was not to interupt the list. The knob in the web site configs about changing from YES to NO had me distracted thinking it was the place to change my setting for this preference. I can tell from Dan's last post, he is also still confused about what that does there. That web knob caused me to be distracted from looking more thoroughly in other places -- like the Defaults.py -- even though I had looked at some things there -- but just for other things at the time -- like the vhost designation -- which I fixed by using the CLI newlist command. Basically, I had to discover which things were better to use the CLI or the web configs. In my experience, I found to create the newlist from CLI and then go to the net list's web site and configure things -- except of course, the archive issue on obscuring. It's real purpose is still a mystery to me as I didn't observe any change on anything bu switching from YES to NO. Next, I'm just looking for a knob to drop the display of the archives in Mailman's web site and have members continue to use only the one they have been used to for several years -- and is not available for email harvesting. I'm not clear on what you're asking for. Could you elaborate? JLS Now that I have successfully changed the obscuring to non-obscuring, the Mailman archive now shows the email addresses which would be available to any spammer that took the time to join -- my site is especially at risk now that I even ID'ed the domain during this thread. My fault in doing that. It would be a simple matter for a spammer to download the compressed archives and then run them through an email extraction script. As I opined before, even the obsured used now in Mailman archives would not be safe if a spammer used a special script of the downloaded archive files to convert the xyz at adomain.net I couldn't do it, but a good script guy could, I imagine. So, I just need to disable access to the Mailman version of the archive which I consider vulnerable to harvesting in its present form. Plus, I don't need it with my own archives available and they are safe. I still want to keep generating the mylist.txt because my scripts use that monthly file. Just don't want it to appear anywhere to the members or one that would join to mis-use it for spam lists. If you search the FAQ for archive, you might find some relevant information. JLS Plan to do more of that now I have time. Would be nicer, it seems if Mailman Xed out the email addresses as well rather than the present obscuring. That's another area of improvement that we have planned for future versions. JLS Just makes a great product all the better!! Keep up the good work and many thanks for the help on my one important issue here. Didn't realize this hadn't come up before. As I said before, I have watched MM mature for several years and even installed it once a couple of years ago (2 or 3) -- but didn't think it was ready until now. Many things have been fixed.improved since then. BTW: One other thing not meaning to be nit picky, but are you aware that FBSD ports show this program as containing numerous vulnerabilities? Here's what the portaudit sez, just FYI: Affected package: mailman-2.1.8_3 Type of problem: mailman -- Multiple Vulnerabilities. Reference:
Re: [Mailman-Users] Obscure addresses problem
At least on Mailman 2.1.6, something about how the page where you enter the administrative password is designed prevents Firefox from remembering that password for me. It's extremely annoying, I have to go look that one up in Passwordsafe each time I use it, which is nearly daily. Anybody have any ideas? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
At 5:56 AM -0700 2006-09-05, Jack Stone wrote: The knob in the web site configs about changing from YES to NO had me distracted thinking it was the place to change my setting for this preference. Yeah, I'm confused too. I'm hoping that one of the core Mailman developers will respond to this thread and tell me what it is that I've missed. So, I just need to disable access to the Mailman version of the archive which I consider vulnerable to harvesting in its present form. Plus, I don't need it with my own archives available and they are safe. See FAQ 3.3, and scroll down to the bottom. BTW: One other thing not meaning to be nit picky, but are you aware that FBSD ports show this program as containing numerous vulnerabilities? I was not personally aware of this issue, but apparently the Mailman developers are. Reference: http://www.FreeBSD.org/ports/portaudit/fffa9257-3c17-11db-86ab-00123ffe8333.html This page links to some others, including http://secunia.com/advisories/21732/, which includes the text: Solution: The vulnerabilities have been fixed in version 2.1.9rc1 and will also be fixed in the upcoming 2.1.9 version soon. Note that the Mailman developers have already upgraded us to 2.1.9rc1 for all our lists hosted on python.org, including this one. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 Founding Individual Sponsor of LOPSA. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
Brad Knowles [EMAIL PROTECTED] wrote:At 6:06 AM -0700 2006-09-03, Jack Stone wrote: I run a separate searchable archive where the whole address is munged with s, but now without the @ regular format, the address is more exposed than before. The archives are basically flat HTML files that are generated by Mailman when messages come in, or by periodic cron jobs. Since they're flat HTML files, if you make a change like this you will need to go back and re-generate all the affected archives in order to make the change visible everywhere. Did you do that? -- Brad Knowles, Brad: I did what you advised but mailman does not adjust to the new setting of NO to not Obscure. Yes, I have regenerated the archives -- the ones that belong to mailman of course. I cannot modify the post-prosessing script because I use the program Mhonarc to generate the searchable version of my archives since Mailman does not include that feature. It has the nice feature of truly obscuring (completely) the email addresses much better than just amember at somewh.ere However, Mhonarc needs the regular email address to see it and convert to [EMAIL PROTECTED] Those wishing to harvest emails can certainly run a script to put the Mailman Obsured method back to a full email -- I cannot tho. Is the obscure a buggy feature or do you have any other suggestions. I haven't seen any other answers in my search. I have watched Mailman mature for years before switching from majordomo. The only aspect keeping me from doing it was the messy archives that could not set the right dates of the message and showed dates far into the future. Too messy for a list with scientists, academics, engineers and the like who would be very picky about that. Please one more attempt to explain to me what to do I'll go away -- happy as a clam if I get the right answer from anyone -- unless I'm the only one on this list with this problem. Thanks for tolerating me on this important issue (for us). See the tech mag that uses the list: http://www.antennex.com I am the publisher, but a mediocre Sys Adm. (^-^) Best regards, Jack L. Stone -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
On Mon, 4 Sep 2006 07:04:37 -0700 (PDT) Jack Stone [EMAIL PROTECTED] wrote: I cannot modify the post-prosessing script because I use the program Mhonarc to generate the searchable version of my archives since Mailman does not include that feature. It has the nice feature of truly obscuring (completely) the email addresses much better than just amember at somewh.ere However, Mhonarc needs the regular email address to see it and convert to [EMAIL PROTECTED] [snip] Please one more attempt to explain to me what to do I'll go away -- happy as a clam if I get the right answer from anyone -- unless I'm the only one on this list with this problem. I think what you are asking is specific to MHonArc. Mailman only calls MHonArc as an external archiver and then Mailman assumes that external archiver knows what it is doing. I believe what you are looking for is called SPAMMODE in MHonArc. SPAMMODE determines if MHonArc will perform actions to deter spam address harvesters. If SPAMMODE is true, it changes the default values of various resources that display email addresses. I don't know the specifics of enabling this in MHonArc as I have just started looking at this myself. You will want to take a look at the MHonArc site for specifics, www.mhonarc.org --Karl -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
Karl Zander [EMAIL PROTECTED] wrote:On Mon, 4 Sep 2006 07:04:37 -0700 (PDT) Jack Stone wrote: I cannot modify the post-prosessing script because I use the program Mhonarc to generate the searchable version of my archives since Mailman does not include that feature. It has the nice feature of truly obscuring (completely) the email addresses much better than just amember at somewh.ere However, Mhonarc needs the regular email address to see it and convert to [EMAIL PROTECTED] [snip] Please one more attempt to explain to me what to do I'll go away -- happy as a clam if I get the right answer from anyone -- unless I'm the only one on this list with this problem. I think what you are asking is specific to MHonArc. Mailman only calls MHonArc as an external archiver and then Mailman assumes that external archiver knows what it is doing. I believe what you are looking for is called SPAMMODE in MHonArc. SPAMMODE determines if MHonArc will perform actions to deter spam address harvesters. If SPAMMODE is true, it changes the default values of various resources that display email addresses. I don't know the specifics of enabling this in MHonArc as I have just started looking at this myself. You will want to take a look at the MHonArc site for specifics, www.mhonarc.org --Karl Karl, you missed the point. Sorry I'm just not being clear enough. I do not have Mailman calling MhonArc. I just want Mailman to do want it is told to do first and all would be fine. I do use SPAMMODE on MHonArc to obtain the es to obliterate the email addresses AFTER Mailman has generated the archives. Mailman doe not depend on MHonArch, but MHonArch's SPAMMODE depends on the output files of Mailman. I cannot get the Mailman knob to NOT Obscure to do that. It just keeps obscuring no matter what I do. If I run MHonArc on the Mailman mylist.mbox, which contains the email addresses in full, then it works. Alas tho, the archive mylist.mbox doesn't split the months as does the mylist-month.txt So, I switched over to using the txt archive to feed MHonArc and then discovered the new problem of the Mailman's method of obscuring the addresses which now defeats MHonArch. I am very familiar with use of MHonArch. Any other thoughts??? (^-^) Best regards, Jack L. Stone -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
At 7:04 AM -0700 2006-09-04, Jack Stone wrote: Brad: I did what you advised but mailman does not adjust to the new setting of NO to not Obscure. Yes, I have regenerated the archives -- the ones that belong to mailman of course. Hmm. In which case, I'm not sure I've got any answers for you. There seems to be some sort of disconnect between the Mailman archive generation process and your custom third-party process, and the techniques that have worked on every other Mailman server that I have ever encountered do not appear to work on your machine. Perhaps someone else will be able to provide some insight. Is the obscure a buggy feature or do you have any other suggestions. I haven't seen any other answers in my search. The Mailman method of obscuring addresses has always worked as described, in all installations I have ever encountered or heard of. I have never heard of anyone having the kinds of problems you are seeing, but then it sounds like you're tying these processes together in a non-standard way, and I'm afraid that I will not be able to provide any further assistance. I have watched Mailman mature for years before switching from majordomo. The only aspect keeping me from doing it was the messy archives that could not set the right dates of the message and showed dates far into the future. That sounds like a problem that was resolved a while back. See FAQ 3.63. Please one more attempt to explain to me what to do I'll go away -- happy as a clam if I get the right answer from anyone -- unless I'm the only one on this list with this problem. You're the only one who's ever reported this problem, so far as I know. All the other sites that use MHonArc have tied that in through the standard Mailman third-party archive mechanism, and I have not heard of anyone having these kinds of problems with that technique. Nor have I heard of anyone using the standard third-party archive mechanism wanting or needing to change the value of the Mailman address obscuration feature, because that is implemented in the Pipermail archive system within Mailman, and that is by-passed when you go through the third-party archive system. So, I'm not sure that anyone is going to be able to help you, but we can always hope. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 Founding Individual Sponsor of LOPSA. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
On Sep 4, 2006, at 12:50 PM, Brad Knowles wrote: The Mailman method of obscuring addresses has always worked as described, in all installations I have ever encountered or heard of. Remember, what he's trying to do is to get pipermail NOT to obscure the addresses. This is completely unrelated to how the resulting files are used or what further processing is done on them. Here's the setting: obscure_addresses (privacy): Show member addresses so they're not directly recognizable as email addresses? Setting this option causes member email addresses to be transformed when they are presented on list web pages (both in text and as links), so they're not trivially recognizable as email addresses. The intention is to prevent the addresses from being snarfed up by automated web scanners for use by spammers. Just out of curiosity, I tried the same thing. I confirmed that the list.mbox did indeed contain the complete, whole, unadulterated addresses, set privacy options--obscure_addresses to NO, then ran bin/arch --wipe on a small test list. The newly created year- month.txt files did still include the standard xxx at xxx obscured email addresses. Maybe we're just trying the wrong setting; is the obscured address a pipermail constant? Is there some other setting that controls this? Dan Dan Phillips Associate Professor Rudi E. Scheidt School of Music University of Memphis [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
Dan Phillips [EMAIL PROTECTED] wrote: On Sep 4, 2006, at 12:50 PM, Brad Knowles wrote: The Mailman method of obscuring addresses has always worked as described, in all installations I have ever encountered or heard of. Remember, what he's trying to do is to get pipermail NOT to obscure the addresses. This is completely unrelated to how the resulting files are used or what further processing is done on them. Dan: THANK YOU so much for going to the trouble of reproducing the problem! I thought I was losing my mind or encapable of explaining the problem. If it is a bug, hope the maintainer is listening to include a fix in the upcoming new version.??? (^-^) Best regards, Jack L. Stone -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
At 2:06 PM -0500 2006-09-04, Dan Phillips wrote: Remember, what he's trying to do is to get pipermail NOT to obscure the addresses. This is completely unrelated to how the resulting files are used or what further processing is done on them. I understand. The problem is that the standard method of using a third-party archive solution should eliminate Pipermail from the picture altogether, and instead replace it with the third-party alternative. I have never before heard of anyone taking the output from Pipermail and then putting that into a third-party archive tool -- that would be like taking the output from sendmail and then piping that through postfix, and clearly redundant. I think maybe the OP may want to review the recommended method of using an external archiving tool like MHonArc with Mailman, such as described in FAQ 4.4. Maybe we're just trying the wrong setting; is the obscured address a pipermail constant? Is there some other setting that controls this? Did you look at your mm_cfg.py to see what the setting was for ARCHIVER_OBSCURES_EMAILADDRS? Here's the comment from Defaults.py for Mailman 2.1.5, if you did not over-ride this setting: # Pipermail archives contain the raw email addresses of the posting authors. # Some view this as a goldmine for spam harvesters. Set this to Yes to # moderately obscure email addresses, but note that this breaks mailto: URLs # in the archives too. ARCHIVER_OBSCURES_EMAILADDRS = Yes -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 Founding Individual Sponsor of LOPSA. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
Brad Knowles [EMAIL PROTECTED] wrote: At 2:06 PM -0500 2006-09-04, Dan Phillips wrote: Remember, what he's trying to do is to get pipermail NOT to obscure the addresses. This is completely unrelated to how the resulting files are used or what further processing is done on them. -- I understand. The problem is that the standard method of using a third-party archive solution should eliminate Pipermail from the picture altogether, and instead replace it with the third-party alternative. I have never before heard of anyone taking the output from Pipermail and then putting that into a third-party archive tool -- that would be like taking the output from sendmail and then piping that through postfix, and clearly redundant. I think maybe the OP may want to review the recommended method of using an external archiving tool like MHonArc with Mailman, such as described in FAQ 4.4. Brad Knowles, -- Considering I have only switched from majordomo (used since 1997) on several lists a week+ ago, I just had not found all of the knobs yet -- nor did I even know what knobs I would need to twist yet to provide the archives needed. All other things are running great and I'm glad I made the switch finally. Adding ARCHIVER_OBSCURES_EMAILADDRS = No to mm_cfg.py did the trick and now have the solution. I looked at FAQ 4.4 and the method described there using an external archiving tool like MHonArc with Mailman methinks is a monster compared to my manner of cron-run scripts that updates my custom archives every 15 minutes to display the added messages. My need for a fix was minor IF I had just know where to look. Next, I'm just looking for a knob to drop the display of the archives in Mailman's web site and have members continue to use only the one they have been used to for several years -- and is not available for email harvesting. I still want to keep generating the mylist.txt because my scripts use that monthly file. Just don't want it to appear anywhere to the members or one that would join to mis-use it for spam lists. Would be nicer, it seems if Mailman Xed out the email addresses as well rather than the present obscuring. I can imagine it would be little effort for spammers to download the Mailman archives and then run a script to return the emails from xyz at adomain.com right back to [EMAIL PROTECTED] All the info is there gieving a false sense of security. [EMAIL PROTECTED] seems a lot safer to me. Anyway, truly appreciate the help from you Brad and especially Dan who understood my issue. I'll spend more time in the Defaults.py looking at more knobs there. (^-^) Best regards, Jack L. Stone -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
At 6:06 AM -0700 2006-09-03, Jack Stone wrote: I run a separate searchable archive where the whole address is munged with s, but now without the @ regular format, the address is more exposed than before. The archives are basically flat HTML files that are generated by Mailman when messages come in, or by periodic cron jobs. Since they're flat HTML files, if you make a change like this you will need to go back and re-generate all the affected archives in order to make the change visible everywhere. Did you do that? -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 Founding Individual Sponsor of LOPSA. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
Brad Knowles [EMAIL PROTECTED] wrote:At 6:06 AM -0700 2006-09-03, Jack Stone wrote: I run a separate searchable archive where the whole address is munged with s, but now without the @ regular format, the address is more exposed than before. The archives are basically flat HTML files that are generated by Mailman when messages come in, or by periodic cron jobs. Since they're flat HTML files, if you make a change like this you will need to go back and re-generate all the affected archives in order to make the change visible everywhere. Did you do that? -- Brad Knowles, I just switched my mail list management from majordom to mailman within the past week. All of my archives prior to the day of the switch are xed out. I'm not concerned about the few that mailman obscured, just wanted the normal address to appear on each message in the new archive files by mailman. My archiving program takes the mailman archive files (after the fact) and prepares the archives with any and all email addresses that appear in mailman's mbox or flat text archive files and generates the archives I have over 10,000 messages with the email obscured as: [EMAIL PROTECTED] to: [EMAIL PROTECTED] whereas, mailman does this: amember at somewhere.com My old method of obscuring is much more obscured. So, why doesn't the change from YES to NO on the obscure not work?? That's all I need so the messages arrive in the mailman archive files with a whole original email address format. (^-^) Best regards, Jack L. Stone -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
Brad Knowles [EMAIL PROTECTED] wrote:At 11:36 AM -0700 2006-09-03, Jack Stone wrote: So, why doesn't the change from YES to NO on the obscure not work?? Because you still need to regenerate the archives, which you apparently did not do. IMO, better yet would to modify your post-processing script so that it understands both address formats, so that it doesn't matter how this particular option is set. -- Brad Knowles, Brad: Sorry I'm so thick-headed, but didn't realize it wouldn'l just start feeding the archives with the new setting. So, I need to regenerate the archives for the setting to take effect as you have twice said. Since I'm just learning mailman, what would my line command flags be to do that. Or, your second suggestion: ...to modify your post-processing script , how would I modify the post-processing script -- so I don't screw it up? Thanks for your support on this one. (^-^) Best regards, Jack L. Stone -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
Jack Stone [EMAIL PROTECTED] wrote:Brad Knowles wrote: At 11:36 AM -0700 2006-09-03, Jack Stone wrote: IMO, better yet would to modify your post-processing script so that it understands both address formats, so that it doesn't matter how this particular option is set. -- Brad Knowles, Sorry, I found how to regenerate the archives in the FAQ search. But, haven't found this one yet: Or, your second suggestion: ...to modify your post-processing script , how would I modify the post-processing script -- so I don't screw it up? Thanks for your support on this one. (^-^) Best regards, Jack L. Stone -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/antennex%40swbell.net Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.027.htp (^-^) Best regards, Jack L. Stone -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Obscure addresses problem
Jack Stone [EMAIL PROTECTED] wrote: Jack Stone wrote: Brad Knowles wrote: At 11:36 AM -0700 2006-09-03, Jack Stone wrote: Did the regen of the archives and NADA Just the same email format presented by mailman archives: amember at somewhere.com Now what. On the second suggestion: I'm a bit off wave today -- you meant modify MY script. I'd rather mailman do what it says when the knobs are reset. (^-^) Best regards, Jack L. Stone -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
