Re: send-hook fails on alias addresses
On Sat, Feb 02, 2002 at 23:58, Knute wrote: Have you tried double quites? send-hook ~t my@address\.com 'unmy_hdr bcc' Does not help. :-( Steffen
Re: Getting start with Mutt and IMAP
On Sat 02-Feb-2002 at 11:53:55AM -0600, William Guynes wrote:
The only thing that worked was spoolfile in {server}INBOX format,
but not in imap://server/INBOX format.
The URL style syntax is new to mutt-1.3.*. If you are using 1.2.5, then
try upgrading to a recent development version like 1.3.27 - imap support
has been much improved.
--
Bruno
Re: mutt and NFS
Ken -- ...and then Ken Weingold said... % % On Sat, Feb 2, 2002, David T-G wrote: % Speaking of landing in a new city, does anyone need a hot SysAdmin? I'm % on the market again... Ken, perhaps you should forward my address to % your IT department ;-) % % What the one of my former employer? I'll send your resume to the NYS % Dept. of Unemployment, where my current paychecks come from. :( Ouch! Hey, maybe they'll throw money my way, too; it's a government program :-) Ah, well. % % % -Ken :-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! msg24147/pgp0.pgp Description: PGP signature
Re: mutt and NFS
Ken -- ...and then Ken Weingold said... % % On Sat, Feb 2, 2002, David T-G wrote: % I'd check the times, then. Log in on the server and check the date and % then, as simultaneously as possible, check the date on your workstation. % If they're more than a second or so off, you can have problems (and % everyone running make in your organization can get funky results, too). % % I ssh to that server. But I emailed my friend who runs it. He said If you can ssh in, then you can check the date. Something as simple as ssh remote date ; date will run date commands there and here and should run them in close sequence (it usually doesn't take long to close an ssh remote command). But whatever. % that the servers run ntp and are synced to within a second. Any other Good enough (though there have been times that I've had to really badger my admin to fix ntp when it falls over). % ideas? I haven't seen it last night, though. And btw, when it was % happening, touching said mailbox file make the Inc:1 disappear. When you do see it, try ls -l --fulltime folderfile ls -lu --fulltime folderfile to see the differences. See if they make sense. % % % -Ken 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! msg24148/pgp0.pgp Description: PGP signature
Re: timeout/mail_check doesn't always work?
Philip -- ...and then Philip Mak said... % % I have the following lines in my .muttrc file: % % set mail_check=5 # check for new mail every 5 seconds % set timeout=10 # if no keypress in 10 seconds, check for new mail Those look like they should get a quick response, even if they might be tough on your server :-) % % It doesn't seem to work correctly always, though. What's been % happening is that I run screen and I leave multiple instances of mutt % open in different folders. How very odd (but isn't screen great? :-) % % I'm inside the mutt that reads ~/Maildir/. I save a message into the % =done folder. 10 minutes later, I switch to the mutt in the =done % folder but it doesn't show the message that I just saved until I press % a key. % % Any idea why? In my business we always ask Is it plugged in? and so here goes. Have you tried :set ?timeout :set ?mail_check in this folder to make sure that the values are set as you expect? It could be as simple as forgetting to source your muttrc after making the changes :-) :-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! msg24149/pgp0.pgp Description: PGP signature
Re: Getting start with Mutt and IMAP
William --
...and then William Guynes said...
%
% I'm trying to get moved over to mutt. I've had it with Pine roles,
% it's driving me nuts.
Welcome!
%
% IMAP implementation has me a bit confused. I have 3 IMAP mailboxes,
% on 3 diferent servers. If I understand the docs correctly, I can
Good enough.
% switch between them using the 'c' command inside Mutt. Typing out
Yep.
% the imap://servername/INBOX isn't working though.
What version of mutt are you running? (Run
mutt -v
at the command line or type 'V' in the index to see.) If you're in 1.2.x,
you'll need to use
{servername}INBOX
as you note below; the imap://... format is a 1.3 development.
%
% The documentation talks about commands available. They don't
% appear to work in the Muttrc file. (Assume, for simplicity, it's a
% single user system and I'm making configs in the master Muttrc file)
Actually, you could make changes in your $HOME/.muttrc or your
$HOME/.mutt/muttrc file just as well; there's no need to mess around as
root. You could even whip up a test /tmp/muttrc and point to it like
mutt -F /tmp/muttrc ...
to test your changes.
% I've tried both mailboxes and account-hook. The only thing that
% worked was spoolfile in {server}INBOX format, but not in
% imap://server/INBOX format. However, that assumes only one IMAP
% box.
Hmmm... Yep. That points to an older version of mutt, I think; we see
that IMAP is working (and that your mutt was buillt with IMAP support).
The mailboxes command should be straightforward and tells mutt where to
look for new mail. In your case, it would probably look about like
mailboxes {server}INBOX {server}mailbox1 {server}mailbox2 ...
and it would probably get pretty ugly having to check multiple accounts if
you weren't using a 1.3.x version. mutt will then let you know whenever
it looks like you have new mail waiting in any of those mailboxes (see
past threads for copious discussion of this design decision :-)
%
% Can someone straighten me out here? The documentation talks about
% initialization files. These are somehow different than RC files?
No, that's the same thing.
%
% The Mutt and IMAP document tends to gloss over these details.
REMEMBER THIS. One thing that mutt needs is improved user documentation.
Unfortunately, the hardest thing for developers and users familiar with
it is to remember what was challenging or get past what is second nature.
Please, please, please take notes of everything that is unclear or needs
work so that it can be fixed up later. You might even contribute to
the documentation effort! Oh, yeah -- and we'll try to help you with
this problem as we go :-)
% E.g.
% 1.1 To point mutt to an IMAP mailbox, write your mailbox in IMAP
% URL format:
% imap://hostname/mailbox
%
% Write it? Write it where? :) rc file? (didn't work, maybe was
% using wrong parameter) initialization file? commandline? (didn't
% work with -f)
You could do it on the command line like
mutt -f {servername}mailbox
or when you change folders with a 'c' like
c
{servername}mailbox
as you mention above.
%
% I'm just missing some mental building blocks that the docs don't
% cover.
Right. In addition to checking your version, let us know where else you
need help and we'll fill in the gaps.
%
% --
% William Guynes
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!
msg24150/pgp0.pgp
Description: PGP signature
Shortcut to mailboxes screen?
Hi folks, I'm a recent convert to mutt from the rigid world of pine... I'm suitably impressed with the near infinite reconfigurability. One thing I've run up against--probably for lack of a decent Google query--is how I might create a macro to bring me to the mailboxes overview in the browser. I know that change-folder, in the index, defaults to showing the next mailbox with new messages, but, sometimes I like to skip over this and see just a list of mailboxes which have new messages. I could see doing this by adding: macro index g change-foldertabtabtab to my macros.muttrc... But, of course, that's only going to work if there are new messages in folders... :) (Otherwise, the number of tabs is different)...Seems inelegant, anyways. Any ideas? Erik. -- ...ironically, perhaps, the best organised dissenters in the world today are anarchists, who are busily undermining capitalism while the rest of the left is still trying to form committees. Jeremy Hardy, The Guardian.
Re: Shortcut to mailboxes screen?
On Sun, Feb 03, 2002 at 11:12:06AM -0500, Erik Rothwell wrote: Hi folks, I'm a recent convert to mutt from the rigid world of pine... I'm suitably impressed with the near infinite reconfigurability. One thing I've run up against--probably for lack of a decent Google query--is how I might create a macro to bring me to the mailboxes overview in the browser. I know that change-folder, in the index, defaults to showing the next mailbox with new messages, but, sometimes I like to skip over this and see just a list of mailboxes which have new messages. I could see doing this by adding: macro index g change-foldertabtabtab macro pager i sync-mailboxchange-folder?toggle-mailboxes macro index i sync-mailboxchange-folder?toggle-mailboxes I got this off someone on the list once. Works great for me. CP
Re: Shortcut to mailboxes screen?
On Sun, Feb 03, 2002 at 08:44:02AM -0800, Collin Peters wrote: macro pager i sync-mailboxchange-folder?toggle-mailboxes macro index i sync-mailboxchange-folder?toggle-mailboxes I got this off someone on the list once. Works great for me. That's perfect! Works like a charm, thanks. Erik. -- E. L. Rothwell PGP Public Key at http://www.keyserver.net/
Re: mutt and NFS
On Sun, Feb 3, 2002, David T-G wrote: % that the servers run ntp and are synced to within a second. Any other Good enough (though there have been times that I've had to really badger my admin to fix ntp when it falls over). % ideas? I haven't seen it last night, though. And btw, when it was % happening, touching said mailbox file make the Inc:1 disappear. When you do see it, try ls -l --fulltime folderfile ls -lu --fulltime folderfile to see the differences. See if they make sense. I will try that when I see the problem again. Thanks. -Ken
regex isn't working in color index ~C ... context
hi, i tried... #color index brightwhite default ~C $alternates color index brightwhite default ~C (parv_@yahoo\.com|parv@(localhost|.*holy\.cow)) ...i get error message while starting mutt... Error in /home/parv/cf/mail/mutt.cf, line 58: parentheses not balanced ...i don't see how above regex for ~C could be invalid. when i tried w/o end parentheses, i get... Error in /home/parv/cf/mail/mutt.cf, line 59: error in pattern at: parv@(localhost|.*holy.cow) ...so, is not possible to specify a regex for ~C even though manual suggests one can... ~C EXPR message is either to: or cc: EXPR ... In the above, EXPR is a regular expression. what am i doing wrong, or missing? - parv --
Re: mutt and NFS
On Sun, Feb 3, 2002, David T-G wrote: When you do see it, try ls -l --fulltime folderfile ls -lu --fulltime folderfile to see the differences. See if they make sense. It's happening again. Weird that ls --help shows --fulltime, but on the command line is says it's an invalid option. :-/ Anyway, 'ls -lu's output time is 2 minutes earlier than 'ls -l's. -Ken
Re: mutt and NFS
ls -l --fulltime folderfile ls -lu --fulltime folderfile It's happening again. Weird that ls --help shows --fulltime, but on the command line is says it's an invalid option. :-/ Anyway, 'ls -lu's output time is 2 minutes earlier than 'ls -l's. On my Linux box (Debian sid) the option is '--full-time' Chris -- Christopher S. Swingley phone: 907-474-2689 Computer / Network Manager email: [EMAIL PROTECTED] IARC -- Frontier ProgramGPG and PGP keys at my web page: University of Alaska Fairbanks www.frontier.iarc.uaf.edu/~cswingle
Re: regex isn't working in color index ~C ... context
On Feb 03, parv [[EMAIL PROTECTED]] wrote: #color index brightwhite default ~C $alternates color index brightwhite default ~C (parv_@yahoo\.com|parv@(localhost|.*holy\.cow)) ...i get error message while starting mutt... Error in /home/parv/cf/mail/mutt.cf, line 58: parentheses not balanced quoting. try: color index brightwhite default ~C \(parv_@yahoo\.com|parv@(localhost|.*holy\.cow))\ (the pattern matching syntax allows for (|) itself, so ~C (... is ambiguous to mutt's parser) msg24161/pgp0.pgp Description: PGP signature
Re: regex isn't working in color index ~C ... context
On Sun, Feb 03, 2002 at 03:38:18PM -0500, parv wrote: hi, i tried... #color index brightwhite default ~C $alternates color index brightwhite default ~C (parv_@yahoo\.com|parv@(localhost|.*holy\.cow)) ...i get error message while starting mutt... Error in /home/parv/cf/mail/mutt.cf, line 58: parentheses not balanced ...i don't see how above regex for ~C could be invalid. when i tried w/o end parentheses, i get... Error in /home/parv/cf/mail/mutt.cf, line 59: error in pattern at: parv@(localhost|.*holy.cow) ...so, is not possible to specify a regex for ~C even though manual suggests one can... ~C EXPR message is either to: or cc: EXPR ... In the above, EXPR is a regular expression. Easily solved. This is due to mutt's weird parsing of its extended regexps that means the brackets get interpreted as part of the ~ patterns stuff instead of EXPR, try this color index brightwhite default ~C '(parv_@yahoo\.com|parv@(localhost|.*holy\.cow))' -- Benjamin Smith [EMAIL PROTECTED], [EMAIL PROTECTED] msg24162/pgp0.pgp Description: PGP signature
Re: regex isn't working in color index ~C ... context
Jeremy Blosser wrote: On Feb 03, parv [[EMAIL PROTECTED]] wrote: #color index brightwhite default ~C $alternates ^^ Am I missing something? I believe the main goal of the original poster is to achieve something like this... color index brightwhite default ~C (parv_@yahoo\.com|parv@(localhost|.*holy\.cow)) ...and this one is just a way to get round the difficulty, isn't it? quoting. try: color index brightwhite default ~C \(parv_@yahoo\.com|parv@(localhost|.*holy\.cow))\ (the pattern matching syntax allows for (|) itself, so ~C (... is ambiguous to mutt's parser) I then would rather suggest to have a look at the ~p and ~P patterns. -- Cedric msg24163/pgp0.pgp Description: PGP signature
Re: regex isn't working in color index ~C ... context
On Feb 03, Cedric Duval [[EMAIL PROTECTED]] wrote: Jeremy Blosser wrote: On Feb 03, parv [[EMAIL PROTECTED]] wrote: #color index brightwhite default ~C $alternates ^^ Am I missing something? I believe the main goal of the original poster is to achieve something like this... Oops. Didn't read closely enough. I then would rather suggest to have a look at the ~p and ~P patterns. Yep. msg24164/pgp0.pgp Description: PGP signature
Re: regex isn't working in color index ~C ... context
i blurted... color index brightwhite default ~C (parv_@yahoo\.com|parv@(localhost|.*holy\.cow)) ...i get error message while starting mutt... to which replied Benjamin Smith thusly (and Jeremy Blosser gave the similar reply)... Easily solved. This is due to mutt's weird parsing of its extended regexps that means the brackets get interpreted as part of the ~ patterns stuff instead of EXPR, try this color index brightwhite default ~C \ '(parv_@yahoo\.com|parv@(localhost|.*holy\.cow))' needless to say that quoting of regex, like above, was enlightening. later, cedric d. suggested to consult the ~p patterns. looking at the muttrc(5), now i say do'h, how could i missed it?. thank you everybody for your replies. - parv --
Re: mutt and NFS
On Sun, Feb 3, 2002, Christopher S. Swingley wrote: ls -l --fulltime folderfile ls -lu --fulltime folderfile It's happening again. Weird that ls --help shows --fulltime, but on the command line is says it's an invalid option. :-/ Anyway, 'ls -lu's output time is 2 minutes earlier than 'ls -l's. On my Linux box (Debian sid) the option is '--full-time' Yup, that was it. It was the hyphen. Thanks. :) Debian as well. Is there any other Linux? ;-) -Ken
