Re: procmail question
Gauthier -- ...and then [EMAIL PROTECTED] said... % On Sun, Jun 18, 2000 at 05:49:47PM -0700, Brian D. Winters wrote: % % Never, never, never filter a mailing list like mutt-users based on % To:, Cc:, From:, Subject:, Reply-To: or Mail-Followup-To: if you can % possibly help it. What happens the first time someone bcc's the list? % Think about it. % % Well, precisely, what happens ? Since the addressing of the list was done in bcc, the contents of which you can't see and which [theoretically] appear nowhere else, you won't see your filter trigger and the mail will fall through the intended rule to some other -- perhaps the bit bucket, for particularly fascist anti-spam configurations. :-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.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: procmail question
Virginie [ ML ]: defaults mda "formail -ds procmail" one can save one exec and much complexity using: mda "/usr/local/bin/procmail -t -f-" clemens
Re: procmail question
On Sun, Jun 18, 2000 at 05:49:47PM -0700, Brian D. Winters wrote: Never, never, never filter a mailing list like mutt-users based on To:, Cc:, From:, Subject:, Reply-To: or Mail-Followup-To: if you can possibly help it. What happens the first time someone bcc's the list? Think about it. Well, precisely, what happens ? Any reasonable mailing list server will add a header identifying the list. The most common header is Sender:, but I've also had to resort to Mailing-List:, X-Mailing-List, and Delivered-To:. In the case of mutt-users, the header I use is Sender:. That gives a rule like this: :0: * ^Sender: owner-mutt $MAILDIR/mutt I bet that rule will work a lot better for you than your current one. I'll try. Thank you for remind such basic and useful things. -- #=---=# " ^^ Gauthier Vandemoortele " | (_/°°-ç[EMAIL PROTECTED] | | | \_`-" | | )/@mmm|| Chée de Wavre, 135c| | \nn \nn B-1360 Perwez | | Belgique | " FOE-Belgium : http://www.ful.ac.be/hotes/amisterre | #=---=#
Re: procmail question
On Mon, Jun 19, 2000 at 07:46:42PM +0200, [EMAIL PROTECTED] wrote: On Sun, Jun 18, 2000 at 05:49:47PM -0700, Brian D. Winters wrote: Never, never, never filter a mailing list like mutt-users based on To:, Cc:, From:, Subject:, Reply-To: or Mail-Followup-To: if you can possibly help it. What happens the first time someone bcc's the list? Think about it. Well, precisely, what happens ? If they Bcc the list, then To, Cc, and From are almost certainly useless and it is very unlikely that they set MFT to something useful either. The other header that I listed is Reply-To. If you are relying on users to set Reply-To to include the list, you have the same problems as with the rest. The story with Reply-To is more complicated though, and is the reason why I qualified my statement with, "if you can possibly help it." Some mailing list software will rewrite the Reply-To on every message, assuming that the list subscribers are not competent enough to figure it out for themselves. (IMHO these servers are defective, since this sort of rewriting has drawbacks. As for user competence, I find that these sorts of lists typically have a high percentage of subscribers who are Windows users. ;) I am subscribed to a couple of these sorts of lists, and unfortunately I can't help but filter on Reply-To, since these servers don't add Sender or (X-)Mailing-List headers either. Reply-To isn't great, but it is still better than resorting to ^TO. Anyway, the end result is that the bcc'd message doesn't get filtered and ends up in your inbox rather than in your mutt box. Now, people probably shouldn't be bccing mailing lists, but why worry about it if there is a solution with no drawbacks which also doesn't rely on the competence of your peers? :) Oops, I almost forgot to mention why I object to filtering on Subject. That is almost as much philosophical as technical. Lists which add [list] to the subject typically do so because of whining from users who cannot filter except visually, cannot filter on arbitrary headers, or don't realize that other headers exist besides From, Date, To, Cc, and Subject. It should be clear from the recent thread about trying to match "Re: re: [list] Re: ..." for non-strict threading that list rewriting of Subject headers can cause problems. There are much better ways of marking list e-mail as such (see above and my previous post), and if your filter can't handle something of the form "Sender: owner-mutt" then you should get a better filter. If nothing else, the subject tag is a waste of screen space that could be used to show me more of the message's real subject. Brian
Procmail Question
I'm trying to set up mutt so mail from mutt-users goes into a mailbox named mutt. This is the filter I made for my .procmailrc. I'm posting this to see if it works and if it doesn't maybe someone would comment on the proper way to configure: :0: * ^From:.*mutt\..* mutt thanks -- dale "As I have always held it a crime to anticipate evils I will believe it a good comfortable road untill I am conpelled to beleive differently." [sic] William Clark of the Lewis Clark Expedition circa 1805
Re: Procmail Question
Dale Morris proclaimed on mutt-users that: :0: * ^From:.*mutt\..* mutt This will catch stuff from [EMAIL PROTECTED] (or whatever) as well :) Try this - #mutt :0: * (^Reply-To:.*|^TO_)mutt-users $MAILDIR/mutt -- Suresh Ramasubramanian + [EMAIL PROTECTED] "Amnesia used to be my favorite word, but then I forgot it."
Re: Procmail Question
Also, I recommend specifying the full path to your mutt folder, rather than just "mutt". In my .procmailrc I set FOLDERS to the appropriate path and use $FOLDERS as the base for all of my delivery recipes, but do whatever makes you happy there. Brian Will this work for the path? # Your Mail directory. _Not_ /var/spool/mail/username MAILDIR=$HOME/Mail thanks -- dale
Re: Procmail Question
On Sun, Jun 18, 2000 at 01:21:21AM -0700, Dale Morris wrote: I'm trying to set up mutt so mail from mutt-users goes into a mailbox named mutt. This is the filter I made for my .procmailrc. I'm posting this to see if it works and if it doesn't maybe someone would comment on the proper way to configure: :0: * ^From:.*mutt\..* mutt I'm first to admit I don't know anything about procmail,... but having said that, here's the procmail recipe I use for that: FORMAIL=/usr/bin/formail ... # mutt-users :0: * ^TOmutt-users | $FORMAIL -A"X-SpamBouncer: Mutt-Users" $HOME/Mail/mutt-users note, I'm using the "SpamBouncer" (another large procmail script) as a spam filter. This recipe adds a "X_SpamBouncer" header to the mail (which you prolly don't need to do), but it ends up in my mutt-users mailbox -- Fred Smith -- [EMAIL PROTECTED] "Not everyone who says to me, 'Lord, Lord,' will enter the kingdom of heaven, but only he who does the will of my Father who is in heaven." -- Matthew 7:21 (niv) -
procmail question
I'm trying to get procmail working on my rh 6.2 system, after reading the
manual and banging my head on the keyboard for several hours, I'm
thoroughly confused--a comfortable state, for me and linux.. my question
is:
I've setup procmail as follows, MAILDIR=$HOME/Mail which is there in my
home directory and includes all the mailboxes I'm saving my mail to. When
I open mutt it reads the mail in /var/spool/mail/dlm. the result is mail
isn't being transferred to my MAILDIR=$HOME/Mail directory. Is this
correct?
What I want to do is have procmail transfer mutt-users messages
/var/spool/mail/dlm to /home/dlm/Mail/mutt, correct? I have a mutt mbox,
and here's how I've setup the .procmailrc recipe:
#mutt
:0:
* (^Reply-To:.*|^TO_)mutt-users
$MAILDIR/mutt
But it doesn't work. I will attach my .procmailrc and .muttrc files if
someone cares to take a look.
Thankyou
-- dale
#
# System configuration file for Mutt
#
ignore received content- mime-version status x-status message-id sender
ignore references return-path lines
#Key mapping
bind pager up previous-line
bind pager downnext-line
bind index \Cu previous-page
bind index \Cd next-page
bind index right collapse-thread
bind index left collapse-thread
# Variables
set askcc
set attribution = "At %{%d} %{%B}, %{%Y} %n wrote:"
set copy = yes
set nobeep
set editor = "pico -t -n60 -z"
set record = "~/Mail/sent"
set signature = "~/.signature"
set status_on_top
set sort = threads
#set pgp_default_version=pgp5
set fast_reply
# SET PAGer_index_lines=`(stty size ; echo s0 5 / 1 + p) | dc`
# Tell mutt about mailboxes
mailboxes = !
mailboxes =anndyck
mailboxes =backup
mailboxes =craptalk
mailboxes =hhenry
mailboxes =mutt
mailboxes =muttlinux
mailboxes =premium1ehm
mailboxes =saved_mail
mailboxes =savedmail
mailboxes =sent
mailboxes =tracy
set quote_regexp="^[ \t]*[a-zA-Z\.]*" # Default: "^[|#:}] "
set status_format="%v: %f %M/%m msgs, %n new %?t tagged, ?%l bytes]"
set index_format="%4C %Z %{%b %d} %-15.15L %3M (%4l) %s"
set reply_regexp="^(re|sv):[ \t]*"
# imitate the old search-body function
macro index \eb '/~b '
# simluate the old url menu
macro index \cb |urlview\n
macro pager \cb |urlview\n
#
# Header weeding (conservative version): explicitly ignore any boring header
#
ignore Received Message-ID Status Content- Resent- Precedence References
ignore In-Reply-To Return-Path Return-Receipt-To Mailer X400
ignore Mime-Version Sender Originator
ignore X-Status X-Loop X-Mailing-List X-Listprocessor X-Face
ignore X-Received X-Mailer X-Envelope-To X-Sender X-Attribution
ignore X-MIME-Autoconverted
# Usenet headers can occur for Cc-ed messages; they can still be
# recognized by the newsgroups header.
ignore Path Lines NNTP-Posting-Host X-Newsreader X-Submitted-Via
#
# Color / video attribute definitions. Not too flashy.
#
color hdrdefault green black
color header brightyellowblack "^From:"
monoheader bold"^From:"
color header brightyellowblack "^Subject:"
monoheader bold"^Subject:"
color header brightred black "^X-.*.Warning"
monoheader bold"^X-.*.Warning"
color header brightred black ".*[Uu]nverified.*"
monoheader bold".*[Uu]nverified.*"
color quoted green black
color signature brightred black
color indicator brightyellowred
color attachment brightmagenta black
color error brightred black
monoerror bold
color status brightwhite blue
color treebrightmagenta black
color tilde brightmagenta black
color bodybrightyellowblack "(ftp|http|gopher|wais|file)://[^ ]+"
monobodybold"(ftp|http|gopher|wais|file)://[^ ]+"
color bodybrightmagenta black "[-a-z_0-9.]+@[-a-z_0-9.]+"
monobodybold"[-a-z_0-9.]+@[-a-z_0-9.]+"
# lists list-name [ list-name ... ]
lists PGP-Basics mutt-users zoot-list PGP-Basics lvlug
subscribe [EMAIL PROTECTED]
subscribe [EMAIL PROTECTED]
subscribe [EMAIL PROTECTED]
subscribe [EMAIL PROTECTED]
alias redhat [EMAIL PROTECTED]
alias dale Dale Morris [EMAIL PROTECTED]
alias hank Hank Henry [EMAIL PROTECTED]
alias ann Ann Dyck [EMAIL PROTECTED]
alias mutt [EMAIL PROTECTED]
alias liming Liming Song [EMAIL PROTECTED]
alias lisa Lisa Williams [EMAIL PROTECTED]
alias huff \"H.David Huffman\" [EMAIL PROTECTED]
alias ethel Ethel Miller [EMAIL PROTECTED]
alias tracy Ron Tracy [EMAIL PROTECTED]
alias traceyl Tracey Leacock [EMAIL PROTECTED]
alias belize [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED],
Re: procmail question
On Sun, Jun 18, 2000 at 12:53:08PM -0700, Dale Morris wrote: I'm trying to get procmail working on my rh 6.2 system, after reading the manual and banging my head on the keyboard for several hours, I'm thoroughly confused--a comfortable state, for me and linux.. my question ... What I want to do is have procmail transfer mutt-users messages /var/spool/mail/dlm to /home/dlm/Mail/mutt, correct? I have a mutt mbox, and here's how I've setup the .procmailrc recipe: #mutt :0: * (^Reply-To:.*|^TO_)mutt-users $MAILDIR/mutt But it doesn't work. I will attach my .procmailrc and .muttrc files if someone cares to take a look. First off, since this sounds like a delivery problem, mutt is not at all relevant. This is a MTA problem. For RH6.2, the default is for your MTA to be sendmail with local delivery handled by procmail. So far, so good. Procmail filtering basics: Procmail filters your incoming messages at time of delivery. If your mutt e-mail ever gets to /var/spool/mail/dlm, then your procmail recipe has already failed. E-mail which gets diverted to /home/dlm/Mail/mutt will never go anywhere near /var/spool/mail/dlm. First question: How is incoming e-mail getting to your system? If you are using fetchmail or it is being delivered directly via SMTP, you are looking good so far. If you are using fetchmail with an odd --mda setting or some other program which is writing it directly to /var/spool/... rather than delivering it to your local SMTP server, we have just identified one of your problems. Assuming that everything is ok to this point, it is time to consider the rule you are using. I am not a procmail guru, so the following advice may not be 100% right, but it works for me: Never, never, never filter a mailing list like mutt-users based on To:, Cc:, From:, Subject:, Reply-To: or Mail-Followup-To: if you can possibly help it. What happens the first time someone bcc's the list? Think about it. Filtering on headers written by the user is a sure recipe for failure. Any reasonable mailing list server will add a header identifying the list. The most common header is Sender:, but I've also had to resort to Mailing-List:, X-Mailing-List, and Delivered-To:. In the case of mutt-users, the header I use is Sender:. That gives a rule like this: :0: * ^Sender: owner-mutt $MAILDIR/mutt I bet that rule will work a lot better for you than your current one. Brian
Re: procmail question
On Sun, Jun 18, 2000 at 12:53:08PM -0700, Dale Morris wrote: I've setup procmail as follows, MAILDIR=$HOME/Mail which is there in my home directory and includes all the mailboxes I'm saving my mail to. When I open mutt it reads the mail in /var/spool/mail/dlm. the result is mail isn't being transferred to my MAILDIR=$HOME/Mail directory. Is this correct? Curious, I also use RH 6.2 and mutt always transfer var/spool/mail/ to ~/Mail. Maybe a MTA/MDA problem in your default configuration? What I want to do is have procmail transfer mutt-users messages /var/spool/mail/dlm to /home/dlm/Mail/mutt, correct? I have a mutt mbox, and here's how I've setup the .procmailrc recipe: But it doesn't work. I will attach my .procmailrc and .muttrc files if someone cares to take a look. Hmm, I also use RH 6.2 and I'm not sure the problem comes from your procmailrc. +Which MTA do you use ? Sendmail or postfix use procmail as default MDA. If you don't use them, then I think you should write the following lines in your .fetchmailrc : defaults mda "formail -ds procmail" #mutt :0: * (^Reply-To:.*|^TO_)mutt-users $MAILDIR/mutt Here I don't think that MAILDIR is necessary, as the location has been already defined at bottom. My procmailrc works and looks like this : MAILDIR=$HOME/Mail VERBOSE=off LOGFILE=$HOME/.log-procmail :0: * ^[EMAIL PROTECTED] IN.mutt-users I didn't need to set Procmail as default MDA in fetchmail, but it has been defined in sendmail's config.mc : FEATURE(local_procmail)dnl Bye (and sorry for my very bad english :) PS : thanks to people who spoke about those options : macro index G "!fetchmail\n" macro pager G "!fetchmail\n" I didn't know them and it works fine. I'm very happy :) -- Virginie - Membre de Parinux (LUG - Paris) [EMAIL PROTECTED]
