On Thu, Jun 20, 2002 at 05:27:29AM -0500, David T-G wrote: > Charles -- > > ...and then [EMAIL PROTECTED] said... > % > % It's unclear to me when mutt is supposed to ask me to update encoding. > % > % What causes mutt to hit that flag? It's unclear to me from the sources > % whether it's something mutt netotiates with the receiver or what. > > First go back and check the archives; this has come up often.
Didn't understand the answers . . . > > The usual cause is a timestamp difference; mutt fires off your editor, > you edit the message and save and quit, and mutt takes you to the compose > screen, but before the mail is sent the timestamp on the message file > changes. When it looks to mutt as though the message file has been > changed, it offers to check to make sure that whatever it chose (plain > text, Q-P, base64) is still the best way to send the mail. Hmmmm . . . so the fact that my computer is slow does it? > Are you using disk space on a network server? I recommend checking the > clock on your PC and on the server and making sure they're synchronized. > If you aren't, then we have some more digging to do. Nope. Before the Cygwin port came out, I'd built it myself, but had the same thing happen. It's not exactly a problem, I suppose. > % I'm using the Cygwin port, with ssmpt as my mta. > > ssmtp shouldn't matter. In theory, neither should cygwin, but it's a > lead if you're not using a network server... > Right. No network server. I've always seen it under Cygwin, both when I built my own copy, and now that there's a mainstream Cygwin port. And at work, I never see it, running under Solaris 5.7 and I AM using a network server. Charles
