Re: [Mailman-Users] attachements question
hi! Where exactly are saved the atatchement files, also in which format uencoded or just like the original attachement file? thank you in advance! At 3:04 PM -0300 2005-09-27, Manuel Kissoyan wrote: My question is, how long are these files saved for people to download They are saved until some other process comes along to clean them out. and are they automatically deleted after a while? That's not part of the standard cron jobs, no. Is there a way for me to manually go in and delete them so they dont build up and take up server space? Sure, you can go manually delete them. Or you can set up a cron job to go delete any attachments more than a certain age. Im assuming they self delete after a while because clicking on one of the link now indicates its not there. That implies that something else is going on. There is no standard cron job that I know of to clean out the old attachments. -- 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 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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] attachements question
Manuel Kissoyan wrote: Where exactly are saved the atatchement files, also in which format uencoded or just like the original attachement file? Scrubbed attachments are stored in the directory archives/private/listname/attachments. In most cases, they are just the original attachment (decoded from the MIME Content-Transfer-Encoding:), but in the case of scrubbed HTML parts, the format depends on the mm_cfg.py setting of ARCHIVE_HTML_SANITIZER. The default is to store HTML attachments 'HTML escaped' which means things like , and are replaced with lt;, gt; and amp; respectively so that opening the attachment in a web browser shows effectively the source HTML rather than the rendered page. -- Mark Sapiro [EMAIL PROTECTED] The 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://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] attachements question
John == John W Baxter [EMAIL PROTECTED] writes: John In addition, the Message-Id values would have to be John filtered, if used as is, for URL-unfriendly characters I don't think so. AFAIK, that was fixed about 2000 RFCs ago. When used as URLs, conforming agents will URL-encode them. How the archive chooses to implement identifying a storage location from the decoded URL is up to it. The URL-encoded string as filename is an obvious choice, but database-based archives might just use the raw Message-ID. BTW, I just realized that Google probably does index Message-IDs already (as long as the archived message includes that header), so Googleability is _not_ an advantage of my scheme over the header digest approach. The ability to algorithmically construct URNs and URLs however still is. John There's also the small point that the presence of John Message-Id: is a SHOULD, not a MUST (some compromise in the John musty past of the IETF, no doubt). I would guess that's for the convenience of folks who use telnet HOST 25 as their MTA. Humans are notoriously bad at generating unique anything.wink Anyway, my algorithm just treats such messages as a collision with all the others that don't have Message-IDs. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can do free software business; ask what your business can do for free software. -- 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] attachements question
At 2:29 PM +0900 2005-09-29, Stephen J. Turnbull wrote: BradBecause some MUAs generate message-ids that are likely Brad to collide. Can we stop pandering to the broken mailers, please? Are we not hackers? We know how to handle collisions. I don't really care how the algorithm is implemented. I care that it works. And I care that it is actually done, and checked into the source tree. -- 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 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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] attachements question
On 9/28/05 1:30 AM, Brad Knowles [EMAIL PROTECTED] wrote: Why archivers don't use Message-Id for the URL, I don't know. Because some MUAs generate message-ids that are likely to collide. In addition, the Message-Id values would have to be filtered, if used as is, for URL-unfriendly characters (eg, Outlook Express tosses in a couple of $ characters). Just another example of not trusting input from untrusted sources. The hash of Message-Id:, Date:, and Received: (all of the Received: headers) would do, except for the case of an insane MTA--the one generating the top Received: header--feeding the same message into Mailman multiple times. Perhaps a representation of the computer's clock would help there. There's also the small point that the presence of Message-Id: is a SHOULD, not a MUST (some compromise in the musty past of the IETF, no doubt). --John -- 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] attachements question
At 8:50 AM -0700 2005-09-28, John W. Baxter wrote: The hash of Message-Id:, Date:, and Received: (all of the Received: headers) would do, except for the case of an insane MTA--the one generating the top Received: header--feeding the same message into Mailman multiple times. Perhaps a representation of the computer's clock would help there. The top Received: header is added by the Mailman mailing list server MTA itself, and that should include the local date/time stamp as of the time of receipt of the message. -- 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 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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] attachements question
Brad == Brad Knowles [EMAIL PROTECTED] writes: Brad At 2:03 PM +0900 2005-09-28, Stephen J. Turnbull wrote: Why archivers don't use Message-Id for the URL, I don't know. Brad Because some MUAs generate message-ids that are likely Brad to collide. Can we stop pandering to the broken mailers, please? Are we not hackers? We know how to handle collisions. Here's the algorithm: 1) Look for a unique ID in the (X-)List-Archive-Message-ID field. If not found: a) Generate a unique ID according to the usual algorithm as if the post were about to be sent from the archive host. b) Add it to the header in the (X-)List-Archive-Message-ID field. 2) Extract the message ID from the message. If none, set the program variable equal to the ID generated in 1, and (optionally) add it as Message-ID to the message's header. 4) Generate the URL for the archived message based on *Message-ID*. 5) Check for collision. 6) If there is a collision, make a directory (could be a file-system directory, could be just an HTML file, could be a digest message) with the URL generated in 4. Generate URLs for the colliding messages based on Message-ID plus List-Archive-Message-ID, and include them in the directory. Conforming implementations MAY also extract MUA information and make nasty comments about the broken MUAs, their implementers, and their users to go with the directory. If Message-ID == List-Archive-Message-ID, go to 1a. At this point a conforming implementation MAY mail /vmunix to its implementer, who obvious snafu'ed. 7) PUT the colliding messages at those URLs. Rationale: 1. You could actually derive an URN from this: archived-message://list-archive.your.org/MESSAGE-ID. 2. The URL is unique and will persist across regeneration of the archive as long is the message is present. 3. People who use conformant software implemented competently should be given precedence. 4. Users who don't subscribe to the archiver's client but somehow get their hands on a message ID can use Google to find it (and the rest of the thread). 5. People who use software that doesn't conform will suffer. Brad For some time now, I've been arguing that they should use a Brad hash of the relevant information (maybe all the headers, Brad maybe just selected headers, maybe the entire message, Brad whatever is reasonable to assume will survive), making sure Brad to at least include the value of the Date:, Message-ID:, Brad and Received: headers as part of that input. This gives 1 and 2, but not 3, 4, and 5. (No, you can't generate a Google search item from knowledge of the algorithm because you don't necessarily have the Received headers.) Seems like overkill for Step 1 of the algorithm, too. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can do free software business; ask what your business can do for free software. -- 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
[Mailman-Users] attachements question
Hi, Wondering if someone know the answer of this, made for one of our clients... With the mailman software for mailing lists, it has the option of scrubbing attatchments to the list and converts them to a link for people who are on the list to click on to get the attatchment rather than everyone having to download it. My question is, how long are these files saved for people to download and are they automatically deleted after a while? Is there a way for me to manually go in and delete them so they dont build up and take up server space? Im assuming they self delete after a while because clicking on one of the link now indicates its not there. Thank you in advance! -- 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] attachements question
At 3:04 PM -0300 2005-09-27, Manuel Kissoyan wrote: My question is, how long are these files saved for people to download They are saved until some other process comes along to clean them out. and are they automatically deleted after a while? That's not part of the standard cron jobs, no. Is there a way for me to manually go in and delete them so they dont build up and take up server space? Sure, you can go manually delete them. Or you can set up a cron job to go delete any attachments more than a certain age. Im assuming they self delete after a while because clicking on one of the link now indicates its not there. That implies that something else is going on. There is no standard cron job that I know of to clean out the old attachments. -- 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 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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] attachements question
Brad == Brad Knowles [EMAIL PROTECTED] writes: Im assuming they self delete after a while because clicking on one of the link now indicates its not there. Brad That implies that something else is going on. There Brad is no standard cron job that I know of to clean out the old Brad attachments. If somebody cleaned out spam or private information, and regenerated the archives, that might change the order, and the link would break. I know this happens with MHonArc (since the URLs it generates are simply the serial number of processing concatenated with a prefix and .html). I don't know about pipermail but I wouldn't be surprised. Why archivers don't use Message-Id for the URL, I don't know. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can do free software business; ask what your business can do for free software. -- 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
