Re: [OT] Only allow mail from selected addresses
On Sun, Apr 28, 2002 at 02:47:22PM +0200, [EMAIL PROTECTED] wrote: > However to rid my private inbox of that last 5% of spam I'd like to only > accept messages from a list of addresses... Relatively untested, but how about: # check whitelist. reverse the sense of the fgrep... FROM=`formail -rtzxTo:` :0: * ? /bin/fgrep -qvxis "$FROM" $HOME/.whitelist junkmail Should work well enough. I did something like this in front of my domain filter (I dump all hotmail.com, for example, but there are a couple I *do* want). -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: color depending on To:
* On Mon, 29 Apr 2002, Flavien wrote: > I must be missing something. It does not work here... :-( Actually, it was me who was missing something. I'm using "color index" to match my old addresses, not "color header". So I'm coloring the matched messages in the index, rather than coloring the headers in the pager. Sorry about that. I see the same problem you are having when I try "color header". It seems like mutt will color all the lines of a matching multi-line header, but the matching pattern must be in the first line. -- John
Re: color depending on To:
Hi, John Iverson gave the following hint : > I use ~C for this and it seems to work fine, even when the > address isn't on the first line of the To: header. Try this: > > color header red black "~C myoldlogin\@myoldaddress\.com" I must be missing something. It does not work here... :-( I daily use the version of mutt in debian/testing which is 1.3.23i. I for some time thought that that was the cause (ya know : the famous Larry Jones quote on "cvs-bug" : "Already fixed in development version." :o) ), so I checked out a fresh mutt tree from cvs and tried your advice on it, with no success. What I'm trying to match are headers like : Subject: Blah blah To: "My Friend" <[EMAIL PROTECTED]>, "Another" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, "Flavien" <[EMAIL PROTECTED]>, "Joe Foobar" <[EMAIL PROTECTED]>, "x" <[EMAIL PROTECTED]>, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> my "[EMAIL PROTECTED]" is lost in there. If it appears on the first line, it matches my regexp : color header red black "To:.*myoldlogin\@myoldaddress.com" Yours : color header red black "~C myoldlogin\@myoldaddress.com" never matches... Is it me, because it works exactly this way on your side, or are there any subtle difference that might be the reason for our differing experiences ? Flavien. -- any new sendmail hole I have to fix before going on vacations? -- Seen on #Linux
Re: color depending on To:
* On Sun, 28 Apr 2002, Flavien wrote: > I have som old addresses that some people still have in their > address-books. I'd like to spot these people by colorizing the headers > when matching one of those addresses. It works pretty well with : > > color header red black 'To:.*myoldlogin\@myoldaddress\.com' I use ~C for this and it seems to work fine, even when the address isn't on the first line of the To: header. Try this: color header red black "~C myoldlogin\@myoldaddress\.com" -- John
OT: IMAP2IMAP Synchronization -- giving up
Hi, I have created alpha version of the Python script for synchronization of two IMAP servers (it need to be debugged and completed, if necessary). However, I have today repented for spending too much time with this as thing, which I am not to do. Therefore, I have upload it to http://www.volny.cz/cepls/ps-pdf/iis.py (there is also iis.py,v in the same location, if you want RCS history) and I am giving up on its further development. If anybody wants to take over, she is certainly welcome. Have a nice day Matej -- Matej Cepl, [EMAIL PROTECTED] 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 The politician attempts to remedy the evil by increasing the very thing that caused the evil in the first place: legal plunder. -- Frederick Bastiat
Re: color depending on To:
Hi, * Flavien [04/28/02 17:36:10 CEST] wrote: > I have som old addresses that some people still have in their > address-books. I'd like to spot these people by colorizing the headers > when matching one of those addresses. It works pretty well with : > color header red black 'To:.*myoldlogin\@myoldaddress\.com' Hmm, you don't need to single quote it since it doesn't contain spaces. > However, when the mail is a "group-mail", from people not > knowing about BCC, the list if recipient can be quite large, and I > usually do not appear on the same line as the 'To:'. I've tried : > color header red black '.*myoldlogin\@myoldaddress\.com' > But as you can guess because I ask, it does not work as I expected > it to. First of all, you can combine these two: color header red black (To|C[Cc])?:.*oldaddress If something like that doesn't work, I can't help because: color header white black ^Subject: also works for long subjects which were split up to multiple lines. Cheers, Rocco. msg27712/pgp0.pgp Description: PGP signature
colorize collapsed threads with new messages
Hi! Is it possible to colorize the visible messages of collapsed threads if the threads contain one or more new messages? -Andre
Re: [OT] Only allow mail from selected addresses
Shawn, et al -- ...and then Shawn McMahon said... % .. % Whitelisting is horribly complicated to get right, and if you get it Agreed. % wrong, it's guaranteed to bounce legitimate mail. Well, only if you also set it up to dump everything instead of retaining the last vestige of sensibility and dumping messages that don't pass into a folder instead of the bit bucket... % % % -- % Shawn McMahon| McMahon's Laws of Linux support: % http://www.eiv.com | 1) There's more than one way to do it % AIM: spmcmahonfedex, smcmahoneiv | 2) Somebody thinks your way is wrong 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! msg27710/pgp0.pgp Description: PGP signature
Re: color depending on To:
* Flavien <[EMAIL PROTECTED]> [2002-04-28 17.36 +0200]: > Hello, Hi. > I have som old addresses that some people still have in their > address-books. I'd like to spot these people by colorizing the headers > when matching one of those addresses. It works pretty well with : [...snip...] I did some testing, and I couldn't make it happen. Maybe some regex-guru knows, but in the meantime, how about limiting? Maybe '~C expr' (to or cc'ed to expr) or '~h expr' (expr in headers)? Sure, these messages won't stand out when you're reading messages, but at least you can check for your outdated address. HTH -- Martin Karlsson -- 0x9C924660 msg27709/pgp0.pgp Description: PGP signature
Re: [OT] Only allow mail from selected addresses
[EMAIL PROTECTED] wrote: > Maybe this is more of a procmail or fetchmail or spamassassin question. > I'm running spamassassin on all mail to my private address. It catches > 95% of all spam. I'm really quite impressed. However to rid my private > inbox of that last 5% of spam I'd like to only accept messages from a > list of addresses, maybe including mail that has made it into my inbox > on previous occasions and addresses of people I've sent stuff to. > > Any ideas on how to accomplish this? i think you want: http://software.libertine.org/tmda/ -- Will Yardley input: william < @ hq . newdream . net . >
Re: mutt macro expansions
On Sun, Apr 28, 2002 at 11:25:51AM +0200, Nicolas Rachinsky wrote: [ Snip. ] > What's the output of ":set ?delete"? I think you have it set to > ask-... and if there are messages to delete your macro is asked, and > then the !isy is taken as answer to the question, and everything goes > wrong. > > Try, if it works with delete set to yes. That was exactly it. Setting delete=yes smoothed out the macro action and allows the macros derived from the isync examples to work as intended. Thank you for the help. --Shannon.
color depending on To:
Hello, I have som old addresses that some people still have in their address-books. I'd like to spot these people by colorizing the headers when matching one of those addresses. It works pretty well with : color header red black 'To:.*myoldlogin\@myoldaddress\.com' However, when the mail is a "group-mail", from people not knowing about BCC, the list if recipient can be quite large, and I usually do not appear on the same line as the 'To:'. I've tried : color header red black '.*myoldlogin\@myoldaddress\.com' But as you can guess because I ask, it does not work as I expected it to. Any advice welcome, Thanks, Flavien. -- *** PUBLIC flooding detected from erikyyy THAT's an erik, pholx ;) -- Seen on #LinuxGER
Re: [OT] Only allow mail from selected addresses
begin [EMAIL PROTECTED] quotation: > 95% of all spam. I'm really quite impressed. However to rid my private > inbox of that last 5% of spam I'd like to only accept messages from a > list of addresses, maybe including mail that has made it into my inbox > on previous occasions and addresses of people I've sent stuff to. > > Any ideas on how to accomplish this? Yes; with procmail, or with your MTA's configuration. I think it's a really bad idea, however; how will mail "make it into your inbox on previous occasions" any longer? What about mailing lists? What if it's somebody at your ISP sending you notification that you must engage in some action or lose your account? Whitelisting is horribly complicated to get right, and if you get it wrong, it's guaranteed to bounce legitimate mail. -- Shawn McMahon| McMahon's Laws of Linux support: http://www.eiv.com | 1) There's more than one way to do it AIM: spmcmahonfedex, smcmahoneiv | 2) Somebody thinks your way is wrong msg27705/pgp0.pgp Description: PGP signature
Re: [OT] Only allow mail from selected addresses
Hi, * [EMAIL PROTECTED] [04/28/02 14:47:22 CEST] wrote: > Maybe this is more of a procmail or fetchmail or spamassassin question. Absolutely. > I'm running spamassassin on all mail to my private address. It catches > 95% of all spam. I'm really quite impressed. However to rid my private > inbox of that last 5% of spam I'd like to only accept messages from a > list of addresses, maybe including mail that has made it into my inbox > on previous occasions and addresses of people I've sent stuff to. There's no automation that I know. But, to present a mechanism for mutt, you could use a folder-hook setting a limit for your inbox. In the pattern for limit you would have to specify a whitelist of addresses not affected. You'll see that with every message making it through, you'll have to adjust your rules. So, it's better to to not do this in mutt but outside. Cheers, Rocco. msg27704/pgp0.pgp Description: PGP signature
Re: adding Sender:
Hi, * David T-G [04/28/02 15:28:12 CEST] wrote: > Volker -- > ...and then V K said... > % > % I have set edit_headers. Why does mutt not add a Sender: header line > % when I add that to the headers in the editor? It works with other > I vaguely recall this coming up before, perhaps with Sender: or perhaps > with User-Agent: or perhaps something else. A quick search through the > archives out to turn it up. Yes. > IIRC, mutt will step on headers that it expects to write for itself, and > that's unfortunately coded in rather than controlled by a variable. The 'Sender:' header should contain the user at the local machine. So it makes sence to let mutt figure it out itself. Cheers, Rocco. msg27703/pgp0.pgp Description: PGP signature
Re: adding Sender:
Volker -- ...and then V K said... % % I have set edit_headers. Why does mutt not add a Sender: header line % when I add that to the headers in the editor? It works with other I vaguely recall this coming up before, perhaps with Sender: or perhaps with User-Agent: or perhaps something else. A quick search through the archives out to turn it up. IIRC, mutt will step on headers that it expects to write for itself, and that's unfortunately coded in rather than controlled by a variable. 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! msg27702/pgp0.pgp Description: PGP signature
Re: [OT] Only allow mail from selected addresses
m2 -- ...and then [EMAIL PROTECTED] said... % % Maybe this is more of a procmail or fetchmail or spamassassin question. Yep. % I'm running spamassassin on all mail to my private address. It catches ... % on previous occasions and addresses of people I've sent stuff to. I'd use the SA whitelist or an lbdb query as the second-to-last stop in your procmail rules to dump into your inbox and then dump the last bits into a spam folder. % % Any ideas on how to accomplish this? You certainly ought to try the SA or perhaps procmail lists for better ideas... % % % -- % o polite % http://plusseven.com/gpg/ 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! msg27701/pgp0.pgp Description: PGP signature
[OT] Only allow mail from selected addresses
Maybe this is more of a procmail or fetchmail or spamassassin question. I'm running spamassassin on all mail to my private address. It catches 95% of all spam. I'm really quite impressed. However to rid my private inbox of that last 5% of spam I'd like to only accept messages from a list of addresses, maybe including mail that has made it into my inbox on previous occasions and addresses of people I've sent stuff to. Any ideas on how to accomplish this? -- o polite http://plusseven.com/gpg/
Re: mutt macro expansions
* Shannon Prickett <[EMAIL PROTECTED]> [2002-04-28 01:46:56 -0700]: > I'm using the isync package from Debian [0.7-1] and mutt from Debian > [1.3.28-2] and attempting to use the folder-hooks from > http://www.cs.hmc.edu/~me/isync/ without success. > > Here are some examples that don't work for me: > > folder-hook '!' 'macro index $ "!isync -aC\n"' > > folder-hook '!' "macro index $ 'isync -aC'" > > The intention is to macro the $ key to flag the messages as deleted, and > update all of my listed mailboxes. If there are no deleted messages in > the folder, no problem. It will fetch new ones. But as soon as I > delete a message and try to use the $-macro, mutt tells me: > > /home/binder/Mail/manjusri/aC is not a mailbox. > > where /home/binder/Mail/manjusri/ is my designated spoolfile. > I suspect this is a case of something being expanded in a way which I'm > not expecting. What's the output of ":set ?delete"? I think you have it set to ask-... and if there are messages to delete your macro is asked, and then the !isy is taken as answer to the question, and everything goes wrong. Try, if it works with delete set to yes. Nicolas
mutt macro expansions
I'm using the isync package from Debian [0.7-1] and mutt from Debian [1.3.28-2] and attempting to use the folder-hooks from http://www.cs.hmc.edu/~me/isync/ without success. Here are some examples that don't work for me: folder-hook '!' 'macro index $ "!isync -aC\n"' folder-hook '!' "macro index $ 'isync -aC'" The intention is to macro the $ key to flag the messages as deleted, and update all of my listed mailboxes. If there are no deleted messages in the folder, no problem. It will fetch new ones. But as soon as I delete a message and try to use the $-macro, mutt tells me: /home/binder/Mail/manjusri/aC is not a mailbox. where /home/binder/Mail/manjusri/ is my designated spoolfile. I suspect this is a case of something being expanded in a way which I'm not expecting. I finally found a workaround, which is to leave $ defaulted to and use this folder-hook, instead: folder-hook '!' "macro index G \ 'isync -aC'" I suppose it's no great hardship to use $ followed by G to sync the deleted messages to the mailbox and subsequently call isync to purge them, but I'm confused as to why the notation is expanding in the ways it seems to be. Can someone point me at a source for information about quoting, expansion and macros in mutt? I've found some useful bits in the manual but nothing seems to explain what I'm seeing and all the Google searches I can think of turn up old bug reports. --Shannon.
