Re: wrapping lines ?
On Fri, Jul 12, 2002 at 11:00:42AM -0500, Dave Goodrich wrote: I added this to my .muttrc and it works perfectly. set editor=vim -u $HOME/.vimrc -c ':set textwidth=74 wrapmargin=4' Another way to do it is to have a separate .vimrc for mutt-purposes. I source my original vimrc, and keep my mutt .vimrc in the $HOME/.mutt/ directory (along with all other mutt configuration -- I have a bunch of mail-specific macros/bindings set up in vim and specifying those on the set editor= command line would be hell). /db
Re: wrapping lines ?
Derrick 'dman' Hudson wrote: You can actually set many mutt specific options to your VIM this way. with some versions of vim, you can also do something like: :au VimEnter mutt-* set tw=72 wrap nosmartindent :au VimEnter mutt-* syntax on (this will apply the options to filenames starting with mutt-) Even better, IMO : augroup Mail au! au FileType mail set tw=70 fo=tcrq2 nomodeline au FileType mail set comments+=n:\|,n:%,n:\: clear the old sig and go back to the beginning of the buffer au BufRead /tmp/mutt* normal :g/^| -- $/,/^$/-1d gg augroup END will 'FileType' (or ft) work with versions of vim prior to 6.x though? -- Will Yardley input: william hq . newdream . net .
Re: Wrong Signature with GPG - gpg.rc
Hi, * Phil Gregory [EMAIL PROTECTED] [02-07-12 01:55]: * Thorsten Haude [EMAIL PROTECTED] [2002-07-11 23:24 +0200]: A lot of the mails i have problems with are form David (no GMX). IIRC, the last time a thread came up where people were having problems in David's emails not verifying, the problem was traced to an MTA that was improperly quoting/unquoting the leading dots in his attribution line. Could you point me to the thread or could you suggest some keywords to google for? Thorsten -- Sometimes it seems things go by too quickly. We are so busy watching out for what's just ahead of us that we don't take the time to enjoy where we are. - Calvin
Re: Wrong Signature with GPG - gpg.rc
Hi, * Rocco Rutte [EMAIL PROTECTED] [02-07-11 23:41]: * Thorsten Haude [02-07-11 23:25:41 +0200] wrote: * Rocco Rutte [EMAIL PROTECTED] [02-07-11 22:29]: * Thorsten Haude [02-07-11 22:10:53 +0200] wrote: * Rocco Rutte [EMAIL PROTECTED] [02-07-11 21:33]: A lot of the mails i have problems with are form David (no GMX). I checked some others with the same problem, also no GMX. To clear things up: GMX on the receiving and not on the sending side. I see. That's no problem here. I sure tried to follow that thread but David's mails are much harder to read than the others. Because of the quoting? ;-) His tips entirely dealed with GPG. I can look it up and tell you the message-id. Yup, the quoting. I read mails by color, and David's are uncolored but much more bumpy than the average tofu mail. You can easily add '%' to the list of known quoting character to make his mails colored, too. I know. What I don't know is why he is doing it in the first place, esp. because otherwise he doesn't seem to try to be a pita, quite the contrary. What I see is this: [-- PGP output follows (current time: Don 11 Jul 2002 23:06:04 CEST) --] gpg: Warnung: Sensible Daten könnten auf Platte ausgelagert werden. gpg: Unterschrift vom Son 09 Jun 2002 19:12:09 CEST, DSA Schlüssel ID 7B9F4700 gpg: FALSCHE Unterschrift von David T-G [EMAIL PROTECTED] [-- Ende der PGP-Ausgabe --] Same here (in English, of course). After repairing what GMX broke I don't get any of these anymore. What I still have is that GPG says it's okay while mutt claims it isn't. I can't see how this could happen (according to the documented GPG return codes). So I seem to have the GMX problem without GMX. Could you tell me what exactly I should be looking for in the mboxes? Could you send be your solution? What are the effects of the problem you still have? All I could see here is that the status column is not changed from 's' to 'S'. It would be really interesting to compare the raw message of one you can't verify to one somebody else can. What raw message? So nothing about verbose GPG output. With 'verbose' I mean what we get. S/MIME produces only a one-liner. What would be verbose the way you think of? We have two cases: One is verified by GPG but not by Mutt, the other one is rejected by both GPG and Mutt. In the first case, you can verify the signature yourself with the verbose output of GPG displayed by Mutt, in the second case you can't. Thanks for your time, Thorsten -- When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. - Edmund Burke
Re: odd behavior -- collapse-all, sorting by thread
Derrick 'dman' Hudson ([EMAIL PROTECTED]) muttered: folder-hook lists.* collapse-all # collapse all threads The other problem is that line causes a collapse-all command not found message, and doesn't actually do anything folder-hook lists push \eV HTH, Michael -- MSDOS didn't get as bad as it is overnight -- it took over ten years of careful development. (By [EMAIL PROTECTED]) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: Wrong Signature with GPG - gpg.rc
Hi, * Derrick 'dman' Hudson [EMAIL PROTECTED] [02-07-12 21:03]: On Thu, Jul 11, 2002 at 10:29:47PM +0200, Rocco Rutte wrote: | * Thorsten Haude [02-07-11 22:10:53 +0200] wrote: | Could you tell more about this? How did you identify the | broken MTA and what did you do to fix it? | | Someone else found out that GMX escapes 'from' at the | beginning of a line to 'from' which was the reason why I | could not verify a few mails. It's a short sed/python/perl | solution to remove it again. As I said, a few still remain. Actually, that MDA MUST do that mangling, or else your mbox will be corrupted. That's the problem with mbox. As a workaround, the PGP/MIME RFCs recommend that the sending MUA use quoted-printable, and escape all From_ lines before transmitting the message. So the sending MUA (Mutt) doesn't? I use maildir as my delivery format, so no message mangling is needed. I tried Maildir once, but it was abysmally slow here. Thorsten -- I say, if your knees aren't green by the end of the day, you ought to seriously re-examine your life. - Calvin
Re: Wrong Signature with GPG - gpg.rc
Hi, * Thorsten Haude [02-07-13 15:24:58 +0200] wrote: * Rocco Rutte [EMAIL PROTECTED] [02-07-11 23:41]: So I seem to have the GMX problem without GMX. Could you tell me what exactly I should be looking for in the mboxes? Could you send be your solution? My solution is to run the body of every mail through: sed 's/^from/from' and sed 's/^From/From' But that won't help you. If you like I can post Gerhard Häring's Python solution, too (he tracked the problem down to GMX). What are the effects of the problem you still have? All I could see here is that the status column is not changed from 's' to 'S'. Right, that's the only effect left after commenting out the two lines of code. It would be really interesting to compare the raw message of one you can't verify to one somebody else can. What raw message? The part of the mbox because allthough the decoded messages may be the same, the raw encoded need not. We have two cases: One is verified by GPG but not by Mutt, the other one is rejected by both GPG and Mutt. The second case is solved for me since those mails made the broken GMX mbox parser react. The first case is what I'm talking about. What I have to mention is that I noticed (when I first noticed the problem) all such mails to non- PGP/MIME mails. Maybe this is important. I had a procmail rule (from mutt documentation) which removes the content- type 'plain' and sets something more suitable. I removed it (because of pgp_check_traditional) but the majority still has inline signatures. Shouldn't this discussion be off list? bye, Rocco
Re: Wrong Signature with GPG - gpg.rc
Hi, * Derrick 'dman' Hudson [02-07-13 00:12:42 +0200] wrote: On Thu, Jul 11, 2002 at 10:29:47PM +0200, Rocco Rutte wrote: | * Thorsten Haude [02-07-11 22:10:53 +0200] wrote: | Could you tell more about this? How did you identify the | broken MTA and what did you do to fix it? | Someone else found out that GMX escapes 'from' at the | beginning of a line to 'from' which was the reason why I | could not verify a few mails. It's a short sed/python/perl | solution to remove it again. As I said, a few still remain. Actually, that MDA MUST do that mangling, or else your mbox will be corrupted. No, the parser is just broken. No matter why a piece of software changes message bodies, changing bodies is always a bad idea since it breaks more things than it attempts to repair. That's the problem with mbox. I don't think GMX uses mbox internally. But even if they did, there're other possibilities than to change bodies. The 'Content-Length' header is just one. Not to store mails in mbox another. The most simple solution is, IMHO, just to set a Content- Length header and further parse a From_ line in the message body. As a workaround, the PGP/MIME RFCs recommend that the sending MUA use quoted-printable, and escape all From_ lines before transmitting the message. Well, such issues require software authors to have lots of knowledge of what exactly they're dealing with. There're MUA which even can't handle threading or header encoding. Not talking about escaping From_ lines in bodies. Mutt not only is great from an ordinary user's point of view because of its configurability. It also does correct header encoding, threading and MIME handling. Including such cool features like escaping From_ lines and leading dots. bye, Rocco
Re: Wrong Signature with GPG - gpg.rc
Hi, * Thorsten Haude [02-07-13 15:24:59 +0200] wrote: [ QP encode mails if From_ lines in body ] So the sending MUA (Mutt) doesn't? Mutt does if $encode_from is set. bye, Rocco
Re: wrapping lines ?
On Sat, Jul 13, 2002 at 04:16:02AM -0700, Will Yardley wrote: | Derrick 'dman' Hudson wrote: | | You can actually set many mutt specific options to your VIM this way. | | with some versions of vim, you can also do something like: | | :au VimEnter mutt-* set tw=72 wrap nosmartindent | :au VimEnter mutt-* syntax on | | (this will apply the options to filenames starting with mutt-) | | Even better, IMO : | | augroup Mail | au! | au FileType mail set tw=70 fo=tcrq2 nomodeline | au FileType mail set comments+=n:\|,n:%,n:\: | clear the old sig and go back to the beginning of the buffer | au BufRead /tmp/mutt* normal :g/^| -- $/,/^$/-1d gg | augroup END | | will 'FileType' (or ft) work with versions of vim prior to 6.x though? I'm pretty sure it does. The difference is that vim itself has less automagic based on filetypes built-in. It can still detect a lot of files (by extension or beginning content). -D -- Windows, hmmm, does it come with a GUI interface that works or just pretty blue screens? http://dman.ddts.net/~dman/ msg29609/pgp0.pgp Description: PGP signature
Re: odd behavior -- collapse-all, sorting by thread
On 07/12/02 22:53 -0500, Derrick 'dman' Hudson wrote: I notice some really odd behavior in mutt. I have it set up with some folder-hooks to sort by threads in all my mailing list folders. This works fine, _except_ for one particular list *iff* I don't have the line folder-hook lists.* collapse-all # collapse all threads in my .muttrc. (remove that line, and the spamassassin list is not threaded, put it in and it is). What can I look for to determine why all but the one list are properly threaded without that line? I've found that folder hooks are sensitive to the order they are executed. I'm not quite certain if this addresses your question, but here's what I've got in my ~/.muttrc: folder-hook =mbox 'push odendl~Nenter' folder-hook =outbox 'push odend' folder-hook =Search 'push odend' folder-hook outbox 'set index_format=%4C %Z %d %-20.20t (%3l) %s' folder-hook Search 'set index_format=%4C %Z %D %-20.20t %-20.20f (%3l) %s' folder-hook Search 'push odend' folder-hook =CGO_Chorus 'push odend' folder-hook =My_Posts 'push odend' folder-hook =My_Replies 'push odend' set sort=threads set sort_aux=subject folder-hook . 'push otescVhome' # NOTE: Need to set specific mailbox hook BEFORE setting default. See my note to myself above. I found that I needed to set all the folders where I wanted the non default behavior, e.g. folder-hook . BEFORE the default is set. Otherwise, it didn't work. HTH. John
Re: how to use the ISP''s smtp server directly
On Fri, 12 Jul 2002, Derrick 'dman' Hudson wrote: [..] http://www-dt.e-technik.uni-dortmund.de/~ma/postfix/vsqmail.html Postfix certainly seems to blow the others away. FWIW I like exim the best and postfix next. I've heard too many horror stories about sendmail, and read too much of djb's attitude. (also exim has some capabilities that postfix doesn't) My ISP uses Exim and I rather like the level of control they've given me for bouncing messages, forwarding mail, using SpamAssassin, etc. Doing this at the ISP level saves wasting my own bandwidth and CPU cycles. I wonder how well Exim performs when compared to Postfix. I'm searching for benchmarking info again now. ;) Thanks for that URL btw. :) -- Lee J. Moore [EMAIL PROTECTED] Benefit the community and reply to the list msg29611/pgp0.pgp Description: PGP signature
Re: Wrong Signature with GPG - gpg.rc
Hi, * Thorsten Haude [02-07-13 15:24:58 +0200] wrote: We have two cases: One is verified by GPG but not by Mutt, Well, I've been asking in a de.ALL newsgroup for help on this issue. The solution (which works, whhooo! ;-) is: + set pgp_good_sign=^\\[GNUPG:\\] VALIDSIG + add '--status-fd=2' to the following commands: pgp_decode_command pgp_verify_command pgp_decrypt_command The disadvantage is that this extends the GPG output with status output. This contains [GNUPG:] VALIDSIG ... if a signature is valid and this output matches $pgp_good_sign. Maybe this isn't new since the value for $pgp_good_sign is Debian-only, what I didn't know is that I have to add '--status-fd=2' to those commands. I'm thinking about sending a mail to mutt-dev with a patch to suggest including it in the official release. It definitely looks better than the ugly hack: ,[ /tmp/mutt-1.4/contrib/gpg.rc ]- | # pattern for good signature - may need to be adapted to locale! | | # set pgp_good_sign=^gpg: Good signature from | | # OK, here's a version which uses gnupg's message catalog: | set pgp_good_sign=`gettext -d gnupg -s 'Good signature from ' | tr -d ''` `- Left are mails which cannot be verified at all. And I guess this is not mutt-related. bye, Rocco
Re: [OT] Re: how to use the ISP''s smtp server directly
Hi, * Charles Cazabon [02-07-11 20:28:47 +0200] wrote: qmail configuration is even easier. http://mandree.home.pages.de/qmail-bugs.html bye, Rocco
Re: odd behavior -- collapse-all, sorting by thread
On Sat, Jul 13, 2002 at 12:25:33PM -0400, John P Verel wrote: | On 07/12/02 22:53 -0500, Derrick 'dman' Hudson wrote: | | I notice some really odd behavior in mutt. I have it set up with some | folder-hooks to sort by threads in all my mailing list folders. This | works fine, _except_ for one particular list *iff* I don't have the | line | folder-hook lists.* collapse-all # collapse all threads | in my .muttrc. (remove that line, and the spamassassin list is not | threaded, put it in and it is). What can I look for to determine why | all but the one list are properly threaded without that line? | | I've found that folder hooks are sensitive to the order they are | executed. Yes, that's as documented. That gives you control over the precedence of commands. | I'm not quite certain if this addresses your question, but here's | what I've got in my ~/.muttrc: | # NOTE: Need to set specific mailbox hook BEFORE setting default. | | See my note to myself above. I found that I needed to set all the | folders where I wanted the non default behavior, e.g. folder-hook . | BEFORE the default is set. Otherwise, it didn't work. I do have a default hook, and it is first. I want it that way so that the specific ones override it (setting $index_format, and also $sort). So I went through all my folder-hooks again ... DOH! The relevant part is like this (the bad folder is 'lists/spamassassin') folder-hook lists.* set sort=threads folder-hook spamset sort=subject Well, duh, mutt did exactly what I told it to, just not what I _meant_ to tell it to :-). Hmm, I also noticed that when I put the (erroneous) collapse-all back in, the push EscV didn't work any more (thanks to both of you for that tip!). Apparently mutt stops processing folder hooks when an error is encountered, thus it short-circuited the sorting by subject for the SA folder. I just fixed it by prepending the spam rule with junk/.* since it is a subdirectory of =junk. -D -- But As for me and my household, we will serve the Lord. Joshua 24:15 http://dman.ddts.net/~dman/ msg29614/pgp0.pgp Description: PGP signature
Re: how to use the ISP''s smtp server directly
On Sat, Jul 13, 2002 at 03:39:16PM +0100, Lee J. Moore wrote: | On Fri, 12 Jul 2002, Derrick 'dman' Hudson wrote: | | [..] | http://www-dt.e-technik.uni-dortmund.de/~ma/postfix/vsqmail.html | | Postfix certainly seems to blow the others away. It does seem that way. | FWIW I like exim the best and postfix next. I've heard too many | horror stories about sendmail, and read too much of djb's attitude. | (also exim has some capabilities that postfix doesn't) | | My ISP uses Exim and I rather like the level of control they've | given me for bouncing messages, forwarding mail, using | SpamAssassin, etc. Doing this at the ISP level saves wasting my | own bandwidth and CPU cycles. I wonder how well Exim performs | when compared to Postfix. I'm searching for benchmarking info | again now. ;) Reread the above URL. It compares postfix, exim, qmail, and sendmail. It seems to indicate that exim is in second place. However, that benchmark is now outdated since exim is at version 4.05 (it used 3.33). | Thanks for that URL btw. :) You're welcome. I got it from the postfix-users list. -D -- Reckless words pierce like a sword, but the tongue of the wise brings healing. Proverbs 12:18 http://dman.ddts.net/~dman/ msg29615/pgp0.pgp Description: PGP signature
how not to encrypt
Sometimes mutt thinks it is supposed to encrypt a message. This is fine since I can tell it not to, except for when I forget to. The problem begins when I press 'y' in the compose menu. Mutt asks for a key to encrypt with, but I might not have a public key for that person. (this really happened a few minutes ago) I really wanted to send the message plain-text, but I couldn't find any command to make mutt cancel the encryption. I ended up using my own key, then forwarding it from my =Sent folder without encrypting it. So, my question is : After pressing send in the compose menu with encryption selected, how can I cancel out of the pick a key menu? -D -- 640K ought to be enough for anybody -Bill Gates, 1981 http://dman.ddts.net/~dman/ msg29616/pgp0.pgp Description: PGP signature
enhanced list support idea
Problem : Sometimes a message received via a mailing list, but doesn't mention the list in any of the recipient headers. (eg a member bounced an off-list reply back to the list) Mutt's list-reply function doesn't recognize any lists in that case. Solution (my idea) : For MLMs that include a List-Post: header, I think it would be useful if mutt would (or could) use that to derive the address of the list. I can think of several ways of handling this -- 1) use List-Post: by default. Doesn't require setting 'lists'. 2) use List-Post: if no 'lists'/'subscribe' addresses are found using current methods 3) use List-Post: in addition to current method 4) a configuration option to choose from the above. Do people think this is a good idea? Can it be added to the wishlist? Is it worthwhile if I managed to find time to make a patch, or would I be on my own to maintain it for each new release? -D -- What good is it for a man to gain the whole world, yet forfeit his soul? Or what can a man give in exchange for his soul? Mark 8:36-37 http://dman.ddts.net/~dman/ msg29617/pgp0.pgp Description: PGP signature
Re: how not to encrypt (includes version)
On Sat, Jul 13, 2002 at 07:55:44PM -0500, Derrick 'dman' Hudson wrote: | So, my question is : | After pressing send in the compose menu with encryption | selected, how can I cancel out of the pick a key menu? Sorry, I had a brain fart. I'm using version 1.4i. -D PS. from the choices in my random .sig, I'll choose 'D' :-) -- A)bort, R)etry, D)o it right this time http://dman.ddts.net/~dman/ msg29618/pgp0.pgp Description: PGP signature
sort options -- threads/date-received , in reverse order
version: 1.4i I want to try a new sort order for my mailling list folders. I am currently using 'sort=threads, sort-aux=date-received'. I've tried adding 'reverse-' to the beginning of each of those, but it isn't the effect I want. What I would like to try is 1) first group the messages according to the thread they are in 2) for each thread, sort the thread itself with date-received 3) order the threads (relative to other threads) in reverse-date-received order Basically I want the same thing I have now, but to reverse the order of the threads, treating each thread as an autonomous unit. The reverse-threads method and the reverse-date-received methods do this, but _also_ invert the contents of each thread. In other words, each thread will be normal (per my current setup), but with the newest thread on top, and so on. Is it possible to achieve what I want with the current code? If not, is this a sensible feature to add to the wishlist? TIA, -D -- There are six things the Lord hates, seven that are detestable to him : haughty eyes, a lying tongue, hands that shed innocent blood, a heart that devises wicked schemes, feet that are quick to rush into evil, a false witness who pours out lies and a man who stirs up dissension among brothers. Proverbs 6:16-19 http://dman.ddts.net/~dman/ msg29619/pgp0.pgp Description: PGP signature
Re: sort options -- threads/date-received , in reverse order
Hi, * Derrick 'dman' Hudson [02-07-14 03:11:37 +0200] wrote: I want to try a new sort order for my mailling list folders. I am currently using 'sort=threads, sort-aux=date-received'. I've tried adding 'reverse-' to the beginning of each of those, but it isn't the effect I want. To answer your question, 'set sort=threads' and 'set sort_aux=reverse-date-received'. What I would like to try is 1) first group the messages according to the thread they are in set sort=threads 2) for each thread, sort the thread itself with date-received 2) doesn't make sence since a thread is already sorted by 1) (according to headers). 3) order the threads (relative to other threads) in reverse-date-received order set sort_aux=reverse-date-received bye, Rocco
Re: how not to encrypt
On Sat, Jul 13, 2002 at 07:55:44PM -0500, Derrick 'dman' Hudson wrote: | So, my question is : | After pressing send in the compose menu with encryption | selected, how can I cancel out of the pick a key menu? Mark Reed suggested, off-list, to try Ctrl-G. Ctrl-G works, but isn't mentioned in the list of keys/commands when I press '?'. (at least I know what to use now) -D -- He who walks with the wise grows wise, but a companion of fools suffers harm. Proverbs 13:20 http://dman.ddts.net/~dman/ msg29621/pgp0.pgp Description: PGP signature
Re: bouncing w/ mutt-1.3.28i
Derrick, et al -- ...and then Derrick 'dman' Hudson said... % % On Fri, Jul 12, 2002 at 08:38:57PM -0700, Will Yardley wrote: % | Derrick 'dman' Hudson wrote: % | On Fri, Jul 12, 2002 at 09:18:21PM -0500, David T-G wrote: % | % | When you bounce a message, mutt takes the message as it was received by % | you and hands it back to sendmail with a new addressee so that sendmail ... % | bounce message to go to you if the bounce failed, rather than to the % | sender of the original message % % I agree. Just don't be surprised when it happens because someone said % nothing is changed :-). Yeah. Good point. % % Oh, actually, the entire envelope is changed. I think David meant to % write headers -- % nothing in the message headers (or body) is changed, and new % headers are added Hmmm... Perhaps I've misunderstood envelope; I thought that it was all of the headers. Anyway, you've all done a good job of further clarifying and to my edification as well :-) % % -D HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg29622/pgp0.pgp Description: PGP signature
Re: sort options -- threads/date-received , in reverse order
On Sun, Jul 14, 2002 at 03:22:32AM +0200, Rocco Rutte wrote: Thanks for your response. | * Derrick 'dman' Hudson [02-07-14 03:11:37 +0200] wrote: | | What I would like to try is | 1) first group the messages according to the thread they are in | | set sort=threads | | 2) for each thread, sort the thread itself with date-received | | 2) doesn't make sence since a thread is already sorted by |1) (according to headers). | | 3) order the threads (relative to other threads) in | reverse-date-received order | | set sort_aux=reverse-date-received That doesn't achieve the effect I want. Here is an example : ~~~ with sort_aux=reverse-date-received 91 r L Jul09 Kurt Lieber (1.2K) Re: return-path user -- local vs. smtp 92 L Jul10 Alexander Saboure(1.3K) |- 93 L Jul10 Philip Hazel (0.4K) | `- 94 L Jul10 Alexander Saboure(0.2K) | |- 95 L Jul10 Alexander Saboure(0.9K) | `- 96 L Jul10 Philip Hazel (0.7K) |- 97 F Jul09 Derrick 'dman' Hu(0.8K) `- ~~~ Notice how, at the same thread level, the older message is at the bottom. (in particular, compare messages 92, 96, and 97. What I want is for that thread to look like this, but still have indices 91-97 (that is, be near the top of the folder) : ~~~ example with sort_aux=date-received 554 r L Jul09 Kurt Lieber (1.2K) Re: return-path user -- local vs. smtp 555 F Jul09 Derrick 'dman' Hu(0.8K) |- 556 L Jul10 Philip Hazel (0.7K) |- 557 L Jul10 Alexander Saboure(1.3K) `- 558 L Jul10 Philip Hazel (0.4K) `- 559 L Jul10 Alexander Saboure(0.9K) |- 560 L Jul10 Alexander Saboure(0.2K) `- ~~~ Notice how the thread itself is in 'date-received' order. However, I want the threads (eg if I collapse-all and then only count the visible messages) to be reverse-date-received. Does this make sense now? Do you see how what I want is different from 'sort=threads sort_aux=reverse-date-received'? -D -- Better a little with righteousness than much gain with injustice. Proverbs 16:8 http://dman.ddts.net/~dman/ msg29623/pgp0.pgp Description: PGP signature
Re: bouncing w/ mutt-1.3.28i
On Sat, Jul 13, 2002 at 10:08:52PM -0500, David T-G wrote: | ...and then Derrick 'dman' Hudson said... | % Oh, actually, the entire envelope is changed. I think David meant to | % write headers -- | % nothing in the message headers (or body) is changed, and new | % headers are added | | Hmmm... Perhaps I've misunderstood envelope; I thought that it was all | of the headers. No, the envelope normally isn't in the headers at all. It will only appear there if you configure your MTA to add 'Return-Path:' and 'Envelope-To:' headers. Here's an example of an SMTP session (eg one for a message bounced by mutt), but with some of the longer content remove for the sake of this mailing list. 220 ns.gbnet.net ESMTP EHLO dman.ddts.net 250-ns.gbnet.net 250-PIPELINING 250 8BITMIME MAIL FROM:[EMAIL PROTECTED] 250 ok RCPT TO:[EMAIL PROTECTED] 250 ok DATA 354 go ahead Received: (all received headers remain, but snipped in this example) Date: Sat, 13 Jul 2002 22:08:52 -0500 From: David T-G [EMAIL PROTECTED] To: Undisclosed-Recipient:; Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.4i Precedence: bulk List-Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe Subject: Re: bouncing w/ mutt-1.3.28i Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=Ah9ph+G2cWRpKogL [body of the message] . 250 OK QUIT 221 ns.gbnet.net closing connection In this case, the envelope sender is [EMAIL PROTECTED] and the envelope recipient is [EMAIL PROTECTED]. The envelope is the data in the SMTP dialog. The headers are part of the DATA segment of the SMTP transfer. As far as SMTP is concerned, headers and body are all part of the message and are a (mostly) a black box. The envelope and the headers often correspond, but don't always (and in the case of spam, often have no relationship at all). -D -- If you hold to [Jesus'] teaching, you are really [Jesus'] disciples. Then you will know the truth, and the truth will set you free. John 8:31-32 http://dman.ddts.net/~dman/ msg29624/pgp0.pgp Description: PGP signature
