Re: Re:
Threads are usually broken because someone's mailer doeesn't generate any useful trackable header like Message-ID, References, or In-Reply-To. I would rather get the person to use a better client, or smack her/his ISP to add this support to their mail system. As for threading by subject, it'd be nice to do what you suggested. But this is an open-source world where code speaks volumes. So writing and submitting a patch would be better. :) On Sat, Jun 17, 2000 at 07:33:16PM -0500, Andrew Eichmann wrote: : :When I thread mailing list messages, often the thread will be broken :up because of differing versions and placement of ``Re:'' in the :subject line, compounded by different mail clients' handling of :the subject line. For example, if the original message's Subject: :line is ``[BOB] What's the frequency, Kenneth?''where ``[BOB]'' is :the mailing list name that gets prepended to the subject, the replies :will :wind up like: : :``Re: [BOB] What's the frequency, Kenneth?'' :``re: [BOB] What's the frequency, Kenneth?'' :``Re: [BOB] re: What's the frequency, Kenneth?'' :``RE: [BOB] What's the frequency, Kenneth?'' :``Re: re: [BOB] What's the frequency, Kenneth?'' :usw. : :I searched on ``Re:'' and ``Subject:'' in the manual and didn't :find anything useful looking. : :Is there a built-in solution to this? Does anybody else have this :problem? I imagine something stripping out all variations of ``Re:'' :before the threads are arranged in the list. This would be child's :play in Perl, the world is not Perl. :-) : :Or should I start putting together a patch, right after I relearn C? -- Eugene Lee [EMAIL PROTECTED]
Re: Re:
I warn you now - this is more than you asked for.
On 2000.06.17, in [EMAIL PROTECTED],
"Andrew Eichmann" [EMAIL PROTECTED] wrote:
the subject line. For example, if the original message's Subject:
line is ``[BOB] What's the frequency, Kenneth?''where ``[BOB]'' is
the mailing list name that gets prepended to the subject, the replies
...
Is there a built-in solution to this? Does anybody else have this
problem? I imagine something stripping out all variations of ``Re:''
I have this problem, too -- it's one of the reasons I can't stand lists
that alter your postings' subject: lines.
My .procmailrc loads a file named "classaction". This file sets some
operational defaults, then loads a bunch of matching rules from another
file called "classes". It then alters messages as documented in
"classaction".
"classaction" and a stripped-down copy of "classes" are attached. In
reality, I process about 120 different lists and other categories of
like mail from this setup. It's fast, but that doesn't actually matter
since it's asynch with my mail-reading.
"$ ${XFROM}" is a procmail macro I use for matching sender addresses.
You can substitute the built-in "^FROM" (or whatever).
You'll note that this setup only marks messages by removing [LISTNAME]
stuff from the subject (if STRIPLAB is set in the list's config), and
adds the X-Label: header. I have mutt set up to do all its list
matching on "~y listname" instead of duplicating all the patterns, so
procmail and mutt are VERY intertwined here.
(X-Label: and "~y" are a 1.3.x thing. This makes it easy to move a
message from one category to another in Mutt's eyes. Once a message is
archived and delivered, it's all about Mutt, and I don't worry about
saving anything that has an X-Label: because I know it's already
archived.)
Anyway, maybe you don't want all that, but it shows how I'm using
procmail to match the expressions. :)
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
###
###
### Handle all mail classes properly, phase 1.
###
### These DEFAULTS hinge archival, labelling, and inbox display on whether
### ${CLASS} is defined. For these options, you need only define ${CLASS}
### to a shorthand for the mail class a message should belong to.
###
### Nullify the class name. If CLASS is undefined, mail will pass through
### the class-action package untouched and unarchived. (Auto-forwarding
### will still occur, though.) ${CLASS} implies a few things:
### 1. Name of the archival folder
### 2. Name for class labelling (X-Label header field or Subject: rewrite)
### If ${CLASS} is literally "null", mail in a given class will be killed off
### after matching.
CLASS=
### If ${CLASS} is set to someting besides "null", and ${ARCHIVE} is set,
### messages will be archived. If ${ARCHIVE} is "yes", the archival folder's
### name will be copied from ${CLASS}. If ${ARCHIVE} is anything else, mail
### will be archived to that folder name.
###
### The archived copy will be unadulterated.
ARCHIVE=yes
### If ${CLASS} is set to someting besides "null", and ${LABEL} is set,
### messages will have an "X-Label:" header field inserted. If ${LABEL}
### is "yes", the X-Label will be set to ${CLASS}. If ${LABEL} is set
### to any other value, the X-Label will be set to that value.
LABEL=yes
### If ${HARDLABEL} is "yes", rewrite
### Subject: Re: foo
### as
### Subject: [$LABEL] Re: foo
### instead of inserting an X-Label: header.
HARDLABEL=no
### If ${STRIPLAB} is set to "yes", remove anything enclosed in square
### brackets from the beginning, or following a leading "Re: ", of the
### Subject: header. If ${STRIPLAB} is set to anything else, remove
### only such tags if they match ${STRIPLAB}. This is for removing
### the tags generated by some mailing-list managers so that we can
### prefer X-Label:s.
STRIPLAB=
### If ${HIDE} is set to "yes", the class-action package will not
### store messages in a class to the default folder (inbox). If ${HIDE}
### is unset, or set to anything besides "yes" , messages will be stored
### to the default folder IN ADDITION to any archival. The copy in the
### default folder will be marked with "Status: O".
HIDE=no
###
### Try to match mail to a list or class. Multiple matches are multiply
### acted upon.
INCLUDERC=$PMDIR/classes
### If CLASS was set to "null", just ditch it and end
:0
* CLASS ?? null
/dev/null
### If CLASS was set and ARCHIVE is set, prepare to archive
:0
* CLASS ?? .+
{
## Check the cache for this dropbox; drop if a repeat.
## Rewriting the value of IDCACHE here allows each list to
## maintain internal uniqueness, but doesn't prevent duplicate
## refiles of messages aimed at two or more separate lists.
IDCACHE=lists/`dirname $CLASS`/.`basename $CLASS`.idcache
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."
mailboxes
Hello List, This is embarrassing. I have made letterboxes in $HOME/Mail using touch. These new files don't open automatically but bring up the "open with" dialogue when clicked. Procmail evidently can't see or open them to deliver mail and it all goes to inbox. How do I make files that open when clicked and more specifically mailboxes that procmail can use? Thanks. -- Dennis Robertson 2/2 Sylvia Street NOOSAVILLE QLD 4566 AUSTRALIA Phone: 61 7 54742343 Mobile: 0419 535539 Fax: Phone for setup.
Re: mailboxes
Dennis -- ...and then Dennis Robertson said... % Hello List, % This is embarrassing. I have made letterboxes in $HOME/Mail using % touch. These new files don't open automatically but bring up the "open % with" dialogue when clicked. Procmail evidently can't see or open them "when clicked", hmm? Sounds like you're probably trying to use a GUI filemanager to fire off mutt -- something outside the scope of this list :-) % to deliver mail and it all goes to inbox. How do I make files that open This sounds like you don't have a .forward file to tell sendmail to hand your mail off to procmail, and perhaps don't have a .procmailrc file to do that on a system where procmail is the MDA but certainly not to tell procmail where to deliver mail. Check out the man pages for procmail and procmailex for starters. % when clicked and more specifically mailboxes that procmail can use? Empty files are fine for both mutt and procmail, so that's no problem. Look into your file manager configs for how to specify that such-and-such is a mailbox and should be opened by mutt. % Thanks. % -- % Dennis Robertson 2/2 Sylvia Street NOOSAVILLE QLD 4566 AUSTRALIA % Phone: 61 7 54742343 Mobile: 0419 535539 Fax: Phone for setup. :-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
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
alias classes
Hi, folks -- Those of you who have ever seen sudo or powerbroker, the [free and expensive, respectively] tools to let ordinary users perform privileged functions under *NIX, will probably understand exactly what I'm about to try to describe. For the rest of you, I hope I can be clear :-) I would like to set up [heirarchical] classes of aliases to use for folder management -- yes, aliases for folder management. Currently I can define alias al [EMAIL PROTECTED] (Al Pal) alias bill [EMAIL PROTECTED] (Bill Friend) alias chuck [EMAIL PROTECTED] (Chuck Buddy) alias pals al,bill,chuck fcc-save-hook \ '[EMAIL PROTECTED]|[EMAIL PROTECTED]|[EMAIL PROTECTED]' \ =PALS/%O for my special pals Al, Bill and Chuck so that their mail goes into their folders under $HOME/Mail/PALS instead of under $HOME/Mail. I'd really like to be able to define a class of pals so that I can say aliasclass PALS al,bill,chuck fcc-save-hook '[[:PALS:]]' =PALS/%O or perhaps alias pals al,bill,chuck fcc-save-hook '[[:pals:]]' -PALS/%O (borrowing a little bit of notation from the GNU regexps) so that I don't have to maintain two lists (the mailing alias *and* the fcc-save-hook). This maps well to creating larger classes, too, by simply including the subclasses instead of the alias itself. Nothing new for aliases themselves, since nested aliases are already supported, but nice for the folder management side. I realize that this is fairly complex and certainly isn't something for 1.2.1 -- but does it sound feasible, worthwhile, and like it might happen one of these days? Or does anyone have any better ideas? TIA 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.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: mailboxes
David T-G proclaimed on mutt-users that: ...and then Dennis Robertson said... % Hello List, % This is embarrassing. I have made letterboxes in $HOME/Mail using % touch. These new files don't open automatically but bring up the "open % with" dialogue when clicked. Procmail evidently can't see or open them "when clicked", hmm? Sounds like you're probably trying to use a GUI filemanager to fire off mutt -- something outside the scope of this list :-) % to deliver mail and it all goes to inbox. How do I make files that open This sounds like you don't have a .forward file to tell sendmail to Or perhaps his "mailboxes" are not mailboxes at all, or are in the wrong format somehow? Try creating a mailbox by saving a mail using mutt (it will ask - "create mailbox y/n". Or if there are no mails, use something like $ echo 'test'|mail [EMAIL PROTECTED] Of course, mutt might not see your mailboxes - so put something like mailboxes `echo $HOME/mail/*` in your .muttrc and see. -- Suresh Ramasubramanian + [EMAIL PROTECTED] Cat, n.: Lapwarmer with built-in buzzer.
Re: alias classes
David T-G proclaimed on mutt-users that: fcc-save-hook \ '[EMAIL PROTECTED]|[EMAIL PROTECTED]|[EMAIL PROTECTED]' \ =PALS/%O for my special pals Al, Bill and Chuck so that their mail goes into their folders under $HOME/Mail/PALS instead of under $HOME/Mail. I'd really like to be able to define a class of pals so that I can say Call me clueless but this sounds more like a mail _delivery_ issue to be managed with fetchmail and procmail rather than mutt. -- Suresh Ramasubramanian + [EMAIL PROTECTED] Cat, n.: Lapwarmer with built-in buzzer.
Re: alias classes
David T-G [EMAIL PROTECTED] wrote on Sun, 18 Jun 2000:
alias pals al,bill,chuck
fcc-save-hook '[[:pals:]]' -PALS/%O
Something I'd like to see was an operator for matching an address or
addresses in an alias, I think that would help you out here. The syntax
would be different ("~somechar alias") but it would do the same thing,
I imagine.
Mikko
--
// Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/
// The Corrs list maintainer // net.freak // DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs /
Despite the high cost of living, it remains very popular.
Re: mailboxes
On 2000.06.18, in [EMAIL PROTECTED], "Dennis Robertson" [EMAIL PROTECTED] wrote: Hello List, This is embarrassing. I have made letterboxes in $HOME/Mail using touch. These new files don't open automatically but bring up the "open with" dialogue when clicked. Procmail evidently can't see or open them You don't mention what file-manager you're using, but many of them figure out the relevant application using the "file" command or /etc/magic. For the files to be recognized as mbox files, you need to have mail in them. As for getting mail in with procmail, see how you do with what Suresh and David said. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: procmail
YES!! It works. The elation is incredible!!##@$ At 18 June, 2000 Dale Morris wrote: I may have got my procmail working!! Just opened my mbox folder and found new mail in mutt!!! I believe what may have done the trick was going into .muttrc and specifying mbox names.. Anyhow, this is kind of a test to see if this will be transferred to my mutt mbox. Sorry if this doesn't show up in thread, I've lost some messages that I posted to the list. It feels great when it works!!! -- 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
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]
