Re: how to edit as new
On Thu, 04 Dec 2008 at 15:56:32 +0800, bill lam wrote: > Hi All, > I want to know how to call a old message either in sent or inbox and > edit its content and then send it as a new message without the old > message-id. Will the attachment in old message also be included? Esc e, yeah. These are all in the manual. Why don't you check that before asking? -- Rgds, Cherife.
Re: how to edit as new
Hi bill, bill lam <[EMAIL PROTECTED]> wrote: > I want to know how to call a old message either in sent or inbox and > edit its content and then send it as a new message without the old > message-id. Will the attachment in old message also be included? I think you're looking for e aka resend-message. Bye, Jörg. -- Objektivität ist die Wahnvorstellung, Beobachtungen könnten ohne Beobachter gemacht werden – Heinz v. Foerster
Re: Header caching not working
On Thu, Dec 04, 2008 at 08:55:22AM +0100, Sander Smeenk wrote: > Quoting Kyle Wheeler ([EMAIL PROTECTED]): > > > >Could it be, that I have to compile with use_imap option? > > Nah, it should work with other things (e.g. Maildir and POP3). > > Well, I'm stumped. Anyone else have an idea? > > Works for me(TM) > > | Mutt 1.5.17+20080114 (2008-01-14) > | ... > | +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE > | ... > > And this is in my config: > > | set header_cache=/home/sanders/.mutt/header_cache/ > > Does the OP use one monolithic configuration file? > Is he sure this value is set correctly? > Typing ':set ?header_cache' should give results. > Are the permissions on the directory okay? > Can his user create files and/or directories there? > > -Sndr. > -- > | Someone who thinks logically provides a nice contrast to the real world. > | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D The only difference is, that I dont have libidn enabled. Is this setting relevant? I have only one config file, .muttrc. When I type while being in mutt: :set ?header_cache, I get a correct result (/home/szymek/mail/hcache/). I can create files and dirs in ~/mail/hcache. I read somewhere, that libidn for mutt is an optional dependency and has something to do with domain names. Thanks Szymon
Re: how to edit as new
On Thu, 04 Dec 2008, Jörg Sommer wrote: > Hi bill, > > bill lam <[EMAIL PROTECTED]> wrote: > > I want to know how to call a old message either in sent or inbox and > > edit its content and then send it as a new message without the old > > message-id. Will the attachment in old message also be included? > > I think you're looking for e aka resend-message. > Hi, Jörg Thank you! That's what I was looking for. -- regards, GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 唐詩161 溫庭筠 送人東遊 荒戍落黃葉 浩然離故關 高風漢陽渡 初日郢門山 江上幾人在 天涯孤棹還 何當重相見 樽酒慰離顏
multiple interactive mutt instance
I always have a mutt running in screen. Is it save to run another interactive instance of mutt? -- regards, GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 唐詩235 杜甫 八陣圖 功蓋三分國 名成八陣圖 江流石不轉 遺恨失吞吳
Re: Header caching not working
Quoting Szymek ([EMAIL PROTECTED]): > > | +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE > The only difference is, that I dont have libidn enabled. > Is this setting relevant? No. IDN is used for domainnames containing sρεςιαl ςλαrαςτεrs. It has nothing to do with headercaching. Also, your mutt -v output does not have to match ours, it's just about the +USE_HCACHE bit. > I have only one config file, .muttrc. When I type while being in > mutt: :set ?header_cache, I get a correct result (/home/szymek/mail/hcache/). > I can create files and dirs in ~/mail/hcache. In that case, i'm at a loss too. It should just work. To really find out what's happening, you'd have to start using strace, gdb and maybe even dig around in the source. > I read somewhere, that libidn for mutt is an optional dependency > and has something to do with domain names. Correct. -Sndr. -- | He had a photographic memory which was never developed. | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D
Re: multiple interactive mutt instance
Quoting bill lam ([EMAIL PROTECTED]): > I always have a mutt running in screen. Is it save to run another > interactive instance of mutt? Yes, that's safe. Although message flags (could) get messed up between the sessions, nothing bad ever happened to me while running multiple sessions on the same Maildir/. Reloading a mailbox (by re-entering it) fixes the message flags issue. With IMAP i've seen strange things happen. Server errors because mutt tries to open messages which aren't there anymore, etc, but none of this caused major problems for me... -Sndr. -- | Man with hand in pocket feel cocky all day. | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D
Re: multiple interactive mutt instance
On Thu, Dec 04, 2008 at 11:02:46PM +0800, bill lam wrote: > I always have a mutt running in screen. Is it save to run another > interactive instance of mutt? I once read somewhere that that's safe, and I've been doing it for years without any problems. I have three mutt instances running in screen, two configured for different IMAP accounts, one configured to access my local spool file. All three instances also access my mailboxes under ~/Mail. -- Joost Kremers Life has its moments
Re: multiple interactive mutt instance
Thanks Joost & Sander for quick response. I am replying from the second instance of mutt. -- regards, GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 唐詩266 王昌齡 春宮曲 昨夜風開露井桃 未央前殿月輪高 平陽歌舞新承寵 簾外春寒賜錦袍
Re: Header caching not working
On Thu, Dec 04, 2008 at 04:03:07PM +0100, Sander Smeenk wrote: > Quoting Szymek ([EMAIL PROTECTED]): > > > > | +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE > > The only difference is, that I dont have libidn enabled. > > Is this setting relevant? > > No. IDN is used for domainnames containing s??l ??rrs. It > has > nothing to do with headercaching. Also, your mutt -v output does not > have to match ours, it's just about the +USE_HCACHE bit. > > > I have only one config file, .muttrc. When I type while being in > > mutt: :set ?header_cache, I get a correct result > > (/home/szymek/mail/hcache/). > > I can create files and dirs in ~/mail/hcache. > > In that case, i'm at a loss too. It should just work. To really find out > what's happening, you'd have to start using strace, gdb and maybe even > dig around in the source. > > > I read somewhere, that libidn for mutt is an optional dependency > > and has something to do with domain names. > > Correct. > > -Sndr. > -- > | He had a photographic memory which was never developed. > | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D > Hi Thanks all of your folks for the help. I dont have actually the time and the skills to manage such a task like deubugging, so I will leve it the way it is. There are not so many mails in my folders (three hundert is most), so I can live without header caching, too. Best regards Szymon
"Invalid mailbox name" with mutt + Dovecot
Hi all. I have been happily using mutt on various Linux boxes over the years (currently Ubuntu gutsy, mutt 1.5.15). I connect via IMAP to my ISP, pair.com. Two weeks ago pair replaced their IMAP server with a Dovecot installation. I do not know what their old server was. Now, when I attempt to access a mailbox other than my inbox with mutt (something like "=spam"), mutt tells me "invalid mailbox name." I can access INBOX just fine. I have asked pair to look into the problem, but they haven't been able to find the answer, though I think they are still trying. It's getting really annoying to not have access to my various folders to store mail in. Lots of googling has failed to find people with similar problems. Does anyone have any insights? Anything particular I should suggest that my ISP try? Any way I can change my mutt config to play better with Dovecot? Or is it time for a new ISP? Relevant bits of .muttrc: set folder="imaps://misilay.pair.com/../mail" set spoolfile="imaps://misilay.pair.com" My inbox on misilay.pair.com is in /var/mail/jphekman; my other mail folders are in ~/mail/. Thanks, Jessica
Re: "Invalid mailbox name" with mutt + Dovecot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, December 4 at 01:35 PM, quoth Jessica Perry Hekman: > Two weeks ago pair replaced their IMAP server with a Dovecot > installation. I do not know what their old server was. I've used Dovecot for several years, and I love it (S fast!), so these things CAN be made to work! > Now, when I attempt to access a mailbox other than my inbox with > mutt (something like "=spam"), mutt tells me "invalid mailbox name." > I can access INBOX just fine. Note that these are two different things. Your INBOX is your $spoolfile, while $folder is what is used when you use shortcuts like '='. > Relevant bits of .muttrc: > > set folder="imaps://misilay.pair.com/../mail" > set spoolfile="imaps://misilay.pair.com" There's your problem. It looks like the old server was probably UW-IMAP, or something that behaved like it. The difference is that these older IMAP servers give you full filesystem access via IMAP. This has bonuses: it means that each each user can keep their mail hierarchy anywhere they like. The downside is that it requires that the users know where their stuff is stored on the server, and has the potential to give *too much* access. Dovecot, as a security measure, presents the user with a much stricter hierarchy. The user doesn't (generally) get to define where their email is stored; they just get to define what they *call* it. Does that make sense? Let me put it another way: in the old server: ../mail -> ~/mail/ ^ ^--- the user (you) controls THIS `--- ... and consequently defines this In the new server: mail -> somewhere ^ ^-- the user DOESN'T control this (the admin does) `-- but the user DOES control this That gives the sysadmin a lot more flexibility to store your email wherever and however he chooses, as long as he maintains a consistent naming. And he doesn't have to give the imap server full access to the entire filesystem; it's storage can be sequestered. This is *really* helpful for virtual domains (where a single server hosts multiple domains that each have different sets of users). On my personal server, my users have *no* idea where their mail is stored (it's /var/lib/vpopmail/domains/$domain/$user/Maildir/ - user home directories are elsewhere, and dovecot can't touch them). Anyway, if I was setting up a Dovecot server for them, I'd set up a namespace where INBOX is /var/mail/$user (just like it used to be), but where the rest of the storage is somewhere else, like /mailstorage/$user/. You MAY be able to access your ~/mail/ folders, depending on how they set up Dovecot, but the way to discover it is by using mutt's browser. (press c to bring it up) If you're lucky, and they configured Dovecot to look for mailfolders (for ALL users) in ~/mail/, then you would just need to set up your mutt like so: set folder="imaps://misilay.pair.com/" set spoolfile="imaps://misilay.pair.com/INBOX" ~Kyle - -- I prefer to be called "EVIL GENIUS!" -- Jumba, from "Lilo & Stitch" -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkk4K9gACgkQBkIOoMqOI15gUwCg+bZ+fnb+BSx4Q6XiMjALytyD 0YYAn1Sh9lajXEySGBiXoL7bHndZPGRt =3nTi -END PGP SIGNATURE-
Re: "Invalid mailbox name" with mutt + Dovecot
On Thu, Dec 04, 2008 at 01:13:28PM -0600, Kyle Wheeler wrote: > Anyway, if I was setting up a Dovecot server for them, I'd set up a > namespace where INBOX is /var/mail/$user (just like it used to be), > but where the rest of the storage is somewhere else, like > /mailstorage/$user/. You MAY be able to access your ~/mail/ folders, > depending on how they set up Dovecot, but the way to discover it is by > using mutt's browser. (press c to bring it up) If you're > lucky, and they configured Dovecot to look for mailfolders (for ALL > users) in ~/mail/, then you would just need to set up your mutt like > so: > > set folder="imaps://misilay.pair.com/" > set spoolfile="imaps://misilay.pair.com/INBOX" That makes perfect sense. And in fact they DO seem to have decided to have Dovecot save folders in ~/mail, so all I needed to do was to make that small config change. (I futzed with that line in config for so long this afternoon but amazingly never tried just leaving off everything after the hostname.) Thank you so much; my life is now slightly easier than it was an hour ago :) Jessica
send attachment interactively from command line
Some other mua such as thunderbird can be invoked from command line to a send a file as attachment interactively such that it creates a new email with that file as attachment. Other details such recipient, subject or body message can be entered before sending. Is that possible with mutt? Thank you in advance. -- regards, GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 唐詩274 韓翃 寒食 春城無處不飛花 寒食東風御柳斜 日暮漢宮傳蠟燭 輕煙散入五侯家
Re: send attachment interactively from command line
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, December 5 at 01:35 PM, quoth bill lam: > Some other mua such as thunderbird can be invoked from command line to > a send a file as attachment interactively such that it creates a new > email with that file as attachment. Other details such recipient, > subject or body message can be entered before sending. Is that > possible with mutt? What do you mean "interactively"? You want a dialog box? A series of prompts? Or do you just want to be able to pass mutt some flags that specify who to send to? ~Kyle - -- A man cannot be held responsible for what his mind does while he's asleep. -- Jean Luc Picard -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkk43v0ACgkQBkIOoMqOI14iOQCgnGkzB/lAQGvmUNa9a2yUIEma aNYAoK2i5XGtUxXqemPPurw//Y6uV1PM =8iQg -END PGP SIGNATURE-
