Re: problem viewing mail
On 9/23/07, Joseph [EMAIL PROTECTED] wrote: ...snip... MAILDIR=$HOME/.maildir##you better make sure it exists Does the maildir exists? I believe MAILDIR should be someting -- Dilip
Creating folders in IMAP - how?
How does one create new folders (as in places to save new mailboxes) when using IMAP? E.g. I want to create a folder called 'howTos' in which I will save several distinct mailboxes called, say, 'build', 'links', etc. If it's of relevance this is on an MS Exchange server with IMAP access. -- Chris Green
Re: Creating folders in IMAP - how?
On Wed Sep 26, 2007 at 12:41:18PM +0100, Chris G wrote: How does one create new folders (as in places to save new mailboxes) when using IMAP? E.g. I want to create a folder called 'howTos' in which I will save several distinct mailboxes called, say, 'build', 'links', etc. If it's of relevance this is on an MS Exchange server with IMAP access. -- Chris Green Use 'c' then '?' to pull up a list of known folders, then use 'C' to create a new one. You may also need to add a list of your mailboxes to .muttrc or source a separate file. For example: # ~/.muttrc source ~/.mutt/mutt_mailboxes # ~/.mutt/mutt_mailboxes mailboxes imap://[EMAIL PROTECTED]/IMAPFolderName1 mailboxes imap://[EMAIL PROTECTED]/IMAPFolderName2 # et cetera ... --- Colby signature.asc Description: Digital signature
Re: More on non-ascii chars in headers
On 25-09-2007, at 21h 35'01, Kyle Wheeler wrote about Re: More on non-ascii chars in headers On Tuesday, September 25 at 11:16 PM, quoth Ionel Mugurel Ciobica: Eyolf =?iso-8859-1?Q?=D8strem?= That is not Unicode. Unicode would be this: | Eyolf =?UTF-8?Q?=C3=98strem?= This is the (safe) way to transfer non-ASCII information over the net. They're *both* safe ways to transfer non-ASCII information over the net. In fact, the iso-8859-1 encoding is probably safer, as more software supports latin-1 encoding than supports utf-8 encoding. Yes, I meant the (Q)mime way is the way to transfer non-ASCII... iso-8859-1 is obsolete. iso-8859-15 is a replacement but more and more people use UTF-8. Although some people still use bare ascii... Ionel
Re: Creating folders in IMAP - how?
On Wed, Sep 26, 2007 at 07:14:40AM -0600, Colby W. wrote: On Wed Sep 26, 2007 at 12:41:18PM +0100, Chris G wrote: How does one create new folders (as in places to save new mailboxes) when using IMAP? E.g. I want to create a folder called 'howTos' in which I will save several distinct mailboxes called, say, 'build', 'links', etc. If it's of relevance this is on an MS Exchange server with IMAP access. -- Chris Green Use 'c' then '?' to pull up a list of known folders, then use 'C' to create a new one. You may also need to add a list of your mailboxes to .muttrc or source a separate file. For example: ... but that creates a mailbox, I want to create a folder in which I can put other mailboxes. Mutt knows about folders (as oppsoed to mailboxes) in IMAP as it marks them in the directory listing with a '+' sign. Aha, but what you can do is create ABC/ABC123 which will create a 'folder' ABC with a mailbox ABC123 in it which is what I want. # ~/.muttrc source ~/.mutt/mutt_mailboxes # ~/.mutt/mutt_mailboxes mailboxes imap://[EMAIL PROTECTED]/IMAPFolderName1 mailboxes imap://[EMAIL PROTECTED]/IMAPFolderName2 I don't seem to need to add any mailboxes commands, navigation once I've created the folders works as I expect. Thanks for the hint in the right direction. -- Chris Green
Re: sorting outgoing mail
Procmail is a delivery agent; it only handles incoming mail. Very true. Ergo, if you /want/ to use procmail to sort outgoing mail, then make it also be incoming mail. Namely, you can BCC yourself, and in your procmail recipes check to see if you are the sender. One downside of doing this though is that if you also BCC others, it won't be reflected in the copy you BCC yourself. -Chip -- Chip Killian http://www.cs.ucsd.edu/~ckillian/ UCSD Graduate Student, Computer Science
Re: sorting outgoing mail
Procmail is a delivery agent; it only handles incoming mail. Automatically sorting outgoing mail (i.e. putting mail into different folders as it is sent) requires send-hooks. While it's true that procmail can act as a delivery agent, it can also filter any mail that you feed into it. If you sent $sendmail to a program that first filters the message, then injects the message to SMTP, you can external outbound message filtering. #!/bin/sh ## ## Use this as $sendmail in mutt ## procmail -p -f [EMAIL PROTECTED] -m $HOME/.procmailrc.outgoing Make sure that .procmailrc.outgoing **always** acts on a message copy using rules beginning with :0 c. Then make sure that the last rule in .procmailrc.outgoing, the one that catches all messages coming into the filter, is like this: :0 | /usr/lib/sendmail -oi -oem -t I haven't tested this approach at all, but it seems like it should work. :) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago Polka music needs to prevail. John Ziobrowski, Polka America Corporation
Re: sorting outgoing mail
* Joseph [EMAIL PROTECTED] [01-01-70 11:34]: Can I use procmail for sorting outgoing mail or I need to use hooks? Yes, you can use procmail via hooks. Write a hook to pipe a copy of your outgoing mail thru a *special* procmailrc containing recipies reflecting your intent. The process would be very similar to a *sandbox* setup to test procmail recipies. 0: !formail procmail -m special.rc Not Tested! an email with some explanation of a sandbox for procmail and a site reference are available: http://wahoo.wahoo.no-ip.org/~pat/sandbox.txt This would be easy to accomplish if the fcc can be a script (I don't know). or, perhaps (also not tested): 0: c | formail procmail -m special.rc 0 | /usr/lib/sendmail -oi -oem -- Patrick Shanahan Plainfield, Indiana, USAHOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://counter.li.org
viewing pdf jpgeg etc attachment
I have a problem with basic setting, it should be straight forward but I am still missing something. I have in a file autoview settings: set mailcap_path=~/.mailcap:/etc/mailcap application/pdf; xpdf %s image/jpeg; kuickshow %s but when I strt mutt I get an error message: Error in /home/joseph/.mutt/autoview, line 8: application/pdf: unknown command Error in /home/joseph/.mutt/autoview, line 9: image/jpeg: unknown command Error in /home/joseph/.mutt/muttrc, line 11: source: errors in /home/joseph/.mutt/autoview muttrc line:11 has only: source ~/.mutt/autoview #Joseph
Re: sidebar patch
On Tuesday, 25 September 2007 at 21:48, Kyle Wheeler wrote: On Tuesday, September 25 at 04:54 PM, quoth Joseph: I've seen an interesting sidebar patch for mutt, though it was just that a patch is not new and was never implemented. I am just curious as to the reason why it was never implemented. Eh? It *was* implemented - that patch is the implementation. If you're asking why it was never added to the mainstream mutt, the answer is a contentious one, but one which can be found by searching the mutt mailing list archives. It was deemed froofy by one of the main mutt developers (http://marc.info/?l=mutt-devm=112118911225394w=2), and heavily broken by one of the others (http://marc.info/?l=mutt-devm=112133798519807w=2). I'm not actually against the idea any more -- just the implementation.
Re: viewing pdf jpgeg etc attachment
=- Joseph wrote on Wed 26.Sep'07 at 12:00:52 -0600 -= I have a problem with basic setting, it should be straight forward but I am still missing something. I have in a file autoview settings: See http://WIKI.mutt.org/?MuttFaq about attachments. -- © 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: viewing pdf jpgeg etc attachment
On Wed, 2007-09-26 at 20:12 +0200, Rado S wrote: =- Joseph wrote on Wed 26.Sep'07 at 12:00:52 -0600 -= I have a problem with basic setting, it should be straight forward but I am still missing something. I have in a file autoview settings: See http://WIKI.mutt.org/?MuttFaq about attachments. It doesn't help! I've followed the instructions from: http://wiki.mutt.org/?MuttFaq/Attachment I put in mailcap: text/html; lynx -stdin -dump -force_html ; copiousoutput in autoview: auto_view text/html and I get an error: Error in /home/joseph/.mutt/mailcap, line 1: text/html: unknown command Error in /home/joseph/.mutt/muttrc, line 13: source: errors in /home/joseph/.mutt/mailcap source: errors in /home/joseph/.mutt/muttrc -- #Joseph
Re: viewing pdf jpgeg etc attachment
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, September 26 at 03:55 PM, quoth Joseph: On Wed, 2007-09-26 at 20:12 +0200, Rado S wrote: =- Joseph wrote on Wed 26.Sep'07 at 12:00:52 -0600 -= I have a problem with basic setting, it should be straight forward but I am still missing something. I have in a file autoview settings: See http://WIKI.mutt.org/?MuttFaq about attachments. It doesn't help! I've followed the instructions from: http://wiki.mutt.org/?MuttFaq/Attachment I put in mailcap: text/html; lynx -stdin -dump -force_html ; copiousoutput in autoview: auto_view text/html and I get an error: Error in /home/joseph/.mutt/mailcap, line 1: text/html: unknown command Error in /home/joseph/.mutt/muttrc, line 13: source: errors in /home/joseph/.mutt/mailcap source: errors in /home/joseph/.mutt/muttrc You're not supposed to source the mailcap file. That is NOT a mutt configuration file, it is a generic file with a specific format that many programs can use. The lines in the mailcap are NOT mutt commands, so mutt cannot understand them in the context of reading its own configuration. As long as the mailcap file is where it's supposed to be (either ~/.mailcap or /etc/mailcap), mutt will find it and use it. ~Kyle - -- No man has a natural right to commit aggression on the equal rights of another, and this is all from which the laws ought to restrain him. -- Thomas Jefferson, July 7, 1786 -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG+tdHBkIOoMqOI14RAu7LAKCwhqGz6vZLV/t10x4AF75lrONhkgCeMgwd 9RXbbxodpSrF5SAsjm54kwk= =pcon -END PGP SIGNATURE-
Re: viewing pdf jpgeg etc attachment
On Wed, Sep 26, 2007 at 01:00:52PM CDT, Joseph [EMAIL PROTECTED] wrote: I have a problem with basic setting, it should be straight forward but I am still missing something. I have in a file autoview settings: set mailcap_path=~/.mailcap:/etc/mailcap application/pdf; xpdf %s image/jpeg; kuickshow %s but when I strt mutt I get an error message: Error in /home/joseph/.mutt/autoview, line 8: application/pdf: unknown command Error in /home/joseph/.mutt/autoview, line 9: image/jpeg: unknown command [...] Where does xpdf and kuickshow reside? If you specify the full path for each command in your mailcap, does that work? -- Eugene
Re: viewing pdf jpgeg etc attachment
On Wed, 2007-09-26 at 17:03 -0500, Kyle Wheeler wrote: -BEGIN PGP SIGNED MESSAGE- [snip] It doesn't help! I've followed the instructions from: http://wiki.mutt.org/?MuttFaq/Attachment I put in mailcap: text/html; lynx -stdin -dump -force_html ; copiousoutput in autoview: auto_view text/html and I get an error: Error in /home/joseph/.mutt/mailcap, line 1: text/html: unknown command Error in /home/joseph/.mutt/muttrc, line 13: source: errors in /home/joseph/.mutt/mailcap source: errors in /home/joseph/.mutt/muttrc You're not supposed to source the mailcap file. That is NOT a mutt configuration file, it is a generic file with a specific format that many programs can use. The lines in the mailcap are NOT mutt commands, so mutt cannot understand them in the context of reading its own configuration. As long as the mailcap file is where it's supposed to be (either ~/.mailcap or /etc/mailcap), mutt will find it and use it. ~Kyle Thanks Kyle yes that worked. Though, it got me confused a bit. I think the command line is totally separate environment when it comes to file association in mutt. In KDE when I click on PDF file I have several choice I can open it with, the default is KPDF. Mutt runs from KDE terminal windows so why can it find a single file association. I have only mailcap in: /home/joseph/.mailcap /etc/mailcap Is KDE file association connected via mime.types files? -- #Joseph
Re: viewing pdf jpgeg etc attachment
On Wed, 2007-09-26 at 17:14 -0500, Eugene wrote: On Wed, Sep 26, 2007 at 01:00:52PM CDT, Joseph [EMAIL PROTECTED] wrote: I have a problem with basic setting, it should be straight forward but I am still missing something. I have in a file autoview settings: set mailcap_path=~/.mailcap:/etc/mailcap application/pdf; xpdf %s image/jpeg; kuickshow %s but when I strt mutt I get an error message: Error in /home/joseph/.mutt/autoview, line 8: application/pdf: unknown command Error in /home/joseph/.mutt/autoview, line 9: image/jpeg: unknown command [...] Where does xpdf and kuickshow reside? If you specify the full path for each command in your mailcap, does that work? /usr/bin/xpdf /usr/kde/3.5/bin/kuickshow these file work from the command line, the same command line I'm starting mutt, so why isn't mutt recognizing them? -- #Joseph
Re: sorting outgoing mail
On 25Sep2007 21:52, Kyle Wheeler [EMAIL PROTECTED] wrote: | On Tuesday, September 25 at 08:29 PM, quoth Joseph: | I know procmail is used to sort an incoming mail but what about outgoing | mail. | Can I use procmail for sorting outgoing mail or I need to use hooks? | | Procmail is a delivery agent; it only handles incoming mail. | Automatically sorting outgoing mail (i.e. putting mail into different | folders as it is sent) requires send-hooks. Well, yes and no. You do have to contrive to hand a copy of the message to procmail, but if you do that it will happily file that copy away for you. I have mutt's sendmail setting set to a shell script that: - sends the message for real - copies the message to a few folders, usually =spool-out I have daemon script watching spool-out that hands messages found there to procmail using the spool-out/.procmailrc file. And lo, my messages are filed. Cheers, -- Cameron Simpson [EMAIL PROTECTED] DoD#743 http://www.cskk.ezoshosting.com/cs/ Perseverance is not a long race; it is many short races one after another. - Walter Elliott
Re: viewing pdf jpgeg etc attachment
On 2007-09-26, Joseph [EMAIL PROTECTED] wrote: On Wed, 2007-09-26 at 17:14 -0500, Eugene wrote: On Wed, Sep 26, 2007 at 01:00:52PM CDT, Joseph [EMAIL PROTECTED] wrote: I have a problem with basic setting, it should be straight forward but I am still missing something. I have in a file autoview settings: set mailcap_path=~/.mailcap:/etc/mailcap application/pdf; xpdf %s image/jpeg; kuickshow %s but when I strt mutt I get an error message: Error in /home/joseph/.mutt/autoview, line 8: application/pdf: unknown command Error in /home/joseph/.mutt/autoview, line 9: image/jpeg: unknown command [...] Where does xpdf and kuickshow reside? If you specify the full path for each command in your mailcap, does that work? /usr/bin/xpdf /usr/kde/3.5/bin/kuickshow these file work from the command line, the same command line I'm starting mutt, so why isn't mutt recognizing them? As Kyle tried to explain, the problem is not that mutt could not find the commands; the problem was that you were trying to have mutt read your mailcap file as a mutt configuration file. Once you fix that problem, mutt should be able to find the viewers (xpdf and kuickshow) just fine. You are correct in assuming that if the viewers can be found from the shell's command line, and you execute mutt from that command line, then mutt should be able to find those viewers. Gary
Re: viewing pdf jpgeg etc attachment
[snip Where does xpdf and kuickshow reside? If you specify the full path for each command in your mailcap, does that work? /usr/bin/xpdf /usr/kde/3.5/bin/kuickshow these file work from the command line, the same command line I'm starting mutt, so why isn't mutt recognizing them? As Kyle tried to explain, the problem is not that mutt could not find the commands; the problem was that you were trying to have mutt read your mailcap file as a mutt configuration file. Once you fix that problem, mutt should be able to find the viewers (xpdf and kuickshow) just fine. Yes, I removed mailcap created in .mutt directory You are correct in assuming that if the viewers can be found from the shell's command line, and you execute mutt from that command line, then mutt should be able to find those viewers. Gary But it doesn't find them. In order for example to view PDF files with xpdf application I have to add to ~/.mailcap: application/pdf; xpdf %s If I don't have this line in there mutt will open PDF file as a text file. Is there a way to automatically generate/update the mailcap file so it will automatically recognized all the extension type type I have associated with mine.type? Updating it manually might not be hard to do but it is time consuming and prone to errors. -- #Joseph
Re: viewing pdf jpgeg etc attachment
On 2007-09-26, Joseph [EMAIL PROTECTED] wrote: [snip Where does xpdf and kuickshow reside? If you specify the full path for each command in your mailcap, does that work? /usr/bin/xpdf /usr/kde/3.5/bin/kuickshow these file work from the command line, the same command line I'm starting mutt, so why isn't mutt recognizing them? As Kyle tried to explain, the problem is not that mutt could not find the commands; the problem was that you were trying to have mutt read your mailcap file as a mutt configuration file. Once you fix that problem, mutt should be able to find the viewers (xpdf and kuickshow) just fine. Yes, I removed mailcap created in .mutt directory You are correct in assuming that if the viewers can be found from the shell's command line, and you execute mutt from that command line, then mutt should be able to find those viewers. But it doesn't find them. In order for example to view PDF files with xpdf application I have to add to ~/.mailcap: application/pdf; xpdf %s If I don't have this line in there mutt will open PDF file as a text file. Is there a way to automatically generate/update the mailcap file so it will automatically recognized all the extension type type I have associated with mine.type? Updating it manually might not be hard to do but it is time consuming and prone to errors. What I meant was that since mutt sees the same PATH that its parent shell sees, mutt will be able to find any program in that PATH as well as the shell can. For mutt to find the proper viewer for an attachment, other things have to be properly configured as well, namely, your mime.types and mailcap files. There is no way to automatically generate a mailcap file. That would require a database of associations between content types and viewers, which is what the mailcap file is. You might be able to find an example mailcap file among the contributions and links at www.mutt.org. Or you could Google for mutt mailcap (without the quotes). Gary
history / save_history params?
So recent versions of mutt seem to have an option to save history; Can anyone tell me the difference between: $save_history and: $history AFAICT, both are set to the value of the number of lines of history to save. I first tried: set save_history set history=99 which didn't work. Setting set save_history=99 seems to work. Does mutt really need both? w
