Re: answer to sender
Hi everyone and sorry to come back with this issue, it's starting to drive me crazy (I had to manually write the correct From: field after hitting L ...). I think my problem is related to my profiles, I have 5 of them. I put all the configuration files in ~/.mutt/profiles/ and source them from ~/.muttrc. First question, should those file contain any my_hdr From: ? Right now I have unmy_hdr * my_hdr From: <[EMAIL PROTECTED]> I tried to remove them and replace with set realname=steve set [EMAIL PROTECTED] set use_from=yes but after doing that, a simple r will put twice the same address in To: and in From:, which is rather cumbersome... I've been fiddling around with the configuration variables for a while now, and reading the manual.txt also, but each time I get a different result (which is normal you'll tell me) and still not what I want. I'd like now to follow a better troubleshooting method, i.e following step by step what's happening but I have not found any way to do this. Any ideas ? Thanks for any help and have a nice weekend. Steve Le ven, avr 04, 2008 at 02:33:32 +0200, Michael Tatge ([EMAIL PROTECTED]) a écrit : > Lignes : 25 > > * On Fri, Apr 04, 2008 Steve ([EMAIL PROTECTED]) muttered: > > I have just purchased a new email account, let's say [EMAIL PROTECTED] > > When they send me a message to this new address, I would like that > > when hitting r, the reply uses the new address as the From field. But > > it doesn't. > > See alternates, reverse_name > Define a regex matching your accounts. And set $reverse_name. > > > What I get is no From field at all. > > See $from, $use_from. Also $use_envelope_from. > > HTH, > > Michael > -- > This kernel runs like a dessicated slug if you have more than 2G of memory > due to a 32-bit overflow. > > -- Andrew Morton, on Linux 2.6.8-rc1-mm1 > > PGP-Key-ID: 0xDC1A44DD > Jabber: [EMAIL PROTECTED] >
Need for help about the "/root/sent is not a mailbox" issue
I have asked some questions before about the non-sending-big-attachments. Many kind friends helped me. However, though I'm still working for a solution, some weird thing happened. My disk is full, and I am really afraid that's due to my several times 'test sending'. so maybe the mutt just put all the mails into /root/sent and they had not really been sent at all though ... Then, my administrator helped me to "clear" the /root/sent, and the disk storage just be okay again But then, I cannot even send anything now. It told me that: /root/sent is not a mailbox But why? What's a "mailbox" ? Can anyone give me some tips? Thanks very much in advance! -- Blog in Chinese http://www.awflasher.com/blog/ Blog in English http://www.ifgogo.com/
Re: Need for help about the "/root/sent is not a mailbox" issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday, June 14 at 08:34 PM, quoth Awflasher(GuoQirui): >But then, I cannot even send anything now. It told me that: > > /root/sent is not a mailbox > >But why? What's a "mailbox" ? Can anyone give me some tips? Thanks >very much in advance! A mailbox is a place to store messages, and mutt can understand four types of mailbox: mbox, maildir, MMDF, and MH. Each kind of mailbox is structured in a specific way to facilitate the operations that you want mailboxes to perform (i.e. delivering new messages and reading random messages). By "facilitate", I mean that in most cases the internal structure is absolutely required in order to avoid corrupting messages. A plain empty folder is NOT a valid mailbox. If you're curious, I'll explain the types of mailboxes that mutt supports. An mbox is a flat text file. There are requirements on the contents of the file and the format of the messages so that each message can be safely distinguished from the others. Message tags (e.g. "replied", "new", "seen", etc.) require modifying the content of the message. An MMDF mailbox is similar to an mbox, but has different methods of distinguishing distinct messages. Again, tagging a message requires modifying the content of the message. An MH mailbox is a folder containing email messages in separate files. This solves several problems associated with mbox, but adds different ones. For example, in order to prevent concurrent message deliveries from writing to the same file, a special non-message file is stored in the directory with the name ".mh_sequences" which has a special internal format. Again, tagging a message requires modifying the content of the message. A Maildir mailbox is like an MH mailbox, but has a unique way of delivery that makes unique filenames easier to generate without locking. Its structure is a folder containing three sub-folders with specific names (i.e. "cur", "new", and "tmp"). Message tags in a Maildir are appended to the message's filename. ~Kyle - -- ...wherever the people are well-informed, they can be trusted with their own government. -- Thomas Jefferson -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkhT4MAACgkQBkIOoMqOI16rDQCdEWDTjzA9jevSKFQK4s7bUcn5 TUEAoIX5pkFwv3vxRLCHDapPRMYUFBv0 =lgOb -END PGP SIGNATURE-
Re: Need for help about the "/root/sent is not a mailbox" issue
Kyle thanks! you are really a great person! On Sat, Jun 14, 2008 at 11:16 PM, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Saturday, June 14 at 08:34 PM, quoth Awflasher(GuoQirui): >>But then, I cannot even send anything now. It told me that: >> >> /root/sent is not a mailbox >> >>But why? What's a "mailbox" ? Can anyone give me some tips? Thanks >>very much in advance! > > A mailbox is a place to store messages, and mutt can understand four > types of mailbox: mbox, maildir, MMDF, and MH. Each kind of mailbox is > structured in a specific way to facilitate the operations that you > want mailboxes to perform (i.e. delivering new messages and reading > random messages). By "facilitate", I mean that in most cases the > internal structure is absolutely required in order to avoid corrupting > messages. > > A plain empty folder is NOT a valid mailbox. > > If you're curious, I'll explain the types of mailboxes that mutt > supports. > > An mbox is a flat text file. There are requirements on the contents of > the file and the format of the messages so that each message can be > safely distinguished from the others. Message tags (e.g. "replied", > "new", "seen", etc.) require modifying the content of the message. > > An MMDF mailbox is similar to an mbox, but has different methods of > distinguishing distinct messages. Again, tagging a message requires > modifying the content of the message. > > An MH mailbox is a folder containing email messages in separate files. > This solves several problems associated with mbox, but adds different > ones. For example, in order to prevent concurrent message deliveries > from writing to the same file, a special non-message file is stored in > the directory with the name ".mh_sequences" which has a special > internal format. Again, tagging a message requires modifying the > content of the message. > > A Maildir mailbox is like an MH mailbox, but has a unique way of > delivery that makes unique filenames easier to generate without > locking. Its structure is a folder containing three sub-folders with > specific names (i.e. "cur", "new", and "tmp"). Message tags in a > Maildir are appended to the message's filename. > > ~Kyle > - -- > ...wherever the people are well-informed, they can be trusted with > their own government. >-- Thomas Jefferson > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iEYEARECAAYFAkhT4MAACgkQBkIOoMqOI16rDQCdEWDTjzA9jevSKFQK4s7bUcn5 > TUEAoIX5pkFwv3vxRLCHDapPRMYUFBv0 > =lgOb > -END PGP SIGNATURE- > -- Blog in Chinese http://www.awflasher.com/blog/ Blog in English http://www.ifgogo.com/
Re: inaccurate estimates of message size
On Wed, Jun 11, 2008 at 11:40:01PM -0700, Brendan Cully wrote: > Personally I think the right thing to do is to show the size of the > message, headers and all. I agree... The headers (for example, the subject line) also clearly contain information which is intended to be conveyed to the recipient: they are indeed part of the message. Or, to draw an analogy: The post office does not charge postage based on the printed words in the body of a letter; they charge based on the wieght of the entire parcel... The packing material is considered part of the parcel. :) -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience. pgpzdcAPX1g6Z.pgp Description: PGP signature
":source ~/.muttrc" command weirdly moves message around in index
Suddenly I've discovered that when I try to re-load my .muttrc with the ":source ~/.muttrc" command, the last message in my index (number 920), is re-positioned as number 576. Other messages are also moved around. If I change folders out of the inbox and then back into it, the message-order is restored to normal. What could be causing this? -- // [EMAIL PROTECTED] //
