Problem displaying special characters (ie. Euro symbol)
Hi all! I have a little problem displaying the Euro symbol (among some others) in mutt. It always ends up in "\200" instead of the Euro symbol. I use XTerm as my terminal. Maybe that's of interest for someone. Mails in which the Euro symbol is displayed wrong were sent with Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit ... mostly by MS Outlook. Unfortunately I couldn't find anything on the list that would help me fix this issue. I use mutt 1.3.28i on a clean MDK 8.2 install with all updates applied. I appologize in case this has been discussed before. So, is the problem to be solved by my mutt configuration or is it an XTerm thing? Thanks for any input. Marc
mutt ignores reply-to if I am the sender.
I wasn't testing the reply-to feature in a mailing list and noticed that mutt was completely ignoring the reply-to if (and only if) it notices that I am the sender (either because hostname is set to the right value or alternates contains the Email in the From field) Is that a bug or a feature that I don't understand? Thanks, Marc -- Microsoft is to software what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ (friendly to non IE browsers) Finger [EMAIL PROTECTED] for PGP key and other contact information
Re: mutt ignores reply-to if I am the sender.
On 9 Aug 2000 15:23:47 -0700, Mikko Hänninen <[EMAIL PROTECTED]> wrote: >When Mutt notices that you're replying to a message that is from you, it >will in fact address the message to the address(es) listed in the >recipient headers (To, Cc). This is so that you can easily send a >followup to your own message to the original recipient, which is mostly >what you want to do, instead of sending an email to yourself. > >Because the Reply-To header defines where to send replies to the author >(in this case you), it is ignored. 1) Can this be disabled? 2) Should this really be a default? The reason I ask is: I Email an announce list, which has an explicit reply-to to a discussion list. The headers look like this: From: Marc MERLIN <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: [VA-Test] testing reply-to Reply-To: [EMAIL PROTECTED] If I hit 'G' or 'R', my answer goes to [EMAIL PROTECTED] bypassing the redirect to [EMAIL PROTECTED] This is quite annoying... Marc -- Microsoft is to software what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ (friendly to non IE browsers) Finger [EMAIL PROTECTED] for PGP key and other contact information
Re: mutt ignores reply-to if I am the sender.
On Thu, Aug 10, 2000 at 02:13:44AM +0300, Mikko Hänninen wrote: > Marc MERLIN <[EMAIL PROTECTED]> wrote on Wed, 09 Aug 2000: > > 1) Can this be disabled? > > Not that I know of, I took a quick glance at the manual and couldn't > find it. Ok, so it's not just me :-) > > I Email an announce list, which has an explicit reply-to to a discussion > > list. > > Yet another proof that Reply-To shouldn't be used for redirecting list > mail traffic. :-) Even if this is a bit beside the point... I agree that Mail-Followup-To is better, but 1) mailman doesn't let me set that for a list to redirect to another one 2) Too many MUAs ignore it > You could supply a proper Mail-Followup-To header (eg. with send-hook > and my_hdr) and then both L (list-reply) and g (group-reply) ought to Yeah, I can fix it for myself as a users, but not for other people who don't use mutt. > An alternative is to use a From address for posting to that list which > isn't covered by your $alternates setting. :-) > Hope this helps, Thanks. > PS "[EMAIL PROTECTED]" ??? Yeah, it's an old mail-news gateway, I didn't remember if the mutt-users list would let me post with an address that isn't subscribed (I subscribe one address per list I read, but I use a different address to post). Long story and a bit broken, never mind :-) Marc -- Microsoft is to software what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ (friendly to non IE browsers) Finger [EMAIL PROTECTED] for PGP key and other contact information
Re: mutt ignores reply-to if I am the sender.
On Wed, Aug 09, 2000 at 06:52:11PM -0500, Aaron Schrab wrote: > At 23:01 + 09 Aug 2000, Marc MERLIN <[EMAIL PROTECTED]> wrote: > > 1) Can this be disabled? > > set reply_self Ah, yes, thanks. (this feature appeared in exim after I wrote my exim.conf. I should re-read the manual every so often to see what new features showed up) Marc -- Microsoft is to software what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ (friendly to non IE browsers) Finger [EMAIL PROTECTED] for PGP key and other contact information
error trying to create IMAP folder w/ mutt 1.2.5i
hi, this is my setup, Linux Box running Courier IMAP 1.1 Debain 2.2 box running mutt 1.2.5i have all the imap stuff setup so that i can browser folders on the server, etc. moving messages around and everything works great in the folder browser, if i hit n to make a new folder i get "Creating mailboxes is not yet supported." friends of mine have gone over mysetup and verified that it works for them on their IMAP servers. Is this a courier problem? thanks, marc britten
mutt and PGP
Hi ! O.K. I've got PGP running on my workstation and want to use it together with mutt now. Has anyone get this running ? I can send mail using: set pgp_encrypt_only_command="pgp +verbose=0 +batchmode -et - %r" But the decryption is not running :-/ set pgp_decrypt_command="PGPPASSFD=0; export PGPPASSFD; cat - %f | pgp +verbose=0 +batchmode -f" Everytime I try to decrypt a mail with this line I get this error: Unrecognized data format: stdin Cannot process input from: stdin Error code = 8 My goal os the following: scroll to the PGP encrypted mail, press ENTER, type in the passphrase, and read the mail like all other non-PGP mails ? Can someone point me to the right direction ? thx Marc -- Bist auch Du ein Dieselhandschuhtanker ?? Dann komm zu ==> http://beam.at/cancerman registered Linux User #165939
Re: mutt 1.2.5i and cyrus iamp ssl
On Sun, Dec 24, 2000 at 04:58:54PM -0500, Ilya wrote: > I also noticed that if I turn on ssl I am asked each time I start mutt of I > want to reject certificate or save it once. Why is there no option to save > it permanently? > thx Hi Ilya ! There is an option with which you can store all your certificates in ! But if mutt doesn't know where to store it it'll ask you each time you connect to the server ;-) try this option: set certificate_file=~/mail/.certificates and your certificates will be stored to that file ! have fun Marc -- registered Linux User #165939
multiple imap mailboxes
How can I manage multiple imap mailboxes in mutt? I'd like to be able to read each mailbox seperately, perhaps using a convenient way to switch between them. I'd also like to avoid having to re-enter my password each time (even if it means compromising security by keeping cleartext passwords in a local file, though I'd like to avoid that also if possible). And finally, with the setup above, I'd like to be able to move messages from one imap mailbox to another. Is this all possible? I've been reading and re-reading the mutt documentation and I can't seem to get myself to understand the mutt macros, key bindings, folder hooks or whatever it takes to pull of what I need. Any hints which might help configure mutt for my needs would be greatly appreciated. Marc
How to setup imap mailboxes
While trying to understand how to configure imap mailboxes in mutt, I came across what I was looking for in the mailing list archive: http://www.mail-archive.com/mutt-users@mutt.org/msg10688.html The relevant part of the posting showed the following mailboxes: > IMAP ../ > IMAP INBOX > IMAP mbox1 > IMAP mbox2 > IMAP subfolder1/ > IMAP #sharedns1/ When I look at my folders, by typing 'c' then '?', I get: 1 drwxr-xr-x 16 usernameusername1024 Jun 30 21:04 ../ Unfortunately, the message in the archive didn't explain how to get from my setup to multiple mailboxes. I tried typing 'n' to create a new mailbox, but mutt returns "Creating mailboxes is not yet supported." (mutt-1.2.5) Anyone mind explaining how I can configure imap mailboxes so that I get a listing as above? Thanks, Marc
Mutt and [q]uitting...
Is it just me and mutt is supposed to do this, or is there actually something I've done wrong to MAKE it do this? scenario: Launch mutt, it drops you into your spool directory. Hit [q], and depending on the setting of $quit (a quadoption), it asks you or doesn't ask you, and either exits, or doesn't. Now, launch mutt and specify '-y'. You get dropped into the mailbox display. Hit [q], and mutt immediately exits. "Waitaminit here, that isn't right, weren't you supposed to ask me before you exited?" If you but once enter a mailbox, $quit seems to start taking effect. Needless to say, I have "set quit=ask-yes" in ~/.muttrc... -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Strange attachement
On Mon, Nov 26, 2001 at 10:45:02PM +0100, Patrik Modesto wrote: > It works. Thanks. But one question. Why mutt doesn't recognise it as a > regular attachement? Because it isn't an attachment. It's part of the message body. Just text. That's how you did it before MIME. ^_^ -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] msg20718/pgp0.pgp Description: PGP signature
Re: Opening Mutt in Folder Menu
On Sat, Dec 08, 2001 at 05:30:20PM -0700, Steven Schneider wrote: > Oh, well I wish that I had dl'd this before I modified my .muttrc. > Right now I have three lines like thus: > > mailboxes ... > mailboxes ... > mailboxes ... How about this? (wrapped, should be all one line in .muttrc) mailboxes ! `find ~/Mail/ -type f | perl -ne 'chomp; print "$_ " unless m/^.*(postponed|sent.mail.*|killfil.*|trash|mbox)$/'` That makes sure your spool directory appears first on the list of mailboxes, and then every other mbox file comes after. Modify the exclusion at the end as appropriate for your particular situation. Can't take credit for it, I snagged it out of the ML. ^_^ -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] msg21331/pgp0.pgp Description: PGP signature
Re: mailbox corruption
On Sat, Dec 08, 2001 at 08:12:48PM -0800, Mike Erickson wrote: > A few times, I've been going through old mail in one of my mailboxes and > noticed a mail with no subject. Opening it up reveals an entire email > message, headers and all, in the body. I'm using sendmail, procmail, > biff n and mbox format. Is this mutt-related? No, more than likely it's mailx-related. Procmail escapes 'From' lines with that damn '>' symbol, and if you read the mbox with mailx, when it writes it back it treats it as a delimiter and assumes that's where the message body begins. Since it's usually the first or second line of the header, sure enough you're left with no message subject and the rest of the headers plus the real body in the body of the message. The funny thing is that mailx can't properly read a mbox that it's destroyed in this manner either. ^_^ You can get the mailbox back easily enough... go in and delete the added blank lines. I've been about to file a bug against the Debian mailx package for forever about this after I finally figured out what was corrupting my mbox file(s). Poking around in Google leads to the fact that it's a known problem with mailx on a variety of systems and distributions. Debian would call it an RC bug, I'm sure. Great, the Woody freeze is tomorrow and I'm contemplating filing an RC bug. Now, of course, if you never use mailx, then I'm all wet and you have some other problem. ^_^ -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] msg21335/pgp0.pgp Description: PGP signature
Re: Opening Mutt in Folder Menu
On Sun, Dec 09, 2001 at 08:19:41AM -0700, Steven Schneider wrote: > Ok, I imagine that I have to substitute my mailboxes/dirs in thoses > lines, but I woundn't mind having those others (i.e. sent, > postponed, trash, etc...) do I have to make those before hand? > Will mutt create those for me when I use a command line like > that? Well, 'postponed' gets created when you postpone a message, the 'sent' construct in mine is because I index sent messages by date, and the 'kill' construct is because I have a procmail recipie that implements a killfile by author and one by date. So no, they'll not get created unless they're needed for something. ^_^ -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] msg21362/pgp0.pgp Description: PGP signature
Re: abort_nosubject=ask-no not working as expected
On Sun, Dec 16, 2001 at 10:29:55PM -0500, John P . Verel wrote: > Does the abort_nosubject option work in 1.2.5? Yes. > My .muttrc entry is: > > set abort_nosubject=ask-no That says "always ask me what I want, make the default answer be 'no'". It's a quadoption. -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] msg21655/pgp0.pgp Description: PGP signature
Re: mutt and NetBSD
Lars Hecking <[EMAIL PROTECTED]> écrit : > > Has anyone built mutt successfully on NetBSD? The native curses seem > to be extremely limited (is this the same for the other BSD's?) and > compilation dies with tons of errors about undefined symbols like > A_NORMAL (color.c) and KEY_NPGAE (keymap.c). > > I'll probably just go and install ncurses ... I'm using NetBSD right now to send this message and yes, if you want a decent curses, able to handle color (which is a blessing in Mutt), go and install ncurses 4.2.
Re: Questions concerning Pop3
Matthew Cordes <[EMAIL PROTECTED]> wrote: > Hello all. I seem to recall a way to make mutt check for new pop mail in the >background, anyone know of it? Additionally, is it possible to make mutt check for >new pop mail at regular intervals? > I recommend that you use fetchmail. To make mutt "do the work" I simply put in the following macros: macro index \Cf "!fetchmail -va\n" "grab pop3 mail verbosely" macro index \Cd "!fetchmail -d 120\n" "grab pop3 mail as daemon" macro index \Cq "!fetchmail -q\n" "kill fetchmail daemon" R. Marc
mailboxes command question
I've started playing with the mailboxes command and it's mutt is not responding how I understand it should according to the docs (or at least how I want it to respond). When I enter mutt using the -y option I see my defined mailboxes: -- Mutt: Mailboxes [1] 1 /var/spool/mail/rmarc 2 =mutt 3 =nanog 4 =rrdtool 5 =sabmag 7 =vpnd 8 =zebra >From what I understand, the [1] is notification that I have new mail in one of my mailboxes. This doesn't tell me WHICH mailbox has the new mail. some of these boxes can get quite large and I'd rather not have to open them to find out if there is new mail. I also have no desire to just toggle through the boxes with new mail. I want to be notified and then make the choice of opening the mailbox. If I get new mail while in mutt, I am notified that new mail has arrived and in what box. What I'd like to see is something like: -- Mutt: Mailboxes [1] 1 /var/spool/mail/rmarc 2 N =mutt 3 =nanog 4 =rrdtool 5 =sabmag 7 =vpnd 8 =zebra Anybody know if it's possible to do something like this within the current stock configuration, or should I simply hack that into mutt? R. Marc
Re: mailboxes command question
Chris Grossmann <[EMAIL PROTECTED]> wrote: > Have you looked at your folder_format variable? I think that "%N" > will give the notification you want, if I understand what you're asking.. No I hadn't. But that was exactly what I was looking for, thank you. R. Marc
Potentual bug
In feeding keybind/macro addiction I've come across a problem in mutt that might be a bug, but could equally as well be user error. This is duplicatable, so I'm leaning toward the bug side of the matter. If I'm in my default mailbox (!) and save a message, that message is then marked for deletion. If I then go into the directory browser and then back to my default mailbox, the mail message is no longer marked for deletion, though it did get copied to whatever folder I saved it to. If I simply mark it for deletion and do the same sequence of actions, the mail also looses it's marking. If I do this in any other folder, the message is deleted as I would expect. Relevant macros: macro pager l ? macro browser i I put these in to ease my transition from pine to mutt (hard to kick a 10 year old habit). Using Mutt 1.0pre2us compiled with ncurses. R. Marc
Re: wmaker and mutt
> I run windowmaker and would like to put an appicon on my desktop;
> perhaps there is here somebody who prefers this combination of a mailer
> and window manager and could help me a bit; any practical suggestions?
You can just make an xterm icon for it, but that's pretty boring. I've set
up wmmail (xbiff type o' thing..check http://bensinclair.com/dockapp/ for
it).
I've attached my config file for it. There's nothing mutt specific about
doing this other than that I call mutt.
R. Marc
{
DisableBeep = No;
DoubleClickTime = 250;
DisplayMessageCount = None;
DisplayColor = "#FF";
DisplayFont = "-*-helvetica-medium-r-*-*-10-*-*-*-*-*-*-*";
DisplayLocation = (0, 10);
ExecuteOnClick = "nxterm +vb +sb -T Mutt -e mutt";
ExecuteOnNewOnce = No;
Animations = {
Empty = {
Delay = 10;
Frames = ("/usr/local/GNUstep/Apps/WMMail.app/Anims/NeXT/Mail1.xpm");
};
Old = {
Delay = 10;
Frames = ("/usr/local/GNUstep/Apps/WMMail.app/Anims/NeXT/Mail1.xpm");
};
New = {
Delay = 2;
Frames = (
"/usr/local/GNUstep/Apps/WMMail.app/Anims/NeXT/Mail1.xpm",
"/usr/local/GNUstep/Apps/WMMail.app/Anims/NeXT/Mail2.xpm",
"/usr/local/GNUstep/Apps/WMMail.app/Anims/NeXT/Mail3.xpm",
"/usr/local/GNUstep/Apps/WMMail.app/Anims/NeXT/Mail2.xpm"
);
};
};
Mailboxes = (
{
Name = "my maildrop";
Type = mbox;
UpdateInterval = 15;
ExecuteOnUpdate = "";
Options = {
CheckTimeStampOnly = No;
Path = "/var/spool/mail/";
MailboxHasInternalData = Yes;
};
}
);
}
Re: wmaker and mutt
> In my opinion, wmmail is useless until you have a permanent connexion. I'm sure you have reason for this opinion, but if you use fetchmail wmmail is simply grand, permanent connection or no, IMHO. [snip] > and most of the time people are trying to minimise their connexion time...so. Hrm...what completely different worlds we live in. Even when I had a modem, I, and most of my friends, tried for 24x7 connections; didn't get it, but we certainly tried. R. Marc
Mutt "unstable" and Imap
I was in a sharing mood, so I thought I'd share :). I just downloaded and installed one of the unstable snapshot releases. Boy is it nice to have browsable imap directories. Only thing I've seen that is "unstable" is that it occasionally dies opening a large mailbox. Everything else works like a charm for me (the dying only happens about every 1 in 5 times for me, certainly nothing to fret about considering how quickly mutt starts back up). R. Marc
Re: Best 'unstable' version for IMAP and how to build it
Chris Green <[EMAIL PROTECTED]> wrote: > What's a reasonable stable version of mutt to build to get the new > IMAP4 goodies? Is the current 'unstable' version a reasonable one to > go for? > Then, when I've got the source, how do I build it? I picked up the snapshot from last friday (9/17) and it works pretty well for me. As noted in a previous post to this group, it does die, but only occasionally opening large mailboxes for me. I originally said about 1 in 5 times, but it's seems more like 1 in 10 now that I've run it all weekend. It dies on me ONLY on large boxes and has never died on me just opening up my inbox. As far as building it is concerned, all I did was: ./prepare --enable-imap make make install R. Marc
Bug in mutt for Solaris?
Hey there, I think I've stumbled across an interesting bug in mutt for Solaris. I could be wrong, but that's why I'm posting to this list first... :) Last night, I sent an email to my work email address, and with it, I attached my /var/mail/$USER file. This morning, upon coming into work, I found that the mail I sent had been stripped of it's attachment, and that the contents had been added to my existing /var/mail/$USER file is this a feature, because as far as I'm concerned, it's a bug that could potentially cause some damage. Here is some info on the mutt client I'm using at work; Mutt 1.0pre3i (1999-09-25) Copyright (C) 1996-9 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.6 [using slang 10003] Compile options: -DOMAIN -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP2 -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/lib/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" ISPELL="/usr/local/bin/ispell" _PGPPATH="/usr/local/bin/pgp" _PGPV2PATH="/usr/local/bin/pgp" To contact the developers, please mail to <[EMAIL PROTECTED]>. Any help on this would be much appreciated. Cheers, Marc -- Marc Silver IS Hosting Infrastructure The Internet Solution Tel: (+27 11) 283 5500 Fax: (+27 11) 283 5001 E-mail: [EMAIL PROTECTED] Web: www.is.co.za
mutt crashes when changing to a folder with lots of emails in it
I'm running mutt 1.5.21 in an Ubuntu 11.10 environment. My mail server is a gmail/imap server. I have about 900 emails (received/sent) in the Gmail/All Mail folder. I have threading turned on with: "set sort_aux=reverse-date-sent" "set sort=threads" in the muttrc file When changing from my inbox, the default folder to open when I start up Gmail, to the "All Mail" folder, mutt crashes (segmentation fault). I start up mutt again and then switch over to All Mail and it opens correctly. The crash only seems to happen when I move to "all mail". On smaller folders, like the "sent" folder which has about 300 emails, I don't experience a crash. I've read about segmentation faults with respect to changing IMAP folders etc. These issues seem to be different to my problem and they were reported against 1.5.19 and 1.5.20 Thanks in advance for any help offered. Regards, Marc --- Wherever you go, there you are Your luggage, however, is another matter.
forground color of the indicator
hi freaks. Is it possible to set the indicator foreground color to none? I mark new, old mails with colors and so i don't want to let the indicator change it. TIA marc(..)
Re: [OT] Only allow mail from selected addresses
On Sun, Apr 28, 2002 at 02:47:22PM +0200, [EMAIL PROTECTED] wrote: > However to rid my private inbox of that last 5% of spam I'd like to only > accept messages from a list of addresses... Relatively untested, but how about: # check whitelist. reverse the sense of the fgrep... FROM=`formail -rtzxTo:` :0: * ? /bin/fgrep -qvxis "$FROM" $HOME/.whitelist junkmail Should work well enough. I did something like this in front of my domain filter (I dump all hotmail.com, for example, but there are a couple I *do* want). -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Mutt's hooks and their logic
On Tue, Jun 11, 2002 at 03:18:51PM +0300, Jussi Ekholm wrote: > I wanted to ask about different hooks and their logic. Here's and > example of a send-hook: > But I was just wondering about the logic Muttþ uses with hooks. > Shouldn't that be plain obvious with that first send-hook, that *only* > add sig.foo to mails going to [EMAIL PROTECTED]? Why on earth do I need > send-hook to define, that I don't want to use sig.foo in every other > mail, as well? No, what happened was that you provided a method that got the signature set to 'sig.foo', but didn't provide any way for it to get set back to 'sig.default'. So... the first message that matched the hook altered the setting, and then there was nothing to set it back to the default. -- Marc Wilson [EMAIL PROTECTED] msg29041/pgp0.pgp Description: PGP signature
Re: navigation questions from a newbie
On Thu, Jun 13, 2002 at 11:19:34AM -0400, Brett Sanger wrote: > Is there an equivalent of the "sent-mail" folder? A convenient way to > make one? If I hand-roll (via perl) the monthly archiving of such folders > to mimic pine's behavior, what locking procedure does mutt use so that I > can ensure I don't trample while it's reading/writing? Do this: # make sure mail gets saved as mailx/pine would... send-hook . "set record=~/Mail/sent-mail-`date +%Y-%m`" set record="=sent-mail-`date +%Y-%m`" This gives you folders in ~/Mail that look like: $ ls Mail/sent-mail-2002* Mail/sent-mail-2002-01 Mail/sent-mail-2002-05 Mail/sent-mail-2002-04 Mail/sent-mail-2002-06 -- Marc Wilson [EMAIL PROTECTED]
Re: how to filter in procmail
On Sun, Jun 23, 2002 at 12:13:12PM -0700, John Smith wrote: > Well, i just subscribed to this list, and I'm wondering how do I filter this > into a separate mailbox with procmail? All the other mailing lists I'm > subscribed to are using X-Mailing-List in the headers. I examined the headers > coming in here, and I can't find something that would help me :-) I use: :0: * ^(From|To|Cc).*mutt-users mutt-users-ml -- Marc Wilson [EMAIL PROTECTED]
[PATCH] crude support for Maildir++ folders in mutt
Hi,
The patch below is a quick & dirty hack to make mutt handle Maildir++
(see http://www.inter7.com/courierimap/README.maildirquota.html).
folders and emulated sub-folders (with '.' as hierarchy separator).
It was generated against the latest mutt-1.5.x development (unstable)
CVS tree.
Here are my .muttrc settings to go with it:
set folder="maildir:/home/marc/Maildir:"
set
mask="!(^(tmp|cur|new|courierimapuiddb|courierimapsubscribed|procmail.log|\.\.ev-summary|\.\.)$)"
set spoolfile=~/Maildir
set record=~/Maildir/.Sent
Again, this is a hack, not a proper solution. Use at your own risk.
I'm no mutt developer, just a user who was tired of waiting forever
for mutt to slowly load big folders through a courier-imap server running
over loopback. Now at least it can access them directly.
I've also applied Michael Elkins's Maildir header caching patch
(http://www.cs.hmc.edu/~me/mutt/patch-1.5.0.me.hcache.8) which
provides a good speed improvement too.
Improvements or a proper implementation are welcome. Please Cc: responses
to marc at mbsi.ca as I do not always monitor the lists.
Cheers
Marc
--- muttlib.c 2002/07/04 12:30:59 1.1
+++ muttlib.c 2002/07/04 12:52:28
@@ -477,6 +477,18 @@
imap_expand_path (s, slen);
#endif
+ if (mx_is_maildir (s) && Maildir) {
+ strcpy(tmp, strchr(s, ':') + 1);
+ if(t = strchr(tmp, ':')) {
+ *t = '/';
+ t++;
+ while(t = strchr(t, '/')) {
+ *t = '.';
+ }
+ }
+ strfcpy(s, tmp, strlen(tmp) + 1);
+ }
+
return (s);
}
--- browser.c 2002/07/04 12:30:59 1.1
+++ browser.c 2002/07/04 12:30:59
@@ -608,6 +614,8 @@
imap_browse (LastDir, &state);
}
#endif
+if (!buffy && mx_is_maildir (LastDir))
+ mutt_expand_path (LastDir, sizeof (LastDir));
}
*f = 0;
--- mailbox.h 2002/07/04 12:30:59 1.1
+++ mailbox.h 2002/07/04 12:30:59
@@ -73,6 +73,7 @@
#ifdef USE_POP
int mx_is_pop (const char *);
#endif
+int mx_is_maildir (const char *);
int mx_access (const char*, int);
int mx_check_empty (const char *);
--- mx.c2002/07/04 12:30:59 1.1
+++ mx.c2002/07/04 12:30:59
@@ -354,6 +354,14 @@
}
#endif
+int mx_is_maildir (const char *p)
+{
+ if (!p)
+return 0;
+
+ return (url_check_scheme (p) == U_MAILDIR);
+}
+
int mx_get_magic (const char *path)
{
struct stat st;
--- url.c 2002/07/04 12:30:59 1.1
+++ url.c 2002/07/04 12:30:59
@@ -36,6 +36,7 @@
{ "pop", U_POP },
{ "pops",U_POPS },
{ "mailto", U_MAILTO },
+ { "maildir", U_MAILDIR },
{ NULL, U_UNKNOWN}
};
--- url.h 2002/07/04 12:30:59 1.1
+++ url.h 2002/07/04 12:30:59
@@ -9,6 +9,7 @@
U_IMAP,
U_IMAPS,
U_MAILTO,
+ U_MAILDIR,
U_UNKNOWN
}
url_scheme_t;
[PATCH] crude support for Maildir++ folders in mutt
Hi,
The patch below is a quick & dirty hack to make mutt handle Maildir++
(see http://www.inter7.com/courierimap/README.maildirquota.html).
folders and emulated sub-folders (with '.' as hierarchy separator).
It was generated against the latest mutt-1.5.x development (unstable)
CVS tree.
Here are my .muttrc settings to go with it:
set folder="maildir:/home/marc/Maildir:"
set
mask="!(^(tmp|cur|new|courierimapuiddb|courierimapsubscribed|procmail.log|\.\.ev-summary|\.\.)$)"
set spoolfile=~/Maildir
set record=~/Maildir/.Sent
Again, this is a hack, not a proper solution. Use at your own risk.
I'm no mutt developer, just a user who was tired of waiting forever
for mutt to slowly load big folders through a courier-imap server running
over loopback. Now at least it can access them directly.
I've also applied Michael Elkins's Maildir header caching patch
(http://www.cs.hmc.edu/~me/mutt/patch-1.5.0.me.hcache.8) which
provides a good speed improvement too.
Improvements or a proper implementation are welcome. Please Cc: responses
to marc at mbsi.ca as I do not always monitor the lists.
Cheers
Marc
--- muttlib.c 2002/07/04 12:30:59 1.1
+++ muttlib.c 2002/07/04 12:52:28
@@ -477,6 +477,18 @@
imap_expand_path (s, slen);
#endif
+ if (mx_is_maildir (s) && Maildir) {
+ strcpy(tmp, strchr(s, ':') + 1);
+ if(t = strchr(tmp, ':')) {
+ *t = '/';
+ t++;
+ while(t = strchr(t, '/')) {
+ *t = '.';
+ }
+ }
+ strfcpy(s, tmp, strlen(tmp) + 1);
+ }
+
return (s);
}
--- browser.c 2002/07/04 12:30:59 1.1
+++ browser.c 2002/07/04 12:30:59
@@ -608,6 +614,8 @@
imap_browse (LastDir, &state);
}
#endif
+if (!buffy && mx_is_maildir (LastDir))
+ mutt_expand_path (LastDir, sizeof (LastDir));
}
*f = 0;
--- mailbox.h 2002/07/04 12:30:59 1.1
+++ mailbox.h 2002/07/04 12:30:59
@@ -73,6 +73,7 @@
#ifdef USE_POP
int mx_is_pop (const char *);
#endif
+int mx_is_maildir (const char *);
int mx_access (const char*, int);
int mx_check_empty (const char *);
--- mx.c2002/07/04 12:30:59 1.1
+++ mx.c2002/07/04 12:30:59
@@ -354,6 +354,14 @@
}
#endif
+int mx_is_maildir (const char *p)
+{
+ if (!p)
+return 0;
+
+ return (url_check_scheme (p) == U_MAILDIR);
+}
+
int mx_get_magic (const char *path)
{
struct stat st;
--- url.c 2002/07/04 12:30:59 1.1
+++ url.c 2002/07/04 12:30:59
@@ -36,6 +36,7 @@
{ "pop", U_POP },
{ "pops",U_POPS },
{ "mailto", U_MAILTO },
+ { "maildir", U_MAILDIR },
{ NULL, U_UNKNOWN}
};
--- url.h 2002/07/04 12:30:59 1.1
+++ url.h 2002/07/04 12:30:59
@@ -9,6 +9,7 @@
U_IMAP,
U_IMAPS,
U_MAILTO,
+ U_MAILDIR,
U_UNKNOWN
}
url_scheme_t;
Re: [PATCH] crude support for Maildir++ folders in mutt
On Thu, Jul 04, 2002 at 10:50:59AM -0700, Will Yardley wrote: > Marc Boucher wrote: > > > > The patch below is a quick & dirty hack to make mutt handle Maildir++ > > (see http://www.inter7.com/courierimap/README.maildirquota.html). > > folders and emulated sub-folders (with '.' as hierarchy separator). > > It was generated against the latest mutt-1.5.x development (unstable) > > CVS tree. > > what exactly didn't work about using mutt with Maildir++ before? i've > never had a problem with it Try mutt -f +Folder or mutt -f +Folder/Subfolder to access ~/Maildir/.Folder or ~/Maildir/.Folder.Subfolder respectively. Marc > > -- > Will Yardley > input: william < @ hq . newdream . net . > >
Re: [PATCH] crude support for Maildir++ folders in mutt
On Thu, Jul 04, 2002 at 11:05:25AM -0700, Will Yardley wrote:
> Marc Boucher wrote:
> > On Thu, Jul 04, 2002 at 10:50:59AM -0700, Will Yardley wrote:
> > > Marc Boucher wrote:
>
> > > > The patch below is a quick & dirty hack to make mutt handle Maildir++
> > > > (see http://www.inter7.com/courierimap/README.maildirquota.html).
> > > > folders and emulated sub-folders (with '.' as hierarchy separator).
> > > > It was generated against the latest mutt-1.5.x development (unstable)
> > > > CVS tree.
> > >
> > > what exactly didn't work about using mutt with Maildir++ before? i've
> > > never had a problem with it
> >
> > Try
> > mutt -f +Folder
> > or
> > mutt -f +Folder/Subfolder
> >
> > to access
> >
> > ~/Maildir/.Folder
> > or
> > ~/Maildir/.Folder.Subfolder
> >
> > respectively.
>
> yeah but you can do mutt -f .Folder
> or
> mutt -f .Folder.Subfolder...
yes, but it's not practical.
> i agree that a patch to enter folder names in the conventional way would
> be nice just wasn't sure what your patch did.
>
> does it also make the folders show up "normally" in the folder index?
not yet, however the updated version below does reverse translation in
mutt_pretty_mailbox()..
Marc
--- muttlib.c 2002/07/04 12:30:59 1.1
+++ muttlib.c 2002/07/04 18:07:54
@@ -477,6 +477,18 @@
imap_expand_path (s, slen);
#endif
+ if (mx_is_maildir (s) && Maildir) {
+ strcpy(tmp, strchr(s, ':') + 1);
+ if(t = strchr(tmp, ':')) {
+ *t = '/';
+ t++;
+ while(t = strchr(t, '/')) {
+ *t = '.';
+ }
+ }
+ strfcpy(s, tmp, strlen(tmp) + 1);
+ }
+
return (s);
}
@@ -737,6 +749,24 @@
}
*q = 0;
+ if(Maildir && url_check_scheme(Maildir) == U_MAILDIR) {
+ char *mp, *mpe;
+
+ mp = strchr(Maildir, ':') + 1;
+ mpe = strchr(mp, ':');
+ if(mpe) {
+ len = mpe - mp;
+ if(!mutt_strncmp(s, mp, len) && s[len] == '/' && s[len+1] == '.') {
+ *s++ = '=';
+ memmove (s, s + len + 1, mutt_strlen (s + len + 1) + 1);
+ mp = s;
+ while(mp = strchr(mp, '.')) {
+ *mp = '/';
+ }
+ }
+ }
+ }
+
if (mutt_strncmp (s, Maildir, (len = mutt_strlen (Maildir))) == 0 &&
s[len] == '/')
{
--- mx.c2002/07/04 10:57:51 1.1
+++ mx.c2002/07/04 12:08:14
@@ -354,6 +354,14 @@
}
#endif
+int mx_is_maildir (const char *p)
+{
+ if (!p)
+return 0;
+
+ return (url_check_scheme (p) == U_MAILDIR);
+}
+
int mx_get_magic (const char *path)
{
struct stat st;
--- url.c 2002/07/04 11:04:46 1.1
+++ url.c 2002/07/04 11:04:50
@@ -36,6 +36,7 @@
{ "pop", U_POP },
{ "pops",U_POPS },
{ "mailto", U_MAILTO },
+ { "maildir", U_MAILDIR },
{ NULL, U_UNKNOWN}
};
--- url.h 2002/07/04 11:04:59 1.1
+++ url.h 2002/07/04 11:05:07
@@ -9,6 +9,7 @@
U_IMAP,
U_IMAPS,
U_MAILTO,
+ U_MAILDIR,
U_UNKNOWN
}
url_scheme_t;
--- browser.c 2002/07/04 11:42:43 1.1
+++ browser.c 2002/07/04 12:06:31
@@ -608,6 +614,8 @@
imap_browse (LastDir, &state);
}
#endif
+if (!buffy && mx_is_maildir (LastDir))
+ mutt_expand_path (LastDir, sizeof (LastDir));
}
*f = 0;
--- mailbox.h 2002/07/04 12:07:27 1.1
+++ mailbox.h 2002/07/04 12:07:37
@@ -73,6 +73,7 @@
#ifdef USE_POP
int mx_is_pop (const char *);
#endif
+int mx_is_maildir (const char *);
int mx_access (const char*, int);
int mx_check_empty (const char *);
reading color quoted replies
I'm wondering how people handle messages coming from outlook users that quote the message they're replying to (or their replies) in color instead of the usual angle indenting (> )? Thanks, Marc
Re: reading color quoted replies
On Tue, Jan 30, 2007 at 02:55:46PM +0100, Michael Tatge wrote: > * On Tue, Jan 30, 2007 Marc Vaillant ([EMAIL PROTECTED]) muttered: > > I'm wondering how people handle messages coming from outlook users that > > quote the message they're replying to (or their replies) in color > > instead of the usual angle indenting (> )? > > Outlook uses a indent string. Default '> '. It just _displays_ quotes > with color. The underlying message is still readable. > I'm not sure I fully understand what you mean. The message is readable, but the clarity that the color provides is lost when I view it in mutt because the only differentiator is color. I could open up the html in a graphical browser but I still can't tell apriori that the message contains the color tags. E.g. the above '> ' quoting would just look like: I'm wondering how people handle messages coming from outlook users that quote the message they're replying to (or their replies) in color instead of the usual angle indenting (> )? Outlook uses a indent string. Default '> '. It just _displays_ quotes with color. The underlying message is still readable. but in a graphical browser, your text would be in a different color than mine. Marc
Re: reading color quoted replies
On Tue, Jan 30, 2007 at 07:31:38PM +0100, Rado S wrote:
> =- Marc Vaillant wrote on Tue 30.Jan'07 at 12:59:46 -0500 -=
>
> > > * On Tue, Jan 30, 2007 Marc Vaillant ([EMAIL PROTECTED]) muttered:
> > > > I'm wondering how people handle messages coming from outlook
> > > > users that quote the message they're replying to (or their
> > > > replies) in color instead of the usual angle indenting (> )?
> >
> > The message is readable, but the clarity that the color provides
> > is lost when I view it in mutt because the only differentiator
> > is color. I could open up the html in a graphical browser but I
> > still can't tell apriori that the message contains the color
> > tags. E.g. the above '> ' quoting would just look like:
> > {...}
> > but in a graphical browser, your text would be in a different
> > color than mine.
>
> To answer your original Q:
> I do _not_ handle such eMail. Period. :)
>
> _You_ have several options:
> 1) educate your eMail partners to quote mutt-friendly (txt-only).
> 2) use autoview with a graphical browser => wiki FAQ.
> 3) use autoview with a script that converts such (*censored*)
> eMail to some sane usable format by converting the html/css
> coloring instructions to '> ' sequences.
>
> I recommend 1).
>
I guess that I was looking for option 3. Some sort of extension for w3m
(or another text based browser) that lets you do something reasonable
when dumping html with FONT COLOR tags to text (other than just removing
the tags).
Are you serious about option 1?
Marc
Re: reading color quoted replies
On Thu, Feb 01, 2007 at 07:21:07PM +0100, Rado S wrote: > =- David Champion wrote on Thu 1.Feb'07 at 10:25:13 -0600 -= > > > > i.e. the way of aiding is not stored in the data > > > itself but left up to the reader (the original www idea). > > > A tool can perform its beefing-up well enough on this simple/ > > > raw data, too, as mutt and other MUAs show. > > > > I agree with you, and I prefer that too, and from his post I > > think Marc is in our camp. > > However, Marc is uncertain about bringing this up with his > limited-/ outlook-only-/ awareness collegues. > I just don't understand how it's practical, or is necessarily a good thing for mutt/mutters to go on that sort of pilgrimage. > > But most people don't care that much, as long as they can tell > > the difference in their way, and most people don't want to > > deviate too far from whatever happens by default. > > That's true ... but is this (default=outlook/ html exclusive) what > we mutters want? (Marc being the one in this case) > This reasoning prevents freedom of "weapon"-choice/ personal > optimization/ general improvement: that's what mutters want. > > Not all defaults/ features are good just because they came first. > Isn't every company/ undertaking interested in improvement to > better succeed? Better "interoperability" suits them, too! > (Especially when they learn that there's an eMail-world beyond > the company limits. ;) This just isn't realistic. What sort of view of mutt do you think an outlook user (potential mutt user) is going to get if I tell them "Hey check out this great text based MUA that I have... only thing is, you know that feature that everyone in the office loves to use with their clients, well you have to tell them not to use it." The reality is that they're going to be thinking "Why would anyone be using a client that crippled them in that way?" And if that's what they're thinking then they're not going to have the view of "interoperability" that you suggest, they're going to view mutt as a program that doesn't (fully) support an "interoperable" standard like html. Shouldn't the mutt developer take your point of view and be interested in improvement to better succeed? In reality, it's mutt's success in retaining and building a user base that's more in jeopardy than my company loosing potential business with mutters. > > As often as people don't care for "a better" way, as often they > don't care for _any_ way, as long as it doesn't bother them much. > They just need a clue not to worry about a minor easy change (like > selecting text/plain '> ' quoting over html in an options box) and > some "conviction" to actually make the step. > People are more friendly/ helpful than many of us worry they are not. Even if they are friendly and comply, ultimately it works against you (see above). > Why keep "suffering" if things can be _easily_ changed when known? > When people learn that a _simple_ change helps both sides without > permanent losses to anyone, they are likely to apply it. > If _we_ mutters don't do anything about it, it won't change by > itself, as you noted _they_ won't do on their own. > > So... what's there to lose? Temporary friction. > What is to gain? Lasting improvement for all. > What does it take: just to ask them and patience to work against > an inert mass. > It won't hurt Marc to ask, except he's afraid of asking. > I'm not afraid to ask, I'm just wise enough to know that its futile, or worse, detrimental. > > Trying to persuade them otherwise often just makes one seem... well, > > too interested in telling others how to work, to put it gently. > > Although I'd love for everyone to work my way, telling them that > > they should usually doesn't work out very well. > > The problem is that mere trying/ learning/ asking is considered as > negative force that must be denied, as if thinking hurts them, > even more so any actual effort no matter how small and despite no > permanent drawbacks for them once applied. > > So it's better not even to try to make things better? > You (Marc) want to support this ignorance? > It's up to you, you have to live with either consequence (short > term no pain or long term gain), neither David nor I. ;) > > Improvement doesn't come without change, and this always causes > friction to some end: no gain without pain. It's just a matter whether > you want a) improvement and b) are willing to do what it takes. > > Often enough it only takes just a little to gain a lot. > The sad thing is people are too scared to make even smallest steps > and see the big gain that lies behind it. Yes, but equally sad are those who waste their lives pipe dreaming. Having enough foresight to know which battles will bring gain sorts the successful from the unsuccessful. Marc
Re: reading color quoted replies
On Fri, Feb 02, 2007 at 05:02:32PM +0100, Rado S wrote:
> {...}
> I'm sorry, explain, I don't see how it works against you when 2 sides
> agree on a common course that helps both by making things simpler.
>
> > I'm not afraid to ask, I'm just wise enough to know that its
> > futile, or worse, detrimental.
>
> How do you know that before actually getting confirmation from them?!
I don't have the time or energy to push this much further so I'm just
going to make a couple comments. I apologize for loosing my cool a bit
in my previous message. I should have admitted that I am afraid: If
%80 comply and %20 don't, then that's at least %20 who think I'm a
lunatic for wasting time working in a crippled environment. I work in a
startup of 10 people. I'm the only reason why our sys admin supports an
IMAP server along with Exchange. I'm the only reason why port 22 needs
to be open on our firewall and forwarded to a linux machine so I can
ssh, ssh tunnel, etc, use mutt, etc. By most in our company, the effort
to keep this going is considered a waste of time. Asking them to
restrict how they use their email--no matter how compelling an argument
I give--has a high probability of just strengthening that view. I don't
want to give them more fodder that might lead to losing my
environment. So, I'm not willing to just take a chance and see what
happens. Here's a Dilbert strip that my CEO put on my desk the other
day:
http://www.dilbert.com/comics/dilbert/archive/dilbert-20070125.html
It's these experiences and anecdotes that contribute to my pessimistic
view.
Re: HTML email, was Re: reading color quoted replies
On Thu, Feb 01, 2007 at 11:04:23PM -0600, Travis H. wrote: > I would say your best angle is a security angle. See if you can get > someone with the authority to recognize that reading your email with a > web browser and/or sending HTML poses a threat to the security of the > company and the users who don't know better. Ok, thanks Travis. I'm still pessimistic about being able to bring about real change this way. Unfortunately, I think that it's likely going to take enough people getting burned before widespread change. > > If you need some "argument by authority", I point you to the fact that > the DoD banned the use of HTML email and OWA: > > http://www.fcw.com/article97178-12-22-06-Web > Perhaps it starts with the DoD. Interestingly, all of the cited anecdotes suggest that html is not getting blocked, but is getting converted to text. Is there still considerable danger in dumping html via w3m or some other html to text converter? That's not a rhetorical question; I really don't know the answer and I'm not suggesting that html email not be banned even if the answer is no. Also, we correspond with several DoD organizations on a weekly basis. We've never had an email blocked, nor have we been told not to send html email. > On a personal level, you can always create an autoresponder that says > something like, "I'm sorry, but I was expecting an email from you and > instead I got a web page. I do not use a web browser to read email, > so I cannot view this. If you wish to communicate by email, please > try sending one." Ok, but I think that a less condescending, more diplomatic message that cites a real reason--like security--would be more effective.
Re: reading color quoted replies
On Mon, Feb 05, 2007 at 05:53:39PM -0600, Jeremy Blosser wrote: > Anyway, to the original question: the elinks and links family of text > browsers can render HTML colors as ascii. If you use those as your HTML > viewers you can get the colors and follow the quoting. Thanks very much. Hoping that it can sensibly dump HTML colors as ascii as well? I'll look into it. Marc
Re: HTML email, was Re: reading color quoted replies
On Thu, Feb 08, 2007 at 06:34:19PM +0100, Rado S wrote: > =- Marc Vaillant wrote on Thu 8.Feb'07 at 11:58:48 -0500 -= > > > Is there still considerable danger in dumping html via w3m or > > some other html to text converter? > > No, see wiki FAQ how to make it work. Ok thanks. I do it now, just wondering if there were any security risks. > > > Also, we correspond with several DoD organizations on a weekly > > basis. We've never had an email blocked, nor have we been told > > not to send html email. > > Some blocks are black holes: no response. > Not being told: maybe the other side sorts them as spam and deals > with it later when searching for false positives rather than > responding normally. The correspondence itself is not lost, but time. > But of course your company might be white-listed, so no problems > at all, no matter how spammy it looks. Understand, thanks. Marc
Re: HTML email, was Re: reading color quoted replies
On Thu, Feb 08, 2007 at 05:38:15PM -0600, Travis H. wrote:
> On Thu, Feb 08, 2007 at 06:34:19PM +0100, Rado S wrote:
> > > Is there still considerable danger in dumping html via w3m or
> > > some other html to text converter?
>
> Well, theoretically, any time you operate on data provided by someone
> who may not be trustworthy, you face a risk. The magnitude of the
> risk is dependent on the complexity of the program you're using to
> process it. {}
Thanks for the info Travis.
Marc
Re: reading color quoted replies
On Thu, Feb 08, 2007 at 05:49:45PM -0600, Travis H. wrote:
> On Thu, Feb 08, 2007 at 06:29:35PM +0100, Rado S wrote:
> > > I work in a startup of 10 people. I'm the only reason {... for
> > > IMAP, ssh, linux.}
> > > By most in our company, the effort to keep this going is
> > > considered a waste of time.
>
> I'd jump ship, honestly. I really don't like the Windows environment;
> I don't know what it's doing well enough, and Redmond makes it as hard
> as possible to learn. It can't easily be automated, etc. etc...
>
> If you would be interested in doing Linux work, send me your
> resume... my employer is trying very hard to find Linux techs.
> {...}
>
I hate the windows environment, but fortunately I don't do anything
close to the os. I'm a scientific programmer/applied mathematician
writing software in C++. I can live with the environment because of
tools like vnc, smb, sshfs, which let me work in linux or os x for 98%
of what I need to do. I used cygwin for about 3 years but grew tired
of its little issues (still using it when I actually must do something
on a windows machine).
Thanks for encouraging me to submit my resume but even though I hate
Windows, I wouldn't change my job for anything right now.
Best,
Marc
Why does a maildir resync take 4mn? (maildir_header_cache_verify = no)
I have set folder="~/Maildir/" set header_cache="~/Maildir/" set maildir_header_cache_verify = no The header cache definitely helps, I can open a 40,000 message maildir in seconds instead of several minutes. However, if the parent directory of the folder I'm viewing, gets modified (let's say I'm in ~/Maildir/.snd/ and I send a new mail), mutt takes a silly time to resync the folder, like 4mn for 40,000 messages. Is there anything I can do to make mutt more bearable in this case like this? Why is mutt resyncing everything when I do have maildir_header_cache_verify set to no? What else can I do to stop this? I have Mutt 1.5.13 (2006-08-11) -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_INODESORT +USE_POP +USE_IMAP -USE_GSS -USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -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_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL Thanks Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/
"N" flag not changing to "O" on some imap servers
Hi all, Sifting through the mailing list archives on this problem and not finding much on this as a general problem. I also haven't been able to access the Wiki so sorry if the answer is there. Anyway, I'm running 1.5.13 and with some IMAP servers I find that unread new messages don't get marked "O" the next time I log in. Any remedy for this, or is it an IMAP server setting that is out of my control? Thanks, Marc
Re: signature at the beginning, not the end
On Thu, Sep 13, 2007 at 11:04:59AM -0400, Ben Gladwell wrote: > Is there a way to tell mutt that I write my response at the top of the > message, not the bottom, and that it should insert the signature right > above the line that says "On , wrote:" Top-posting is evil, and should always be discouraged. I suppose since you do that, you don't edit your replies either? -- Marc Wilson | The graveyards are full of indispensable men. -- [EMAIL PROTECTED] | Charles de Gaulle
Re: signature at the beginning, not the end
On Sat, Sep 15, 2007 at 07:12:59PM +0100, Arthur Dent wrote: > I have still not plucked up the courage to admit that I never saw the > reply to my post and I have no idea what was said! Your argument is spurious. Any decently managed mailing list maintains archives of past messages. It is not necessary for you to archive the entire list locally. -- Marc Wilson | Audacity, and again, audacity, and always audacity. [EMAIL PROTECTED] | -- G.J. Danton pgpSgI6EGsAN0.pgp Description: PGP signature
Re: OS X (Intel) build problems
On Thu, Oct 18, 2007 at 11:39:58PM -0400, David King wrote: > Hi, I'm new to mutt and I'm trying to build it on OS X (10.4.10, Intel), > GNU make (3.80), and GNU gcc (4.0.1). I installed the ncurses-5.6 and > libiconv-1.11 libs like the INSTALL file said I would need to. I then > did ./configure and ./make install everything completed without errors. > When I try to run mutt however it gives me the following: > If you're still having problems and you're ok with version 1.5.13 or 1.4.2.2 then why not just use darwinports http://darwinports.com. It's as simple as typing port install mutt-devel for 1.5.13 or port install mutt for 1.4.2.2 Marc
upgrade to 1.5.17 and header cache no longer working
Hi, I just upgraded mutt from 1.5.13 to 1.5.17 and header cache no longer seems to work. I'm using the darwinports install. Below is the output from mutt -v. My muttrc has "set header_cache=~/Mail". I deleted the db files in ~/Mail from my previous version. All that ends up in ~/Mail are empty "imaps:[EMAIL PROTECTED]" directories for each of my imap accounts. Thanks, Marc Mutt 1.5.17 (2007-11-01) Copyright (C) 1996-2007 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: Darwin 8.4.1 (i386) ncurses: ncurses 5.5.20051010 (compiled with 5.5) libiconv: 1.11 hcache backend: Sleepycat Software: Berkeley DB 4.4.20: (January 10, 2006) Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_INODESORT +USE_POP +USE_IMAP -USE_SMTP -USE_GSS +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/opt/local/share/mutt" SYSCONFDIR="/opt/local/etc" EXECSHELL="/bin/sh" -MIXMASTER To contact the developers, please mail to <[EMAIL PROTECTED]>. To report a bug, please visit http://bugs.mutt.org/.
Re: upgrade to 1.5.17 and header cache no longer working
On Thu, Nov 29, 2007 at 08:55:30AM -0600, Kyle Wheeler wrote: > On Thursday, November 29 at 07:15 AM, quoth Marc Vaillant: > > I just upgraded mutt from 1.5.13 to 1.5.17 and header cache no > > longer seems to work. I'm using the darwinports install. Below is > > the output from mutt -v. My muttrc has "set header_cache=~/Mail". > > I deleted the db files in ~/Mail from my previous version. All that > > ends up in ~/Mail are empty "imaps:[EMAIL PROTECTED]" directories for > > each of my imap accounts. > > I'm not certain, but I believe that it may require a / on the end when > you're intending to use a directory of cache files. > Hmm, tried that but it still doesn't work. Thanks, Marc
Re: upgrade to 1.5.17 and header cache no longer working
On Thu, Nov 29, 2007 at 05:29:46PM +0100, Rocco Rutte wrote: > Hi, > > * Marc Vaillant wrote: > >> I just upgraded mutt from 1.5.13 to 1.5.17 and header cache no longer >> seems to work. I'm using the darwinports install. Below is the output >> from mutt -v. My muttrc has "set header_cache=~/Mail". I deleted the >> db files in ~/Mail from my previous version. All that ends up in ~/Mail >> are empty "imaps:[EMAIL PROTECTED]" directories for each of my imap >> accounts. > > So the same as in: > > http://dev.mutt.org/trac/ticket/2978 > > applies to you, too? Any chance you can try installing mutt with support > for gbdm and report if that works? Thanks Rocco, that was exactly it. I installed with support for gbdm and it works now. Sorry to bother everyone, I should have checked there first. I will notify the macports maintainer. 73, Marc
Re: Leopard Migration Hammered Mutt
On Thu, Jan 24, 2008 at 06:21:05PM +0100, Thomas Roessler wrote: > On 2008-01-24 15:36:11 +, [EMAIL PROTECTED] wrote: > > > Recently, I switched from and older MacBook Pro to a new MacBook > > using Apple's Migration Assistant. All User issues went well, > > but unix issues did not fair so well. One of which was my mutt > > setup which had worked for years, and even many months under > > Leopard. > > > Now I get the following when I attempt to evoke mutt: > > > -bash: mutt: command not found > > > Could someone walk me through this slowly? I have some unix > > background, but it's been quite a while since I've configured > > mutt. > > That actually sounds as though your PATH environment variable is > hosed now. > If it turns out that it's not a path issue, use MacPorts http://www.macports.org to reinstall. Once you've installed macports, it's as easy as typing sudo port install mutt-devel Best, Marc
Re: Leopard Migration Hammered Mutt
On Sat, Jan 26, 2008 at 05:13:11PM +, [EMAIL PROTECTED] wrote:
> export shows:
>
> PATH="/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin"
>
> Mutt is in /sw/bin/
>
> How can I add /sw/bin/ to my path?
>
put
export PATH=${PATH}:/sw/bin
in ~/.profile
Marc
emails that make mutt fail to open my mailbox
Every once in a while (like every year) I get a message that completely fracs up mutt's access to my mailbox (IMAP). Or some sequence of events corrupts a message to manifest this problem. Mutt parses my entire mailbox, and then at the end it completely fails to open it. However, there is no problem with access to my mailbox from other IMAP clients. This happened to me yesterday. I turned on debugging which reports the following at the end of parsing the mailbox: 5< a0005 NO The requested message could not be converted to an RFC-822 compatible format. IMAP queue drained Error opening mailbox The entire debug level 3 log--sans most of the private information--can be found at: http://stuff.vaillant.fastmail.fm/muttdebug0Info.txt When I moved all the messages I received yesterday out of my mailbox, everything worked fine. I've also attached mutt -v output. I'm using headercache with GDBM and I did try deleting my cache which didn't solve the problem. Any help is greatly appreciated. Thanks, Marc Mutt 1.5.17 (2007-11-01) Copyright (C) 1996-2007 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: Darwin 8.4.1 (i386) ncurses: ncurses 5.5.20051010 (compiled with 5.5) libiconv: 1.11 hcache backend: GDBM version 1.8.3. 10/15/2002 (built Nov 29 2007 12:09:03) Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_INODESORT +USE_POP +USE_IMAP -USE_SMTP -USE_GSS +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/opt/local/share/mutt" SYSCONFDIR="/opt/local/etc" EXECSHELL="/bin/sh" -MIXMASTER To contact the developers, please mail to <[EMAIL PROTECTED]>. To report a bug, please visit http://bugs.mutt.org/.
Re: Mutt tty problems on Mac OS X 10.5.4 and mutt 1.5.18
I don't understand why there are so many problems? Are you using the macports install? The following macports install: sudo port install mutt-devel +debug+gdbm+headercache+imap+pop+ssl works out of the box for me on 10.5.4. No issues at all running it in a Terminal, nor in a gnu screen session in Terminal. Marc On Wed, Aug 20, 2008 at 09:02:02AM -0700, [EMAIL PROTECTED] wrote: > On Wed, Aug 20, 2008 at 09:48:56AM -0500, Kyle Wheeler wrote: > > > I wonder? what version of ncurses are you linked to? (mutt -v will tell > > you) I use ncurses 5.6.20061217, but I installed that myself via MacPorts. > > Mutt 1.5.18 (2008-05-17) > Copyright (C) 1996-2008 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: Darwin 9.4.0 (i386) > ncurses: ncurses 5.4.20041023 (compiled with 5.4) > libiconv: 1.11 > Compile options: > -DOMAIN > -DEBUG > -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE > +USE_FCNTL -USE_FLOCK > +USE_POP +USE_IMAP +USE_SMTP -USE_GSS +USE_SSL_OPENSSL > -USE_SSL_GNUTLS +USE_SASL +HAVE_GETADDRINFO > -HAVE_REGCOMP +USE_GNU_REGEX > +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET > +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM > +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME > -CRYPT_BACKEND_GPGME > -EXACT_ADDRESS -SUN_ATTACHMENT > +ENABLE_NLS +LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET > +HAVE_LANGINFO_YESEXPR > +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE > -ISPELL > SENDMAIL="/usr/sbin/sendmail" > MAILPATH="/var/mail" > PKGDATADIR="/sw/share/mutt" > SYSCONFDIR="/sw/etc" > EXECSHELL="/bin/sh" > -MIXMASTER > To contact the developers, please mail to <[EMAIL PROTECTED]>. > To report a bug, please visit http://bugs.mutt.org/. > > patch-1.5.18.sidebar.20080517.txt > > Just for grins, I ran this on one of the Linux systems I use which > does display properly, a gentoo ~amd64. It is older but ncurses is > newer. Since ascii_chars at least makes the display readable, I think > I will stick with that and the old ncurses rather tn install more > custom software. > > Mutt 1.5.16 (2007-06-09) > Copyright (C) 1996-2007 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.6.26-gentoo-r1 (x86_64) > ncurses: ncurses 5.6.20061217 (compiled with 5.6) > libidn: 1.9 (compiled with 1.5) > Compile options: > -DOMAIN > -DEBUG > +HOMESPOOL -USE_SETGID +USE_DOTLOCK +DL_STANDALONE > -USE_FCNTL +USE_FLOCK -USE_INODESORT > -USE_POP +USE_IMAP -USE_SMTP -USE_GSS -USE_SSL_OPENSSL +USE_SSL_GNUTLS > +USE_SASL +HAVE_GETADDRINFO > -HAVE_REGCOMP +USE_GNU_REGEX > +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET > +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM > +CRYPT_BACKEND_CLASSIC_PGP -CRYPT_BACKEND_CLASSIC_SMIME > -CRYPT_BACKEND_GPGME > -EXACT_ADDRESS -SUN_ATTACHMENT > +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS > +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR > +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE > ISPELL="/usr/bin/ispell" > SENDMAIL="/usr/sbin/sendmail" > MAILPATH="Maildir" > PKGDATADIR="/usr/share/mutt" > SYSCONFDIR="/etc/mutt" > EXECSHELL="/bin/sh" > MIXMASTER="mixmaster" > To contact the developers, please mail to <[EMAIL PROTECTED]>. > To report a bug, please visit http://bugs.mutt.org/. > > patch-1.5.6.dw.pgp-timeout.1 > patch-1.5.6.dw.mbox-hook.1 > patch-1.5.16.rr.compressed.1 > patch-1.5.4.lpr.collapse_flagged Lukas P. Ruf <[EMAIL PROTECTED]> > > -- > ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. > Felix Finch: scarecrow repairman & rocket surgeon / [EMAIL PROTECTED] > GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 > I've found a solution to Fermat's Last Theorem but I see I've run out of room > o
Re: Mutt tty problems on Mac OS X 10.5.4 and mutt 1.5.18
On Fri, Aug 22, 2008 at 07:10:18AM -0700, [EMAIL PROTECTED] wrote: > On Fri, Aug 22, 2008 at 09:30:27AM -0400, Marc Vaillant wrote: > > I don't understand why there are so many problems? Are you using the > > macports install? The following macports install: > > > > sudo port install mutt-devel +debug+gdbm+headercache+imap+pop+ssl > > > > works out of the box for me on 10.5.4. No issues at all running it in a > > Terminal, nor in a gnu screen session in Terminal. > > This is my first Mac experience. I just used the mutt that runs when > I type "mutt" -- I have been assuming it's part of the OS X 10.5.4 > release. Ok, if macports isn't installed on your machine, you need to install it. It's a software management system: http://www.macports.org/install.php Once it's installed, all you need to do is type sudo port install mutt-devel and it will download mutt and all it's dependencies, compile them and install. I use imap with ssl and headercache so I also include those variants and instead type: sudo port install mutt-devel +gdbm+headercache+imap+ssl Best, Marc
Re: Mutt tty problems on Mac OS X 10.5.4 and mutt 1.5.18
On Fri, Aug 22, 2008 at 03:01:08PM -0700, [EMAIL PROTECTED] wrote: > On Fri, Aug 22, 2008 at 09:20:47AM -0500, Kyle Wheeler wrote: > > On Friday, August 22 at 07:10 AM, quoth [EMAIL PROTECTED]: > > > This is my first Mac experience. I just used the mutt that runs > > > when I type "mutt" -- I have been assuming it's part of the OS X > > > 10.5.4 release. > > > > Interesting! Where did you get your Mac? Apple does not distribute a > > version of mutt in any form, so I had been assuming that you compiled > > your own. If it was already on your computer, perhaps someone else put > > it there? > > The plot thickens! I got it from the sysadmin at work who buys them > from the Apple store. As far as I know, all the sysadmin does is > configure the networking and (for devs) install Parallels, which is an > abomination. I shall enquire! > > I will also check the ports install. Definitely try the macports install. The macports distributions are well maintained. I bet you'll be up and running with no problems in 15 minutes. Macports, in general, will simplify your life :) Marc
Re: Mutt on Macbook
On Fri, Dec 19, 2008 at 06:56:38PM -0500, Joseph wrote: > Getting started with a Mac and being spoiled with Debian, > > I tried Macports to get mutt. > > But I got an old version. > > How do I get a current copy, and how do I stay current on it? > port install mutt-devel That will get you 1.5.18 In general, I think that you will find that macports packages are better maintained than fink. To see the available add on features port variants mutt-devel which gives: idn: Internationalized Domain Name support pop: POP support imap: IMAP support ssl: Secure Sockets Layer support sasl: Simple Authentication and Security Layer support debug: Debugging support gnuregex: Use the GNU regular expression library compress: Compressed folders headercache: Enable header caching (requires gdbm or qdbm) qdbm: Use QDBM database gdbm: Use GNU dbm database db4: Use Berkeley DB database nntp: NNTP support deepif: Allow nested if-else sequences in strings date_conditional: Allow the format of dates in the index to vary based on how recent the message is xlabel: Custom message-tagging - X-Label: smtp: Include internal SMTP relay support trash: Add a Trash folder sidebar: Add a sidebar with a list of folders gpgme: Enable GPGME crypto support So for example to add imap, headercache, and ssl support do port install mutt-devel+imap+headercache+ssl Best, Marc
Re: Mutt on Macbook
On Sat, Dec 20, 2008 at 08:10:39AM -0500, Joseph wrote: > On 12/19/08, Marc Vaillant wrote: > > On Fri, Dec 19, 2008 at 06:56:38PM -0500, Joseph wrote: > > > Getting started with a Mac and being spoiled with Debian, > > > > > > I tried Macports to get mutt. > > > > > > But I got an old version. > > > > > > How do I get a current copy, and how do I stay current on it? > > > > > > > > > port install mutt-devel > > > > That will get you 1.5.18 > > > > In general, I think that you will find that macports packages are better > > maintained than fink. > > Great, thanks for the answers. In case someone else is learning, it > seems you need to do sudo port install mutt-devel +imap +headercache +ssl > > Note the spaces needed. Sorry, typo. Space should only be needed between the package name and the variants: sudo port install mutt-devel +imap+headercache+ssl Marc
Re: what is the benefit of imap?
On Thu, Mar 19, 2009 at 10:23:30AM +0100, Stephan Seitz wrote: > On Thu, Mar 19, 2009 at 09:06:14AM +, Chris G wrote: >> Are they on your LAN? Using IMAP across the internet (even with a >> good ADSL connection) can never really be as quick as a local mbox >> spool, especially if you're dealing with attachments and such. Think >> about it - a 1Mbyte attachment is going to take some seconds to pull >> across even a 2 or 3Mb/s ADSL link whereas it's going to be near >> instantanous from a local file. > > Sorry, but I think, here you are wrong. Good IMAP-Clients don’t download > the attachments without your interaction (at least you can configure them > in such a way). So the reading of the mails should be fast in both ways. > But if you wish to open an attachment, IMAP is better than using SSH and > local spool. Is there a way to view the body of an imap message without mutt actually fetching (not saving) all attachments? Fetching a 5-10mb attachment just to view the body text is a significant annoyance when I'm away from my local work LAN. I'd like to be able to view the body text and have mutt fetch the attachments only when I hit "v" -> "return" to view the attachment. > With IMAP you only download the attachment, and then the > local application will deal with it. With SSH and local spool you must > start the application remote. >
Re: what is the benefit of imap?
On Thu, Mar 19, 2009 at 09:06:16AM -0500, Kyle Wheeler wrote: > On Thursday, March 19 at 09:21 AM, quoth Marc Vaillant: > >> Sorry, but I think, here you are wrong. Good IMAP-Clients don’t > >> download the attachments without your interaction (at least you can > >> configure them in such a way). So the reading of the mails should > >> be fast in both ways. But if you wish to open an attachment, IMAP > >> is better than using SSH and local spool. > > > > Is there a way to view the body of an imap message without mutt actually > > fetching (not saving) all attachments? > > Not with mutt. Since mutt was originally designed for viewing a local > mail spool, it has no concept of "partial" messages. Mutt's IMAP > features are really there to simulate a local mail spool, which means > certain features like that would be tough to add (not impossible, but > tough). Ok, understood. > > Depending on your definitions, that may mean that mutt isn't a "good" > IMAP client. It's *reliable*, and it *works*, but it certainly doesn't > take advantage of all the features of IMAP that it theoretically > could. I agree. Support for IMAP in mutt certainly has improved over the years though. Before header-cache, IMAP was basically unusable without something like offlineimap. > > > Fetching a 5-10mb attachment just to view the body text is a > > significant annoyance when I'm away from my local work LAN. I'd like > > to be able to view the body text and have mutt fetch the attachments > > only when I hit "v" -> "return" to view the attachment. > > Suggest the feature to the developers. Better yet, implement it > yourself and submit a patch! Be warned, though: that patch would take > a *lot* of work. I've been a user for over a decade now. I'd love to contribute, I just don't have time right now :( Marc
Mutt 1.5.19 segfault on FreeBSD (mutt-devel port)
Hi all, I've just compiled mutt 1.5.19 on my freebsd (7.1) laptop and mutt 1.5.19 is unable to start. I've a working config from another freebsd.. All infos i can provides : mutt -v Mutt 1.5.19 (2009-01-05) Copyright (C) 1996-2009 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: FreeBSD 7.1-STABLE (i386) ncurses: ncurses 5.7.20081102 (compiled with 5.6) libiconv: 1.11 libidn: 1.13 (compiled with 1.13) hcache backend: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003) Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL +USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +COMPRESSED +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT -ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -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 . To report a bug, please visit http://bugs.mutt.org/. patch-1.5.17.sidebar.20080412 vvv.quote patch-1.5.0.ats.date_conditional.1 dgc.deepif.1 vvv.initials rr.compressed gdb mutt Program received signal SIGSEGV, Segmentation fault. 0x28693c12 in memcpy () from /lib/libc.so.7 (gdb) bt #0 0x28693c12 in memcpy () from /lib/libc.so.7 #1 0x282db449 in c2i_ASN1_BIT_STRING () from /lib/libcrypto.so.5 #2 0x282d8eb9 in asn1_ex_c2i () from /lib/libcrypto.so.5 #3 0x282d97a1 in asn1_ex_c2i () from /lib/libcrypto.so.5 #4 0x282da12c in ASN1_item_ex_d2i () from /lib/libcrypto.so.5 #5 0x282d9bde in asn1_ex_c2i () from /lib/libcrypto.so.5 #6 0x282d9ee7 in asn1_ex_c2i () from /lib/libcrypto.so.5 #7 0x282da688 in ASN1_item_ex_d2i () from /lib/libcrypto.so.5 #8 0x282d9bde in asn1_ex_c2i () from /lib/libcrypto.so.5 #9 0x282d9ee7 in asn1_ex_c2i () from /lib/libcrypto.so.5 #10 0x282da688 in ASN1_item_ex_d2i () from /lib/libcrypto.so.5 #11 0x282d9bde in asn1_ex_c2i () from /lib/libcrypto.so.5 #12 0x282d9ee7 in asn1_ex_c2i () from /lib/libcrypto.so.5 #13 0x282da688 in ASN1_item_ex_d2i () from /lib/libcrypto.so.5 #14 0x282daab1 in ASN1_item_d2i () from /lib/libcrypto.so.5 #15 0x282ae405 in d2i_X509 () from /lib/libcrypto.so.5 #16 0x2838127a in ssl3_get_server_certificate () from /usr/lib/libssl.so.5 #17 0x28382812 in ssl3_connect () from /usr/lib/libssl.so.5 #18 0x2838a7ea in SSL_connect () from /usr/lib/libssl.so.5 #19 0x2837333b in ssl23_connect () from /usr/lib/libssl.so.5 #20 0x2838a7ea in SSL_connect () from /usr/lib/libssl.so.5 #21 0x080e509f in ?? () #22 0x288b3040 in ?? () #23 0x0021 in ?? () #24 0x0004 in ?? () #25 0x in ?? () #26 0x288b3040 in ?? () #27 0x28886bc0 in ?? () #28 0x28886bc0 in ?? () #29 0x0009 in ?? () #30 0x0088 in ?? () #31 0x288aebc0 in ?? () #32 0x0009 in ?? () #33 0x2838c5fa in SSL_set_fd () from /usr/lib/libssl.so.5 #34 0x080e5015 in ?? () #35 0x288a2000 in ?? () #36 0x288aeaf0 in ?? () #37 0xbfbfd388 in ?? () #38 0x080c6fc8 in ?? () #39 0x0001 in ?? () #40 0x in ?? () #41 0xbfbfd478 in ?? () #42 0xbfbfd38c in ?? () #43 0x28709400 in ?? () #44 0x288aeaf0 in ?? () #45 0xbfbfd3b8 in ?? () #46 0x080e3626 in ?? () #47 0x288a2000 in ?? () #48 0x288a2000 in ?? () #49 0xbfbfd3a8 in ?? () ---Type to continue, or q to quit--- #50 0x080e4033 in ?? () #51 0x0001 in ?? () #52 0x0574 in ?? () #53 0xbfbfd3a8 in ?? () #54 0x080e4e00 in ?? () #55 0x in ?? () #56 0x in ?? () #57 0xbfbfd7e8 in ?? () #58 0x080e3da7 in ?? () #59 0x288a2000 in ?? () #60 0x28709400 in ?? () #61 0xbfbfd7e8 in ?? () #62 0x080efd42 in ?? () #63 0x288a2000 in ?? () #64 0x288a2000 in ?? () #65 0x in ?? () #66 0x70616d69 in ?? () #67 0x2f2f3a73 in ?? () #68 0x70616d69 in ?? () #69 0x6c69702e in ?? () #70 0x7973746f in ?? () #71 0x6d657473 in ?? () #72 0x656e2e73 in ?? () #73 0x39393a74 in ?? () #74 0x2f33 in ?? () #75 0x in ?? () #76 0x in ?? () #77 0x in ?? () #78 0x in ?? () #79 0x in ?? () #80 0x in ?? () #81 0x in ?? () #82 0x in ?? () #83 0x in ?? () #84 0x in ?? () #85 0x287140b4 in ?? () #86 0x28140e00 in ?? () #87 0x7ffd in ?? () #88 0x0208 in ?? () #89 0x287140b2 in ?? () #90 0x7fff in ?? () #91 0x281db800 in ?? () #92 0x281dba00 in ?? () #93 0x281dbc00 in ?? () #94 0x281dbe00 in ?? () #95 0x281dc000 in ?? () #96 0x in ?? () #97 0x0070 in ?? () #98 0
Re: Compiling mutt for OS X; using SMTP option. What libraries
Just use macports. Type $ port install mutt-devel +pop+smtp+ssl+sasl+headercache to see all the available options you can type $ port variants mutt-devel which will give: mutt-devel has the variants: idn: Internationalized Domain Name support pop: POP support imap: IMAP support ssl: Secure Sockets Layer support sasl: Simple Authentication and Security Layer support debug: Debugging support gnuregex: Use the GNU regular expression library compress: Compressed folders headercache: Enable header caching (requires gdbm or qdbm) qdbm: Use QDBM database gdbm: Use GNU dbm database db4: Use Berkeley DB database nntp: NNTP support deepif: Allow nested if-else sequences in strings date_conditional: Allow the format of dates in the index to vary based on how recent the message is xlabel: Custom message-tagging - X-Label: smtp: Include internal SMTP relay support trash: Add a Trash folder sidebar: Add a sidebar with a list of folders gpgme: Enable GPGME crypto support universal: Build for multiple architectures Best, Marc On Mon, Mar 30, 2009 at 10:38:06AM -0500, russurquha...@verizon.net wrote: > > Hi, > > I've been trying to compile mutt to use SMTP. I've used the following > configure: > > ./configure --prefix=/usr/local --with-curses --with-regex > --enable-locales-fix \ > --enable-pop --enable-smtp --with-sasl --enable-hcache --with-ssl > $ make > > > when i get to the make part, it bombs out looking for sasl. > > My question, what additional applications/libraries are needed? Is this > written in any documentation somewhere? Do i NEED fink to do this? > > I'm a somewhat technical tech writer, that would gladly share any info > he finds out if someone could help on this! > > Thanks, > > > Russ
Re: looking for simple "rss to .signature"-script
Hi, > I'm looking for a way to integrate the latest post on my blog into my > .signature-file. I remember having come across something like this > months ago, but can't seem to find it now. Maybe you know a simple > solution? The result should look something like my manual sig below. I recently discovered a tool called xmlstarlet which lets you extract stuff from xml data. Maybe you could use something like this on your blog's rss feed: $ curl -s http://michaelmaurer.net/rss.xml | \ xmlstarlet sel -t -m /rss/channel/item -v link -n | \ head -n1 > ~/.signature Marc
why is there no auto $ (save changes to mailbox)?
Hi all, I've been a happy mutt user for over a decade. Of course there are a few minor features here and there that I wish mutt had. The one that's really getting to me lately is that as far as I know, there is no automatic way to execute "$". i.e. save changes to mailbox. This is particularly a problem for IMAP because losing your internet connection (e.g. sleeping your laptop) usually means losing mailbox changes. If there is a mechanism for accomplishing this now please let me know. Otherwise, it seems natural for it to be an action during mail check? Shouldn't there be at least an auto save/recover mechanism? Thanks, Marc
Re: why is there no auto $ (save changes to mailbox)?
On Mon, Aug 10, 2009 at 04:44:57PM +0200, Michael Tatge wrote: > * On Mon, Aug 10, 2009 09:23AM -0400 Marc Vaillant > * (vaill...@fastmail.fm) muttered: > > there is no automatic way to execute "$". i.e. save changes to > > mailbox. This is particularly a problem for IMAP because losing your > > internet connection (e.g. sleeping your laptop) usually means losing > > mailbox changes. > > No, there isn't. And that's a good thing (TM). I don't want messages to > be auto deleted. which may suggest that that sync-mailbox isn't properly abstracted. Perhaps you should be able to sync message flags separately from confirming message deletion. > If you want such a feature you always make a macro that does that. > e.g. macro index Thanks, I will try that. Marc
Re: why is there no auto $ (save changes to mailbox)?
On Mon, Aug 10, 2009 at 04:44:57PM +0200, Michael Tatge wrote: > * On Mon, Aug 10, 2009 09:23AM -0400 Marc Vaillant > * (vaill...@fastmail.fm) muttered: > > there is no automatic way to execute "$". i.e. save changes to > > mailbox. This is particularly a problem for IMAP because losing your > > internet connection (e.g. sleeping your laptop) usually means losing > > mailbox changes. > > No, there isn't. And that's a good thing (TM). I don't want messages to > be auto deleted. Actually I'm remembering that there is the delete config option which takes care of this. > If you want such a feature you always make a macro that does that. > e.g. macro index mutt errors on this macro. Marc
Re: why is there no auto $ (save changes to mailbox)?
On Mon, Aug 10, 2009 at 12:11:27PM -0500, Kyle Wheeler wrote: > On Monday, August 10 at 12:34 PM, quoth Marc Vaillant: > >> If you want such a feature you always make a macro that does that. > >> e.g. macro index > > > >mutt errors on this macro. > > That's because it's incomplete. You have to insert whatever key you > normally have bound to the function in the middle. > For example, by default, is bound to , so by > default, the following macro would work: > > macro index No errors but it doesn't seem to sync. Marc
Re: why is there no auto $ (save changes to mailbox)?
On Tue, Aug 11, 2009 at 09:10:49AM +, ed wrote: > On Mon, Aug 10, 2009 at 09:23:59AM -0400, Marc Vaillant wrote: > > Hi all, > > > > I've been a happy mutt user for over a decade. Of course there are a > > few minor features here and there that I wish mutt had. The one that's > > really getting to me lately is that as far as I know, there is no > > automatic way to execute "$". i.e. save changes to mailbox. This is > > particularly a problem for IMAP because losing your internet connection > > (e.g. sleeping your laptop) usually means losing mailbox changes. If > > there is a mechanism for accomplishing this now please let me know. > > Otherwise, it seems natural for it to be an action during mail check? > > Shouldn't there be at least an auto save/recover mechanism? > > Hi, > > Personally, I'd use screen :) I do use screen, but it doesn't help for this problem when you are running mutt locally and not on a remote machine via ssh access. Marc
Re: why is there no auto $ (save changes to mailbox)?
On Tue, Aug 11, 2009 at 07:26:57AM +0200, Rejo Zenger wrote: > ++ 10/08/09 16:44 +0200 - Michael Tatge: > >> there is no automatic way to execute "$". i.e. save changes to > >> mailbox. This is particularly a problem for IMAP because losing your > >> internet connection (e.g. sleeping your laptop) usually means losing > >> mailbox changes. > > > >No, there isn't. And that's a good thing (TM). I don't want messages to > >be auto deleted. > > No messages will be "auto deleted". > > The only thing that happens is that messages you earlier have marked as > "to be deleted" will be actually deleted. Or better, any changes you > have made to the status of the message is comitted. The behaviour > wouldn't be any different from exiting a mailbox or pressing "$". > > And, in the spirit of mutt, such a setting would be configurable. One > can turn it on or off and set the interval. > > I can't think of a reason why this would be bad (especialy if it's > configurable and the default is "off"). Thanks Rejo, I'm glad that I'm not the only one that would see this as a valuable feature. For now--per Michael's suggestion, I have covered most of the cases with the following macros: macro index macro compose y macro pager q This doesn't cover N -> O flag changes but at least I'm not losing reply and read flags. Marc
Re: why is there no auto $ (save changes to mailbox)?
On Tue, Aug 11, 2009 at 06:41:51PM +0200, Rocco Rutte wrote: > On Tue, Aug 11, 2009 at 07:26:57AM +0200, Rejo Zenger wrote: > > > No messages will be "auto deleted". > > > > The only thing that happens is that messages you earlier have marked as > > "to be deleted" will be actually deleted. Or better, any changes you > > have made to the status of the message is comitted. The behaviour > > wouldn't be any different from exiting a mailbox or pressing "$". > > > > And, in the spirit of mutt, such a setting would be configurable. One > > can turn it on or off and set the interval. > > > > I can't think of a reason why this would be bad (especialy if it's > > configurable and the default is "off"). > > There're some good reasons not to do it and "help" people by making > it harder for them to shoot in their feet. > > For eexample, you tag tag delete messages and cover messages you > didn't want, or have hooks like me that mark duplicates for duplication > which would delete valid mail automatically if I weren't paying > attention to them immediately. But when I have to care of the manually, > I just do the whole syncing business myself. Can't this easily be controlled? set delete=ask-yes. If that's not enough, it suggests that deleting messages should be abstracted from sync-mailbox so that you can sync flags and delete messages independently. Loosing reply flags on e.g. support email--where you often can't remember if you've replied b/c you don't know the person and you're answering the same question over and over--is really a pain. Marc
mutt can't fix itself from hcache corruption
My hcache gets corrupted periodically (that's not my main beef, though it's frequent enough to be annoying also) and mutt can't fix itself permanently without me manually deleting the hcache file. If I don't delete the hcache file, mutt perpetually detects the corruption and refetches all the headers upon every load, instead of refetching only once and fixing the cache. Is this expected behavior? If so, is there a setting that would tell mutt to overwrite the hcache when encountering a corruption? I'm running 1.5.21_1 with tokyocabinet in snow leopard, and I have debug level 3 outputs if needed. During the failing hcache parse, I see the following message in the debug output "bad cache entry at 1085, giving up". Thanks, Marc
[ANNOUNCE] mutt_ldap_query-2.3
Dear all,
I have just released a new version of my mutt_ldap_query perl script
(version 2.3). Now it incorporates a builtin table of common servers
and associated search bases allowing simpler commands by implementing a
nickname key based lookup (changes inspired from a patch sent by Adrian
Likins <[EMAIL PROTECTED]>).
# Version History (major changes only)
# 2.3 (12/28/1999):
# added better parsing of the options, a shortcut for avoiding
# -s and -b options by using the script builtin table of common
# servers and associated search bases performing a nickname key based
# lookup (changes inspired from a patch sent by Adrian Likins
# <[EMAIL PROTECTED]>), performed some Y2K cleanups ;-)
# 2.2 (11/02/1999):
# merged perl style fixes proposed by Warren Jones <[EMAIL PROTECTED]>
# 2.1 (4/14/1998):
# first public release
Enjoy!
--
Marc de Courville -=- Centre de Recherche Motorola -=- [EMAIL PROTECTED]
-=- {Free,Net}BSD, Linux: You can also get less bang for more bucks.-=-
Opinions hereabove are my own and not those of my organization
mutt_ldap_query.pl version 2.3
==
The latest version of the code can be retrieved at
ftp://ftp.mutt.org/pub/mutt/contrib
This code is distributed under the GNU General Public License (GPL). See
http://www.opensource.org/gpl-license.html and http://www.opensource.org/.
mutt_ldap_query parses ldapsearch command outputs in order to provide
mutt with the required formatted input for using Brandon Blong's
"External Address Query" feature now part of mutt distribution.
This perl script can be interfaced with mutt by defining in your .muttrc:
set query_command = "mutt_ldap_query.pl '%s'"
Multiple requests are supported: the "Q" command of mutt accepts as argument
a list of queries (e.g. "Gosse de\ Courville").
usage: mutt_ldap_query -s -b -n
[[] ...]
-s query ldap server
-b use as the starting point for the search instead of the default
-n shortcut for avoiding -s and -b options by using the script builtin
table of common servers and associated search bases performing a
lookup
examples of queries:
classical query:
mutt_ldap_query.pl -s ldap.crm.mot.com -b 'o=Motorola,c=US' Gosse
and its shortcut version using a nickname
mutt_ldap_query.pl -n crm Gosse de\ Courville
References:
- ldapsearch is a ldap server query tool present in ldap-3.3 distribution
http://www.umich.edu/~rsug/ldap)
- mutt is the ultimate email client
http://www.mutt.org
- historical Brandon Blong's "External Address Query" feature patch for mutt
http://www.fiction.net/blong/programs/mutt/#query
Marc de Courville <[EMAIL PROTECTED]>
December 29, 1999
mutt_ldap_query-2.3.pl
[ANNOUNCE] mutt_ldap_query-3.0
Dear all,
this is the second release of the day which contains some enhancements and
some bug-fixes of my mutt_ldap_query perl script.
mutt_ldap_query performs ldap queries using either ldapsearch command
or the perl-ldap module and it outputs the required formatted data for
feeding mutt when using its "External Address Query" feature.
This version 3.0 implements another query method using perl-ldap module
which can be enabled by the -p boolean flag. This way the whole ldap
query can be performed in perl! The default behavior still uses
ldapsearch...
Enjoy!
--
Marc de Courville -=- Centre de Recherche Motorola -=- [EMAIL PROTECTED]
-=- {Free,Net}BSD, Linux: You can also get less bang for more bucks.-=-
Opinions hereabove are my own and not those of my organization
mutt_ldap_query-3.0.pl
mutt_ldap_query.pl version 3.0
==
The latest version of the code can be retrieved at
ftp://ftp.mutt.org/pub/mutt/contrib
This code is distributed under the GNU General Public License (GPL). See
http://www.opensource.org/gpl-license.html and http://www.opensource.org/.
mutt_ldap_query performs ldap queries using either ldapsearch command
or the perl-ldap module and it outputs the required formatted data for
feeding mutt when using its "External Address Query" feature.
This perl script can be interfaced with mutt by defining in your .muttrc:
set query_command = "mutt_ldap_query.pl '%s'"
Multiple requests are supported: the "Q" command of mutt accepts as argument
a list of queries (e.g. "Gosse de\ Courville").
usage: mutt_ldap_query [-p] -s -b -n
[[] ...]
-p use perl-ldap module instead of ldapsearch (which is the default)
-s query ldap server
-b use as the starting point for the search instead of the default
-n shortcut for avoiding -s and -b options by using the script builtin
table of common servers and associated search bases performing a
lookup
examples of queries:
classical query:
mutt_ldap_query.pl -s ldap.crm.mot.com -b 'o=Motorola,c=US' Gosse
and its shortcut version using a nickname
mutt_ldap_query.pl -n crm Gosse de\ Courville
References:
- perl-ldap module
http://www.perl.com/CPAN-local/authors/id/GBARR
- ldapsearch is a ldap server query tool present in ldap-3.3 distribution
http://www.umich.edu/~rsug/ldap)
- mutt is the ultimate email client
http://www.mutt.org
- historical Brandon Blong's "External Address Query" feature patch for mutt
http://www.fiction.net/blong/programs/mutt/#query
Marc de Courville <[EMAIL PROTECTED]>
December 29, 1999
Problem wit aliases
Dear Group, I have just started mutt and am having some problems with aliases. From having looked at some scripts and some existing ones I gathered that the format of an alias definition was as follows: alias alias_namedescriptions\ ^ one space here where is the tab-character and \< and \> denote the '<' and '>' characters. Unfortunately this doesn't seem to work and some aliases are not recognized. Is there anything else I need to know (documentation to read, etc.) Thanks in avance, Marc van Dongen -- Marc van Dongen, CS Dept | phone: +353 21 903578 University College Cork, NUIC | Fax: +353 21 903113 College Road, Cork, Ireland | Email: [EMAIL PROTECTED]
Re: Problem wit aliases
Jon Walthour ([EMAIL PROTECTED]) wrote: : To make sure you get the format right, open a message (like this one) : and press 'a' and follow the steps. It will write out the .mutt-aliases : file for you. From there, you should be able to get the proper format. Thanks Jon, I was aware of the existence of a functionality like that, but then if I want to use an alias to send emails to the people in a class I am teaching, I have to type in all their password (or use paste and copy) which seems a bit awkward. If I know the format, it's a bit easier (especially if the list is very long and if I have it stored in a file somewhere). Regards, Marc van Dongen -- Marc van Dongen, CS Dept | phone: +353 21 903578 University College Cork, NUIC | Fax: +353 21 903113 College Road, Cork, Ireland | Email: [EMAIL PROTECTED]
Re: problem wit aliases
Jeremy Blossom wrote: [...] : > Unfortunately this doesn't seem to work and some aliases are : > not recognized. Is there anything else I need to know : > (documentation to read, etc.) : Section 3.2 of the manual. Thanks! Regards, Marc van Dongen -- Marc van Dongen, CS Dept | phone: +353 21 903578 University College Cork, NUIC | Fax: +353 21 903113 College Road, Cork, Ireland | Email: [EMAIL PROTECTED]
Re: Q: new mail
Mikko Hänninen ([EMAIL PROTECTED]) wrote: : Marc van Dongen <[EMAIL PROTECTED]> wrote on Tue, 14 Mar 2000: : > Is there any way to tell mutt to inform me if new : > mail has arrived? At the moment I am using xbiff : > for that purpose but I would like to get rid of it. : : Sure. List your incoming mailboxes with the "mailboxes" command in : your .muttrc. : : For more info, look up the command's entry in the manual. I'll have a look at it. Thanks! Regards, Marc
Q: new mail
Dear group, Is there any way to tell mutt to inform me if new mail has arrived? At the moment I am using xbiff for that purpose but I would like to get rid of it. Tehanks in advance. Regards, Marc van Dongen -- Marc van Dongen, CS Dept | phone: +353 21 4903578 University College Cork, NUIC | Fax:+353 21 4903113 College Road, Cork, Ireland | Email: [EMAIL PROTECTED]
Aborted unmodified message.
Hi there, I just re-installed vim on my system. When I now try to compose a message after I enter the name of the recipient mutt does not allow me to write a message. Istead it displays a Aborted unmodified message. message. Any suggestions how to overcome this problem? Thanks in advance. Marc van Dongen -- Marc van Dongen, CS Dept | phone: +353 21 4903578 University College Cork, NUIC | Fax:+353 21 4903113 College Road, Cork, Ireland | Email: [EMAIL PROTECTED] PS: This message was sent by a different mutt from a different machine.
Re: Aborted unmodified message.
Suresh Ramasubramanian ([EMAIL PROTECTED]) wrote: : I rather suspect that the path to vim is wrong in his .muttrc : Especially if he had an rpm install which would dump vim in /bin or /usr/bin - : and then compiled a new vim from a tarball, that'd put it into /usr/local/bin : : Use `which vim` to locate where the vim is on your box - and edit the editor : variable in your .muttrc to reflect the new location. That wasn't it. The ``path'' to vim was correct---It was using an alias. I explicitly set the path to where vim resides but that didn't work. Thanks. Regards, Marc van Dongen
Re: Aborted unmodified message.
David Champion ([EMAIL PROTECTED]) wrote: : > I just re-installed vim on my system. : > When I now try to compose a message : > after I enter the name of the recipient : > mutt does not allow me to write a message. : > Istead it displays a : > Aborted unmodified message. : > message. : : set abort_unmodified=ask-no That's not the problem. Mutt doesn't seem to let me edit at all. With this setting, I can postpone a message for later, then recall it and use `e` to edit but mutt won't let me Regards, Marc van Dongen
Re: Aborted unmodified message.
David T-G ([EMAIL PROTECTED]) wrote: : % mutt does not allow me to write a message. : % Istead it displays a : % Aborted unmodified message. : % message. : % : % Any suggestions how to overcome this problem? : : You might start by checking your $editor setting in your muttrc and your My editor setting points to an existing vim which works. : $EDITOR and $VISUAL settings in your shell; if they're still pointing to EDITOR=VISUAL= : a now-nonexistent mutt, you won't have an editor so you'll never edit the : message and so it won't be modified and (because you have the abort : setting to "yes" instead of one of the other possibilities) so mutt will : throw it away. I can see that. : If you can't figure out what's up, try setting mutt's $editor to a : quickie script which calls vim and then waits for a keypress before : exiting so that you can see any error messages that go by. I changed the editor setting to a script that prints something, reads a line and then starts to edit. It doesn't seem to be called when I press `e.' I still get the `unmodified' message. So should I set EDITOR and VISUAL to something? I just upgraded to a higher solaris 8. Maybe that has to do something with the problem as well. Regards, Marc van Dongen
Re: Aborted unmodified message.
David T-G ([EMAIL PROTECTED]) wrote: [snip] : % : If you can't figure out what's up, try setting mutt's $editor to a : % : quickie script which calls vim and then waits for a keypress before : % : exiting so that you can see any error messages that go by. : % : % I changed the editor setting to a script that prints something, : % reads a line and then starts to edit. It doesn't seem to be : % called when I press `e.' I still get the `unmodified' message. : : No, make sure that you *first* call vim and you *then* wait. You need to : see that vim is really called and see what messages, if any, it returns. I overlooked the purpose of you suggestion. It doesn't make any difference. The script doesn't get called. [snip] : Possbile, but not probable. I'm still betting on a vim config, though a : full /tmp as already mentioned might be a good place to start (my vim : tmpdir is $HOME/tmp; I forget about the defaults sometimes :-) I'll have a look at that. Thanks. Regards, Marc van Dongen
Re: Aborted unmodified message.
Mikko Hänninen ([EMAIL PROTECTED]) wrote: : Marc van Dongen <[EMAIL PROTECTED]> wrote on Wed, 27 Sep 2000: : > I changed the editor setting to a script that prints something, : > reads a line and then starts to edit. It doesn't seem to be : > called when I press `e.' I still get the `unmodified' message. : : What doesn't get called when you press e, the script? (Just making : sure I got that right..) The script to which the editor setting in my .muttrc points doesn't get called. : correct. If it's correct, you can check that Mutt can execute it, with : the ! command: : : !/path/to/your/editor/here Good one. I hadn't thought of trying that. It fails Other shell commands fail as well : You don't say what the values are, so something to try (if you haven't : yet) is to put full paths into the settings. Maybe our PATH setting The path is set up properly. As a matter of fact, the editor setting in the .muttrc is an absolute pathname. : isn't set up the way you think it is, if you're launching Mutt via some : graphical shell for instance. This shouldn't be a problem if it's I'm launching mutt from the command-line prompt in a ``regular'' window. Thanks. Regards, Marc van Dongen
Re: Aborted unmodified message.
Mikko Hänninen ([EMAIL PROTECTED]) wrote: [snip] : > Good one. I hadn't thought of trying that. It fails : > Other shell commands fail as well [snip] : I have no idea why you couldn't run any commands from within Mutt : though, I've never heard of this kind of problem. Can you even : start /bin/sh (or your own shell)? Nope. All commands fail. As I mentioned earlier on, I upgraded from sparc-sun-solaris-2.7 to sparc-sun-solaris-2.8 and rebuilt mutt from scratch. I did this before as well without serious problems. I haven't gor a clue what is going on here. Maybe this is an operating system related problem. I am using the CDE desktop at the moment but the problem also manifests itself if I use the openwindows desktop. Regards, Marc van Dongen
Re: Aborted unmodified message.
Suresh Ramasubramanian ([EMAIL PROTECTED]) wrote: : Get out of both desktops into the sun shell... try mutt there. No success either:-( Regards, Marc van Dongen
Re: Aborted unmodified message.
Bruce DeVisser ([EMAIL PROTECTED]) wrote: : And what does :set ?shell return? shell="/usr/bin/bash" which is correct. Regards, Marc van Dongen
Re: Aborted unmodified message.
Morten Liebach ([EMAIL PROTECTED]) wrote: [snip] : This _is_ a long shot, but: what happens when you try to invoke vim from : your shell? It works great! [snip] Regards, Marc van Dongen
Re: Aborted unmodified message.
David T-G ([EMAIL PROTECTED]) wrote: : It may be correct, but it isn't stock :-) Try settin $shell to /sbin/sh, : which is guaranteed to be completely self-contained. If *that* works, I am assuming you are asking me to write a wrapper script around mutt to set the shell. That didn't work. Now I am assuming you are asking me put a shell= line in my .muttrc. That didn't work either. : then try using /bin/sh to see if your shared libs are all healthy. : If *that* works, then it's all bash's fault. That didn't work for the wrapper nor for the shell= variant. : Note that I don't want to start a shell war; in fact, as much as I : hate to admit it, I think I'm becoming a bash convert because of ksh : limitations :-) Good lad! Thanks again. Regards, Marc van Dongen
Re: Aborted unmodified message.
Mikko Hänninen ([EMAIL PROTECTED]) wrote: : OK.. And you can get a shell (via a terminal window), so you know the : binary is executable etc.? I am not exactly sure what you mean. External programs, like knews can start vim as an external program to compose an email message. [snip] : Like someone else suggested, try getting a shell without a windowing : environment, and then try with that. That way you can check the values : of PATH etc., and know for sure it's not the windowing environment : getting in the way. I don't actually think it is, however since weird : things are happening I'd try to eliminate every potential source of : confusion. That doesn't work there either. Thanks. Regards, Marc van Dongen
[ANNOUNCE] new version of mutt_ldap_query script
Dear all,
please find attached to this email the new version of mutt_ldap_query
perl script that performs ldap queries for mutt.
The distribution now includes a module for interfacing with little
brother database (m_ldap).
Enjoy!
--8<--8<--8<--8<---cut here--->8-->8-->8-->8--
mutt_ldap_query.pl version 3.1
==
The latest version of the code can be retrieved at
ftp://ftp.mutt.org/pub/mutt/contrib
This code is distributed under the GNU General Public License (GPL). See
http://www.opensource.org/gpl-license.html and http://www.opensource.org/.
mutt_ldap_query performs ldap queries using either ldapsearch command
or the perl-ldap module and it outputs the required formatted data for
feeding mutt when using its "External Address Query" feature.
This perl script can be interfaced with mutt by defining in your .muttrc:
set query_command = "mutt_ldap_query.pl '%s'"
Multiple requests are supported: the "Q" command of mutt accepts as argument
a list of queries (e.g. "Gosse de\ Courville").
Alternatively mutt_ldap_query can be interfaced with the more generic
little brother database query program (http://www.spinnaker.de/lbdb/)
using:
set query_command = "lbdbq '%s'"
and by specifying in your ~/.lbdb/lbdbrc file another method of query
just adding to the METHODS variable the m_ldap module e.g.:
METHODS='m_inmail m_passwd m_ldap m_muttalias m_finger'
and the right path to access m_ldap in MODULES_PATH e.g.
MODULES_PATH="/usr/local/lib $HOME/.lbdb/modules"
(if you moved m_ldap in ~/.lbdb/modules).
Just make sure to use the correct path for calling mutt_ldap_query
in the m_ldap script.
The following variables of the mutt_ldap_query will have to be customized
for matching your site configuration:
# hostname of your ldap server
my $ldap_server = "ldap.crm.mot.com";
# ldap base search
my $search_base = "o=Motorola, c=US";
# path of the ldapsearch command if you are not using the perl_ldap modules
my $LDAPSEARCH="/usr/bin/ldapsearch";
usage: mutt_ldap_query [-p] -s -b -n
[[] ...]
-p use perl-ldap module instead of ldapsearch (which is the default)
-s query ldap server
-b use as the starting point for the search instead of the default
-n shortcut for avoiding -s and -b options by using the script builtin
table of common servers and associated search bases performing a
lookup
-l supress number of matches output (suited for interfacing with little
brother database http://www.spinnaker.de/lbdb/)
examples of queries:
classical query:
mutt_ldap_query.pl -s ldap.crm.mot.com -b 'o=Motorola,c=US' Gosse
and its shortcut version using a nickname
mutt_ldap_query.pl -n crm Gosse de\ Courville
References:
- perl-ldap module
http://www.perl.com/CPAN-local/authors/id/GBARR
- ldapsearch is a ldap server query tool present in ldap-3.3 distribution
http://www.umich.edu/~rsug/ldap)
- mutt is the ultimate email client
http://www.mutt.org
- historical Brandon Blong's "External Address Query" feature patch for mutt
http://www.fiction.net/blong/programs/mutt/#query
- little brother database is an interface query program for mutt that allow
multiple searches for email addresses based on external query scripts
just like this one 8-)
http://www.spinnaker.de/lbdb/
Marc de Courville <[EMAIL PROTECTED]>
October 9th, 2000
--8<--8<--8<--8<---cut here--->8-->8-->8-->8--
--
Marc de Courville -=- Centre de Recherche Motorola -=- [EMAIL PROTECTED]
-=- {Free,Net}BSD, Linux: You can also get less bang for more bucks.-=-
Opinions hereabove are my own and not those of my organization
mutt_ldap_query-3.1.tar.gz
Re: [ANNOUNCE] new version of mutt_ldap_query script
According to Brian Salter-Duke <[EMAIL PROTECTED]> (on 10/10/00):
> On Mon, Oct 09, 2000 at 01:39:51PM +0200, Marc de Courville wrote:
> > Dear all,
> >
> > please find attached to this email the new version of mutt_ldap_query
> > perl script that performs ldap queries for mutt.
> > The distribution now includes a module for interfacing with little
> > brother database (m_ldap).
> >
> > Enjoy!
> >
> Why not submit the m_ldap module to Roland for inclusion in the lbdb
> tarball? I suggest altering:-
as mentioned Roland, I already did propose this module.
But as underlined, it deserve more thinking and work to have a clean
and easy user configuration.
I will work on it as soon as I have some time.
Thanks for the remark BTW.
Kind regards,
--
Marc de Courville -=- Centre de Recherche Motorola -=- [EMAIL PROTECTED]
-=- {Free,Net}BSD, Linux: You can also get less bang for more bucks.-=-
Opinions hereabove are my own and not those of my organization
[ANNOUNCE] mutt_ldap_query script version 3.3
Dear all,
please find attached to this email the new version of mutt_ldap_query
perl script that performs ldap queries for mutt.
This is more a less a bugfix release.
Since version 3.1 the distribution now includes a module for interfacing
with little brother database (m_ldap).
The next step is the full integration into lbdb in collaboration with
Roland Rosenfeld.
Thanks to all the users who reported bugs so far.
Enjoy!
Version History (major changes only)
* 3.3 (02/15/2001):
- fixed typo in server_db (pointed out by [EMAIL PROTECTED])
- added "ignorant" option: -i to search with wildcards
* 3.2 (01/12/2000):
- now use get_value intead of ->[0]
* 3.1 (03/10/2000):
- added the -l option that suppresses the number of matches output
- for better interfacing with little brother database
- http://www.spinnaker.de/lbdb/
--8<--8<--8<--8<---cut here--->8-->8-->8-->8--
mutt_ldap_query.pl version 3.3
==
The latest version of the code can be retrieved at
ftp://ftp.mutt.org/pub/mutt/contrib
This code is distributed under the GNU General Public License (GPL). See
http://www.opensource.org/gpl-license.html and http://www.opensource.org/.
mutt_ldap_query performs ldap queries using either ldapsearch command
or the perl-ldap module and it outputs the required formatted data for
feeding mutt when using its "External Address Query" feature.
This perl script can be interfaced with mutt by defining in your .muttrc:
set query_command = "mutt_ldap_query.pl '%s'"
Multiple requests are supported: the "Q" command of mutt accepts as argument
a list of queries (e.g. "Gosse de\ Courville").
Alternatively mutt_ldap_query can be interfaced with the more generic
little brother database query program (http://www.spinnaker.de/lbdb/)
using:
set query_command = "lbdbq '%s'"
and by specifying in your ~/.lbdb/lbdbrc file another method of query
just adding to the METHODS variable the m_ldap module e.g.:
METHODS='m_inmail m_passwd m_ldap m_muttalias m_finger'
and the right path to access m_ldap in MODULES_PATH e.g.
MODULES_PATH="/usr/local/lib $HOME/.lbdb/modules"
(if you moved m_ldap in ~/.lbdb/modules).
Just make sure to use the correct path for calling mutt_ldap_query
in the m_ldap script.
The following variables of the mutt_ldap_query will have to be customized
for matching your site configuration:
# hostname of your ldap server
my $ldap_server = "ldap.mot.com";
# ldap base search
my $search_base = "ou=employees, o=Motorola, c=US";
# path of the ldapsearch command if you are not using the perl_ldap modules
my $LDAPSEARCH="/usr/bin/ldapsearch";
# list of the fields that will be used for the query
my @fields = qw(commonName gn sn cn uid);
# list of the fields that will be used for composing the answer
my $expected_answers = "gn sn preferredRfc822Recipient ou c telephonenumber";
usage: mutt_ldap_query [-i] [-p] [-s ] [-b ] [-n
] [[] ...]
-p use perl-ldap module instead of ldapsearch (which is the default)
-s query ldap server
-b use as the starting point for the search instead of the default
-n shortcut for avoiding -s and -b options by using the script builtin
table of common servers and associated search bases performing a
lookup
-l supress number of matches output (suited for interfacing with little
brother database http://www.spinnaker.de/lbdb/)
-i ignorant mode: search using wildcard for *name_to_query* (requires a
longer processing from LDAP server but is quite convenient :)
-h generates this help message
examples of queries:
classical query:
mutt_ldap_query.pl -s ldap.crm.mot.com -b 'o=Motorola,c=US' Gosse
and its shortcut version using a nickname
mutt_ldap_query.pl -n crm Gosse de\ Courville
References:
- perl-ldap module
http://perl-ldap.sourceforge.net/
- ldapsearch is a ldap server query tool present in ldap-3.3 distribution
http://www.umich.edu/~rsug/ldap)
- mutt is the ultimate email client
http://www.mutt.org
- historical Brandon Blong's "External Address Query" feature patch for mutt
http://www.fiction.net/blong/programs/mutt/#query
- little brother database is an interface query program for mutt that allow
multiple searches for email addresses based on external query scripts
just like this one 8-)
http://www.spinnaker.de/lbdb/
Marc de Courville <[EMAIL PROTECTED]>
February 15th, 2001
--8<--8<--8<--8<---cut here--->8-->8-->8-->8--
--
Marc de Courville -=- Centre de Recherche Motorola -=- [EMAIL PROTECTED]
-=- {Free,Net}BSD, Linux: You can also get less bang for more bucks.-=-
Opinions hereabove are my own and not those of my organization
mutt_ldap_query-3.3.tar.gz
[Announce] mutt_ldap_query 2.2
Dear all,
please find attached to this email the new improved version (thanks
Warren!) of my LDAP query perl script that can be interfaced with mutt
by defining in your .muttrc:
set query_command = "mutt_ldap_query.pl '%s'"
This script parses the outputs of ldapsearch (ldap server
query tool present in the ldap-3.3 distribution available at
http://www.umich.edu/~rsug/ldap) in order to pass the required formatted
data to mutt. It relies on Brandon Blong's "External Address Query"
feature patch (http://www.fiction.net/blong/programs/mutt/#query)
that is now part of the mutt distribution.
Multiple requests are supported: the "Q" command of mutt accepts as argument
a list of queries (e.g. "Foo Bar de\ Courville").
The script will likely to require some hand customization in order to match
your site configuration. Namely the two following lines will have to be
changed:
my $ldap_server = "ldap";
my $BASEDN = "o=Motorola, c=US";
as well as the parsing itself according the name of the fields defined
in the LDAP server you wish to query.
Enjoy!
--
Marc de Courville -=- Centre de Recherche Motorola -=- [EMAIL PROTECTED]
-=- {Free,Net}BSD, Linux: You can also get less bang for more bucks.-=-
Opinions hereabove are my own and not those of my organization
mutt_ldap_query.pl
