Re: Mutt not following RFC821 strictly?
On Mon, Jul 10, 2000 at 11:30:14AM +0530, Suresh Ramasubramanian wrote: Magnus Bodin proclaimed on mutt-users that: As of RFC 821 http://rfc821.x42.com/ the local part of an e-mail address can consist of other characters than a-z0-9 and should then be quoted (see local-part and quoted-string). It seems though, that the mutt client does not support the use of an address like "address with spaces"@x42.com which indeed is a valid and working I don't know ... yeah ... RFC 821 (page 29) does say this ... but let's see what goes on. I sent out a mail to my catchall domain kcircle.com - 'suresh test'@kcircle.com ' should be " according to the RFC. See the headers ... Received: from cs2.hyd.office.juno.com (cs2.hyd.office.juno.com [208.238.62.3]) by no9.superb.net (8.9.3/8.9.3) with ESMTP id BAA12436 for 'suresh.test'@kcircle.com; Mon, 10 Jul 2000 01:49:48 -0400 (EDT) Hmmm... my sendmail 8.8.x mailserver converts spaces to dots. I don't think so. Try talking raw SMTP to it and it won't convert things. Received: from lotus ([EMAIL PROTECTED] [208.238.62.74]) by cs2.hyd.office.juno.com (8.8.6.Beta0/8.8.7/juno-1.1) with ESMTP id L21035 for 'suresh test'@kcircle.com; Mon, 10 Jul 2000 11:19:46 +0530 (IST) My mua (I used pegasus mail for 'doze for this test) sends the space quite ok. It is a sendmail issue and not a mutt issue I suppose. IT IS NOT a sendmail issue. It is definitively a mutt issue. Pine works, but mutt breaks the addresses at the spaces. I btw, don't use sendmail, I use qmail, and I've checked qmail with raw SMTP too, and it works like a charm. So the MTA is not to blame in this case. You _can_ write something that's 100% rfc compliant and won't work anywhere ;) That's not true. /magnus -- http://x42.com/
Re: Mutt not following RFC821 strictly?
* Suresh Ramasubramanian [EMAIL PROTECTED]: Magnus Bodin proclaimed on mutt-users that: As of RFC 821 http://rfc821.x42.com/ the local part of an e-mail address can consist of other characters than a-z0-9 and should then be quoted (see local-part and quoted-string). It seems though, that the mutt client does not support the use of an address like "address with spaces"@x42.com which indeed is a valid and working I don't know ... yeah ... RFC 821 (page 29) does say this ... but let's see what goes on. I sent out a mail to my catchall domain kcircle.com - 'suresh test'@kcircle.com You need to use double quotes, or else mutt breaks it up into several addresses. "suresh test"@kcircle.com appears to work fine with mutt. See the headers ... Received: from cs2.hyd.office.juno.com (cs2.hyd.office.juno.com [208.238.62.3]) by no9.superb.net (8.9.3/8.9.3) with ESMTP id BAA12436 for 'suresh.test'@kcircle.com; Mon, 10 Jul 2000 01:49:48 -0400 (EDT) Hmmm... my sendmail 8.8.x mailserver converts spaces to dots. My sendmail-8.9.3-15 appears to handle it: ... Jul 10 00:16:41 novara sendmail[32751]: AAA32751: to="this works"@novara.avenue, delay=00:00:01, mailer=local, stat=User unknown ... ...unless it adds the dots later. David
Re: Mutt not following RFC821 strictly?
Magnus Bodin proclaimed on mutt-users that: ' should be " according to the RFC. ah thanks ... so, I did three things ... 1. Talked raw smtp : rcpt to:"suresh test"@kcircle.com Result - Works. 2. Sent using mutt to "suresh test"@kcircle.com and then sent to "suresh test"@kcircle.com just in case it breaks to [EMAIL PROTECTED] and [EMAIL PROTECTED] I can't replicate it ... Headers ... Received: from cs3.hyd.office.juno.com (cs3.hyd.office.juno.com [208.238.62.6]) by no9.superb.net (8.9.3/8.9.3) with ESMTP id CAA14996 for "suresh test"@kcircle.com; Mon, 10 Jul 2000 02:27:39 -0400 (EDT) Received: (from sureshr@localhost) by cs3.hyd.office.juno.com (8.8.6.Beta0/8.8.7/juno-1.1) id L27594 for "suresh test"@kcircle.com; Mon, 10 Jul 2000 11:57:37 +0530 (IST) in both cases. -- Suresh Ramasubramanian + [EMAIL PROTECTED] Universe, n.: The problem.
Re: tagging unread
On Jul 9, David Champion wrote: On 2000.07.09, in [EMAIL PROTECTED], "Jason Helfman" [EMAIL PROTECTED] wrote: I searched threw the manual and it looks us though you may not be able to tag something as unread. If this is the case, why? If I am wrong, can you please point me to the right place in the manual... Keystrokes: w set-flag n (for new) Actually, 'N' is a special toggle function which does not presuppose the initial 'w'. But be sure you press capital N (shift-N). Holger
Re: Mutt not following RFC821 strictly?
On Mon, Jul 10, 2000 at 01:23:10AM -0400, Rich Lafferty wrote: On Mon, Jul 10, 2000 at 07:05:05AM +0200, Magnus Bodin ([EMAIL PROTECTED]) wrote: As of RFC 821 http://rfc821.x42.com/ the local part of an e-mail address can consist of other characters than a-z0-9 and should then be quoted (see local-part and quoted-string). It seems though, that the mutt client does not support the use of an address like "address with spaces"@x42.com which indeed is a valid and working e-mail address. Or is there some way to enter addresses explicitly thus not having it "parse-mangled".. How are you adding it now? What failed that makes you say it's not supported? -Rich Look further down in the thread. /magnus -- http://x42.com/
Re: Mutt not following RFC821 strictly?
Magnus Bodin muttered: As of RFC 821 http://rfc821.x42.com/ the local part of an e-mail address can consist of other characters than a-z0-9 and should then be quoted (see local-part and quoted-string). It seems though, that the mutt client does not support the use of an address like "address with spaces"@x42.com which indeed is a valid and working e-mail address. Or is there some way to enter addresses explicitly thus not having it "parse-mangled".. I can send to "test me"@localhost very well. Mutt 1.2.4i sendmail-8.9.3-20 Received: (from t@localhost) by deep-thought.seidenbergstr (8.9.3/8.9.3) id OAA17385 for "test me"@localhost; Mon, 10 Jul 2000 14:56:45 +0200 Which error do you get? HTH, Michael -- Nobody said computers were going to be polite. PGP-fingerprint: DECA E9D2 EBDD 0FE0 0A65 40FA 5967 ACA1 0B57 7C13
Re: Mutt not following RFC821 strictly?
On Mon, Jul 10, 2000 at 03:00:12PM +0200, Michael Tatge wrote: Magnus Bodin muttered: As of RFC 821 http://rfc821.x42.com/ the local part of an e-mail address can consist of other characters than a-z0-9 and should then be quoted (see local-part and quoted-string). It seems though, that the mutt client does not support the use of an address like "address with spaces"@x42.com which indeed is a valid and working e-mail address. Or is there some way to enter addresses explicitly thus not having it "parse-mangled".. I can send to "test me"@localhost very well. Mutt 1.2.4i sendmail-8.9.3-20 Received: (from t@localhost) by deep-thought.seidenbergstr (8.9.3/8.9.3) id OAA17385 for "test me"@localhost; Mon, 10 Jul 2000 14:56:45 +0200 Which error do you get? Look further down the thread. It is an error that may be qmail-inject specific with arguments on the command line. /magnus -- http://x42.com/
Re: Mutt not following RFC821 strictly?
On Mon, Jul 10, 2000 at 11:21:42AM +0200, Magnus Bodin ([EMAIL PROTECTED]) wrote: On Mon, Jul 10, 2000 at 01:23:10AM -0400, Rich Lafferty wrote: On Mon, Jul 10, 2000 at 07:05:05AM +0200, Magnus Bodin ([EMAIL PROTECTED]) wrote: It seems though, that the mutt client does not support the use of an address like "address with spaces"@x42.com which indeed is a valid and working e-mail address. Or is there some way to enter addresses explicitly thus not having it "parse-mangled".. How are you adding it now? What failed that makes you say it's not supported? -Rich Look further down in the thread. Sorry, that was a bit of a trick. If you'll look at my message, you'll see that it was From: Rich Lafferty "rich+mailbox with spaces"@bofh.concordia.ca and was sent by Mutt. Mutt certainly supports the use of an address like that. -Rich -- -- Rich Lafferty --- Sysadmin/Programmer, Instructional and Information Technology Services Concordia University, Montreal, QC (514) 848-7625 - [EMAIL PROTECTED] --
Re: Mutt not following RFC822 strictly?
On Mon, Jul 10, 2000 at 09:43:28AM -0400, Rich Lafferty wrote: On Mon, Jul 10, 2000 at 11:21:42AM +0200, Magnus Bodin ([EMAIL PROTECTED]) wrote: On Mon, Jul 10, 2000 at 01:23:10AM -0400, Rich Lafferty wrote: On Mon, Jul 10, 2000 at 07:05:05AM +0200, Magnus Bodin ([EMAIL PROTECTED]) wrote: It seems though, that the mutt client does not support the use of an address like "address with spaces"@x42.com which indeed is a valid and working e-mail address. Or is there some way to enter addresses explicitly thus not having it "parse-mangled".. How are you adding it now? What failed that makes you say it's not supported? -Rich Look further down in the thread. Sorry, that was a bit of a trick. If you'll look at my message, you'll see that it was From: Rich Lafferty "rich+mailbox with spaces"@bofh.concordia.ca and was sent by Mutt. Mutt certainly supports the use of an address like that. Yes I know. I've commented further down the thread. It's a qmail-inject issue. It does this when sending (on the command line) quoted adresses containing spaces. And by the way. The subject should have read RFC 822 from the beginning, sorry about that. /magnus -- http://x42.com/
Re: browsing imap folders, and other questions
On Sun, Jul 09, 2000 at 01:17:56PM -0700, Mark D. Anderson wrote:
...[snip]...
I apologize; I got off-track. What I meant to say is:
then enter an IMAP server spec: e.g., {imap.demo.int/ssl}
That will put you into browse mode on that IMAP path.
--
-D. [EMAIL PROTECTED] NSIT University of Chicago
I guess you're looking for
mailboxes {imap.server.int} =inbox =foo =bar
then you can browse them using 'c' then TAB and then you should see them.
Hope this helps
Kai
--
x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x
Kai Blin(mailto:[EMAIL PROTECTED]) Webmaster
Inst. of Human Genetics Dept. of Molecular Genetics
Wilhelmstr 27 phone (49)7071-2974890
D 72074 Tuebingen, Germany fax (49)7071-295233
http://www.uni-tuebingen.de/uni/thm/molgen/molgen.html
Do molecular biologists wear designer genes?
x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x
1.2 slower than 1.0 over NFS
We are currently using mutt-1.0i on solaris 2.6. I would like to upgrade to 1.2.4 but it is a _lot_ slower than 1.0 when reading my mailbox over NFS. Compiling with --disable-fcntl helps, but that doesn't seem to be recommended according to the FAQ on www.mutt.org. The same FAQ also claims that the 'current' version's usage of fcntl over NFS has been made faster but that's certainly not my experience. Am I doing something wrong? Should I just use --disable-fcntl and not worry about the FAQ or is there another solution? Thanks in advance for your help, -Ives Aerts __ Ives Aerts (Senior RD engineer) Sony Digital Media Europe [EMAIL PROTECTED] St. Stevens Woluwestr. 55 `Vampires are make-believe, just like elves, B-1130 Brussels, Belgium gremlins and Eskimos.' PHONE: +32 (0)2 724 86 11 (Homer Simpson) FAX : +32 (0)2 724 86 88
Re: gzip patch with maildir
2000-07-09-01:10:51 Ronny Haryanto: [...] And for archives I don't think there's any advantage of using maildir over mbox, which loads faster. [...] In the context of a discussion of the compressed folders patch, I don't disagree with your statement, but taken in isolation I'd have to disagree: Maildirs for archives can be pretty sexy if you index your archives with something like glimpse. But something like the compressed folders patch wouldn't be desired in that case anyway. -Bennett PGP signature
Re: Fcc'ing to sent...
Jason -- ...and then Jason Helfman said... % % set record=+sent/ ... % % I have all the folders working, however, postponed and sent still seem % to be actually files, not in the folder Maildir format that I am seeing % now. Try either removing your sent file and creating a sent maildir or specifying some other maildir as your $record just for this test. You can't have a file and a directory with the same name (IMAP appearances notwithstanding), so mutt can't find sent/new (maybe sent/cur) to drop in the new item because the sent is a file. % % Thanks. HTH HAND % -- % /helfman % % "At any given moment, you may find the ticket to the circus that has always % been in your possession." % Fingerprint: 2F76 2856 776A 3E07 9F3E 452A 17D9 9B28 D75E 0A36 % GnuPG http://www.gnupg.org Get Private! 1024D/D75E0A36 :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Mutt not following RFC821 strictly?
On Mon, Jul 10, 2000 at 03:37:11PM +0200, Magnus Bodin wrote: On Mon, Jul 10, 2000 at 03:00:12PM +0200, Michael Tatge wrote: Magnus Bodin muttered: As of RFC 821 http://rfc821.x42.com/ the local part of an e-mail address can consist of other characters than a-z0-9 and should then be quoted (see local-part and quoted-string). It seems though, that the mutt client does not support the use of an address like "address with spaces"@x42.com which indeed is a valid and working e-mail address. Or is there some way to enter addresses explicitly thus not having it "parse-mangled".. I can send to "test me"@localhost very well. Mutt 1.2.4i sendmail-8.9.3-20 Received: (from t@localhost) by deep-thought.seidenbergstr (8.9.3/8.9.3) id OAA17385 for "test me"@localhost; Mon, 10 Jul 2000 14:56:45 +0200 Which error do you get? Look further down the thread. It is an error that may be qmail-inject specific with arguments on the command line. And the reason is that mutt sends the address RFC821-encoded. (as per SMTP). I enter "adress with spaces"@x42.com when I mean address with [EMAIL PROTECTED] Mutt just passes "address with spaces"@x42.com as the third argument. But qmail-inject expects mail addresses UNQUOTED. /magnus
keymaps header file
Hey guys. I'm rebuilding mutt-1.2i, and I'm having a problem that I don't think I had before. Making all in charmaps No suffix list. For charmap support, please read INSTALL cd . \ CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status creating Makefile linking ./intl/libgettext.h to intl/libintl.h gcc -DSHAREDIR=\"/opt/corp/projects/pegasus/bin/Unsupported/share/mutt\" -DSYSCONFDIR=\"/opt/corp/projects/pegasus/bin/Unsupported/etc\" -DBINDIR=\"/opt/corp/projects/pegasus/bin/Unsupported/bin\" -DHAVE_CONFIG_H=1 -I. -I. -Iintl -I/opt/corp/projects/pegasus/bin/Unsupported/include -I/opt/corp/projects/pegasus/bin/Unsupported/include -I./intl -Wall -pedantic -g -O2 -c addrbook.c In file included from mutt_menu.h:23, from addrbook.c:20: keymap.h:112: keymap_defs.h: No such file or directory *** Error exit code 1 Is this header part of the source tree, or should it be on this HP-UX system? I don't remember getting this compile error before. Mike -- Michael P. Soulier, 1Z22, SKY Tel: 613-765-4699 (ESN: 39-54699) Optical Networks, Nortel Networks, SDE Pegasus "...the word HACK is used as a verb to indicate a massive amount of nerd-like effort." -Harley Hahn, A Student's Guide to UNIX Nortel Linux User's Group Ottawa: (internal) http://nlug.ca.nortel.com:8080
Re: keymaps header file
Michael -- ...and then Michael Soulier said... % Hey guys. I'm rebuilding mutt-1.2i, and I'm having a problem that I don't % think I had before. You probably did, but may not have noticed. % ... % keymap.h:112: keymap_defs.h: No such file or directory % *** Error exit code 1 % % Is this header part of the source tree, or should it be on this HP-UX % system? I don't remember getting this compile error before. It's fixed in 1.2.4; if you're using something less than that, then make keymap_defs.h ; make ought to do it for you. % % Mike % % -- % Michael P. Soulier, 1Z22, SKY Tel: 613-765-4699 (ESN: 39-54699) % Optical Networks, Nortel Networks, SDE Pegasus % "...the word HACK is used as a verb to indicate a massive amount % of nerd-like effort." -Harley Hahn, A Student's Guide to UNIX % Nortel Linux User's Group Ottawa: (internal) http://nlug.ca.nortel.com:8080 :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: keymaps header file
That appears to have done it. Thanks. Mike On Mon, Jul 10, 2000 at 02:24:53PM -0400, David T-G wrote: Michael -- ...and then Michael Soulier said... % Hey guys. I'm rebuilding mutt-1.2i, and I'm having a problem that I don't % think I had before. You probably did, but may not have noticed. % ... % keymap.h:112: keymap_defs.h: No such file or directory % *** Error exit code 1 % % Is this header part of the source tree, or should it be on this HP-UX % system? I don't remember getting this compile error before. It's fixed in 1.2.4; if you're using something less than that, then make keymap_defs.h ; make ought to do it for you. % % Mike % % -- % Michael P. Soulier, 1Z22, SKY Tel: 613-765-4699 (ESN: 39-54699) % Optical Networks, Nortel Networks, SDE Pegasus % "...the word HACK is used as a verb to indicate a massive amount % of nerd-like effort." -Harley Hahn, A Student's Guide to UNIX % Nortel Linux User's Group Ottawa: (internal) http://nlug.ca.nortel.com:8080 :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* -- Michael P. Soulier, 1Z22, SKY Tel: 613-765-4699 (ESN: 39-54699) Optical Networks, Nortel Networks, SDE Pegasus "...the word HACK is used as a verb to indicate a massive amount of nerd-like effort." -Harley Hahn, A Student's Guide to UNIX Nortel Linux User's Group Ottawa: (internal) http://nlug.ca.nortel.com:8080
autoconf version
Hey guys. So 1.2i is building, but I just tried 1.2.4i for the hell of it, and I got this. [bmerh56e-pegctrl-mutt-1.2.4]$ make cd . aclocal -I m4 cd . autoheader /opt/corp/unsupported/bin/autoheader: Symbol `PROTOTYPES' is not covered by /opt/corp/unsupported/share/autoconf/acconfig.h ./acconfig.h *** Error exit code 1 Does that mean that I need to upgrade autoconf now? Mike -- Michael P. Soulier, 1Z22, SKY Tel: 613-765-4699 (ESN: 39-54699) Optical Networks, Nortel Networks, SDE Pegasus "...the word HACK is used as a verb to indicate a massive amount of nerd-like effort." -Harley Hahn, A Student's Guide to UNIX Nortel Linux User's Group Ottawa: (internal) http://nlug.ca.nortel.com:8080
Mutt-1.2.4i Fails to Find PGP5 Keys
I'm trying to upgrade to 1.2.4, but there's a problem with encrypting mail with PGP 5. Let's say I've written a message to "recipient@fqdomain". After I enter "p" in the Compose menu, and then "e" for encrypt, I see the message: "Looking for keys matching "recipient@fqdomain"... for a few moments, then the message: "Enter keyID for recipient@fqdomain:" Now, if I type in either a KeyID like 0x5B421795, or text that IDs "recipient's" full name, and hit Enter, all that happens is that "Enter keyID for recipient@fqdomain:" reappears. I've sourced the file pgp5.rc, and my .muttrc-1.2.4i file gives no error messages on startup. My Mutt-1.0i encrypts just fine, so I know that pgp.cfg and keyrings are OK and accessible. I feel that I'm overlooking something obvious, but what? Howard Arons -- Powered by SuSE Linux 6.3 -- Kernel upgraded to 2.2.16 Communications by Mutt 1.0i
