RE: image tags rewritten by MHonArc
Jym Dyer [mailto:[EMAIL PROTECTED]] wrote: >I would only advise doing that, though, if you are confident of >the integrity of the HTML in the messages being sent. Otherwise >you're opening the door to having your archives spreading and >perpetuating spam, feeding information back to spammers, and >having your archive readers sit there waiting while their >browser tries to download 300MB pornography ads from slow, flaky >webservers in Korea. Speaking from experience, are we? :-) Ricky
RE: Condensing multiple re, fw and fwds (was Removeing RE and Prefix)
Completely untested, but you could try: s/(Re:\s*|Fwd:\s*)+/Re:/ Note, of course, that this turns all 'Fwd:'s into 'Re:'s Ricky -Original Message- From: Simeon Nevel [mailto:[EMAIL PROTECTED]] Sent: Thursday 28 February 2002 4:57 PM To: [EMAIL PROTECTED] Subject: Condensing multiple re, fw and fwds (was Removeing RE and Prefix) Jym Dyer <[EMAIL PROTECTED]> said: > > Re: Fwd: Re[2]: Fwd: Re: [sftest] ME TOO! > > without throwing "[sftest]" in there four more times. While we're on the subject.. is there a single regexp that can reduce an an abitrary collection of Re's and Fwd's to a single Re: ? I currently preprocess my incoming messages with a perl prog consisting a long series of regexps to deal with this. I would be nice if I could craft a couple of stripsubjectcode expressions that would deal with this. It would give me an excuse to upgrade my MHonArc ;) Simeon -- If you're not outraged, you're not paying attention
RE: Removeing RE and Prefix
I think that I would still include the \s* after the \] in the regexp, because this will also remove any spaces following it Ricky -Original Message- From: Jym Dyer [mailto:[EMAIL PROTECTED]] Sent: Thursday 28 February 2002 4:07 PM To: [EMAIL PROTECTED] Subject: Re: Removeing RE and Prefix > Try: > > s/\[sftest\]//; > > The regular expression you're using requires that the > "[sftest]" be the first thing in the subject and must be > followed by a colon. =v= This is the right way to go, as it parallels the prevailing use of subject line keywords such as "[sftest]". Generally the mailing list software will insert it at the front (or after an initial "Re: "), but only after doing a very simple search to see whether the string is any part of the subject line. That lets it deal with stuff like: Re: Fwd: Re[2]: Fwd: Re: [sftest] ME TOO! without throwing "[sftest]" in there four more times. <_Jym_>
RE: Removeing RE and Prefix
Well, you could try one of the following regexps: s/\[sftest\]\s+//; This will remove the first '[sftest]' in the subject (even if not at the start of the subject line) s/^\s*(Re:\s?)?\s*\[sftest\]\s+/$1/; This will remove '[sftest]' following a 'Re:' followed by any number of whitespaces at the beginning of a string... HTH, Ricky -Original Message- From: Birger Mortensen [mailto:[EMAIL PROTECTED]] Sent: Thursday 28 February 2002 1:36 PM To: [EMAIL PROTECTED] Subject: Removeing RE and Prefix Is there a way to remove old prefix'es ? I am using : s/^\[sftest\]://; But it don't get subjects like this one :Re: [sftest] Hmm Og var til denne via WEB I have a test setup at http://mail.sf.dk/MHonArc/SFtest/ Im using MhonArc 2.5.1 on a ezmlm arkive Birger Mortensen
RE: Preferring text/plain over text/html?
I think you misunderstand -- this is the text/plain section of the message. This is _not_ something done by the MUA -- I know, because the actual message was somewhat less terse. It is really the fault of the "MSA" (Mail Sending Agent), and probably somewhat the fault of the person who wrote the message... Ricky -Original Message- From: Earl Hood [mailto:[EMAIL PROTECTED]] Sent: Friday 08 February 2002 3:06 PM To: [EMAIL PROTECTED] Subject: Re: Preferring text/plain over text/html? On February 8, 2002 at 13:59, "Morse, Richard E." wrote: > What if the text/plain message is merely a message saying "I'm sorry, but thi > s > message cannot be displayed in you mailer. The actual message has been attac > hed > as an HTML message." -- This has happened. Live with it. Seriously, this is extremely bad behavior of the MUA. The sematics of multipart/alternative is to have each part be reasonable *alternatives* of each other. With the example you provided, this is not the case. The MUA should have not bothered with using multipart/alternative and just set the main Content-Type to text/html. The receipient's MUA will be responsible for telling the receipient if the MUA is unable to render the data received. Also, if the main type was text/html and the receipient's MUA was MIME aware but did not support text/html, it would still show the raw HTML text. This is desired fallback behavior of a MIME-aware MUA when encountering unknown text media types. I.e. The MUA would treat the data as text/plain for purposes of displaying the message to the user. IMO, it is unreasonable to have MHonArc try to deal with such a situation. --ewh
RE: Preferring text/plain over text/html?
What if the text/plain message is merely a message saying "I'm sorry, but this message cannot be displayed in you mailer. The actual message has been attached as an HTML message." -- This has happened. Ricky -Original Message- From: Mike Acar [mailto:[EMAIL PROTECTED]] Sent: Wednesday 06 February 2002 5:18 PM To: [EMAIL PROTECTED] Subject: Re: Preferring text/plain over text/html? Earl Hood <[EMAIL PROTECTED]> wrote: > Some thought needs to be applied on what would be the best way to > support such a feature. One part is that actual implementation, the > other is how the user would tell MHonArc about multipart/alternative > preference ordering. Well, by far the most common is text/plain and text/html sent by such clients as Outhouse (which you love so well ;), so the obvious thing would be simply adding a prefer-multipart-plain-over-html config option. More generally I guess you could have a config section that specified a a multipart type and a list of MIME types in order of preference... A truly generic solution might be difficult to describe elegantly in a config file. -- Brilliance and gorgeousness| Mike Acar And we tell ourselves we don't want the treasures | [EMAIL PROTECTED] But we hate the glass anyway |
RE: Removing messages from one of multiple archives
Although, of course, I am not the final word on the subject, I would imagine that using the "outdir" parameter would specify the database... Ricky -Original Message- From: Ed Reiss [mailto:[EMAIL PROTECTED]] Sent: Tuesday 29 January 2002 11:04 PM To: [EMAIL PROTECTED] Subject: Removing messages from one of multiple archives I've been handed over the process of creating and managing two mailman mailing lists that use Mhonarc as a web archive tool. I need to remove some archived test messages I've been sending to the mailing lists and I found reference to the RMM command in the mhonarc docs online at: http://www.mhonarc.org/MHonArc/doc/resources/rmm.html Since I'm managing two archives I noticed that the command docs don't mention how one specifies the archive from which the messages should be removed. Can someone clarify the format of the command when there are several archives, and the specified messages should be removed from only one of them? Thanks for your help, Ed Reiss [EMAIL PROTECTED]
RE: Error locking the outdir...
H I guess that I haven't yet sat down and learned about ProcMail -- so that is the next thing that I should do Thanks! I may be asking more questions about this soon Ricky -Original Message- From: J C Lawrence [mailto:[EMAIL PROTECTED]] Sent: Thursday 10 January 2002 9:29 PM To: Morse, Richard E. Cc: [EMAIL PROTECTED] Subject: Re: Error locking the outdir... On Thu, 10 Jan 2002 17:05:17 -0500 Richard E Morse wrote: > Regarding this: suppose that I don't want to have to create a new > user account for each list I'm archiving? Is there any way that I > can have MHonArc choose different archives based on some header > value? I could then set up aliases to redirect all the archives > to one "archive" user, but then filter based on the "to" field... What I do: Inbound mail to be archived goes to an archiver account. Procmail files that mail in per-list folders. A cronjob runs periodically and calls list-customised MHonArc RC's to archive each list. (Its actually a little more generic than that as I use a standard RC which includes a small per-list custom template which defines things like list owner email address etc). Relevant files: ftp://ftp.kanga.nu/pub/Kanga.Nu/WebArchives/ The template bit: ftp://ftp.kanga.nu/pub/Kanga.Nu/WebArchives/MHonArc/variables.rc The cronjoba: ftp://ftp.kanga.nu/pub/Kanga.Nu/WebArchives/scripts/makeArchives ftp://ftp.kanga.nu/pub/Kanga.Nu/WebArchives/scripts/moveQuarters -- J C Lawrence -(*)Satan, oscillate my metallic sonatas. [EMAIL PROTECTED] He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.
RE: Error locking the outdir...
Regarding this: suppose that I don't want to have to create a new user account for each list I'm archiving? Is there any way that I can have MHonArc choose different archives based on some header value? I could then set up aliases to redirect all the archives to one "archive" user, but then filter based on the "to" field... Thanks, Ricky -Original Message- From: Earl Hood [mailto:[EMAIL PROTECTED]] Sent: Thursday 10 January 2002 3:29 PM To: [EMAIL PROTECTED] Subject: Re: Error locking the outdir... BTW, I recommend changing your setup to do archive updates via a cron job, using an archiving account to receive the mail. This way, mail will always get delivered to your system. If problems occur with MHonArc, you can have it fixed without the loss of any mail.
