Re: A few mutt questions
On Sat, Jan 26, 2008 at 11:10:59AM +0100, Nicolas Rachinsky wrote: folder-hook . unmy_hdr To folder-hook foo my_hdr To: [EMAIL PROTECTED] Works like a charm. Since I have a small Python script which, given a list of subscribed mailing list addresses and their folders, autogenerates the appropriate bits of muttrc and procmailrc, this was easily implemented. --D. signature.asc Description: Digital signature
Re: A few mutt questions
On Sat, Jan 26, 2008 at 02:53:09PM +, Michael Kjorling wrote: Try something like this: set recall=no folder-hook . 'bind index m mail' folder-hook '+mutt-users/?$' 'macro index m mailkill-linemutt-users@mutt.org' Actually I now went with Nicholas' my_hdr approach which works very well. But thanks! --D. signature.asc Description: Digital signature
Re: A few mutt questions
On Sat, Jan 26, 2008 at 04:05:10PM -0600, David Champion wrote: It certainly supports this, but it depends on the mail source itself to say what's read. Mutt can alter these flags, but so can other tools. Well, long story short, I see neither 'N' or 'O' flags. My mail comes from three IMAP accounts via fetchmail, exim, procmail. When I do $ fetchmail tail -f .procmail.log, I see messages like this pouring out: From [EMAIL PROTECTED] Mon Jan 28 09:21:47 2008 Subject: Re: Leopard Migration Hammered Mutt Folder: Lists/mutt/61 3927 which looks correct. When I then start mutt I can find this exact message in the appropriate dir, of course, but it's not marked any different than all the others which I've read during a previous mutt session. AFAIK there are no other programs running that touch my mail. Any hints? --D. signature.asc Description: Digital signature
Re: Leopard Migration Hammered Mutt
On Sun, Jan 27, 2008 at 09:31:17PM CST, Bill [EMAIL PROTECTED] wrote:
Since I would like to add /sw/bin to my /etc/profile I opened it, but only
discovered:
___
# System-wide .profile for sh(1)
if [ -x /usr/libexec/path_helper ]; then
eval `/usr/libexec/path_helper -s`
fi
if [ ${BASH-no} != no ]; then
[ -r /etc/bashrc ] . /etc/bashrc
fi
___
This is not what I expected, and can't think of where I should add /sw/bin/
to my path.
Forget messing with /etc/profile. Did you try my suggestion?
A short time ago, Eugene wrote:
/sw indicates Fink.
http://www.finkproject.org/doc/bundled/install-fast.php
The last command runs a little script to help set up your Unix paths
(and other things) for use with Fink. In most cases, it will run
automatically, and prompt you for permission to make changes. If the
script fails, you'll have to do things by hand.
(If you need to do things by hand, and you are using csh or tcsh, you
need to make sure that the command source /sw/bin/init.csh is executed
during startup of your shell, either by .login, .cshrc, .tcshrc, or
something else appropriate. If you are using bash or similar shells,
the command you need is . /sw/bin/init.sh, and places where it might
get executed include .bashrc and .profile.)
So basically add the line . /sw/bin/init.sh into your ~/.profile or
~/.bash_profile init files. This should add /sw/bin to your PATH, and
set up other Fink-related environment variables as well.
--
Eugene
buffy-size
Hello, i'm using mutt 1.5.17 on FreeBSD 6.2-STABLE-20070808. Because my maildir is on nfs i use the buffy_size patch. This generally works i see new mails in my folders which is okay. I also see new mails in folders which are very old, but maybe this is normal for the first run. Don't konw exactly how this works. Unfortunately when i reopen my mutt it says that the same old mailfolders contains new mails which isn't true. A few weeks ago i used mutt 1.5.14 where this problem doesn't occur. Did i missed something? greetz alex -- We're sysadmins. To us, data is a protocol-overhead.
How to identify unread (new/old) mail -- another bit of info
Hello, mutt still refuses to identify mail that hasn't been read. Even if new mail comes in during a session while the inbox is open. But here's the thing: 1. No MUA is running, mail comes into inbox. 2. I open mutt. All mail shows up as read. 3. I quit mutt. 4. I start Claws-Mail. Inbox shows up with the same messages, of course, but all marked as Unread. 5. Without doing anything else, I quit Claws. 6. I start mutt again, and, lo and behold, the mail is suddenly unread (albeit old). Trying to hunt down the source of this information, I copied the new messages in inbox between step 1 and 2 (from the shell, not an MUA). I then did a diff on the mails in inbox and the saved copy after each of the above steps, trying to find out if the various MUAs do something to the messages to mark them read/unread. At no point did I find any difference. Claws uses a couple of files with a .sylpheed_ prefix in the MH mailboxes, presumably to store such meta-information. But mutt doesn't. The header_cache feature is disabled, or at least that's what I think: $ mutt -D | grep header_cache header_cache= maildir_header_cache_verify is set header_cache_pagesize=16384 $ This is very annoying. I need to see new mail in my inboxes. Does anybody else have a fetchmail/procmail combo sorting stuff into various inboxes under ~/Mail, and how do they manage to mark stuff as new? Thanks, --D. signature.asc Description: Digital signature
Another mutt and gpg question
Hello, encrypting, signing, checking signatures: all works. Sort of. Two hassles: 1. I can't access encrypted mail that I send. When I try to read it, I get Could not copy message. 2. when I receive an encrypted mail, I see a text block of gibberish that I have to manually pipe through GPG externally. Why doesn't mutt auto-detect encrypted mails, like it does with signed mails? Thanks, --D. signature.asc Description: Digital signature
Re: Another mutt and gpg question
* Dan H. [EMAIL PROTECTED] [2008-01-28 14:28 +0100]: Content-Description: kjlkj ??? 1. I can't access encrypted mail that I send. When I try to read it, I get Could not copy message. See the thread starting with [EMAIL PROTECTED] Nicolas -- http://www.rachinsky.de/nicolas
Re: Another mutt and gpg question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, January 28 at 02:28 PM, quoth Dan H.: 1. I can't access encrypted mail that I send. When I try to read it, I get Could not copy message. That's by design (but it's a rather uninformative error message). Encrypted email can only be read by those who have the private key to decrypt it. In order to read encrypted mail that you send you have to either 1) encrypt it to yourself as well (you can do this by changing gpg's configuration, or by adding --encrypt-to with your own PGP key to all of the mutt encryption commands in your muttrc) or 2) set fcc_clear, so that sent messages are saved to your Sent box unencrypted. 2. when I receive an encrypted mail, I see a text block of gibberish that I have to manually pipe through GPG externally. Why doesn't mutt auto-detect encrypted mails, like it does with signed mails? set pgp_auto_decode=yes At this point (i.e. now that you're at the it'd be more convenient if...), I strongly recommend reading through the muttrc man page. You'll find all *kinds* of interesting and useful settings in there. ~Kyle - -- No matter what side of the argument you are on, you always find people on your side that you wish were on the other. -- Jascha Heifetz -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHnfFQBkIOoMqOI14RAorhAJ9xC0C80Gu8rZJB9fveUmW88O9uOQCg+mkI 8bQ23BGNyHevx0bpzD9QCNQ= =CNM7 -END PGP SIGNATURE-
Re: automatically check for new mail
On Mon, Jan 28, 2008 at 06:19:59PM +, Raffi Khatchadourian wrote: On Mon 28.Jan'08 at 18:33:17 +0100, Steve S wrote: I'm new to mutt, so this question my have been asked before (I found nothing on the web/in the wiki etc.). In my muttrc I have bind browser n check-new which works ok. I hit `n` manually from time to time to see if there is new mail. Is it possible to do that automatically in the background (ala cron)? Are you using mailboxes? If so, this should be done automatically. Yes, I'm using Maildir format boxes: set mbox_type=Maildir set folder=~/Maildir set spoolfile=~/Maildir set record=+sent set postponed=+postponed mailboxes +spam +inbox +sent +postponed ... My MRA is gets mail controled by a cronjob, but in mutt's folder browser, I see folders makred with 'N' only when I (a) hit `n` or (b) close mutt and restart it. s.
Re: automatically check for new mail
On Mon 28.Jan'08 at 18:33:17 +0100, Steve S wrote: I'm new to mutt, so this question my have been asked before (I found nothing on the web/in the wiki etc.). In my muttrc I have bind browser n check-new which works ok. I hit `n` manually from time to time to see if there is new mail. Is it possible to do that automatically in the background (ala cron)? Are you using mailboxes? If so, this should be done automatically.
Re: automatically check for new mail
On Mon, Jan 28, 2008 at 07:50:11PM +0100, Steve S wrote: On Mon, Jan 28, 2008 at 06:19:59PM +, Raffi Khatchadourian wrote: On Mon 28.Jan'08 at 18:33:17 +0100, Steve S wrote: I'm new to mutt, so this question my have been asked before (I found nothing on the web/in the wiki etc.). In my muttrc I have bind browser n check-new which works ok. I hit `n` manually from time to time to see if there is new mail. Is it possible to do that automatically in the background (ala cron)? Are you using mailboxes? If so, this should be done automatically. Yes, I'm using Maildir format boxes: set mbox_type=Maildir set folder=~/Maildir set spoolfile=~/Maildir set record=+sent set postponed=+postponed mailboxes +spam +inbox +sent +postponed ... My MRA is gets mail controled by a cronjob, but in mutt's folder browser, I see folders makred with 'N' only when I (a) hit `n` or (b) close mutt and restart it. edit: I played with $timeout and $mail_check: set timeout=10 set mail_check=5 I sent a mail to myself, downloaded new mail and went back to the browser, all without quitting mutt. If I understand the manual correctly, mutt should have checked after ~ 10s that new mail has arrived. But no 'N' flag showed up whatsoever (until I finally hit `n`). Am I missing something obvious here? Thanks. s.
automatically check for new mail
Hi I'm new to mutt, so this question my have been asked before (I found nothing on the web/in the wiki etc.). In my muttrc I have bind browser n check-new which works ok. I hit `n` manually from time to time to see if there is new mail. Is it possible to do that automatically in the background (ala cron)? s.
Re: automatically check for new mail
On Mon, Jan 28, 2008 at 10:03:40PM +, Raffi Khatchadourian wrote: On Mon 28.Jan'08 at 19:50:11 +0100, Steve S wrote: My MRA is gets mail controled by a cronjob, but in mutt's folder browser, I see folders makred with 'N' only when I (a) hit `n` or (b) close mutt and restart it. What are you using to get new mail? Also, what version of mutt do you have? I'm using getmail and procmail. Mutt 1.5.17 (on Debian testing). s.
Re: automatically check for new mail
On Mon 28.Jan'08 at 19:50:11 +0100, Steve S wrote: My MRA is gets mail controled by a cronjob, but in mutt's folder browser, I see folders makred with 'N' only when I (a) hit `n` or (b) close mutt and restart it. What are you using to get new mail? Also, what version of mutt do you have?
Re: A few mutt questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, January 28 at 09:28 AM, quoth Dan H.: On Sat, Jan 26, 2008 at 04:05:10PM -0600, David Champion wrote: It certainly supports this, but it depends on the mail source itself to say what's read. Mutt can alter these flags, but so can other tools. Well, long story short, I see neither 'N' or 'O' flags. My mail comes from three IMAP accounts via fetchmail, exim, procmail. If memory serves, the way that MH folders keep track of new versus read messages is the same way that mboxes do, which is via a header embedded in the message (Status: or something like that). It seems entirely possible to me that the IMAP servers are using some similar means of storing messages, and that the messages may already HAVE that header in them (possibly indicating that they have been read) when you fetchmail them. Thus, when they are re-delivered to your mailbox via procmail, they look like messages that have been previously read. Since mutt doesn't keep a separate record of what has or has not been read in mailboxes (it relies on the mailbox's contents to be accurate), that could potentially be the problem. Open up those messages with a pager (e.g. less Lists/mutt/61), and see if they don't have something that looks like: Status: read already in them. If they do, then fixing the problem is a simple matter of adding a filter to your procmail script, right near the beginning, that looks like this: :0 f |formail -I Status ~Kyle - -- Selfishness is not living as one wishes to live, it is asking others to live as one wishes to live. -- Oscar Wilde -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHne7xBkIOoMqOI14RAufeAJ9GSxBqaoBxSPuXa6cd/W/3VkNIEACeKq4l MJ8/9n27Yn7BG9qjKOzsCzQ= =zVqm -END PGP SIGNATURE-
Re: Multiple IMAP accounts
Hello Florian, On Sunday, January 27, 2008 at 12:41:52 +0100, Florian Unglaub wrote: I set up accounthooks for each account to define spoolfiles, mbox, records etc. You misuse account-hooks; Setup folder-hooks instead. checks on new mail in account B won't work until I manually open one mailbox in account B. unset imap_passive Bye!Alain. -- Everything about locales on Sven Mascheck's excellent site at new location URL:http://www.in-ulm.de/~mascheck/locale/. The little tester utility is at URL:http://www.in-ulm.de/~mascheck/locale/checklocale.c.
Re: automatically check for new mail
On Mon, Jan 28, 2008 at 06:33:17PM +0100, Steve S wrote: Hi I'm new to mutt, so this question my have been asked before (I found nothing on the web/in the wiki etc.). In my muttrc I have bind browser n check-new which works ok. I hit `n` manually from time to time to see if there is new mail. Is it possible to do that automatically in the background (ala cron)? s. Here I run fetchmail -d 180, which puts a fetchmail proccess into daemon mode and rerun it each 180 sec period. -- Atenciosamente, Leonardo Caldas ICQ: 801133| I don't care if the software I run is GTalk: leonardo.caldas | unstable crap, as long as it is the LATEST Skype: leonardo.caldas | unstable crap. Yahoo: leonardocaldas | signature.asc Description: Digital signature
