Why doesn't mutt use summary files like Netscape to reduce mbox load
time?
Is there a command to advance to the next unread message in any mailbox
specified by the 'mailboxes' setting?
When I send mail fcc-ed to one of the mailboxes in 'mailboxes', mutt
reports new mail in that mailbox. Is there any way to avoid this?
When I type ":set pgp_verify_sig no", mutt 1.2.4i says, "unknown
variable", though this variable is listed in my manual.txt. mutt -v
reports
> Mutt 1.2.4i (2000-07-07)
> Copyright (C) 1996-2000 Michael R. Elkins and others.
> Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
> Mutt is free software, and you are welcome to redistribute it
> under certain conditions; type `mutt -vv' for details.
>
> System: Linux 2.2.5-15 [using slang 10202]
> Compile options:
> -DOMAIN
> -DEBUG
> -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK
> -USE_IMAP -USE_GSS -USE_SSL -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX
> +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -ENABLE_NLS
> SENDMAIL="/usr/sbin/sendmail"
> MAILPATH="/var/spool/mail"
> SHAREDIR="/usr/local/share/mutt"
> SYSCONFDIR="/usr/local/etc"
> ISPELL="/usr/bin/ispell"
With PGP/MIME, is there any easy solution that allows people with
PGP/MIME-capable mail clients to receive PGP/MIME and everybody else to
receive traditional PGP messages? I'm thinking a procmail recipe that
looks at incoming email and puts the sender's email address in
/home/dan/.pgpmime-capable or /home/dan/.pgpmime-notcapable.
If the email is PGP/MIME, the sender goes in .pgpmime-capable.
If the email is PGP traditional, the sender goes in
.pgpmime-notcapable .
If the User-Agent or X-Mailer or From is one of those that deal
really really horribly with PGP/MIME (Outlook (Express?),
Hotmail, et al.), the sender goes in pgpmime-notcapable .
Then, in .muttrc...
sendhook . 'unset pgp_create_traditional'
# If we don't know, send them PGP/MIME to encourage them to
# use PGP/MIME.
source "sed -e \"s/^\\(.*\\)$/send-hook '~t \1' 'set
pgp_create_traditional'/\" < /home/dan/.pgpmime-notcapable"
source "sed -e \"s/^\\(.*\\)$/send-hook '~t \1' 'unset
pgp_create_traditional'/\" < /home/dan/.pgpmime-capable"
# (The escaping of shell commands in .muttrc is miserable, btw).
Is there any better solution? Are there any other clients that deal
horribly with PGP/MIME?
BTW, how do you verify PGP/MIME signatures with PGP 6 for Windows?
--
Daniel J. Peng
/"\
\ / ASCII Ribbon Campaign
Who is John Galt? X Against Outlook & HTML Mail
/ \ http://www.thebackrow.net/
Q: How many surrealists does it take to change a light bulb?
A: Two, one to hold the giraffe, and the other to fill the bathtub
with brightly colored machine tools.
[Surrealist jokes just aren't my cup of fur. Ed.]
