Though controversial, I feel that this patch is in the best interest of
promoting the use of PGP with Mutt.
This patch adds a new boolean variable $pgp_search_text which will cause Mutt
to search for the first non-blank line in every text/plain message to see if
it is a mislabeled old-style PGP
On 2000-01-04 10:40:46 +0100, Martin Schröder wrote:
The year 100 is converted by date_format="%Y-%m-%d %H:%M:%S %Z"
to 2000. Problem of mutt or of strftime?
I wouldn't really consider this a problem - after all, it cought
quite a bit of y2k-related nonsense emitted by other software, and,
in
I just realized that this patch does not solve the problem which started this
whole thread, which is dealing with an IMAP server. Unless there is a way
to fetch the first couple of lines of the body of a message with IMAP, I don't
see a clean way to accomplish automatic handling. The next best
Mikko Hänninen [[EMAIL PROTECTED]] wrote:
Mat [EMAIL PROTECTED] wrote on Thu, 30 Dec 1999:
set reverse_name# reply as the user to whom the mail was sent to
This is what you want.
If it doesn't work, make sure you don't have any "my_hdr From:"
definitions.
Also, be sure to make
Okay, back on the default delete question. In order to automatically
save all messages to archive instead of deleting them, I made a macro
for key "d." Unfortunately, this is still not the action that I want
because it forces me to hit enter for every file. I'm on a large
number of lists, and I
Jonathan Pennington [[EMAIL PROTECTED]] wrote:
Okay, back on the default delete question. In order to automatically
save all messages to archive instead of deleting them, I made a macro
for key "d." Unfortunately, this is still not the action that I want
because it forces me to hit enter for
Hi,
If I have my threads collapsed in a mailbox, and tag them with T*, not
all messages are selected; only the ones visible in the index! The
messages that are hidden in the collapsed threads are NOT selected.
How can I solve this apart from first expanding the threads?
Ray
--
Raymond A.
Raymond A. Meijer [[EMAIL PROTECTED]] wrote:
If I have my threads collapsed in a mailbox, and tag them with T*, not
all messages are selected; only the ones visible in the index! The
messages that are hidden in the collapsed threads are NOT selected.
How can I solve this apart from first
Jeremy Blosser [EMAIL PROTECTED] wrote on Wed, 05 Jan 2000:
To my knowledge you can't. Operations act only on messages that are
non-hidden. This is consistent with this being true when you apply a limit
to messages, and then expect operations to only act inside the limit you
gave.
Maybe
On Wednesday, 05 January 2000 at 01:45, Michael Elkins wrote:
I just realized that this patch does not solve the problem which started this
whole thread, which is dealing with an IMAP server. Unless there is a way
to fetch the first couple of lines of the body of a message with IMAP, I don't
On Wed, Jan 05, 2000 at 01:45:33AM -0800, Michael Elkins wrote:
I just realized that this patch does not solve the problem which started this
whole thread, which is dealing with an IMAP server. Unless there is a way
to fetch the first couple of lines of the body of a message with IMAP, I
I get the following message from my ISP. I see it on Mutt and Eudora. I am
using Fetchmail and IMAP to fetch mail from the ISP. Is this anything I
need to worry about?
- Forwarded message from Mail System Internal Data -
Date: Tue, 4 Jan 2000 18:17:08 -0700 (MST)
From: Mail System
On Wed, Jan 05, 2000 at 04:33:36AM -0700, shawn å. wrote:
Hi, I have a weird problem with accented charactures... Mutt won't display
them. All I get are ?? instead of àáâãäå. I know they are there, 'cause
when I do a reply, vim shows the ?'s as à's. I have 'set allow_8bit' in my
At 11:18 PM 01/04/00 , Mikko Hänninen wrote:
John Verel [EMAIL PROTECTED] wrote on Tue, 04 Jan 2000:
I'm trying to print using enscript. If I set the print_command
variable to enscript, it prints fine. However, if I use any of the
arguments available for enscript, such as the -f variable
Can anyone tell me how to handle a MIME attachment that was encoded
using BinHex 4.0? I received an e-mail containing several JPEG photos
that were attached as follows:
--=_947052952==_
Content-Type: application/mac-binhex40; name="putin4.jpg"
Content-Disposition:
On Wed, Jan 05, 2000 at 06:18:13AM +0200, Mikko Hänninen wrote:
John Verel [EMAIL PROTECTED] wrote on Tue, 04 Jan 2000:
I'm trying to print using enscript. If I set the print_command
variable to enscript, it prints fine. However, if I use any of the
arguments available for enscript, such
At 09:09 PM 1/5/00 -0500, Andrew J. Schorr wrote:
Can anyone tell me how to handle a MIME attachment that was encoded
using BinHex 4.0? I received an e-mail containing several JPEG photos
that were attached as follows:
[snip]
Content-Type: application/mac-binhex40; name="putin4.jpg"
Slightly off-topic (flames in private mail, please), but applicable to
mutt:
getmail 0.95 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
Andrew J. Schorr [EMAIL PROTECTED] wrote on Wed, 05 Jan 2000:
Is there any way of configuring the mailcap file to handle such an
attachment automatically? And where does one find a BinHex 4.0 decoder
that runs on Solaris and/or Linux? Is uudeview the best bet (I found
it on freshmeat.net)?
Sitaram Iyer [EMAIL PROTECTED] wrote on Wed, 05 Jan 2000:
I'm confused. Does mutt need fixing or does USA.NET or do both?
Both. The Y2K problem with 2-digit years (which are legal according to
the RFC, but are also pretty stupid and shouldn't be used...) has been
reported already several
Mikko Hänninen [EMAIL PROTECTED] wrote on Thu, 06 Jan 2000:
Both. The Y2K problem with 2-digit years (which are legal according to
snip
Sorry, that went to the wrong place, when I was munging about the
recipient headers. :-( Apologies for the extra post (and this one
too).
Mikko
--
//
21 matches
Mail list logo
