Re: Mark all messages in folder read
On Sun, Mar 18, 2001 at 07:47:58PM +0100, Stefan Schwandter wrote: Hello all, is there a way to quickly mark all messages in a mail folder (similar to do a catch up in a newsreader) ? T.enter;^R That is: T.enter Tag all messages matching '.' (means all of them) ;^R Mark all tagged messages (threades) as read (that's ctrl-r) Finally you can untag all the messages with ^T.enter -- Tommi Komulainen [EMAIL PROTECTED] GPG 1024D/68388EE66FD6 DD79 EB38 BF6F 3533 09C0 04A8 9871 6838 8EE6 PGP signature
Re: moving mail from inbox problem
On Sat, Jan 27, 2001 at 09:45:23PM +0100, Bostjan Muller wrote: the mail that was in my INBOX, and was read was then moved to my mbox folder, but with version 1.3 that doesn't happen anymore... could you please help me find out how to make it move the read mail? I have read the docs and have found nothing on this subject. I think the settings you're looking for are: set mbox=~/mbox set move=yes Replace ~/mbox with your own mbox of course. HTH -- Tommi Komulainen [EMAIL PROTECTED] GPG 1024D/68388EE66FD6 DD79 EB38 BF6F 3533 09C0 04A8 9871 6838 8EE6 PGP signature
Re: SSL Error, Mutt 1.2.5
On Fri, Jan 19, 2001 at 02:13:57PM -0700, Tres Hofmeister wrote:
The build goes fine, but when I attempt to connect to our
SSL-wrapped IMAP server, I get an error immediately after accepting
the site certificate. For example:
tres$ mutt -f '{imap/ssl}'
[I see:
-- Mutt: SSL Certificate check
(r)eject, accept (o)nce
]
I type "o", then Mutt fails with this error:
SSL connection using (NONE)
This is not an error message, it's an informational message telling you
the SSL parameters used on the connection. Seeing 'NONE' there means that
the connection is *unencrypted*, and we all know that sending passwords
over an unencrypted link is not a good idea. Instead of 'NONE' you should
see something more like 'EDH-RSA-DES-CBC3-SHA' to indicate that the
connection is secure.
IIRC the reason for 'NONE' is that there's a slight mismatch between
client and server SSL protocols and versions. See below.
Any suggestions?
Four words: RTFM =)
In this case the FM would be README.SSL:
--88--
Troubleshooting
---
If after doing the above, you are unable to successfully connect, it
is likely that your IMAP server does not support one of the SSL protocols.
There exist three different protocols, TLSv1, SSLv2, and SSLv3. To check
each of these, you use the following:
openssl s_client -host imap server -port port -verify -debug -no_tls1
openssl s_client -host imap server -port port -verify -debug -no_ssl2
openssl s_client -host imap server -port port -verify -debug -no_ssl3
You can also combine the options until you get a successfull connect. Once
you know which options do not work, you can set the variables for non-working
protocols to know. The variables for the protocols are ssl_use_tlsv1,
ssl_use_sslv2, and ssl_use_sslv3.
--88------
--
Tommi Komulainen [EMAIL PROTECTED]
GPG 1024D/68388EE66FD6 DD79 EB38 BF6F 3533 09C0 04A8 9871 6838 8EE6
PGP signature
Re: SSL Error, Mutt 1.2.5
On Fri, Jan 19, 2001 at 04:13:55PM -0700, Tres Hofmeister wrote: I've already tried all of Mutt's ssl_use_* options in various combinations, with no difference in the behaviour. The "openssl" tests all seem to be about the same, looks like there's a handshaking problem. The results are below. Are you sure you tried all the combinations? I managed to get a reasonable response from the server with the following command: openssl s_client -host imap.rap.ucar.edu -port 993 -verify -debug \ -no_tls1 -no_ssl3 So, 'unset ssl_use_tlsv1 ssl_use_sslv3' should fix this problem. Maybe this is a problem with the stunnel "wrapper" I'm using on the IMAP server, though why it should work with Netscape Messenger is beyond me. Maybe Netscape Messenger doesn't use OpenSSL...? :) -- Tommi Komulainen [EMAIL PROTECTED] GPG 1024D/68388EE66FD6 DD79 EB38 BF6F 3533 09C0 04A8 9871 6838 8EE6 PGP signature
Re: save-hook drama
On Sat, Oct 21, 2000 at 03:00:09PM +1000, Darrin Mison wrote: I can't figure out for the life of me why this doesn't work save-hook ~s\\fm-news =freshmeat_list Subject: [fm-news] newsletter for Friday, October 20th Maybe because there is no '\fm-news' in the subject. Be careful with backslashing. Try: save-hook '~s fm-news' =freshmeat_list -- Tommi Komulainen [EMAIL PROTECTED] PGP signature
Re: Mutt in batch mode
On Wed, Oct 11, 2000 at 04:44:56PM -0400, Jean-Paul Laberge wrote: I'd like to know how to use 'mutt' in batch mode, without a user intervention. I use the following command: mutt -a attached.txt -s "Test from MUTT" jplaberge@.aircanada.ca but I'm always going in the user interface. Is it possible to do it? And, if yes, do you know how to do it? It is possible, just pass the message body (or /dev/null if none) to standard input. This ought to be in the FAQ: mutt -a attached.txt -s "Test from MUTT" jplaberge@.aircanada.ca /dev/null -- Tommi Komulainen [EMAIL PROTECTED] PGP signature
Re: [Off-topic] Q: Mutt-like IRC client?
On Mon, Jun 26, 2000 at 09:56:35AM +0100, Dave Ewart wrote: Apologies for the off-topic post, but I figure Mutt users might be a good group of people to make a recommendation. I use Mutt and SLRN and am looking for a similarly-configurable (colours etc.) IRC client. Any suggestions? You seem to have received a few suggestions, but none of those mentioned anything about irssi (http://irssi.org/) :-( Check it out unless you already found your favorite :) Oh, and once you get your irc-client up and running, don't forget to stop by in #mutt on DALnet. It's been a quiet channel. -- Tommi Komulainen [EMAIL PROTECTED] PGP signature
Re: mutt and POP3-SSL
On Mon, Jul 03, 2000 at 01:17:33PM +0200, Stephan Seitz wrote: mutt-1.2 supports SSL-IMAP. Can I use the POP-support over SSL too? I didn't find any hints in README.SSL about POP3 and SSL. The SSL-libs are the same for IMAP and POP, so it shouldn't be a problem, or am I wrong? There are no hints because there's no support for POP3 over SSL. I have the impression that people are encouraged to use fetchmail instead of the (very) limited POP-capability in mutt, and that's my suggestion too. It wouldn't be a problem, not for the reason you stated though, but I think you'd be better off with fetchmail, anyway. But if there's more demand for POP3 over SSL, I will take a look at it. -- Tommi Komulainen [EMAIL PROTECTED] PGP signature
Re: mutt-1.2: imap/ssl certificates
On Wed, May 10, 2000 at 02:05:30PM +0200, Andre Wobst wrote: Hi, I've troubles with the imap ssl certificates, saved in the file certificate_file, which I set to ~/.mutt.certificate_file in my ~/.muttrc. If I do so, I can accept a certificate not only once but always (otherwise this option isn't available). The certificate is stored in the file ~/.mutt.certificate_file. But next time I start mutt again, it asks me again for the certificate check. If I accept it again, the certificate is again added to the file ~/.mutt.certificate_file and it is exactly the same like before -- now stored twice in the same file. How can I store the certificate that way, that mutt acceptes it automatically next time -- what's wrong in the way I'm doing it? For starters, you're doing nothing wrong, mutt is. The problem is that the X509_verify function, which I use to compare the certificates, doesn't work quite the way I expected. Instead of verifying the server certificate using the server public key (both available after connecting to the server), it needs the issuer's public key to verify the server certificate. If the server certificate is self-signed, the public keys are the same and the verification succeeds, otherwise not. You might be able to use the automatic certificate verification by getting the issuer's (public) certificate, it should be available somewhere in your organization, and putting that in the $certificate_file. I'll see if I can fix this once I have the time. I really should start reading for some exams... :) -- Tommi Komulainen [EMAIL PROTECTED] PGP signature
Re: mutt-1.2: imap/ssl certificates
On Tue, May 16, 2000 at 12:41:27PM +0300, Tommi Komulainen wrote:
On Wed, May 10, 2000 at 02:05:30PM +0200, Andre Wobst wrote:
Hi,
I've troubles with the imap ssl certificates, saved in the file
certificate_file, which I set to ~/.mutt.certificate_file in my
~/.muttrc. If I do so, I can accept a certificate not only once but
always (otherwise this option isn't available). The certificate is
stored in the file ~/.mutt.certificate_file. But next time I start
mutt again, it asks me again for the certificate check. If I accept it
again, the certificate is again added to the file
~/.mutt.certificate_file and it is exactly the same like before -- now
stored twice in the same file. How can I store the certificate that
way, that mutt acceptes it automatically next time -- what's wrong in
the way I'm doing it?
For starters, you're doing nothing wrong, mutt is.
Please find attached a patch that fixes this bug.
I'll see if I can fix this once I have the time. I really should start
reading for some exams... :)
Oh dear. Well, there's always tomorrow...
--
Tommi Komulainen [EMAIL PROTECTED]
? Muttrc.head
Index: imap/imap_ssl.c
===
RCS file: /home/roessler/cvs/mutt/imap/imap_ssl.c,v
retrieving revision 1.12
diff -u -r1.12 imap_ssl.c
--- imap/imap_ssl.c 2000/04/26 07:32:42 1.12
+++ imap/imap_ssl.c 2000/05/16 21:56:14
@@ -284,7 +284,40 @@
}
}
+static int check_certificate_file (X509 *peercert)
+{
+ unsigned char peermd[EVP_MAX_MD_SIZE];
+ unsigned int peermdlen;
+ X509 *cert = NULL;
+ int pass = 0;
+ FILE *fp;
+
+ if (!X509_digest (peercert, EVP_sha1(), peermd, peermdlen))
+return 0;
+
+ if ((fp = fopen (SslCertFile, "rt")) == NULL)
+return 0;
+
+ while ((cert = READ_X509_KEY (fp, cert)) != NULL)
+ {
+unsigned char md[EVP_MAX_MD_SIZE];
+unsigned int mdlen;
+
+if (!X509_digest (cert, EVP_sha1(), md, mdlen) || peermdlen != mdlen)
+ continue;
+
+if (memcmp(peermd, md, mdlen) == 0)
+{
+ X509_free (cert);
+ pass = 1;
+ break;
+}
+ }
+ fclose (fp);
+ return pass;
+}
+
static int ssl_check_certificate (sslsockdata * data)
{
char *part[] =
@@ -297,23 +330,8 @@
char *line = NULL, *c;
/* automatic check from user's database */
- if ((fp = fopen (SslCertFile, "rt")))
- {
-EVP_PKEY *peer = X509_get_pubkey (data-cert);
-X509 *savedkey = NULL;
-int pass = 0;
-while ((savedkey = READ_X509_KEY (fp, savedkey)))
-{
- if (X509_verify (savedkey, peer))
- {
- pass = 1;
- break;
- }
-}
-fclose (fp);
-if (pass)
- return 1;
- }
+ if (SslCertFile check_certificate_file (data-cert))
+return 1;
menu = mutt_new_menu ();
menu-max = 15;
PGP signature
Re: mutt-1.2: imap/ssl certificates
On Wed, May 10, 2000 at 02:05:30PM +0200, Andre Wobst wrote: I've troubles with the imap ssl certificates, saved in the file certificate_file, which I set to ~/.mutt.certificate_file in my ~/.muttrc. If I do so, I can accept a certificate not only once but always (otherwise this option isn't available). The certificate is stored in the file ~/.mutt.certificate_file. But next time I start mutt again, it asks me again for the certificate check. If I accept it again, the certificate is again added to the file ~/.mutt.certificate_file and it is exactly the same like before -- now stored twice in the same file. How can I store the certificate that way, that mutt acceptes it automatically next time -- what's wrong in the way I'm doing it? You're the second person reporting this erratic behaviour. Unfortunately I have no idea what is going on. The certificate checking is done completely with SSL-library functions. So, either I'm doing something wrong, or those functions are broken on your platform. I think the first option is more likely but I'm yet to figure out why it goes wrong, and only in some cases. Feel free to send any suggestions directly to me or to mutt-dev mailing list. -- Tommi Komulainen [EMAIL PROTECTED]
Re: Multiple IMAP accounts?
On Sat, Mar 25, 2000 at 06:14:43PM -0600, Ben Beuchler wrote:
Has anyone come up with a way to access multiple IMAP accounts on
different servers from mutt? Or even a way to configure a macro that
will switch me from one to the other?
Been there, done that, forgot the documentation :-]
mailbox {[EMAIL PROTECTED]}
Works even with multiple accounts on the same server.
--
Tommi Komulainen [EMAIL PROTECTED]
Re: IMAP/SSL Support Broken?
On Sat, Jan 15, 2000 at 10:51:33PM -0800, Jeremy Katz wrote:
I've recompiled cvs mutt with --enable-imap and --enable-ssl (with openssl
installed) and all goes fine. ldd of mutt shows that it is linked
against libssl correctly. But, after changing my .muttrc to refer to
the server as {server:993/ssl}INBOX, mutt still connects to port 143 and
doesn't try to do SSL-ized IMAP. Any clues as to what's going on?
Hmm.. strange. Have you tried running it without specifying the port?
Port 993 is used as default in SSL mode so there's no need to specify
it explicitly. If that fixes the problem, then I know where to look.
If not, well...
It seems that I won't be having much time to develop mutt this spring
anyway but I'll see what I can do.
--
Tommi Komulainen [EMAIL PROTECTED]
Re: IMAP/SSL Support Broken?
On Tue, Jan 18, 2000 at 01:12:58PM -0800, Jeremy Katz wrote: Actually, I have no clue why it was trying to connect to port 143 at the time. It is now connecting to 993, but saying it is unable to get certificate from peer. Eh.. you didn't touch a thing but it just started working? strace output: Thanks, it revealed the IP so I quickly made my own tests: -8--8- ~% openssl s_client -host 152.1.2.236 -port 993 -verify -debug verify depth is 0 CONNECTED(0003) :error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:203: -8--8- Hmm.. so there's something wrong with SSL handshaking.. Now, disabling protocols one by one I got this: -8--8- ~% openssl s_client -host 152.1.2.236 -port 993 -verify -debug -no_tls1 verify depth is 0 CONNECTED(0003) depth=0 /C=US/ST=North Carolina/L=Raleigh/O=North Carolina State [EMAIL PROTECTED] verify error:num=18:self signed certificate verify return:1 depth=0 /C=US/ST=North Carolina/L=Raleigh/O=North Carolina State [EMAIL PROTECTED] verify return:1 ... -8--8- Which means it should work fine if you just disable the TLS protocol. There's no way to do this in mutt right now, so you're out of luck unless you can persuade your server administrator to change their configuration. Or you could try using stunnel or something, I think they can be configured to disable some protocols. Maybe we need to introduce a new variable allow disabling/enabling certain SSL protocols, or even better, modify the connection logic to notice unsupported protocols and try again without them. I'm not sure if the latter is even possible. I was under the impression that there's no harm in enabling all protocols and that if one isn't supported, another on would be tried. Apparently, I was wrong. -- Tommi Komulainen [EMAIL PROTECTED]
Re: Changing IMAP username on same IMAP server
On Tue, Nov 23, 1999 at 02:22:36PM +, Chris Green wrote:
My username is [EMAIL PROTECTED] (yes, it really is!), would
mutt cope with {[EMAIL PROTECTED]@mailandnews.co.uk}inbox ?
I posted a new patch to mutt-dev mailing list. It can handle your weird
username. :-]
--
Tommi Komulainen [EMAIL PROTECTED]
Re: Changing IMAP username on same IMAP server
On Tue, Nov 23, 1999 at 08:54:22AM +, Chris Green wrote:
Thanks for the information about mailandnews. I can see your point.
This patch would thus log out and log back in if the imap_user is
changed?
Actually, no. Previously a connection to a server was identified from
the address and the port number. If a connection to the same address
and port already existed, it was used, otherwise mutt would login.
The username was never checked, the patch just includes the username
in the decision whether mutt needs to login or not.
You can specify a username in the folder path, eg. {username@host}Mail/box,
and mutt will know how to handle it. You can also use $imap_user to change
the username, if one isn't given in the folder path, before you open that
folder.
--
Tommi Komulainen [EMAIL PROTECTED]
Re: Changing IMAP username on same IMAP server
On Tue, Nov 23, 1999 at 02:22:36PM +, Chris Green wrote:
You can specify a username in the folder path, eg. {username@host}Mail/box,
and mutt will know how to handle it. You can also use $imap_user to change
the username, if one isn't given in the folder path, before you open that
folder.
My username is [EMAIL PROTECTED] (yes, it really is!), would
mutt cope with {[EMAIL PROTECTED]@mailandnews.co.uk}inbox ?
Uh, no, you can't have '@' in the user/hostname.. I though '@' could be
considered as a 'forbidden' character in usernames. Weird system they are
having at mailandnews if you ask me.
I think I'll take another look at the parser...
--
Tommi Komulainen [EMAIL PROTECTED]
Re: Changing IMAP username on same IMAP server
On Wed, Nov 17, 1999 at 10:02:22AM +, Chris Green wrote: I have two IMAP accounts on the same IMAP4 server, how can I tell mutt to change from one to the other? If I just source a file which does a 'set imap_user=new user name' mutt doesn't seem to know anything has changed. The IMAP server is the same so the $folder and $spoolfile names are unchanged (so is the password for that matter!). I think that currently the only way to use different username on the same server would be to run another instance of mutt. Just out of curiosity, why are you using two mail accounts? Wouldn't it be easier to have the other account forward all the mail to the other, and have it drop mails in different folders with procmail? Anyway, I just posted a patch to add this feature to mutt-dev. It should be in the CVS shortly. -- Tommi Komulainen [EMAIL PROTECTED]
