Selecting headers to delete on pop3 server
Hello, I have mutt 1.0-i happily running on a RH6.2 box, but haven't figured yet how to do what follows. When ones subscribes to a mailing list, he or she is only interested in a (small) part of the threads discussed. For example, I am subscribed to mutt-users and have (currently) no IMAP. What I would like to do is: 1) Whenever I see the first message of an uninteresting thread, I tell mutt that I'm not interested in it. 2) mutt writes this to some log file 3) Next time I dial up, a script reads this log file, connects to the pop server and deletes everything which is FROM the mailing list AND with that header. 4) only at this point fetchmail starts and downloads only what might be interesting 5) the log file is cleaned every few days. I know how to do points 3,4,5, but how do I tell mutt to create this log file? Has somebody already done this? Any help is appreciated! Marco Fioretti
Re: Displaying foreign characters..
Mark, I have been trying to solve this problem from a long time ago and at the end I got it in this way: I set LC_ALL=en_US.ISO-8859-1 and installed locales package. It works! Let me know. Bye. Roberto. On Fri, Feb 02, 2001 at 06:30:19PM +1100 or thereabouts, Mark Triggs wrote: Hey all, When I receive mail containing characters with accent marks, I'm tending to get gibber like '\204' and the like.. A friend and I have been borking around with the various locale types trying to get these characters to display correctly, but are having no luck.. We've tried using the charset option, in .muttrc, and also played around with the LC_CTYPE and LANG environment variables, but none of these seem to have any effect.. Can anyone shed some light on this? Thanks Mark -- [EMAIL PROTECTED] || [EMAIL PROTECTED] Fingerprint: 1024D/3A2EC93E 901A DCF2 C894 7115 BFFF D2B0 50E1 989F 3A2E C93E
Re: Selecting headers to delete on pop3 server
On Fri, Feb 02, 2001 at 09:26:02AM +0100 or thereabouts, Marco Fioretti wrote: Hello, I have mutt 1.0-i happily running on a RH6.2 box, but haven't figured yet how to do what follows. When ones subscribes to a mailing list, he or she is only interested in a (small) part of the threads discussed. For example, I am subscribed to mutt-users and have (currently) no IMAP. What I would like to do is: 1) Whenever I see the first message of an uninteresting thread, I tell mutt that I'm not interested in it. 2) mutt writes this to some log file It occurs to me that you could use some kind of send or save hook to run a script which greps the from line into a log file. Perhaps something like forward to bitbucket@localhost and use a send hook on that address 3) Next time I dial up, a script reads this log file, connects to the pop server and deletes everything which is FROM the mailing list AND with that header. 4) only at this point fetchmail starts and downloads only what might be interesting 5) the log file is cleaned every few days. I know how to do points 3,4,5, but how do I tell mutt to create this log file? Has somebody already done this? Post the rest would you? -- Conor Daly Met Eireann, Glasnevin Hill, Dublin 9, Ireland Ph +353 1 8064217 Fax +353 1 8064275 9:59am up 1:11, 4 users, load average: 0.00, 0.10, 0.10
Re: Move mailfolders bigger than X mails
Bostjan Muller ([EMAIL PROTECTED]) said something to this effect on 02/02/2001: Hi! I am subscribed to quite a few mailing lists, and every of those mailing lists has it's procmail rule and is distributed to it's maibox. I view my mail through an imap server, since I view it from random locations/machines, and at the end of the month there are more than 5000 emails in some of those mailboxes, which slows down my imap server considerably. I was wondering if there is a way that some program would check when there are more than let's say 2000 mails in an mailbox and than move those mails to some other file and create an empty file where the last mailbox was. And then it would do the same for the next 2000 mails, except it wouldn't move them but append them. I use procmail to sort messages based on the date as well as the list, for example: :0 * ^Mailing-List:.*modperl.*@apache.org modperl-`date +"%m-%Y"` This puts this month's mail from [EMAIL PROTECTED] into =modperl-02-2001. Then, I have a cron job for the first of each month: 0 1 1 * * (cd /home/darren/mail; ln -s modperl-`date +"%m-%Y"` modperl) So that the mailbox =modperl always points to the current month's mailbox; older mailboxes are still available specifically. Finally, I have =modperl in my mailboxes list. (darren) -- You can put a man through school, but you cannot make him think. -- Ben Harper
Re: Selecting headers to delete on pop3 server
Conor Daly wrote: ... 1) Whenever I see the first message of an uninteresting thread, I tell mutt that I'm not interested in it. 2) mutt writes this to some log file It occurs to me that you could use some kind of send or save hook to run a script which greps the from line into a log file. Perhaps something like forward to bitbucket@localhost and use a send hook on that address My first idea had been to save all these "to-be-deleted" messages into a trash folder, and have the external script filtering ^Subject and ^From lines out of the folder. If possible however, I would like to implement something that doesn't require extra resources (i.e. extra mailboxes for complete messages or bogus accounts) What would REALLY do the trick is some "shell excape" which just makes mutt do the following: echo subject_and_From_header some_file I did read the whole manual some time ago, but I can't remember any "shell-excape", i.e. something that make mutt execute shell commands with dynamic arguments. Is something like that available? Post the rest would you? I found several pop clients written in perl that can be easily modified to fetch the headers only from the pop server, and send "delete" commands when some header matches a certain pattern. I don't have any URL here, but a search on CPAN would find them. Another source for this is the example code of the O'Reilly Book "Advanced Perl Programming", available on their ftp site: that book is what gave me the idea. Marco
Re: Selecting headers to delete on pop3 server
Marco Fioretti wrote:
I found several pop clients written in perl that can be easily
modified to fetch the headers only from the pop server, and send
"delete" commands when some header matches a certain pattern.
I don't have any URL here, but a search on CPAN would find them.
Another source for this is the example code of the O'Reilly Book
"Advanced Perl Programming", available on their ftp site: that
book is what gave me the idea.
Marco
There it goes (there are many others like this on the net..)
@rem = '-*- Perl -*-';
@rem = '
@echo off
c:\perl\bin\perl f:/local/bin/checkmail.cmd %1 %2 %3 %4 %5 %6 %7 %8 %9
goto endofperl
';
# This perl script can be used to pre-scan your POP mailbox on your ISP
to
# delete any mail with objectionable headers before you go to the
trouble of
# downloading the whole message. It only reads the headers, and can be
# customized to look for any patterns of interest.
# To use it you need the latest and greatest perl version 5.004 (soon to
be
# released) and the Net::POP3 and Mail::Header optional modules
installed.
# (Instructions for how to get perl won't fit here - see www.perl.com
for
# lots of good info). You will need to edit the line after @echo off
(above)
# to contain the full path name of perl and where you put this script.
# You also need to customize a lot of stuff in this script, including
(but
# probably not limted to):
#
# * The lines up at the top with the absolute path names of perl and
this
# script in them.
#
# * The mail server and password information below.
#
# * The regular expressions and algorithms used to actually check the
# mail headers for what you want to classify as spam and delete.
use Net::POP3;
use Mail::Header;
# Configure the interesting parameters here
#
$postoffice=''; # fill in this with something like postoffice.isp.com
$user=''; # fill this in with your mail user name
$password=''; # fill this in with your mail server password
$verbose=1;
# Call scan_header with the Mail::Header object as the first argument
and
# the message size as the 2nd arg. If it returns a value, then that
value is
# the reason the mail should be deleted. If it returns undef, the mail
is
# left intact;
#
# NOTE: Edit this routine to put in your very own reasons for deleteing
# mail.
#
sub scan_header {
my $head, @rec, $r, @tags, $t, $msgsize;
($head, $msgsize) = @_;
if ($msgsize 10) {
return "Message bigger than 100K, probable mailbomb";
}
@tags = $head-tags();
$goodguy = 0;
foreach $t (@tags) {
if ($t=~/^X-Advertisement/i) {
return "Found X-Advertisement header";
}
if ($goodguy == 0) {
# If this mail isn't explicity being sent to me or being sent
on
# one of the mailing lists I know about or forwarded from work,
etc
# then it is highly suspicious...
if (($t=~/From/i) || ($t=~/To/i) || ($t=~/Cc/i)) {
@rec = $head-get($t);
foreach $r (@rec) {
# Fill in tests to check for your mail address, the
# mail addresses associated with any mailing lists you
# are on, etc. These are only examples...
if (($r=~/Tom\.Horsley\@worldnet\.att\.net/i) ||
($r=~/kermit\@columbia\.edu/i) ||
($r=~/fdc\@watsun\.cc\.columbia\.edu/i) ||
($r=~/ntemacs\-users\@cs\.washington\.edu/i)) {
$goodguy = 1;
}
}
}
}
# If any of these standard goons show up in any headers, trash the
# sucker...
if (($t=~/From/i) || ($t=~/Received/i) || ($t=~/Reply/i) ||
($t=~/Sender/i) || ($t=~/^X-/) || ($t=~/^To/i) ||
($t=~/Comments/i)) {
@rec = $head-get($t);
foreach $r (@rec) {
# As above, replace any of these (or just add more) with
# your own list of bad guys.
if ($r=~/cyberpromo\.com/i) {
return "Found cyberpromo.com in $t header";
}
if ($r=~/savetrees\.com/i) {
return "Found savetrees\.com in $t header";
}
if ($r=~/earthlink\.net/i) {
return "Found earthlink\.net in $t header";
}
if ($r=~/\@shoppingplanet\.com/i) {
return "Found \@shoppingplanet.com in $t header";
}
}
}
}
# These subjects were repeated over and over at one time, so I stuck
# in an explicit check for them...
@rec = $head-get('Subject');
foreach $r (@rec) {
if ($r=~/Free Fax/i) {
return "Found \"Free Fax\" in Subject header";
}
if ($r=~/credit limit/i) {
return "Found \"credit limit\" in Subject header";
}
}
if ($goodguy == 0) {
return "No good guys in any From: To: or Cc: header";
}
return undef;
}
# Call delete_spam with postoffice, user, password to be scanned.
#
sub delete_spam {
Re: Selecting headers to delete on pop3 server
On Fri, Feb 02, 2001 at 01:53:03PM +0100 or thereabouts, Marco Fioretti wrote: Conor Daly wrote: ... 1) Whenever I see the first message of an uninteresting thread, I tell mutt that I'm not interested in it. 2) mutt writes this to some log file It occurs to me that you could use some kind of send or save hook to run a script which greps the from line into a log file. Perhaps something like forward to bitbucket@localhost and use a send hook on that address My first idea had been to save all these "to-be-deleted" messages into a trash folder, and have the external script filtering ^Subject and ^From lines out of the folder. If possible however, I would like to implement something that doesn't require extra resources (i.e. extra mailboxes for complete messages or bogus accounts) What would REALLY do the trick is some "shell excape" which just makes mutt do the following: echo subject_and_From_header some_file I did read the whole manual some time ago, but I can't remember any "shell-excape", i.e. something that make mutt execute shell commands with dynamic arguments. Is something like that available? No time now, will think... -- Conor Daly Met Eireann, Glasnevin Hill, Dublin 9, Ireland Ph +353 1 8064217 Fax +353 1 8064275 1:20pm up 4:32, 7 users, load average: 0.01, 0.05, 0.04
Re: Move mailfolders bigger than X mails
* On 02-02-01 at 13:34 darren chamberlain ([EMAIL PROTECTED]) wrote: +Here quoted text begins+ I use procmail to sort messages based on the date as well as the list, for example: :0 * ^Mailing-List:.*modperl.*@apache.org modperl-`date +"%m-%Y"` This puts this month's mail from [EMAIL PROTECTED] into =modperl-02-2001. Then, I have a cron job for the first of each month: 0 1 1 * * (cd /home/darren/mail; ln -s modperl-`date +"%m-%Y"` modperl) So that the mailbox =modperl always points to the current month's mailbox; older mailboxes are still available specifically. Finally, I have =modperl in my mailboxes list. (darren) -- You can put a man through school, but you cannot make him think. -- Ben Harper +and here the quote ends+ I have a procmail rule that does that witout using cron, but that is still too much monthly mail for me, I need to split the mail folders, when thethe amount of mails in them reaches certain number. Bostjan -- Botjan Mller [NEONATUS], [EMAIL PROTECTED], http://neonatus.net/~neonatus For my PGP key finger: [EMAIL PROTECTED], RSA id: 0x90178DBD, ICQ #:7506644 Celular: +386(0)41243189, Powered by Debian GNU/LiNUX , Student of VFUL "Its not a bug...just think of it as a new undocumented feature" - M$ TechSupport
Re: Selecting headers to delete on pop3 server
What would REALLY do the trick is some "shell excape" which just makes mutt do the following: echo subject_and_From_header some_file I did read the whole manual some time ago, but I can't remember any "shell-excape", i.e. something that make mutt execute shell commands with dynamic arguments. Is something like that available? No time now, will think... Idea: we may achieve the desired effect ( i.e. passing information to some external program) if it were possible to define (within mutt or from the prompt) a mailbox which is actually a pipe, right? As in set MAIL_TO_BE_DISCARDED = "| my_program.pl" Maybe named pipes would do it, what do you think? Marco
Re: How to show attatchments
On Wed, Jan 31, 2001 at 02:16:13PM +0100, smund Skjveland wrote: I've set up my .mailcap so that when I try to view an shudder HTML mail, it is passed to lynx which parses it and returns formatted text. This is the entry: text/html; lynx -dump -force_html %s; copiousoutput; What I'd like to do is to have this shown like a normal mail, so that mutt has lynx parse the mail automatically instead of having to view the HTML attachment separately. Anyone? -- smund Skjveland ([EMAIL PROTECTED]) Add to your .muttrc: auto_view text/html -- Duncan Watson Application Engineer [For best reading adjust your window width to the length of this line -djw] 123456789012345678901234567890123456789012345678901234567890123456789012345
Re: Mutt and IMAP
On Thu Feb 1 12:52:35 2001, Brendan Cully wrote:
1) How do I browse an IMAP folder if I don't want to specify it as my
default mail directory ? If I try to open {user@server}INBOX or simply
{user@server}, I see the messages, but I can't browse the folders. I can
browse the folders if I specify it as my default mail dir (set
folder=...), but that's not what I want because I already use a local
mail folder with a lot of mailboxes in it.
You could try tab-completing it - type {user@server}INBOXtab. you
might need an extra tab there... not the best, I know.
Okay, it works. But now the problem is : once I moved to another folder,
I can't move back to the original. The main part of the mails are
directly in the INBOX folder (we're a helpdesk - don't ask me why they
don't use a TRUE helpdesk software...) and, when I switch to a subfolder
of INBOX, I can't get back to INBOX : pressing Enter will display the
subfolders list, and pressing SPACE will produce an error ("Error trying
to visualize file" - it's not the exact message, I translate from
french).
Any idea ?
Thanks in advance.
--
Raphaël HALIMI
Re: Selecting headers to delete on pop3 server
At 13:53 +0100 02 Feb 2001, Marco Fioretti [EMAIL PROTECTED] wrote: What would REALLY do the trick is some "shell excape" which just makes mutt do the following: echo subject_and_From_header some_file macro pager X '| formail -XFrom: -XSubject: -XMessage-ID: some_file\n' macro index X '| formail -XFrom: -XSubject: -XMessage-ID: some_file\n' -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ One good reason why computers can do more work than people is that they never have to stop and answer the phone.
Re: Selecting headers to delete on pop3 server
At 15:27 -0600 02 Feb 2001, I wrote: macro pager X '| formail -XFrom: -XSubject: -XMessage-ID: some_file\n' macro index X '| formail -XFrom: -XSubject: -XMessage-ID: some_file\n' Oops, need to use double quotes not single qoutes there: macro pager X "| formail -XFrom: -XSubject: -XMessage-ID: some_file\n" macro index X "| formail -XFrom: -XSubject: -XMessage-ID: some_file\n" -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ Standards are crucial. And the best thing about standards is: there are so _many_ to choose from!
Re: Selecting headers to delete on pop3 server
On Fri, Feb 02, 2001 at 03:56:45PM +0100 or so it is rumoured hereabouts, Marco Fioretti thought: What would REALLY do the trick is some "shell excape" which just makes mutt do the following: echo subject_and_From_header some_file I did read the whole manual some time ago, but I can't remember any "shell-excape", i.e. something that make mutt execute shell commands with dynamic arguments. Is something like that available? No time now, will think... Idea: we may achieve the desired effect ( i.e. passing information to some external program) if it were possible to define (within mutt or from the prompt) a mailbox which is actually a pipe, right? As in set MAIL_TO_BE_DISCARDED = "| my_program.pl" Maybe named pipes would do it, what do you think? Marco I'm not familiar enough with the mutt "set" capabilities to comment on that. How do you get the message into the pipe? "save" perhaps? Did some thinking though... What I had been thinking about was to do something with "set editor" and use a send-hook and macro to _forward_ the unwanted message to the filtering script. Something like: macro index escD forward-messagebitbucket@localhostenter with send-hook bitbucket set editor="~/bin/maildump" Now, using that, the ~/bin/maildump looks like #!/bin/bash maildump ### # get "From" and "Subject" lines to use for filtering from pop server # We're masquerading as an editor here for mutt so we get the message # filename on $1. That's kinda handy since we don't need to worry about # cat or anything. grep -A10 - Forwarded message $1 /tmp/maildump$$.tmp 2/dev/null grep From /tmp/maildump$$.tmp /tmp/dump$$.tmp grep Subject /tmp/maildump$$.tmp /tmp/dump$$.tmp # command to incorporate /tmp/dump$$.tmp into the pop3 filter script # You already know how to do this don't you? rm -f /tmp/maildump$$.tmp /tmp/dump$$.tmp exit 0 end maildump ## Once this returns, mutt sees that the temporary file it used for the message hasn't changed and just "aborts unmodified message" which is just the desired effect. Since forwarding includes the original incoming "From" and "Subject" headers we'll pick them up just after the "Forwarded message" line. My problem here has been not knowing *quite* how to set the send-hook correctly. With the example quoted above, the editor variable gets left as "~/bin/maildump" for ordinary mails but if I include a default send-hook for "set editor", it gets used even for "bitbucket" mails which should trigger the "bitbucket" send-hook. I used send-hook . set editor="vim +\'set tw=74\' +\'/^$\'" send-hook bitbucket set editor="~/bin/maildump" but the default hook gets used for all mails. I thought I would solve it by using the following: send-hook !bitbucket@localhost set editor="vim +\'set tw=74\' +\'/^$\'" send-hook bitbucket@localhost set editor="~/bin/maildump" but that wouldn't behave correctly with the "set tw=74" for the default editor command so I used: send-hook !bitbucket@localhost source ~/.muttrc which contains (among other stuff): set editor="vim +'set tw=74' +'/^$'" as the default editor. A bit crude and kludgey but it works. ### So, in summary, ~/.muttrc contains the following: set editor="vim +'set tw=74' +'/^$'" send-hook !bitbucket@localhost source ~/.muttrc send-hook bitbucket@localhost set editor="~/bin/maildump" macro index escD forward-messagebitbucket@localhostenter macro pager escD forward-messagebitbucket@localhostenter using escD on a message will "forward" the message to ~/bin/maildump for processing. This will extract the "From" and "Subject" lines and push them to a .conf file for the pop3 filter script and will then return unmodified to mutt which will just discard the "forwarded" message. The exact method of extraction of the necessary info is left as an exercise for the reader (Marco :-) who will then post the full set of scripts (won't you?) 'cos I don't know any perl to go hacking the pop filter. feature request for perl pop filter A nice method to check for message size and get headers only but leave the message on the server for later review. OH! Could you get the "body" and leave the attachments on the server? Probably not. /feature request for perl pop filter Howsat? Conor -- Conor Daly [EMAIL PROTECTED] Domestic Sysadmin :-) - faenor.cod.ie 9:21pm up 102 days, 3:50, 0 users, load average: 0.08, 0.02, 0.01 Hobbiton.cod.ie 9:19pm up 7 days, 11:08, 1 user, load average: 0.01, 0.00, 0.00
Re: Selecting headers to delete on pop3 server
On Fri, Feb 02, 2001 at 03:30:54PM -0600 or so it is rumoured hereabouts, Aaron Schrab thought: At 15:27 -0600 02 Feb 2001, I wrote: macro pager X '| formail -XFrom: -XSubject: -XMessage-ID: some_file\n' macro index X '| formail -XFrom: -XSubject: -XMessage-ID: some_file\n' Oops, need to use double quotes not single qoutes there: macro pager X "| formail -XFrom: -XSubject: -XMessage-ID: some_file\n" macro index X "| formail -XFrom: -XSubject: -XMessage-ID: some_file\n" Now you're just getting fancy on me! :-) -- Conor Daly [EMAIL PROTECTED] Domestic Sysadmin :-) - faenor.cod.ie 11:05pm up 102 days, 5:34, 1 user, load average: 0.00, 0.01, 0.02 Hobbiton.cod.ie 11:03pm up 7 days, 12:52, 2 users, load average: 0.12, 0.05, 0.01
mutt.octet.filter
Hi, In reading attachments of type: application/octet-stream with .pdf extension i did the following: 1. downloaded the mutt.octet.filter by Dave Pearson and put in my home directory. 2. Created ~/.muttrc and put this line in it: auto_view application/octet-stream 3. in /etc/mailcap i added the line "application/octet-stream; mutt.octet.filter %s; copiousoutput". In mutt when trying to see attachments of type: .pdf i get: command: mutt.octet.filter h: mutt.octet.filter: command not found file.pdf How do i fix this error?. J _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: mutt.octet.filter
On Sat, Feb 03, 2001 at 05:34:25AM -, Jim M. wrote: Hi, In reading attachments of type: application/octet-stream with .pdf extension i did the following: 1. downloaded the mutt.octet.filter by Dave Pearson and put in my home directory. 2. Created ~/.muttrc and put this line in it: auto_view application/octet-stream 3. in /etc/mailcap i added the line "application/octet-stream; mutt.octet.filter %s; copiousoutput". In mutt when trying to see attachments of type: .pdf i get: command: mutt.octet.filter h: mutt.octet.filter: command not found file.pdf How do i fix this error?. You need to put mutt.octet.filter in a directory that is in your PATH variable, or refer to it in your mailcap by its full path name. -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications Product Generation Unit | Spokane, Washington, USA
permission denied
Hi, I entered the "application/octet-stream; /usr/local/bin/mutt.octet.stream %s; copiousoutput" in my /etc/mailcap file. I get the error: permission denied. In /usr/local/bin, I have: -rw-r--r-- 1 userid userid .. . mutt.octet.stream How do i fix this?. Thanx, J _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: permission denied
On Sat, Feb 03, 2001 at 06:25:38AM -, Jim M. wrote: Hi, I entered the "application/octet-stream; /usr/local/bin/mutt.octet.stream %s; copiousoutput" in my /etc/mailcap file. I get the error: permission denied. In /usr/local/bin, I have: -rw-r--r-- 1 userid userid .. . mutt.octet.stream How do i fix this?. The short answer is, execute this command: chmod 755 /usr/local/bin/mutt.octet.stream (Are you sure that's not mutt.octet.filter?) A slightly longer answer is that you need to give users permission to execute that file. This done by changing the permissions, or the mode bits, of the file using the chmod (CHange MODe) command. The least significant 9 bits are composed of 3 groups of three bits each. Each group of three bits determines the Read, Write and eXecute permissions for a set of users: the file's owner (User), the file's Group, and Others. So, for example, 755 is an octal representation of these bits giving the owner read, write and execute permissions, and giving everyone else read and execute permissions. The 'ls -l' command would show these as "-rwxr-xr-x". Since this is pretty basic and important stuff to know when using a Unix system, I would recommend that you find a good introductory book on using Unix: Matt Welsh's "Running Linux" (3rd edition) would be a good choice. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications Product Generation Unit | Spokane, Washington, USA
Re: mutt.octet.filter
[mutt-dev removed to the reply list, this isn't a mutt development issue] On Sat, Feb 03, 2001 at 05:34:25AM -, Jim M. wrote: In mutt when trying to see attachments of type: .pdf i get: command: mutt.octet.filter Is mutt.octet.filter in your path? -- Dave Pearson: | mutt.octet.filter - autoview octet-streams http://www.davep.org/ | mutt.vcard.filter - autoview simple vcards Mutt: | muttrc2html - muttrc - HTML utility http://www.davep.org/mutt/ | muttrc.sl - Jed muttrc mode
