Problem with save_name when folder points to an IMAP server
I have noted a problem with the IMAP support in mutt 1.3.25i (and
earlier 1.3 versions)
When configuring mutt to use save_name with a folder directory on an
IMAP server it fails to locate the IMAP-folder for the user and ends
up saving the message in the record folder.
I have seen the following error messages:
Permission denied: /jan
Can't open /ekolin: not a selectable mailbox
Has anybody else encoutered this problem?
Relevant parts of .muttrc:
set folder=imap:[EMAIL PROTECTED]/
set record=+sent
set save_name=yes
set force_name=no
Output from .muttdebug when it sending a mail to myself which should
have been Fcc:d to
imap:[EMAIL PROTECTED]/ekolin
but ends up in
imap:[EMAIL PROTECTED]/sent
Mutt 1.3.25i started at Wed Jan 16 09:41:49 2002
.
Debugging at level 4.
Using default IMAP port 143
Using default IMAPS port 993
mutt_alloc_color(): Color pairs used so far: 1
mutt_alloc_color(): Color pairs used so far: 2
mutt_alloc_color(): Color pairs used so far: 3
mutt_alloc_color(): Color pairs used so far: 4
mutt_alloc_color(): Color pairs used so far: 5
mutt_alloc_color(): Color pairs used so far: 6
mutt_alloc_color(): Color pairs used so far: 7
mutt_alloc_color(): Color pairs used so far: 8
mutt_alloc_color(): Color pairs used so far: 9
mutt_alloc_color(): Color pairs used so far: 10
mutt_alloc_color(): Color pairs used so far: 11
mutt_alloc_color(): Color pairs used so far: 12
imap_cmd_step: grew buffer to 512 bytes
* OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN]
neruda.got.gatespace.com IMAP4rev1 2001.315 at Wed, 16 Jan 2002 09:41:48 +0100 (CET)
a CAPABILITY
* CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES
THREAD=ORDEREDSUBJECT MULTIAPPEND LOGIN-REFERRALS STARTTLS AUTH=LOGIN
Handling CAPABILITY
a OK CAPABILITY completed
imap_authenticate: Using any available method.
Sending LOGIN command for ekolin...
a0001 OK [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT
THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User ekolin authenticated
a0002 LIST
* LIST (\NoSelect) /
a0002 OK LIST completed
Delimiter: /
a0003 SELECT INBOX
* 87 EXISTS
Handling EXISTS
cmd_handle_untagged: New mail in INBOX - 87 messages total.
* 0 RECENT
* OK [UIDVALIDITY 942934710] UID validity status
* OK [UIDNEXT 38708] Predicted next UID
.
a0006 STATUS /ekolin (UIDVALIDITY)
* NO Can't open /ekolin: not a selectable mailbox
Handling untagged NO
Can't open /ekolin: not a selectable mailbox
a0006 NO STATUS failed: Can't open /ekolin: not a selectable mailbox
imap_access: Can't check STATUS of /ekolin
a0007 STATUS ekolin (UIDVALIDITY)
* STATUS ekolin (UIDVALIDITY 942934557)
a0007 OK STATUS completed
a0008 APPEND ekolin (\Seen) {517}
+ Ready for argument
Date: Wed, 16 Jan 2002 09:42:39 +0100
From: Gunnar Ekolin [EMAIL PROTECTED]
To: Gunnar Ekolin [EMAIL PROTECTED]
Subject: test
Message-ID: [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.25i
Status: RO
tesras
--
Gunnar Ekolin, Gatespace AB, [EMAIL PROTECTED]
Phone: +46-31 743 98 19(CRT): +46-31 701 42 19
Telefax: +46-31 711 64 16Mobile: +46-70 796 77 19
a0008 OK APPEND completed
mx_close_message (): unlinking /tmp/mutt-porter-18984-2
Note that this time the message was actually saved in the apprpriate
place, but when I get the 'Permission denied /user' message it ends
upp in the record folder.
Gunnar Ekolin
--
Gunnar Ekolin, Gatespace AB, [EMAIL PROTECTED]
Re: Move deleted messages to trash
On Tue, Jan 15, 2002 at 05:11:32PM -0600, Jeremy Blosser wrote: | On Jan 15, Andreas Herceg [[EMAIL PROTECTED]] wrote: | On Tue, Jan 15, 2002 at 02:57:07PM -0500, Justin R. Miller wrote: | | Use what I recommended, in addition to a modified $delete value (consult | | the manual). The delete confirmation dialog is optional :-) | | I don't think the $delete value will help. The delete confirmation comes | to action, only when deleting from the trash. | | I think whot James meant, was the confirmation to append the messages to | the trash-folder. At least that's my problem. | | Then check $confirmappend. Sure, I already had that Idea. What I tried was: folder-hook trash set confirmappend=no What I achieved this way is that appending a message *from* the trash has not to be confirmed. Appending a message *to* trash has still to be confirmed. -- Andreas Herceg [EMAIL PROTECTED]
Hook?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone. I'm about to send out a whole bunch of mails and I wondered what would be the easiest way to ensure that they all go to the same Outbox for easy reference. At the moment all my stuff is saved to ~/Mail/Outbox/name_of_recipient What do you think? - -- Nick Wilson Tel:+45 3325 0688 Fax:+45 3325 0677 Web:www.explodingnet.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8RX+9HpvrrTa6L5oRAmGXAJ9xvvv0OJVnxOVCQQrjY+7gmb3ITgCdH7yA LwgzuYVJOy142DxP5fSUuyc= =9OtO -END PGP SIGNATURE-
message-hooks
I'm trying to do something here, maybe it's not doable - who knows? what I want is that whenever I write or reply to a certain address, that message will be automagically BCCed to another address. I tried using send-hooks, but those do not seem to affect the current message, only subsequent messages. send-hook . 'unmy_hdr Bcc:' send-hook [EMAIL PROTECTED] 'my_hdr Bcc: [EMAIL PROTECTED]' (from memory) Is it possible? -- Dan Boger [EMAIL PROTECTED] msg23155/pgp0.pgp Description: PGP signature
Re: Hook?
* Nick Wilson [EMAIL PROTECTED] [16-01-2002 14:26]: | I'm about to send out a whole bunch of mails and I wondered what would | be the easiest way to ensure that they all go to the same Outbox for | easy reference. You mean a bunch of separate mails? Then you could just issue the set fcc=yourOutbox command, send the mails, and reset it when you're done. If all mails match a certain pattern (section 4.2 of TFM), you could use a send-hook for this purpose, like: send-hook ~s SUBJECT set fcc=yourOutbox | At the moment all my stuff is saved to ~/Mail/Outbox/name_of_recipient | | What do you think? Hope this is what you meant, and that this helps. -- René Clerc - ([EMAIL PROTECTED]) Said the attractive, cigar-smoking housewife to her girl-friend: I got started one night when George came home and found one burning in the ashtray. msg23156/pgp0.pgp Description: PGP signature
Re: Hook?
On Wed, Jan 16, 2002 at 02:42:43PM +0100, René Clerc [EMAIL PROTECTED] wrote: You mean a bunch of separate mails? Then you could just issue the set fcc=yourOutbox command, send the mails, and reset it when you're done. My mutt don't know fcc, I think you meant record. Nicolas
Re: Hook?
* On 16-01-02 at 14:47 * René Clerc said * Nick Wilson [EMAIL PROTECTED] [16-01-2002 14:26]: | I'm about to send out a whole bunch of mails and I wondered what would | be the easiest way to ensure that they all go to the same Outbox for | easy reference. You mean a bunch of separate mails? Then you could just issue the set fcc=yourOutbox command, send the mails, and reset it when you're done. Yep, that's right. I guess that's what I'll be needing. Hope this is what you meant, and that this helps. It sure does, thanks Rene. -- Nick Wilson Tel:+45 3325 0688 Fax:+45 3325 0677 Web:www.explodingnet.com msg23158/pgp0.pgp Description: PGP signature
Re: Hook?
Hi, Newbie question: Is it possible to have set record = outbox depending on sender thanks, Phil. On Wed, Jan 16, 2002 at 02:47:40PM +0100, Nicolas Rachinsky wrote: On Wed, Jan 16, 2002 at 02:42:43PM +0100, René Clerc [EMAIL PROTECTED] wrote: You mean a bunch of separate mails? Then you could just issue the set fcc=yourOutbox command, send the mails, and reset it when you're done. My mutt don't know fcc, I think you meant record. Nicolas
Re: Suggestion of adding some contents
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thus spake Nicolas Rachinsky ([EMAIL PROTECTED]): 3. When I get clearer with gpg, I try to make my 'uid' more informative for others. But I found gpg doesn't provide good maintaining method to update them. You can not update uid except using adduid/deluid. You can not(?) change the 'preference' order of those uid's. The worse, I found I have no way to remove my old uid's in keyserver - they just accumulate. Strange gpg. You can't do this easily, but I think there is something in the manual. This feature will be added in GnuPG 1.0.7, which is supposed to be out soon. For now, the most recently added uid is the preferred one. As for removing an old uid, there is something about using your revocation certificate and re-uploading the key. DO NOT JUST USE YOUR REVOCATION CERTIFICATE! It is *something to do with it* (that's the best lead I can give). Your best bet is to search the gnupg-users mailing list archives. It comes up frequently. - -- [!] Justin R. Miller [EMAIL PROTECTED] PGP 0xC9C40C31 -=- http://codesorcery.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8RY9U94d6K8nEDDERAreRAJ41j/7CUcrI+WHk0tICeCpn0EuP9QCeJVOm MeMtQEpt8TYRQt0xdkEDOos= =LX+i -END PGP SIGNATURE-
Re: Hook?
* Nicolas Rachinsky [EMAIL PROTECTED] [16-01-2002 14:49]: | On Wed, Jan 16, 2002 at 02:42:43PM +0100, René Clerc [EMAIL PROTECTED] wrote: | You mean a bunch of separate mails? Then you could just issue the set | fcc=yourOutbox command, send the mails, and reset it when you're | done. | | My mutt don't know fcc, I think you meant record. Of course. Stupide me ;) -- René Clerc - ([EMAIL PROTECTED]) No woman, no cry. -Bob Marley msg23161/pgp0.pgp Description: PGP signature
Re: Hook?
On Wed, Jan 16, 2002 at 02:56:04PM +0100, Philip Wittamore wrote: Hi, Newbie question: Is it possible to have set record = outbox depending on sender thanks, Phil. You can use fcc-hook for setting the record folder based on the recipient, if you're changing $from in a hook to get different senders, you can just set $record where ever you set $from. -- Benjamin Smith [EMAIL PROTECTED], [EMAIL PROTECTED] msg23162/pgp0.pgp Description: PGP signature
Re: Hook?
* On 16-01-02 at 14:47 * René Clerc said If all mails match a certain pattern (section 4.2 of TFM), you could use a send-hook for this purpose, like: send-hook ~s SUBJECT set fcc=yourOutbox Well, I'm afraid that I'm a bit of a dummy, after much reading of TFM I'm none the wiser. Here's the deal: each mail that I am sending that needs to be in a 'special' Outbox has a subject line that starts with att: So some examples would be: att: somebloke att: somegeezer att: somedoris and I'd like then to all be in the same place. I can't use 'set record' because I have fcc-save-hook . =Outbox/%0 So I need to go with a subject line match. A little guidance here would be very appreciated indeed. Many thanks -- Nick Wilson Tel:+45 3325 0688 Fax:+45 3325 0677 Web:www.explodingnet.com msg23163/pgp0.pgp Description: PGP signature
Re: Hook?
On 020116, at 17:30:03, Nick Wilson wrote each mail that I am sending that needs to be in a 'special' Outbox has a subject line that starts with att: and I'd like then to all be in the same place. I can't use 'set record' because I have fcc-save-hook . =Outbox/%0 For fcc-hook and save-hook, the hook processing stops with the first match. Perhaps this would work: fcc-hook ~s att: =Outbox/att fcc-hook . =Outbox/%0 save-hook .=Outbox/%0 -- David Ellement
Re: Hook?
On Jan 16, Nick Wilson [[EMAIL PROTECTED]] wrote: each mail that I am sending that needs to be in a 'special' Outbox has a subject line that starts with att: So some examples would be: att: somebloke att: somegeezer att: somedoris and I'd like then to all be in the same place. I can't use 'set record' because I have fcc-save-hook . =Outbox/%0 So I need to go with a subject line match. I'm not that up on fcc-hook stuff but in general doing fcc-save-hook . =Outbox/%0 fcc-save-hook ~s ^att: =Outbox/someplace should get what you want. The first will continue to apply as the default and anything that matches the second will use it instead. msg23165/pgp0.pgp Description: PGP signature
Re: adding an attribution-like line for Cc's
Eric Smith [EMAIL PROTECTED] said something to this effect on 01/15/2002: Occasionally, I Cc an email and the recipient of the Cc assumes that the email is directed to them (and not just copied to them). Is it possible to add an attribution-like line similar to: This is a copy of an email sent to main_recipient Would be nice to have this for Bcc (and bounce) as well. A related issue I am having in connection with my hack to have a copy of _all_ mails that I send interactively with mutt in a single folder. I have this folder-hook: folder-hook . my_hdr X-outgoing: save But when I reply to an email (or forward, or bounce), then I do not get this header inserted as I want. Can you get your editor to do it? It sounds like that might be the right place for it to happen. (darren) -- What is ideology but the rationalisation of a vested interest?
Re: message-hooks
Date: Wed, 16 Jan 2002 08:36:55 -0500 From: Dan Boger [EMAIL PROTECTED] To: Mutt Users [EMAIL PROTECTED] Subject: message-hooks I'm trying to do something here, maybe it's not doable - who knows? what I want is that whenever I write or reply to a certain address, that message will be automagically BCCed to another address. I tried using send-hooks, but those do not seem to affect the current message, only subsequent messages. send-hook . 'unmy_hdr Bcc:' send-hook [EMAIL PROTECTED] 'my_hdr Bcc: [EMAIL PROTECTED]' Doesn't message-hook do what you describe here? -- FreeBSD 4.4-STABLE 7:21PM up 3 days, 23:18, 21 users, load averages: 0.03, 0.02, 0.00
Re: message-hooks
On Wed, Jan 16, 2002 at 07:21:28PM +0100, Roman Neuhauser wrote: what I want is that whenever I write or reply to a certain address, that message will be automagically BCCed to another address. I tried using send-hooks, but those do not seem to affect the current message, only subsequent messages. send-hook . 'unmy_hdr Bcc:' send-hook [EMAIL PROTECTED] 'my_hdr Bcc: [EMAIL PROTECTED]' Doesn't message-hook do what you describe here? nope, doesn't seem to do anything at all! -- Dan Boger [EMAIL PROTECTED] msg23168/pgp0.pgp Description: PGP signature
Re: 1.3.25 builds with S-LANG - PuTTy colors now munged
On Sun, Jan 06, 2002 at 04:18:19PM -0500, Jack Baty [EMAIL PROTECTED] wrote: After installing from the port, colors are no longer working properly using Putty. By not working I mean that it seems the foreground and background colors are reversed in some cases. Text that was previously green on a default background is now black on a green background. The default background does not seem to show through. In other cases, the text color is completely different from those defined in my .muttrc. No other changes were made that I'm aware of, so I started poking around in the makefile. I noticed that during the install that slang was also installed, which I'd not seen before. The Makefile says... # In general you can choose between using the SLANG port (which is really # recommended and is now the default) and ncurses (WITH_MUTT_NCURSES). If you # don't want to use SLANG define WITHOUT_MUTT_SLANG. Now, before I go around messing with trying to go back to using ncurses, I'd like to know if anyone knows if there's a way to fix the color issue while still using slang, since that seems to now be recommended. I know nothing about curses or S-LANG btw, so I'm pretty much flying blind here. Same problem here, but mutt seems to work fine, when build with WITHOUT_MUTT_SLANG=YES. Nicolas
Re: message-hooks
On Wed, Jan 16, 2002 at 01:16:59PM -0500, Dan Boger wrote: On Wed, Jan 16, 2002 at 07:21:28PM +0100, Roman Neuhauser wrote: what I want is that whenever I write or reply to a certain address, that message will be automagically BCCed to another address. I tried using send-hooks, but those do not seem to affect the current message, only subsequent messages. send-hook . 'unmy_hdr Bcc:' send-hook [EMAIL PROTECTED] 'my_hdr Bcc: [EMAIL PROTECTED]' Doesn't message-hook do what you describe here? nope, doesn't seem to do anything at all! ok, I spoke prematurely... it does seem to work when I'm viewing a message that matches [EMAIL PROTECTED], but that's not quite the same... I want sending messages to [EMAIL PROTECTED], if it's a reply, or a forward, or a new message, I want it BCCed... -- Dan Boger [EMAIL PROTECTED] msg23170/pgp0.pgp Description: PGP signature
Re: Ispell is too quiet when run from the Compose menu
On 2002.01.13, in [EMAIL PROTECTED], David T-G [EMAIL PROTECTED] wrote: I don't necessarily agree that mutt should spit out a message, though I can see that this could be confusing. What I would do would be to go ... % Feedback is an important element of any user interface, GUI or % text-based, UNIX or not. Yes, but so is providing only the right amount, rather than too much or too little. Consider running mutt on a remote server that you're connected to over a slow or high-latency line, or one prone to dropping link. You press 'i'; did [ia]spell complete with no errors, or has it not run yet? It might be hard to tell: if the link is indeed slow, it can take more time yet to get a response to other activity, and instigating this activity just to check the status of ispell is a larger waste of precious bandwidth than a mere No spelling errors found message. The key here is usability. Adherence to the so-called Unix philosophy is false if it makes the tool in question less usable. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: 1.3.25 builds with S-LANG - PuTTy colors now munged
On Wed, 16 Jan 2002, Nicolas Rachinsky wrote: On Sun, Jan 06, 2002 at 04:18:19PM -0500, Jack Baty [EMAIL PROTECTED] wrote: After installing from the port, colors are no longer working properly using Putty. By not working I mean that it seems the foreground and background colors are reversed in some cases. Text that was previously green on a default background is now black on a green background. The default background does not seem to show through. In other cases, the text color is completely different from those defined in my .muttrc. No other changes were made that I'm aware of, so I started poking around in the makefile. I noticed that during the install that slang was also installed, which I'd not seen before. The Makefile says... # In general you can choose between using the SLANG port (which is really # recommended and is now the default) and ncurses (WITH_MUTT_NCURSES). If you # don't want to use SLANG define WITHOUT_MUTT_SLANG. indeed (I haven't seen any discussion that indicates there was any technical reason for this - a shame, since that tends to increase my own incoming bug reports from people who don't know how to set their environment). Now, before I go around messing with trying to go back to using ncurses, I'd like to know if anyone knows if there's a way to fix the color issue while still using slang, since that seems to now be recommended. I know nothing about curses or S-LANG btw, so I'm pretty much flying blind here. not really (barring bugs in mutt, there's no intrinsic difference between what's doable with ncurses or slang). There were some trivial bugs reported for color support, but my experience with sending patches _to_ mutt-dev was that they were ignored (not even rejected), so there's little reason to pursue that. Same problem here, but mutt seems to work fine, when build with WITHOUT_MUTT_SLANG=YES. Nicolas -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Handling high volume mailing lists - looking for ideas
Hi, I'am looking for tips/ideas on how to best manage subscriptions to multiple high volume mailing lists. Here's my current setup: I'm subscribed to multiple lists which get seperated into multiple incoming folders by procmail. Every now and then I scan through the new mail for some of the lists. I usually flag threads that I'd like to follow later. I have hooks set up to display messages in the index in different colors if they are from me, new, flagged or old. This helps somewhat but for some lists (e.g. debian-user or linux-kernel) there can be more then 300 messages a day, so it's hard to keep track of interesting threads. In two or three days even flagged messages can get so far down the list that they are hard to find... On the other hand I prefer to keep old messages searchable so every time I have a problem I can look for similar topics before bothering anybody. (On a side note: New messages are colored in a different color in the index fairly easily, but is there a way to color also the top message of each thread if there are new messages in the thread, so that it is visible at one glance even if the treads are collapsed?) Ideally what I thought would be nice to have is: New messages arrive into the incoming folders as before. But in the incoming folder I want to keep only new messages or threads I started/replied to or those I have flagged. So either on closing the folder (changing to a different one) or on opening it every message that is not new or from me or flagged is moved to an archive folder (ideally one that is named dynamically to include the current year and month). Is there a good way to achieve this? (Note, that the best solution would be to always keep the whole thread, but if that's not possible, I guess it would be still very good if I could only keep all messages from me and all flagged messages.) I'd greatly appreciate any thoughts on this matter! Many thanks for your help in advance! best regards, Balazs
Re: Ispell is too quiet when run from the Compose menu
David -- ...and then David Champion said... % % On 2002.01.13, in [EMAIL PROTECTED], % David T-G [EMAIL PROTECTED] wrote: % % I don't necessarily agree that mutt should spit out a message, though I % can see that this could be confusing. What I would do would be to go % ... % % Feedback is an important element of any user interface, GUI or % % text-based, UNIX or not. % % Yes, but so is providing only the right amount, rather than too much or % too little. % % Consider running mutt on a remote server that you're connected to over a % slow or high-latency line, or one prone to dropping link. You press 'i'; Sure. % did [ia]spell complete with no errors, or has it not run yet? It might % be hard to tell: if the link is indeed slow, it can take more time yet Hmmm... I'll concede that point. I wonder if, on such a slow line, there's actually a screen flash that's usually hidden by a fast connection that might serve as an indicator... % to get a response to other activity, and instigating this activity just % to check the status of ispell is a larger waste of precious bandwidth % than a mere No spelling errors found message. Right. That's why not spitting out any message is a *good* thing, in general; it's superfluous. % % The key here is usability. Adherence to the so-called Unix philosophy % is false if it makes the tool in question less usable. I believe I completely agree wit you :-) % % -- % -D. [EMAIL PROTECTED]NSITUniversity of Chicago :-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! msg23174/pgp0.pgp Description: PGP signature
Re: 1.3.25 builds with S-LANG - PuTTy colors now munged
On Jan 16, Thomas E. Dickey [[EMAIL PROTECTED]] wrote: On Wed, 16 Jan 2002, Nicolas Rachinsky wrote: On Sun, Jan 06, 2002 at 04:18:19PM -0500, Jack Baty [EMAIL PROTECTED] wrote: After installing from the port, colors are no longer working properly ... The Makefile says... # In general you can choose between using the SLANG port (which is really # recommended and is now the default) and ncurses (WITH_MUTT_NCURSES). If you # don't want to use SLANG define WITHOUT_MUTT_SLANG. indeed (I haven't seen any discussion that indicates there was any technical reason for this - a shame, since that tends to increase my own incoming bug reports from people who don't know how to set their environment). Well, FWIW, I'm pretty sure he's talking about his own vendor's mutt package (port is a BSD-ism, right?). Regular Mutt still defaults to ncurses, and there's certainly no mention of the above text in Mutt's Makefile. using Putty. By not working I mean that it seems the foreground and background colors are reversed in some cases. Text that was previously green on a default background is now black on a green background. The default background does not seem to show through. In other cases, the text color is completely different from those defined in my .muttrc. No other changes were made that I'm aware of, so I started poking around in the makefile. I noticed that during the install that slang was also installed, which I'd not seen before. Now, before I go around messing with trying to go back to using ncurses, I'd like to know if anyone knows if there's a way to fix the color issue while still using slang, since that seems to now be recommended. I know nothing about curses or S-LANG btw, so I'm pretty much flying blind here. not really (barring bugs in mutt, there's no intrinsic difference between what's doable with ncurses or slang). There were some trivial bugs One difference I discovered recently that made me switch my build back to ncurses (heh) is that S-Lang has a rather low value for COLOR_PAIRS. At around 30 color entries, any additional ones started reverting back to normal... this might actually explain the problem Jack is having. (The real number is probably 25, since it has to be a square, but duplicate color pairs don't count against the total, and I didn't research it all the way down yet.) Anyway, I switched my home build back to ncurses, and I'm not experiencing the problems I previously had with it. I still am on various servers, even using the exact same mutt and ncurses builds, but I'm still looking into what's really wrong there. reported for color support, but my experience with sending patches _to_ mutt-dev was that they were ignored (not even rejected), so there's little reason to pursue that. You might have better luck submitting them as actual bug reports in the BTS. There's a lot of mail of these lists, not everything is seen. The BTS provides tracking, which is useful. msg23175/pgp0.pgp Description: PGP signature
Re: Move deleted messages to trash
Andreas, et al -- ...and then Andreas Herceg said... % % On Tue, Jan 15, 2002 at 05:11:32PM -0600, Jeremy Blosser wrote: % | On Jan 15, Andreas Herceg [[EMAIL PROTECTED]] wrote: % | On Tue, Jan 15, 2002 at 02:57:07PM -0500, Justin R. Miller wrote: % | | Use what I recommended, in addition to a modified $delete value (consult % | | the manual). The delete confirmation dialog is optional :-) % | % | I don't think the $delete value will help. The delete confirmation comes % | to action, only when deleting from the trash. % | % | I think whot James meant, was the confirmation to append the messages to % | the trash-folder. At least that's my problem. % | % | Then check $confirmappend. % % Sure, I already had that Idea. What I tried was: % % folder-hook trash set confirmappend=no % % What I achieved this way is that appending a message *from* the trash % has not to be confirmed. Appending a message *to* trash has still to be % confirmed. You've seen why that won't work. Using a folder-hook on your current folder, or changing the macro to turn it off and then on, would do the trick. % % % -- % Andreas Herceg % [EMAIL PROTECTED] :-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! msg23176/pgp0.pgp Description: PGP signature
Re: Handling high volume mailing lists - looking for ideas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * On 16-01-02 at 21:23 * Balazs Javor said Hi, I'am looking for tips/ideas on how to best manage subscriptions to multiple high volume mailing lists. Here's my current setup: I'm subscribed to multiple lists which get seperated into multiple incoming folders by procmail. Every now and then I scan through the new mail for some of the lists. I usually flag threads that I'd like to follow later. I have hooks set up to display messages in the index in different colors if they are from me, new, flagged or old. This helps somewhat but for some lists (e.g. debian-user or linux-kernel) there can be more then 300 messages a day, so it's hard to keep track of interesting threads. In two or three days even flagged messages can get so far down the list that they are hard to find... On the other hand I prefer to keep old messages searchable so every time I have a problem I can look for similar topics before bothering anybody. Well, with the holp of more than a few of the people here I set it up so that when I delete mail from mailing lists they get sent to ~Mail/Trash/list-name meaning that I can very quickly get rid of uninteresting threads and then read the good ones whilst still keeping an archive. (On a side note: New messages are colored in a different color in the index fairly easily, but is there a way to color also the top message of each thread if there are new messages in the thread, so that it is visible at one glance even if the treads are collapsed?) Like that idea, hope *someone* knows :) - -- Nick Wilson Tel:+45 3325 0688 Fax:+45 3325 0677 Web:www.explodingnet.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8Rep3HpvrrTa6L5oRAlkCAKCbjW2EmpckooyaajSXnw6uP6Lh8ACcCHor tATcdbz3YGAptzcW2ytYvHQ= =GsKM -END PGP SIGNATURE-
Re: Move deleted messages to trash
James -- ...and then James Hamilton said... % % I usually delete a whole slue of messages at a time. For example I had ~150 messages to scan through in my inbox this morning. Most of them spam system email etc. Can someone suggest a way to mark them for deletion then when i sync-mailbox have the messages marked for deletion move to the trash folder? The method listed below makes me answer yes to each message I delete which is much more work than just keeping a backup of everything I recieve and going to it when I am missing mail.. If you want to have a trash folder, I highly recommend Cedric Duval's trash_folder patch. Meanwhile, checking your $confirmappend and $delete settings to set them to no (perhaps in your macro) will get rid of the prompting. HTH 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! msg23178/pgp0.pgp Description: PGP signature
Re: 1.3.25 builds with S-LANG - PuTTy colors now munged
On Wed, 16 Jan 2002, Jeremy Blosser wrote: Well, FWIW, I'm pretty sure he's talking about his own vendor's mutt package (port is a BSD-ism, right?). Regular Mutt still defaults to ncurses, and there's certainly no mention of the above text in Mutt's Makefile. generally (you're correct there). Some porters do a good job, some don't. Unfortunately (in contrast to Debian), FreeBSD's porters seem to work as a mob (makes it hard to keep track of who is handling a package). not really (barring bugs in mutt, there's no intrinsic difference between what's doable with ncurses or slang). There were some trivial bugs One difference I discovered recently that made me switch my build back to ncurses (heh) is that S-Lang has a rather low value for COLOR_PAIRS. At around 30 color entries, any additional ones started reverting back to normal... this might actually explain the problem Jack is having. (The real number is probably 25, since it has to be a square, but duplicate color pairs don't count against the total, and I didn't research it all the way down yet.) that seems familiar (but ncurses does use a square, though pair 0 is treated specially). -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Hook?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * On 16-01-02 at 18:11 * Jeremy Blosser said On Jan 16, Nick Wilson [[EMAIL PROTECTED]] wrote: each mail that I am sending that needs to be in a 'special' Outbox has a subject line that starts with att: So some examples would be: att: somebloke att: somegeezer att: somedoris and I'd like then to all be in the same place. I can't use 'set record' because I have fcc-save-hook . =Outbox/%0 So I need to go with a subject line match. I'm not that up on fcc-hook stuff but in general doing fcc-save-hook . =Outbox/%0 fcc-save-hook ~s ^att: =Outbox/someplace should get what you want. The first will continue to apply as the default and anything that matches the second will use it instead. Okay guys, I now have: fcc-save-hook ~s att: =Outbox/att does it work? does if @#*! Bit of a tough bugger this one :) Cheers - -- Nick Wilson Tel:+45 3325 0688 Fax:+45 3325 0677 Web:www.explodingnet.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8RfSMHpvrrTa6L5oRAv0qAJ4iEt7QHmyJRnGUcL24qBiAclDtywCfWnH9 9PlROyO6rxhbSZM/x0Eikx8= =K/jW -END PGP SIGNATURE-
Re: 1.3.25 builds with S-LANG - PuTTy colors now munged
Thomas E. Dickey wrote: generally (you're correct there). Some porters do a good job, some don't. Unfortunately (in contrast to Debian), FreeBSD's porters seem to work as a mob (makes it hard to keep track of who is handling a package). there is generally a maintainter, no? aura% grep MAINTAINER /usr/ports/mail/mutt-devel/Makefile MAINTAINER= [EMAIL PROTECTED] aura% grep MAINTAINER /usr/ports/mail/mutt/Makefile MAINTAINER?=[EMAIL PROTECTED] w
Controlling when new mail appears in boxes?
I use procmail to filter mail into several different mailboxes. Some I need to monitor continually, while others I only want to look at once a day or so, and others only every few days. As I have things set up now, all these mailboxes are in my ~/Mail directory, and mailboxes set to `echo ~/Mail/*` The problem is that this way I'm always made immediately aware of new mail in busy mailboxes, so those mailboxes are impinging on my consciousness more than I'd like. Is there a way to control the frequency with which Mutt checks for new mail in specific mailboxes (immediately for some important boxes, every few hours for others, every couple of days for others)? It's a pain to try to remember how long it's been since I read mail in a particular box. Forgive me if this is already covered somewhere in the documentation. -- .~. /v\ Lance Simmons // \\ [EMAIL PROTECTED] /( )\ __^_^
Re: Controlling when new mail appears in boxes?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thus spake Lance Simmons ([EMAIL PROTECTED]): Is there a way to control the frequency with which Mutt checks for new mail in specific mailboxes (immediately for some important boxes, every few hours for others, every couple of days for others)? It's a pain to try to remember how long it's been since I read mail in a particular box. I'm not aware of a native way, but I had toyed with the idea of adjusting the value of $mailboxes based on the time of day/week/etc. For example, only reading list mail while not at work (or similar). That should be easy enough, either with shell scripts to output the value of $mailboxes, or maybe a cron job to tweak the .muttrc. Just my $0.02. - -- [!] Justin R. Miller [EMAIL PROTECTED] PGP 0xC9C40C31 -=- http://codesorcery.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8Rfkj94d6K8nEDDERArbJAKCUcjxoq6+RRHSwod1BoDce31yGhgCePtzw D6e6awYpNAOwNoId1uGW8SY= =5cNq -END PGP SIGNATURE-
smtp authentication
Hey people. I know Mutt does not deliver mail, but Rogers just switched to requiring smtp authentication and I'd prefer to smarthost through them. Is anyone aware of an smtp server that does authentication? Thanks, Mike -- Michael P. Soulier [EMAIL PROTECTED], GnuPG pub key: 5BC8BE08 ...the word HACK is used as a verb to indicate a massive amount of nerd-like effort. -Harley Hahn, A Student's Guide to Unix msg23184/pgp0.pgp Description: PGP signature
Re: LDAP and mutt.
Hey all. On Fri, Oct 26, 2001 at 01:58:06PM -0700,([-30]7867.09) in a galaxy far far away, Gary Johnson muttered on the list: There is a list of scripts to do just that at http://www.fiction.net/blong/programs/mutt/ under External Address Query Scripts. I adapted one of them, mutt_ldap_query2.pl, (ldapsearch wrapper modified by Warren Jones) to work with my company's LDAP server. For starters, I'm an ldap newbie, so be gentle with me ;) I've used this script successfully in the past but then I ran with the OpenLdap 1.2 suite. I recently upgraded to RH Linux 7.2 (from RH 6.2) which comes with OpenLdap 2.0 (openldap-2.0.11-13 and openldap-clients-2.0.11-13). When I run the ldap query perl script, I get: ldap_sasl_interactive_bind_s: No such attribute ldapsearch failed: According to a Google search this means: This indicates that LDAP SASL authentication function could read the Root DSE but it contained no supportedSASLMechanism attribute. The Ldap host is a M$ Exchange server. I've tried all the SASL Mechs listed in the RFC's and the only one that gave me some sort of response was the DIGEST-MD5 mech, but I don't think that should be the right method because of the authentication involved ( I used to be able to query the ldap host without supplying some form of login credentials). I also tried using the ldap query perl script by Marc de Courville using the NET::LDAP module before ldapsearch is called but to no avail. Anyone know a solution? Marco. -- Marco van Lienen [EMAIL PROTECTED] S@H:3097WU/5.729yr -- setiathome.ssl.berkeley.edu Will you find aliens? Why did it happen ? BOFH Excuse: Error #763: hard disk not ready, close door. msg23185/pgp0.pgp Description: PGP signature
Re: smtp authentication
Michael P. Soulier wrote: I know Mutt does not deliver mail, but Rogers just switched to requiring smtp authentication and I'd prefer to smarthost through them. Is anyone aware of an smtp server that does authentication? sendmail, i'm pretty sure does (i know cause i'm dealing with trying to get RID of sendmail's attempts to authenticate against every server it connects to right now). basically you put the auth info in /etc/mail/default-auth-info (or whatever, but i think that's the default location). sendmail.org/~ca/ should have more info on this postfix doesn't attempt this by default, even if built with SASL, but i don't think it would be terribly difficult to get this setup with postfix either. w
Re: Controlling when new mail appears in boxes?
On Wed, Jan 16, 2002 at 05:05:24PM -0500, Justin R. Miller wrote: Is there a way to control the frequency with which Mutt checks for new mail in specific mailboxes I'm not aware of a native way, but I had toyed with the idea of adjusting the value of $mailboxes based on the time of day/week/etc. That solution would work if I frequently restarted Mutt. In fact, however, I often have a single instance of Mutt running for hours at a time. So I'd have to remember how long has it been since I restarted Mutt? -- .~. /v\ Lance Simmons // \\ [EMAIL PROTECTED] /( )\ __^_^ Old musicians never die, they just decompose.
Re: smtp authentication
I'll give it a shot, but as I understand it, according to RFC 2554, any MTA that receives an authenticated email will forward that authentication. So, is there a way to get Mutt to send an authenticated email to my local server? I found a page on doing this with Exim as well, but I'm wondering if I can get the client to do it. Mike On 16/01/02 Will Yardley did speaketh: sendmail, i'm pretty sure does (i know cause i'm dealing with trying to get RID of sendmail's attempts to authenticate against every server it connects to right now). basically you put the auth info in /etc/mail/default-auth-info (or whatever, but i think that's the default location). sendmail.org/~ca/ should have more info on this postfix doesn't attempt this by default, even if built with SASL, but i don't think it would be terribly difficult to get this setup with postfix either. w -- Michael P. Soulier [EMAIL PROTECTED], GnuPG pub key: 5BC8BE08 ...the word HACK is used as a verb to indicate a massive amount of nerd-like effort. -Harley Hahn, A Student's Guide to Unix msg23188/pgp0.pgp Description: PGP signature
Re: Controlling when new mail appears in boxes?
On 16:03 16 Jan 2002, Lance Simmons [EMAIL PROTECTED] wrote: | I use procmail to filter mail into several different mailboxes. Some I | need to monitor continually, while others I only want to look at once a | day or so, and others only every few days. | | As I have things set up now, all these mailboxes are in my ~/Mail | directory, and mailboxes set to `echo ~/Mail/*` | | The problem is that this way I'm always made immediately aware of new | mail in busy mailboxes, so those mailboxes are impinging on my | consciousness more than I'd like. Well, this isn't strictly an in mutt solution, but I don't use $mailboxes to monitor email. Instead my procmail recipe runs a small shell script when delivering to particular folders, and that script writes a line to a file I'm monitoring in a small always-open xterm citing folder, author and subject. Works for me. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ Q: What's the difference between a psychotic and a neurotic? A: A psychotic doesn't believe that 2 + 2 = 4. A neurotic knows it's true, but it bothers him.
problem with 1.3.25
I'm using mutt 1.2.5 on Solaris 8 Intel. It works fine. I'm using ncurses 5.2 with it. I see color and everything. However, I today compiled mutt 1.3.25 and made sure I compiled it with ncurses support. However, upon launch I get a bunch of errors that the color 'default' is not defined: Error in /home/cconstan/.muttrc, line 326: default: no such color Error in /home/cconstan/.muttrc, line 327: default: no such color here's the output of a mutt -v on 1.3.5: Mutt 1.3.25i (2002-01-01) Copyright (C) 1996-2001 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: SunOS 5.8 (i86pc) [using ncurses 5.2] Compile options: -DOMAIN +DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META -HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGIN FO_YESEXPR +HAVE_ICONV +ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=/public/bin/ispell SENDMAIL=/usr/lib/sendmail MAILPATH=/var/mail PKGDATADIR=/public/i86pc/mutt-1.3.25/share/mutt SYSCONFDIR=/etc/localhost/mutt-1.3.25 EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the flea(1) utility. anyone have any ideas? it's the same .muttrc from before. It's also the same one I use at home which uses mutt 1.3.25, here's the output from that version of mutt -v (Linux): Mutt 1.3.25i (2002-01-01) Copyright (C) 1996-2001 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.4.17 (i586) [using ncurses 5.2] Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_GSS -USE_SSL +USE_GNUTLS +USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET ++HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=/usr/bin/ispell SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/share/mutt SYSCONFDIR=/etc EXECSHELL=/bin/sh MIXMASTER=mixmaster To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the flea(1) utility. patch-1.3.24.rr.compressed.1 patch-1.3.24.appoct.2 patch-1.3.15.sw.pgp-outlook.1 patch-1.3.24.admcd.gnutls.1 Md.use_editor Md.paths_mutt.man Md.muttbug_no_list Md.use_etc_mailname Md.muttbug_warning Md.gpg_status_fd patch-1.2.xtitles.1 patch-1.3.23.1.ametzler.pgp_good_sign anyone have ideas as to what is up? -- Carl B. Constantine University of Victoria Programmer Analyst http://www.uvic.ca UNIX System Administrator Victoria, BC, Canada [EMAIL PROTECTED]
more on color and 1.3.25
further to my last post, here's a sample of my .muttrc: color signature brightred default color tilde blue default color tree brightmagenta default color underline yellow default color body yellow default [;:]-[)/(|] # colorise smileys color body yellow default [;:][)/(|] color body brightblue default (http|ftp|news|telnet|finger)://[^ ]* color index yellow default ~N # New color index yellow default ~O # Old color index cyan default '~t adm' # mail to the adm group color index cyan default '~c adm' # mail to the adm group color index magentadefault '~t uvsubnet' # mail to CNUG list color index magentadefault '~c uvsubnet' # mail to CNUG list color index brightgreendefault '~p'# mail to myself color index brightcyan default '~P'# mail from myself color index brightred default '~s dump' color index brightmagenta default '~s backup' color index magentadefault ~F # Flagged color index blue default ~T # Tagged color index reddefault ~D # Deleted again, ideas why I get an error on default under mutt 1.3.25 and Solaris 8? -- Carl B. Constantine University of Victoria Programmer Analyst http://www.uvic.ca UNIX System Administrator Victoria, BC, Canada [EMAIL PROTECTED]
Re: Controlling when new mail appears in boxes?
On Thu, 17 Jan 2002, Cameron Simpson wrote: Well, this isn't strictly an in mutt solution, but I don't use $mailboxes to monitor email. Instead my procmail recipe runs a small shell script when delivering to particular folders, and that script writes a line to a file I'm monitoring in a small always-open xterm citing folder, author and subject. I wouldn't mind taking a look at both the script and the recipe, if you don't mind. I've been wondering how to do that.
Re: problem with 1.3.25
Carl B . Constantine wrote: However, I today compiled mutt 1.3.25 and made sure I compiled it with ncurses support. However, upon launch I get a bunch of errors that the color 'default' is not defined: Error in /home/cconstan/.muttrc, line 326: default: no such color Error in /home/cconstan/.muttrc, line 327: default: no such color hrmm works ok for me. bacall% mutt -v Mutt 1.3.25i (2002-01-01) Copyright (C) 1996-2001 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: SunOS 5.8 (sun4m) [using ncurses 5.2] Compile options: -DOMAIN +DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP -USE_IMAP -USE_GSS -USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID -HAVE_GETADDRINFO -ISPELL SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/local/share/mutt SYSCONFDIR=/usr/local/etc EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the flea(1) utility. bacall% uname -srm SunOS 5.8 sun4m i'm using the sunfreeware ncurses: bacall% pkginfo | grep ncurses application SMCncurs ncurses what configure options did you use to build mutt? you might need to do something like: LDFLAGS=-Wl,-R/usr/local/lib ./configure --with-libiconv-prefix=/usr/local i think there's a more elegant way to do it, but this way worked for me. w
Re: problem with 1.3.25
On Wed, Jan 16, 2002 at 04:12:40PM -0800, Carl B . Constantine wrote: I'm using mutt 1.2.5 on Solaris 8 Intel. It works fine. I'm using ncurses 5.2 with it. I see color and everything. However, I today compiled mutt 1.3.25 and made sure I compiled it with ncurses support. However, upon launch I get a bunch of errors that the color 'default' is not defined: probably the configure script is (as noted in the previous report) not adding -lncurses to $LIBS and is finding the Solaris curses library instead. (Another clue is that resizeterm isn't found). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: problem with 1.3.25
On Wed, Jan 16, 2002 at 04:25:54PM -0800, Will Yardley wrote: i'm using the sunfreeware ncurses: ...which is perhaps a problem in itself (I've several reports that this package is installed with conflicting names versus the Solaris curses library). imho, that package should be deleted. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Controlling when new mail appears in boxes?
On 16/01/02, from the brain of Knute tumbled: On Thu, 17 Jan 2002, Cameron Simpson wrote: Well, this isn't strictly an in mutt solution, but I don't use $mailboxes to monitor email. Instead my procmail recipe runs a small shell script when delivering to particular folders, and that script writes a line to a file I'm monitoring in a small always-open xterm citing folder, author and subject. I wouldn't mind taking a look at both the script and the recipe, if you don't mind. I've been wondering how to do that. Me too, that sounds very interesting. Can you share it to the list? -- Michael Montagne [EMAIL PROTECTED] http://www.boora.com
Re: problem with 1.3.25
* Thomas Dickey ([EMAIL PROTECTED]) wrote: On Wed, Jan 16, 2002 at 04:12:40PM -0800, Carl B . Constantine wrote: I'm using mutt 1.2.5 on Solaris 8 Intel. It works fine. I'm using ncurses 5.2 with it. I see color and everything. However, I today compiled mutt 1.3.25 and made sure I compiled it with ncurses support. However, upon launch I get a bunch of errors that the color 'default' is not defined: probably the configure script is (as noted in the previous report) not adding -lncurses to $LIBS and is finding the Solaris curses library instead. (Another clue is that resizeterm isn't found). I doubt it, ncurses is in /public/lib on my system. mutt -v reporst that it's using ncurses 5.2 at the top. Here's what I passed to configure: ./configure --prefix=/public/i86pc/mutt-1.3.25 --sysconfdir=/etc/localhost/mutt-1.3.25 --with-ncurses=/public --with-mailpath=/var/mail --enable-pop --enable-imap --with-ssl=/public --enable-nfs-fix --enable-mailtool --with-included-gettext anyone else have any ideas, it is rather annoying. -- Carl B. Constantine University of Victoria Programmer Analyst http://www.uvic.ca UNIX System Administrator Victoria, BC, Canada [EMAIL PROTECTED]
Re: LDAP and mutt.
On Wed, Jan 16, 2002 at 11:57:11AM +0100, Marco van Lienen wrote: When I run the ldap query perl script, I get: ldap_sasl_interactive_bind_s: No such attribute ldapsearch failed: Try invoking ldapsearch with a -x switch. This tells it to not try and bind using sasl authentication. -- David Rock [EMAIL PROTECTED] msg23198/pgp0.pgp Description: PGP signature
Re: Controlling when new mail appears in boxes?
On 17:49 16 Jan 2002, Michael Montagne [EMAIL PROTECTED] wrote:
| On Thu, 17 Jan 2002, Cameron Simpson wrote:
| Well, this isn't strictly an in mutt solution, but I don't use
| $mailboxes to monitor email. Instead my procmail recipe runs a small
| shell script when delivering to particular folders, and that script
| writes a line to a file I'm monitoring in a small always-open xterm
| citing folder, author and subject.
|
| I wouldn't mind taking a look at both the script and the recipe, if you
| don't mind. I've been wondering how to do that.
|
| Me too, that sounds very interesting. Can you share it to the list?
Well, bear in mind you did ask this of someone with a heavily customised
environment.
Also note that I automgenerate my .procmailrc with this tool:
http://freshmeat.net/projects/cats2procmailrc/
so the apprently painful verbosity is done by a program from this single line:
!attn CSKK[EMAIL PROTECTED]
The ! means make an alert line, attn is the folder, CSKK is a tagline
and [EMAIL PROTECTED] is a target email address to match on.
So on to the example procmail recipe:
: 0
* ^(to|cc|bcc):.*cskk@optushome\.com\.au
{
: 0hc
| mhdrs | { while read hdr body; do eval HDR_$hdr=\$body; done; alert -c
yellow `timecode` +attn $HDR_FROM; $HDR_SUBJECT; }
: 0hf
| sed -e 's/^Subject: *\[[^ ]*\] */Subject: /' -e 's/^Subject: *[Rr][Ee] *:
*\[[^ ]*\] */Subject: Re: /' -e 's/^Subject:/ [CSKK]/'
: 0
attn/.
}
Now, note that only the first bit matters. This recipe does three things
on detection of email for [EMAIL PROTECTED]:
- generates an alert for my window
- hacks the subject line to mark it with [CSKK] and tidy it up a bit
- drops it in my +attn folder when my high priority email goes
So the core trick is to use the {...} stuff to do a few things in a
given recipe, and thus to have an alert action for specific rules.
That said, mhdrs is a tiny perl script to crudely grab header lines from
the mail message (supplied on stdin by procmail):
http://www.zip.com.au/~cs/scripts/mhdrs
and write them out in shell friendly form. The while loop sucks them up
and makes variables like $HDR_SUBJECT etc for use by the alert command,
which is just a script:
http://www.zip.com.au/~cs/scripts/alert
to deposit the supplied line onto the logfile, in yellow in this instance.
Then my FvwmButtons at the screen top has a 3 line transparent rxvt
which runs tail -f on the logfile.
And lo, when such email arrives it's mentioned quietly but obviously at
the top of my screen.
--
Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/
I'm beginning to like them llamas more and more... - Curtis Jackson
Re: Controlling when new mail appears in boxes?
Very nice. Now I just need to figure out how to get it all set up in my
environment! ;)
On Thu, 17 Jan 2002, Cameron Simpson wrote:
On 17:49 16 Jan 2002, Michael Montagne [EMAIL PROTECTED] wrote:
| On Thu, 17 Jan 2002, Cameron Simpson wrote:
| Well, this isn't strictly an in mutt solution, but I don't use
| $mailboxes to monitor email. Instead my procmail recipe runs a small
| shell script when delivering to particular folders, and that script
| writes a line to a file I'm monitoring in a small always-open xterm
| citing folder, author and subject.
|
| I wouldn't mind taking a look at both the script and the recipe, if you
| don't mind. I've been wondering how to do that.
|
| Me too, that sounds very interesting. Can you share it to the list?
Well, bear in mind you did ask this of someone with a heavily customised
environment.
Also note that I automgenerate my .procmailrc with this tool:
http://freshmeat.net/projects/cats2procmailrc/
so the apprently painful verbosity is done by a program from this single line:
!attn CSKK[EMAIL PROTECTED]
The ! means make an alert line, attn is the folder, CSKK is a tagline
and [EMAIL PROTECTED] is a target email address to match on.
So on to the example procmail recipe:
: 0
* ^(to|cc|bcc):.*cskk@optushome\.com\.au
{
: 0hc
| mhdrs | { while read hdr body; do eval HDR_$hdr=\$body; done; alert -c
yellow `timecode` +attn $HDR_FROM; $HDR_SUBJECT; }
: 0hf
| sed -e 's/^Subject: *\[[^ ]*\] */Subject: /' -e 's/^Subject: *[Rr][Ee] *:
*\[[^ ]*\] */Subject: Re: /' -e 's/^Subject:/ [CSKK]/'
: 0
attn/.
}
Now, note that only the first bit matters. This recipe does three things
on detection of email for [EMAIL PROTECTED]:
- generates an alert for my window
- hacks the subject line to mark it with [CSKK] and tidy it up a bit
- drops it in my +attn folder when my high priority email goes
So the core trick is to use the {...} stuff to do a few things in a
given recipe, and thus to have an alert action for specific rules.
That said, mhdrs is a tiny perl script to crudely grab header lines from
the mail message (supplied on stdin by procmail):
http://www.zip.com.au/~cs/scripts/mhdrs
and write them out in shell friendly form. The while loop sucks them up
and makes variables like $HDR_SUBJECT etc for use by the alert command,
which is just a script:
http://www.zip.com.au/~cs/scripts/alert
to deposit the supplied line onto the logfile, in yellow in this instance.
Then my FvwmButtons at the screen top has a 3 line transparent rxvt
which runs tail -f on the logfile.
And lo, when such email arrives it's mentioned quietly but obviously at
the top of my screen.
