Re: trash folder in 1.5.18
Hi David! On Tue, 19 Aug 2008, David Champion wrote: > > >> http://cedricduval.free.fr/mutt/patches/#trash is only upto the > > >> mutt version 1.5.5.1; there are no patches after that. I am guessing > > >> that it has been included in the original code. > > > > > > It has not been. > > Cedric hasn't updated it AFAIK, but a google > on "cedric duval trash patch" turns up > http://scie.nti.st/2007/6/21/mutt-trash-folder-patch-for-1-5-16 . Maybe > that version will apply more cleanly to 1.5.18. You could also get the source code from Debian, which includes the trash-folder patch. They have a version for 1.5.18 regards, Christian -- When the Universe was not so out of whack as it is today, and all the stars were lined up in their proper places, you could easily count them from left to right, or top to bottom, and the larger and bluer ones were set apart, and the smaller yellowing types pushed off to the corners as bodies of a lower grade ... -- Stanislaw Lem, "Cyberiad"
Re: attachment checking with smtp sending
=- P Kapat wrote on Mon 18.Aug'08 at 18:44:18 -0400 -= > http://wiki.mutt.org/?ConfigTricks/CheckAttach > > But I am also using the smtp_url in my muttrc to set gmail's smtp > srever. So, is it possible to modify/use this CheckAttach script > in my setup? CheckAttach takes this chain: mutt -> $sendmail -> "sendmail" and adds a check mutt -> $sendmail -> own-script-for-check -> "sendmail" Now, where comes smtp_url into play here? I guess right before $sendmail, so ... -- © Rado S. -- You must provide YOUR effort for your goal! EVERY effort counts: at least to show your attitude. You're responsible for ALL you do: you get what you give.
Re: config file
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, August 18 at 09:35 PM, quoth Ravi Uday: >> Thats pretty much I had.. but then I cant see the >> >> --BEGIN PGP MESSAGE-- Can't read them, or are they not there? >> There is a attachment in the mail and that contains the signature >> part..! Can we have it inlined in the body of hte mail ? Sounds like you're not having mutt actually verify the signature. Add the following to your muttrc: set crypt_verify_sig=yes ~Kyle - -- Compassion is the basis of morality. -- Arnold Schopenhauer -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkiq1KgACgkQBkIOoMqOI16O2wCg2vCrf+QuS9iUHBuwI2GbQYZr u4MAoIZmr+z5wQzUenfjuG4dTwYGDh6J =gapP -END PGP SIGNATURE-
Re: config file
Hi Kyle, signature is indeed verified.. When i send a mail, I see this in the body of the mail: [-- PGP output follows (current time: Tue Aug 19 09:53:01 2008) --] gpg: Signature made Tue Aug 19 09:45:35 2008 PDT using DSA key ID E4D5F777 gpg: Good signature from "xx <[EMAIL PROTECTED]>" [-- End of PGP output --] [-- The following data is signed --] xx [-- End of signed data --] And then there is an attachment (as seen from Outlook 'ATT00076.dat' which has : -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (SunOS) iD8DBQFIqvivwPhtruTV93cRAvQVAKCCUNzqUt4NAgW4NVGtgvscir0PbACeLugg TIGka5xULC+sJIkgKRQ0wl8= =KZe1 -END PGP SIGNATURE- So how can we have this embedded in the body of the mail itself ? and have the name of the file attachment changed to 'signature.asc' When you send a mail, I can see in the body: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 -BEGIN PGP SIGNATURE- ... -END PGP SIGNATURE- I would like to have the same format..in the body of the mail itself :) Thanks, - Ravi On Tue, Aug 19, 2008 at 7:11 AM, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Monday, August 18 at 09:35 PM, quoth Ravi Uday: >>> Thats pretty much I had.. but then I cant see the >>> >>> --BEGIN PGP MESSAGE-- > > Can't read them, or are they not there? > >>> There is a attachment in the mail and that contains the signature >>> part..! Can we have it inlined in the body of hte mail ? > > Sounds like you're not having mutt actually verify the signature. Add > the following to your muttrc: > > set crypt_verify_sig=yes > > ~Kyle > - -- > Compassion is the basis of morality. > -- Arnold Schopenhauer > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iEYEARECAAYFAkiq1KgACgkQBkIOoMqOI16O2wCg2vCrf+QuS9iUHBuwI2GbQYZr > u4MAoIZmr+z5wQzUenfjuG4dTwYGDh6J > =gapP > -END PGP SIGNATURE- >
Re: config file
> signature is indeed verified.. Okay... > And then there is an attachment (as seen from Outlook 'ATT00076.dat' > which has : You're using Outlook as your reference? > So how can we have this embedded in the body of the mail itself ? Uh... Most folks *don't* want that in the body of the mail itself. But you can force it; try adding the following to your muttrc: auto_view application/pgp-signature And then add the following to your mailcap: application/pgp-signature; cat %s; copiousoutput > and have the name of the file attachment changed to 'signature.asc' You don't want to do this. See the mailing list archives for the full discussion of why mutt doesn't specify a filename (hint: it's not really a file, it's part of the MIME structure). > When you send a mail, I can see in the body: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > -BEGIN PGP SIGNATURE- > ... > -END PGP SIGNATURE- > > I would like to have the same format..in the body of the mail itself A, I see. You want old-style signatures. Add the following to your muttrc: set pgp_autoinline=yes Generally, though, old-style signatures (which I use for this mailing list, because I'm often assisting people with broken email clients or configurations) have some pretty severe drawbacks. For example, it's impossible to sign your attachments, or to deal with non-ASCII email (there are some hacks, but they're unreliable workarounds for dealing with broken clients and are only applicable to specific ASCII-like character sets). As another example, the email that I'm replying to included some bits that looked like the old-style signatures, but were invalid. Email clients that attempt to verify old-style signatures will take one look at that and scream "FORGED EMAIL!", and may refuse to display your email at all. You cannot include that kind of data in the body of your email and use old-style signatures, otherwise your message risks being considered corrupt by savvy email clients (I had to jump through a few hoops in order to make mutt display your corrupt message). Thankfully, most pgp programs will try to prevent you from doing stupid things like that, and will mangle your messages in order to prevent invalid messages. But my point stands. With the exception of mailing lists where I may be dealing with people with broken mail clients (such as this one), I recommend avoiding that old style of PGP signature. It's intrusive and not very capable. PGP/MIME (the newer style of PGP signature) is MUCH better, and neatly avoids all those problems. The only reason I use them for this list is because some ancient versions of Outlook Express get confused by the PGP/MIME signature and refuse to display the message (which is idiotic, but that's Microsoft for you), but whenever I have to send something in a non-ASCII character set, I switch back to PGP/MIME. ~Kyle
Mutt tty problems on Mac OS X 10.5.4 and mutt 1.5.18
I have a relatively new Max Pro Book (Book Pro?) running OS X 10.5.4 and mutt 1.5.18. Using a standard Terminal with the default TERM value of xterm, mutt has a terrible time displaying, with two symptom that I have seen: 1. Re: Subject: headers show up in the summary display as lots of ~T with a few other line noise chars thrown in for good measure. The original message which starts the thread has its Subject: displayed properly. I don't think it is the replies being garbled or in some other character set because all Subject: headers look fine when I read the actual message. This is always repeatable. 2. When you hit SPACE to read the body of a message, then finish and "q" back to the summary listing, sometimes the previous message display does not clear first and the summary is simply written on top of it, requiring ^L to clean up the summary listing. This is only sometimes, not always, and I have tried changing TERM to vt100 with no effect (it is the default xterm). I have other machines I ssh into and use mutt on them and never have seen these problems, either using ssh on this Mac or on other computers. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & rocket surgeon / [EMAIL PROTECTED] GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o
Re: Mutt tty problems on Mac OS X 10.5.4 and mutt 1.5.18
I'm using pretty much the same combination without any trouble. One key point is to make sure that mutt and the terminal agree about the terminal emulation (try xterm-color) and the character set (try utf-8). In Terminal.app, use the Advanced tab in the settings dialogue to change these points. Regards, -- Thomas Roessler <[EMAIL PROTECTED]> On 2008-08-19 15:02:48 -0700, [EMAIL PROTECTED] wrote: > From: [EMAIL PROTECTED] > To: mutt-users@mutt.org > Date: Tue, 19 Aug 2008 15:02:48 -0700 > Subject: Mutt tty problems on Mac OS X 10.5.4 and mutt 1.5.18 > X-Spam-Level: > X-Bogosity: Ham, tests=bogofilter, spamicity=0.00, version=1.1.6 > > I have a relatively new Max Pro Book (Book Pro?) running OS X 10.5.4 > and mutt 1.5.18. Using a standard Terminal with the default TERM > value of xterm, mutt has a terrible time displaying, with two symptom > that I have seen: > > 1. Re: Subject: headers show up in the summary display as lots of ~T > with a few other line noise chars thrown in for good measure. The > original message which starts the thread has its Subject: displayed > properly. I don't think it is the replies being garbled or in > some other character set because all Subject: headers look fine > when I read the actual message. This is always repeatable. > > 2. When you hit SPACE to read the body of a message, then finish and > "q" back to the summary listing, sometimes the previous message > display does not clear first and the summary is simply written on > top of it, requiring ^L to clean up the summary listing. This is > only sometimes, not always, and I have tried changing TERM to > vt100 with no effect (it is the default xterm). > > I have other machines I ssh into and use mutt on them and never have > seen these problems, either using ssh on this Mac or on other computers. > > -- > ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. > Felix Finch: scarecrow repairman & rocket surgeon / [EMAIL PROTECTED] > GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 > I've found a solution to Fermat's Last Theorem but I see I've run out of room > o > >
Re: Mutt tty problems on Mac OS X 10.5.4 and mutt 1.5.18
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, August 19 at 03:02 PM, quoth [EMAIL PROTECTED]: > Using a standard Terminal with the default TERM value of xterm Ugh! Don't do that. Apple's Terminal is NOT an xterm, so telling your applications that it IS an xterm is going to produce bad results (as you've seen). > 1. Re: Subject: headers show up in the summary display as lots of > ~T with a few other line noise chars thrown in for good measure. > The original message which starts the thread has its Subject: > displayed properly. I don't think it is the replies being garbled > or in some other character set because all Subject: headers look > fine when I read the actual message. This is always repeatable. Sounds like mutt's trying to use the line-drawing characters, and your Terminal settings aren't allowing you to. First, in your Terminal Preferences, you need to make sure that it's allowed to "Use bold fonts" and is allowed to "Display ANSI colors". Second, check out what encoding you're using, make sure your LANG environment variable is correct. And finally, set TERM to something useful. "xterm-color" is better, so is "dtterm", both of which can be selected from the pop-up in the Advanced tab of your terminal settings panel, but the best TERM setting for Apple's Terminal is one of the nsterms (get it? NeXTStep Term = nsterm). I use nsterm-16color, and I have a custom nsterm-16color termcap file (search the archives, I posted how to create and install just such a beast). If that's all a bit much for you (and I wouldn't blame you if it is), then you should probably just use a real xterm (install X11 from Apple's install CDs if you haven't already). > 2. When you hit SPACE to read the body of a message, then finish and >"q" back to the summary listing, sometimes the previous message >display does not clear first and the summary is simply written on >top of it, requiring ^L to clean up the summary listing. This is >only sometimes, not always, and I have tried changing TERM to >vt100 with no effect (it is the default xterm). Yeah - those are all essentially symptoms of the same problem. The issue here is this: every terminal uses different "commands" for manipulating its display. Most basic Unix users will never notice because they don't use anything more complicated than "less" (even programs like vi and emacs often default to using slower, more basic terminal commands), but applications like mutt really take advantage of the more advanced terminal features. If mutt thinks your terminal is an xterm (because of your TERM setting), it's going to use the advanced xterm commands defined in your xterm termcap file (or, more accurately, the curses library that mutt was linked to when it was compiled will do that). Most terminals accept the basic xterm commands, just to be useful, but usually have their own ways of doing the advanced tricks (like selective redisplay or scrolling certain areas of the terminal, and so forth). If your terminal isn't actually an xterm, those advanced commands (that mutt uses a LOT) probably won't work like they're supposed to. In order for such things to work "right", you need a termcap file that describes your terminal's capabilities *accurately*. Does that make sense? But take heart! The beast is conquerable! I've been using Apple's Terminal with mutt for a while now, and (after a fair bit of fiddling to get it just right) it behaves itself just fine. Try setting your TERM to nsterm-16color, and that should help a lot. There are a few things that are still not *quite* right that way, because the nsterm termcap files that Apple ships are a little incomplete, but they can be fixed (see the mutt archives for details). Hope that helps, ~Kyle - -- Always forgive your enemies; nothing annoys them so much. -- Oscar Wilde -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkirS30ACgkQBkIOoMqOI14QfQCg1aX+JD9QukIVYGiSGSvTKL8T yFMAn1Z7jwGyKSiA4modEmZRWPgXPwiR =CJIL -END PGP SIGNATURE-
Re: Mutt tty problems on Mac OS X 10.5.4 and mutt 1.5.18
On Tue, Aug 19, 2008 at 05:38:53PM -0500, Kyle Wheeler wrote: > On Tuesday, August 19 at 03:02 PM, quoth [EMAIL PROTECTED]: > > Using a standard Terminal with the default TERM value of xterm > First, in your Terminal Preferences, you need to make sure that it's > allowed to "Use bold fonts" and is allowed to "Display ANSI colors". > Second, check out what encoding you're using, make sure your LANG > environment variable is correct. > > And finally, set TERM to something useful. "xterm-color" is better, so > is "dtterm", both of which can be selected from the pop-up in the > Advanced tab of your terminal settings panel, but the best TERM > setting for Apple's Terminal is one of the nsterms (get it? NeXTStep > Term = nsterm). I use nsterm-16color, and I have a custom > nsterm-16color termcap file (search the archives, I posted how to > create and install just such a beast). Those were already set. I'll go look for those nsterm entries, maybe that will help. I ried every choice -- ansi dtterm rxvt vt52 vt100 vt102 xterm xterm-color The only difference was white text on a black background (ugh), so I settled on vt102 for now. Here is a copy and paste of sample bogus lines. The first is what I sent, the second is the copy (allstaff expands to, well, everybody), and the third is a response. Yet all three look like the first one once you open up the message itself. I don't think they are picture chars, since search for capital T finds the Ts. F 0.2K Aug 18 To allstaff Pies F 0.8K Aug 18 To allstaff ?~T~\=> + 0.7K Aug 18 Karen?~T~T?~T~@> I poked around trying to find /etc/termcapp and /etc/terminfo, no luck. There are others elsewhere, but Terminal seems to have a very limited subset of terminal types, so I didn't put any more time into them. I have been using mutt for who knows how many years now. I have sometimes had problems on other systems, real Unixes, and had to switch among xterm, rxvt, and vt100 in both xterm and rxvt to find working combinations. I may end up having to install the real xterm or rxvt here too, but I'd prefer to customize this PC as little as possible like that. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & rocket surgeon / [EMAIL PROTECTED] GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o
