Re: [OT] Vim
--mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alas! Ken Weingold spake thus: On Mon, Aug 26, 2002, Kai Weber wrote: + Ken Weingold [EMAIL PROTECTED]: =20 Yeah, but with procmail I can send them to /dev/null. With Spamassassin they go to my spam folder for review. =20 You can use procmail to filter the spamassasin'ated mails to /dev/null, too. =20 I would never do that. Sometimes Spamassassin catches real mail as spam. blacklisting adds 100 to the score. All you really have to do is set your procmail rules so that mails with a score over 90 are sent to /dev/null, and mails with less are sent to your spam folder. Then you get pretty much the best of both worlds. --=20 Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- All I ask of life is a constant and exaggerated sense of my own importance. --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9azhwPTh2iSBKeccRAuXhAJ9EcIrhiFouSpuHdCZglHSrcwdQSwCfQ4yf MwDXfxdUEKUH22GsiZEKWZc= =dOmP -END PGP SIGNATURE- --mP3DRpeJDSE+ciuQ--
Re: [OT] Vim
--cvVnyQ+4j833TQvp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alas! Michael Leone spake thus: it's been my experience that the latest SA (v2.31) is much better at=20 distinguishing real mail from spam than earlier version. And v2.40 is due Really Really Soon Now, they say. I've been using v 2.31 for a couple weeks now and I've seen *NO* troubles with it. It has caught every spam, and allowed every real message that I've gotten so far. I only get 50 to 100 emails per day, unlike some people here, but a 0% failure rate is pretty good, no? --=20 Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- Unix will self-destruct in five seconds... 4... 3... 2... 1... --cvVnyQ+4j833TQvp Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9azjrPTh2iSBKeccRAmD5AJ9lyM+dDEvgfhDIK1GwqAoVQjwBTwCfVNw8 a7hYoxjAAtkFIMyYbzvkins= =jctu -END PGP SIGNATURE- --cvVnyQ+4j833TQvp--
Re: mutt-newbie list
* Steve Wollkind [EMAIL PROTECTED] wrote: mutt and I'm trying to get mailing list support to work. I put the 'subscribe mutt-users' in my .muttrc and these messages are flagged L correctly, but for some reason when I try to save them it prompts me to save them by the author's address, and not mutt-users. No, I don't have the save_address option turned on. Are you looking for save-hooks? For example: save-hook '~C .+@mutt\.org$' +Backup/mutt/ Paul
reply formatting
I know that i can set the subject line to be used with a forwarded mail with the 'forward_format' line in my .muttrc but i don't seem to be able to find the equivalent for the reply function. what i want is to modify the default quote header. forgive my possibly cryptic explanation but i do not think in a way fully compatible with you earth people. to make it clear: the bit i want to change is the bit that goes in the body and says something like 'on sunday 24th, joe foo said:' -- Mat Harris OpenGPG Public Key ID: CC14DD34 [EMAIL PROTECTED]matthewh.genestate.com msg30443/pgp0.pgp Description: PGP signature
Re: reply formatting
* Mat Harris [EMAIL PROTECTED] [08-27-02 07:16]: I know that i can set the subject line to be used with a forwarded mail with the 'forward_format' line in my .muttrc but i don't seem to be able to find the equivalent for the reply function. what i want is to modify the default quote header. forgive my possibly cryptic explanation but i do not think in a way fully compatible with you earth people. to make it clear: the bit i want to change is the bit that goes in the body and says something like 'on sunday 24th, joe foo said:' Check the manual (/usr/local/doc/mutt/manual.txt in SuSE), for: 6.3.15. attribution Type: string Default: On %d, %n wrote: This is the string that will precede a message which has been included in a reply. For a full listing of defined printf()-like sequences see the section on ``$index_format. -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org
Re: reply formatting
thanks, i would never have found it, called that. On Tue, Aug 27, 2002 at 01:11:45PM +0100, Mat Harris wrote: I know that i can set the subject line to be used with a forwarded mail with the 'forward_format' line in my .muttrc but i don't seem to be able to find the equivalent for the reply function. what i want is to modify the default quote header. forgive my possibly cryptic explanation but i do not think in a way fully compatible with you earth people. to make it clear: the bit i want to change is the bit that goes in the body and says something like 'on sunday 24th, joe foo said:' -- Mat HarrisOpenGPG Public Key ID: CC14DD34 [EMAIL PROTECTED] matthewh.genestate.com -- Mat Harris OpenGPG Public Key ID: CC14DD34 [EMAIL PROTECTED]matthewh.genestate.com msg30445/pgp0.pgp Description: PGP signature
Re: mutt-newbie list
In message 3 of the current thread, Paul Gabriel wrote: * Steve Wollkind [EMAIL PROTECTED] wrote: mutt and I'm trying to get mailing list support to work. I put the 'subscribe mutt-users' in my .muttrc and these messages are flagged L correctly, but for some reason when I try to save them it prompts me to save them by the author's address, and not mutt-users. No, I don't have the save_address option turned on. Are you looking for save-hooks? For example: save-hook '~C .+@mutt\.org$' +Backup/mutt/ I may be. That could be quite useful for other reasons as well (like friends who send me email from many addresses). I guess I was under the mistaken impression that mutt would automatically try to save list email to a folder for the list and not the sender. Steve -- Steve Wollkind 810 C San Pedro [EMAIL PROTECTED] College Station, TX 77845 http://njord.org/~steve 979.696.3153 -- Teach your kids: Copyright made baby Jesus cry. msg30446/pgp0.pgp Description: PGP signature
File browser statusbar
Hi. Where do I change the stuff displayed in the file browsers statusbar? Johan Svedberg
overriding the charset for headers
Hello, this has been discussed in the past, but I couldn't find an adequate solution for my particular problem. I often receive messages with either unquoted 8-bit headers (in lines like From:, To:, Subject:, etc.) or, worse, with characters quoted and wrong charset specified. Example 1: My console can display koi8-r. I receive a mail encoded in windows-1251 with an unquoted header. Mutt converts the body to koi8-r, and I can read the contents. However, Mutt doesn't know the header charset, so it is displayed without conversion, and I can't read it. For instance, 192 is Acyr in 1251, but I see it as yucyr with my koi8-r font. I wish I could specify the header charset manually (as I do with ^E for message bodies) so that Mutt could convert the subject and other fields. Example 2: My console can display iso-8859-9. I receive a mail encoded in iso-8859-9. Headers are quoted, and the charset is set to iso-8859-1 (Subject: =?iso-8859-1?Q?some_8859-9-encoded_text?=). Mutt reads the charset, and displays 8859-9-specific characters as question marks, as they are not present in my 8859-9 font. E.g., 254 is scedilla in 8859-9, but Mutt thinks it is 8859-1, and tries to display thorn, which is not available in the font. Again, the only solution I see is to override the charset manually. I can't just charset-hook iso-8859-1 iso-8859-9 since I can as well receive mail encoded in koi8-r, but flagged as iso-8859-1. I'm using 1.4. I think LC_CTYPE and charset are set correctly in both cases. BTW, why does Mutt use both of these variables? I would find logical if charset have overridden LC_CTYPE. I can't see the rationale behind the current implementation, and find it counter-intuitive. Could anyone please shed some light on this, too? I would appreciate any help. Thanks in advance, Baurjan. P.S. Please cc to me, I'm not subscribed. I have lists mutt-users and set followup_to in my .muttrc, but I can't see any Followup-To: lines in the mail sent.
Re: overriding the charset for headers
On Tue, Aug 27, 2002 at 08:06:00PM +0300, Baurjan Ismagulov wrote: P.S. Please cc to me, I'm not subscribed. I have lists mutt-users and set followup_to in my .muttrc, but I can't see any Followup-To: lines in the mail sent. Oops, turns out that Mutt sets Mail-Followup-To: upon sending, this field doesn't appear in postponed folder. Having received such a message, how can one have Mutt set To: and/or Cc: fields automatically (Mail-Followup-To: contains both sender and list addresses)? r and L set To: list only. With kind regards, Baurjan.
Re: overriding the charset for headers
It has come to my attention...
...that Baurjan Ismagulov said on Tuesday, Aug 27 2002:
Hello,
Hi,
I often receive messages with either unquoted 8-bit headers (in lines
like From:, To:, Subject:, etc.) or, worse, with characters quoted and
wrong charset specified.
My condolences. This sounds like a job for procmail's formail program.
Example 1:
My console can display koi8-r. I receive a mail encoded in windows-1251
with an unquoted header. Mutt converts the body to koi8-r, and I can
read the contents. However, Mutt doesn't know the header charset, so it
is displayed without conversion, and I can't read it. For instance, 192
is Acyr in 1251, but I see it as yucyr with my koi8-r font.
I wish I could specify the header charset manually (as I do with ^E for
message bodies) so that Mutt could convert the subject and other fields.
Using procmail/formail and iconv you might be able to accomplish
rewriting of the mail headers based on the sender so they are properly
escaped. You'll have to hit up the folks at procmail-users for that
though, as I wouldn't know how to do it. Tricky situation. Bottom
line is, those senders are using broken mail clients. Though it may
seem anti-social, ya might want to drop a few hints to this. I don't
think mutt's the only mail client that would get confused by such
email.
Example 2:
My console can display iso-8859-9. I receive a mail encoded in
iso-8859-9. Headers are quoted, and the charset is set to iso-8859-1
(Subject: =?iso-8859-1?Q?some_8859-9-encoded_text?=). Mutt reads the
charset, and displays 8859-9-specific characters as question marks, as
they are not present in my 8859-9 font. E.g., 254 is scedilla in 8859-9,
but Mutt thinks it is 8859-1, and tries to display thorn, which is not
available in the font.
Hmm, here's an idea for a procmail recipe that should work, but I
haven't tested this myself.
:0 fhw
* ^From: Evil Sender [EMAIL PROTECTED]
{
:0 h
SUBJECT=| formail -xSubject: | sed 's/iso-8859-1/iso-8859-9/i'
:0:
|formail -ISubject: $SUBJECT $DEFAULT
}
I would hope this would do the trick, but I can't be sure if you'd
need to reformat the header. I wouldn't think so. Anyone?
$ man procmailex for more ideas.
Again, the only solution I see is to override the charset manually. I
can't just charset-hook iso-8859-1 iso-8859-9 since I can as well
receive mail encoded in koi8-r, but flagged as iso-8859-1.
Yeah, definitely a job for formail.
I'm using 1.4. I think LC_CTYPE and charset are set correctly in both
cases. BTW, why does Mutt use both of these variables? I would find
logical if charset have overridden LC_CTYPE. I can't see the rationale
behind the current implementation, and find it counter-intuitive. Could
anyone please shed some light on this, too?
Hmm, from my experience, charset does override LC_CTYPE. I'll have to
double check that. To my knowledge, charset is set based on your
locale if you don't explicitly set it in your muttrc. Anyone?
I would appreciate any help.
Hope I was helpful. I'm not an expert by any means and for everyone
else, correct me if my information is wrong. I'm pretty spotty on
most of this stuff.
Thanks in advance,
Baurjan.
You're welcome.
--
--Sam
UC Davis, California USA
msg30450/pgp0.pgp
Description: PGP signature
Re: mutt and gnupg setup
Hi Justin! On Mon, Aug 26, 2002 at 05:32:59PM -0400, Justin R. Miller wrote: I have recently installed gnupg-1.0.7 and I'd like to use it with mutt. But I can't use gnupg with mutt out of the box: the muttrc has to modified to tell mutt explicitely the different commands to sign and encrypt, etc. Where can I find such a setup for gnupg? See my guide at the URL below. Thanks a lot for the link! Good introduction, but I missed the procmail recipe to rewrite old-style inline PGP messages as S/MIME messages that you mentioned in your text. Bye, Markus
Re: mutt and gnupg setup
Hi Gregor! On Sun, Aug 25, 2002 at 06:21:52PM +0200, Gregor Zattler wrote: Well, do I have to use that gpg-2comp in order to use gpg with mutt? You need this wrapper script if and only if you want to communicate signed+encrypted with a person who uses pgp2.6.x So, in order to be able to communicate with anybody who uses any version of pgp or gnupg, I have to use that script. If so you must remove the comment hashes '#' on lines which use gpg-2comp and set hashes '#' on the correspioning lines without gpg-2comp usage. Okay, I did that. Note that you can not communicate with this setup with a user who does not use RSA v3 keys... I'm still pretty new to gnupg and cryptography in general. Which users does that affect? gnupg doesn't use RSA, does it? Thanks for your hints so far. Bye, Markus
Re: overriding the charset for headers
At 21:23 +0300 27 Aug 2002, Baurjan Ismagulov [EMAIL PROTECTED] wrote: message, how can one have Mutt set To: and/or Cc: fields automatically (Mail-Followup-To: contains both sender and list addresses)? r and L set To: list only. Let me guess, you're trying this with a message you sent? You can fix this with: set metoo reply_self -- Aaron Schrab [EMAIL PROTECTED] http://www.schrab.com/aaron/ live fast, die young, leave a big core file... -- Ben Low in 7rk70e$j3i$[EMAIL PROTECTED]
Re: mutt and gnupg setup
Markus, et al -- ...and then Markus Nißl said... % % On Mon, Aug 26, 2002 at 05:32:59PM -0400, Justin R. Miller wrote: % ... % See my guide at the URL below. % % Thanks a lot for the link! Good introduction, but I missed the % procmail recipe to rewrite old-style inline PGP messages as % S/MIME messages that you mentioned in your text. S/MIME? Don't you mean PGP/MIME? I don't know of anything that will convert PGP to S/MIME :-) And the conversion isn't necessary now because you can recognize an old-style message with esc-P and thus not risk mucking up your message by blatantly changing MIME headers. % % Bye, % % Markus HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg30454/pgp0.pgp Description: PGP signature
not recognizing PGP signatures in encrypted+signed messages
If I send myself a signed message, Mutt says PGP signature successfully verified., which is very nice. But if I send a signed and encrypted message, it says PGP signature could NOT be verified., which is not so good. Anybody have an idea why? This is happening on a system with Mutt 1.4i and gpg 1.0.7. Thanks. -Guy
