Re: Disabling fcc when sending from command line

[Mikko Hänninen]

David T-G [EMAIL PROTECTED] wrote on Sat, 08 Jan 2000:
 What I do for that kind of thing is just have a spare muttrc hanging
 around (.mutt/muttrcc-nosave) that first sources my main muttrc (to set
 the sender name and such) and then unsets some things (like pgp_autosign
 and fcc and X-headers and such).

But you can't un-do hooks (fcc-hooks)...  And doesn't only the first
matching get used, so you can't even set up a default which overrides
things later?

I did think of something else:

echo test | mutt -s test [EMAIL PROTECTED] -e 'set copy=no'

That seems to work!


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 /
Favourite MAC error message: "Not enough memory to eject disk!"

Mutt-Outlook with PGP Encryption

[Jean-Sebastien Morisset]

I've been having some problems with a friend who's using a broken MIME
reader (outlook). I've used the filter trick to sign messages, but applying
this same trick to encryption is a pain -- PGP will ask who the destination
is when I've already entered it in mutt!

I've written a script to parse the message headers and start PGP with the
recipients list, but my problem is accessing the headers. Sure, there's a
tmp file in /tmp, but there can be more than one. I can compare the body,
but left-over tmp messages might have the same body but different
destinations.

So, can anyone suggest how I can read the message headers in a filter?

Thanks,
js.
-- 
Jean-Sebastien Morisset, Sr. UNIX Administrator
up2 technologies inc.
[EMAIL PROTECTED], www.up2me.com

 PGP signature

ANNOUNCE: getmail v.0.98, a 'fetchmail' replacement

[Charles Cazabon]

Slightly off-topic (flames in private mail, please), but applicable to
mutt:

getmail 0.98 is now available from
http://www.qcc.sk.ca/~charlesc/software/getmail/

getmail is intended as a simple replacement for fetchmail, for those who
don't need all of its various features, configuration options, and bugs.
It retrieves mail only from POP3 servers, and delivers reliably to Maildirs.
mbox delivery is also possible, but should not be attempted over NFS.

It is written in Python and released under the GPL version 2.

It can retrieve all mail, or only unread messages, from an unlimited number
of POP3 mailboxes on one or more POP3 servers.  Configuration and usage is
straightforward and simple.  getmail now has experimental support for
domain (multidrop) mailboxes, with delivery instructions on a per-recipient
basis.

Changes since version 0.95:

-experimental support for domain (multidrop) mailboxes.  Please read the
  documentation for configuration and limitation information.

-Slightly changed creation of 'From ' mbox delimiter line for overly picky
  mail clients.

-Options to delete retrieved mail, and to only retrieve unread mail,
  can now be specified on a per-account basis in the .getmailrc file.
  The options are specified in each account section, with 'delete=value'
  and 'readall=value', where value is '1', 'true', or 'yes', or '0',
  'no', or 'false'.

-Changed password entry method.

-Fixed a bug which resulted in failure to deliver to an mbox file when
  there was no Return-Path: header in a retrieved email.

-Fixed a bug where explicitly specifying the --dont-delete or -l options
  (even though they are the default) caused mail to be deleted from the
  POP3 server.

-The GETMAIL environment variable is now unnecessary if your getmail
  configuration/data directory is located at $HOME/.getmail

-Some unnecessary code removed.

-Exit codes changed.  0 means mail retrieved, 1 means no mail, -1 means
  fatal error, and 100/101 are exits due to options --help and --dump.


Any questions, feedback, etc, is greatly appreciated, but should be done
in private email.

Charles Cazabon
-- 
---
Charles Cazabon [EMAIL PROTECTED]
GPL'ed software available at:  http://www.qcc.sk.ca/~charlesc/software/
My opinions are just that -- my opinions.
---

giving $realname precedence over $reverse_name

[Troy Davis]

Is it possible for $realname to take precedence over $reverse_name
(essentially turning $reverse_name into just "reverse_email")?

Occasionally I receive emails to: "Troy Davis (e-mail)" [EMAIL PROTECTED] 
or others where responding with that name would be strange.  I'm using 
1.1.1i.

Suggestions appreciated,

Troy