Re: SASL authentication failed
On Mon, Feb 18, 2013 at 8:06 PM, Kevin J. McCarthy m...@8t8.us wrote: Mehturt wrote: Yes, I'm using this already. The question is - is there an equivalent of Thunderbird's Normal Password and SSL/TLS? I'm using: set smtp_url=smtps://user:pass@host:465 And I tried smtp_authenticators set to plain and login, but it did not work. I can post .muttdebug* if required. Just a few random things to try. First off, comment out smtp_authenticators in your muttrc and let mutt try all the methods. Thanks, I tried that already, also tried plain and login, which the server advertises. Try out port 587 and TLS (note the smtp:// instead of smtps://) set smtp_url=smtp://user:pass@host:587 Tried that, no change. If you are on Debian/Ubuntu, make sure you have the libsasl2-modules package installed. I am on Debian, and I have it installed.
Re: Highlight treads related to me
On 2013–02–18 s. keeling wrote: Since I use folding by default, I would like to highlight entire Please explain what folding is? When I look in saved folders, they're threaded and specific threads are colorized. What do you mean? Sorry, I mixed up the terminology. In editors it's called folding, mutt calls it “collapsing”. It displays only the first message of each thread by default. folder-hook . 'push collapse-all' bind index space collapse-thread It makes sense to add the number of collapsed messages to the index_format in this case. Marco signature.asc Description: Digital signature
Re: SASL authentication failed
On Mon, Feb 18, 2013 at 7:47 PM, Torsten Flammiger nos...@netfg.net wrote: I'm trying to use mutt with my company's SMTP server (IMAP works fine). I always get SASL authentication failed when sending message. I use msmtp. A simple yet effective command line smtp utility. It works fine with SSL/TLS here .muttrc: set sendmail=/usr/bin/msmtp .msmtprc account default host YOUR SMTP RELAY port 25 from your from address auth on user SALS username password YOUR PW tls on tls_starttls on # logfile ~/.msmtp.log ## if you need to tls_certcheck off See also: http://msmtp.sourceforge.net/doc/msmtp.html Thanks. Previously I used esmtp with mutt, but now since the functionality is built in mutt, I tried to use it. So I tried msmtp and it worked just fine with this configuration, thanks a lot. Now I need to find out what the difference is.
Re: Highlight treads related to me
- Marco net...@lavabit.com [2013-02-19 00:12:52 +0100] - : On 2013–02–18 Marco wrote: Since I use folding by default, I would like to highlight entire threads as well. I only see the highlighted messages when I unfold the thread. Note: The message highlighting described in the other thread works fine for threads I started. This question is about highlighting messages I responded to. Marco Marco, this is what I do: folder-hook . ' \ ... ;\ uncolor index ~x kode5.net ;\ ... \ ' folder-hook mutt '\ ... ;\ color index black green ~x kode5.net ;\ ... \ ' The first folder-hook is the default. It removes the coloured threading in folders such as my inbox and others that are not mailing list mailboxes or those which are not threaded, for whatever reason. The second folder-hook, in this case for my mutt mailing list mailbox, and the same is true for all other mailing list mailboxes, sets the colour black on green on mails that have my domain in the messages that have been followed up to in threads in which I have participated. Forgive the line continuation but i have lots of other settings in my folder-hooks and writing a single line for the entire hook would render it unreadable. The pattern ~(~something) is for doing things to messages within threads, as someone suggested already. You could play with that a bit. But I think my suggestion will work for you; obviously, use your own hostname/domainname in the expression. -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: SASL authentication failed
- Kevin J. McCarthy m...@8t8.us [2013-02-18 11:06:57 -0800] - : Mehturt wrote: Yes, I'm using this already. The question is - is there an equivalent of Thunderbird's Normal Password and SSL/TLS? I'm using: set smtp_url=smtps://user:pass@host:465 And I tried smtp_authenticators set to plain and login, but it did not work. I can post .muttdebug* if required. Just a few random things to try. First off, comment out smtp_authenticators in your muttrc and let mutt try all the methods. Yes - mutt automatically tries all the appropriate authentication methods the smtp server will accept, so Kevin is right here. Just let mutt work it out. Try out port 587 and TLS (note the smtp:// instead of smtps://) set smtp_url=smtp://user:pass@host:587 I'm not even sure you need to specify a port here if you use smtps://... - again, mutt should connect to the smtp server using the correct port for ssl/tls connections. To start, try stripping out the password bit in the url. So just try it with smtps://usern...@host.example.com. If you get that working, then add in the password bit; but, you can set $smtp_pass for this if you require/prefer. If you are on Debian/Ubuntu, make sure you have the libsasl2-modules package installed. -Kevin Again, take Kevin's advice - make sure all the sasl libraries are correctly installed. Check out this page, for some tips on using mutt in this way: http://linsec.ca/Using_mutt_on_OS_X#Setting_up_SMTP_Support You might find it useful. Don't worry that this is on Mac OS X, the principles are the same. -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Highlight treads related to me
On 2013–02–19 James Griffin wrote: The first folder-hook is the default. It removes the coloured threading in folders such as my inbox and others that are not mailing list mailboxes or those which are not threaded, for whatever reason. I use the same technique. The second folder-hook, in this case for my mutt mailing list mailbox, and the same is true for all other mailing list mailboxes, sets the colour black on green on mails that have my domain in the messages that have been followed up to in threads in which I have participated. The problem is that ~x triggers on the References field. However, the first message does not have a References field and unfortunately that is the most important message to highlight, since that's the only visible message (I collapse the threads by default). One step further would be to trigger on messages I responded to. That yields correct results if I respond to the original posting, but it fails if I respond to a deeper nested mail in a long thread. The pattern ~(~something) is for doing things to messages within threads, as someone suggested already. I couldn't get this working. But frankly, I didn't quite grasp yet what it's supposed to do. I will read the docs once more and try again later. Marco signature.asc Description: Digital signature
Re: Highlight treads related to me
- Marco net...@lavabit.com [2013-02-19 11:08:08 +0100] - : On 2013–02–19 James Griffin wrote: The first folder-hook is the default. It removes the coloured threading in folders such as my inbox and others that are not mailing list mailboxes or those which are not threaded, for whatever reason. I use the same technique. The second folder-hook, in this case for my mutt mailing list mailbox, and the same is true for all other mailing list mailboxes, sets the colour black on green on mails that have my domain in the messages that have been followed up to in threads in which I have participated. The problem is that ~x triggers on the References field. However, the first message does not have a References field and unfortunately that is the most important message to highlight, since that's the only visible message (I collapse the threads by default). One step further would be to trigger on messages I responded to. That yields correct results if I respond to the original posting, but it fails if I respond to a deeper nested mail in a long thread. The pattern ~(~something) is for doing things to messages within threads, as someone suggested already. I couldn't get this working. But frankly, I didn't quite grasp yet what it's supposed to do. I will read the docs once more and try again later. Marco I've had trouble getting it to work in my patterns as well. You use my pattern and extend it by including another pattern. ~P, ~v and ~f : messages from you, messages which are part of a collapsed thread and messages from EXPR respectively could be included in the pattern I provided. I'd go for ~P personally, so perhaps: color index black green ~P ~x example.com; ~P AND ~x (so logical AND) both true, not one or the other, could work? I haven't tested it yet but will do later maybe. -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Highlight treads related to me
- Marco net...@lavabit.com [2013-02-19 10:07:03 +0100] - : On 2013–02–18 s. keeling wrote: Since I use folding by default, I would like to highlight entire Please explain what folding is? When I look in saved folders, they're threaded and specific threads are colorized. What do you mean? Sorry, I mixed up the terminology. In editors it's called folding, mutt calls it “collapsing”. It displays only the first message of each thread by default. folder-hook . 'push collapse-all' bind index space collapse-thread It makes sense to add the number of collapsed messages to the index_format in this case. Marco Another way of doing this is to use the message-id: header, like so: color index black green '~h ^message-id:.*hostname.example.com' Use you machine hostname in that pattern, that should also work. Use the uncolor function in the default folder-hook to remove it from mailboxes you do not wish to have this coloured index on these messages. -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Highlight treads related to me
Hi Marco, On Tue, Feb 19, 2013 at 11:08:08AM +0100, Marco wrote: On 2013–02–19 James Griffin wrote: The pattern ~(~something) is for doing things to messages within threads, as someone suggested already. I couldn't get this working. But frankly, I didn't quite grasp yet what it's supposed to do. I will read the docs once more and try again later. I think it was quite badly explained: ~(…) returns threads, that contain at least one message where the inner pattern matched. So the example ~(~P) as listed in the documentation will give you all threads that contain a message you sent. I just tried it on my mutt-mailbox, with :color index yellow default ~(~P) and it colored all threads I participated in yellow as expected. This also affected the collapsed view: http://imgur.com/d2BhIa4 So if your alternates are set up so that all your mail-addresses are listed it should work pretty neat. It only leaves you to apply this only to the mailboxes you want to. Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Highlight treads related to me
On 2013–02–19 Andre Klärner wrote: I think it was quite badly explained: ~(…) returns threads, that contain at least one message where the inner pattern matched. So the example ~(~P) as listed in the documentation will give you all threads that contain a message you sent. I just tried it on my mutt-mailbox, with :color index yellow default ~(~P) and it colored all threads I participated in yellow as expected. It works. And it's so simple! So if your alternates are set up so that all your mail-addresses are listed it should work pretty neat. It only leaves you to apply this only to the mailboxes you want to. I've already done that before for the version without ~(). Thanks a lot. Marco signature.asc Description: Digital signature
Re: Highlight treads related to me
- Andre Klärner kan...@ak-online.be [2013-02-19 13:23:08 +0100] - : Hi Marco, I think it was quite badly explained: ~(…) returns threads, that contain at least one message where the inner pattern matched. So the example ~(~P) as listed in the documentation will give you all threads that contain a message you sent. A reference and suggestion to the pattern was given twice in the thread. The documentation and man pages provide all the explanation that is needed. I am quite sure Marco is capable of typing man muttrc at his terminal to find out what it does. I just tried it on my mutt-mailbox, with :color index yellow default ~(~P) and it colored all threads I participated in yellow as expected. This also affected the collapsed view: http://imgur.com/d2BhIa4 My understanding is, that the pattern ~(~P) will only highlight the messages sent from Marco within the thread. It won't highlight all the messages in the thread, namely those not sent by Marco. This is not what he wants. ... -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Highlight treads related to me
On 2013–02–19 James Griffin wrote: A reference and suggestion to the pattern was given twice in the thread. The documentation and man pages provide all the explanation that is needed. I am quite sure Marco is capable of typing man muttrc at his terminal to find out what it does. Indeed. And I am glad you took the time to help me achieving my goal. I just tried it on my mutt-mailbox, with :color index yellow default ~(~P) and it colored all threads I participated in yellow as expected. This also affected the collapsed view: http://imgur.com/d2BhIa4 My understanding is, that the pattern ~(~P) will only highlight the messages sent from Marco within the thread. It won't highlight all the messages in the thread, namely those not sent by Marco. From man muttrc: ~(PATTERN) messages in threads containing messages matching a certain pattern, e.g. all threads containing messages from you: ~(~P) This is not what he wants. This is exactly what I wanted. Marco signature.asc Description: Digital signature
Re: Highlight treads related to me
- Marco net...@lavabit.com [2013-02-19 14:54:11 +0100] - : On 2013–02–19 James Griffin wrote: A reference and suggestion to the pattern was given twice in the thread. The documentation and man pages provide all the explanation that is needed. I am quite sure Marco is capable of typing man muttrc at his terminal to find out what it does. Indeed. And I am glad you took the time to help me achieving my goal. I just tried it on my mutt-mailbox, with :color index yellow default ~(~P) and it colored all threads I participated in yellow as expected. This also affected the collapsed view: http://imgur.com/d2BhIa4 My understanding is, that the pattern ~(~P) will only highlight the messages sent from Marco within the thread. It won't highlight all the messages in the thread, namely those not sent by Marco. From man muttrc: ~(PATTERN) messages in threads containing messages matching a certain pattern, e.g. all threads containing messages from you: ~(~P) This is not what he wants. This is exactly what I wanted. Marco Indeed. It seems I did not/do not fully understand how that pattern works. I've tried it in the past and the results were not as I expected, so my mistake there and on this occasion. The most important thing is that you have got your solution and you're now happy with the result. Best wishes. -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Supporting readline editing in Mutt entry fields
Hi Michael and David, On Mon, Feb 18, 2013 at 06:34:05PM +, Michael Elkins wrote: It has been a very long time since I looked at readline, but the time the problem was that readline wants control of drawing on the screen, which conflicts with mutt's use of the curses library. readline is more for line-oriented input than entire screen-oriented applications. You'd also have to rewrite the completion functions to integrate with readline. I see both your points and realise the issue is more complicated than I had hoped. But I would still try to take a look at it. If I can't use readline then maybe I could implement readline like features myself. In any case, this would be an interesting exercise for me since I have never written a patch for a complex C program. Since this is a one off question for now, I took the liberty to post on the users list to avoid subscribing to mutt-dev. Sorry about that. Thanks a lot, -- Suvayu Open source is the future. It sets us free.
Re: Highlight treads related to me
- Andre Klärner kan...@ak-online.be [2013-02-19 13:23:08 +0100] - : Hi Marco, I think it was quite badly explained: ~(…) returns threads, that contain at least one message where the inner pattern matched. So the example ~(~P) as listed in the documentation will give you all threads that contain a message you sent. I just tried it on my mutt-mailbox, with :color index yellow default ~(~P) and it colored all threads I participated in yellow as expected. This also affected the collapsed view: http://imgur.com/d2BhIa4 So if your alternates are set up so that all your mail-addresses are listed it should work pretty neat. It only leaves you to apply this only to the mailboxes you want to. I have just tried this pattern: ~(~n -50) which should tag all messages in threads, even collapsed threads, and it does not tag the messages in collapsed threads, only the first message in the thread. According to how this pattern works, surely all the messages in the collapsed thread with a score up-to 50 should be tagged? -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Highlight threads related to me
[Corrected subject, for archive search purposes] - Marco net...@lavabit.com [2013-02-19 00:12:52 +0100] - : On 2013–02–18 Marco wrote: Since I use folding by default, I would like to highlight entire Hi Marco (sorry about private mail, thought I'd lost this thread.) When you say folding do you mean this config (or something like it) snippet? ## # Collapse all threads except for threads with unread messages. set collapse_unread=no folder-hook . 'push collapse-all' -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X
Re: Highlight threads related to me
On 2013–02–20 Chris Bannister wrote: When you say folding do you mean this config (or something like it) snippet? ## # Collapse all threads except for threads with unread messages. set collapse_unread=no folder-hook . 'push collapse-all' Yes, I meant collapsing. I mixed up the terminology. This is the relevant part of my muttrc: bind index space collapse-thread folder-hook . 'push collapse-all' set collapse_unread = no Marco signature.asc Description: Digital signature
Re: Supporting readline editing in Mutt entry fields
If are interested in it as a programming exercise, I would recommend trying to add functionality that is missing in mutt's line editor rather than trying to fiddle with readline. But if you did find a way for them to coexist, I'd be interested in the result as well.
Re: Supporting readline editing in Mutt entry fields
Hi Michael, On Tue, Feb 19, 2013 at 06:57:41PM +, Michael Elkins wrote: If are interested in it as a programming exercise, I would recommend trying to add functionality that is missing in mutt's line editor rather than trying to fiddle with readline. But if you did find a way for them to coexist, I'd be interested in the result as well. I was hoping to look at both and finally go with whichever is cleaner/simpler. My problem is I do not know where to start in the mutt source; as in, which methods/files to look at. Any help regarding the starting point would be awesome. Cheers, -- Suvayu Open source is the future. It sets us free.
Re: Supporting readline editing in Mutt entry fields
Hi Suvayu, On Tue, Feb 19, 2013 at 09:46:25PM +0100, Suvayu Ali wrote: On Tue, Feb 19, 2013 at 06:57:41PM +, Michael Elkins wrote: If are interested in it as a programming exercise, I would recommend trying to fiddle with readline. But if you did find a way for them to coexist, I'd be interested in the result as well. I was hoping to look at both and finally go with whichever is cleaner/simpler. My problem is I do not know where to start in the mutt source; as in, which methods/files to look at. Any help regarding the starting point would be awesome. just for my interest: what exact features are your missing? I for myself did not notice any missing parts. Thanks and regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Supporting readline editing in Mutt entry fields
Hi Andre, On Wed, Feb 20, 2013 at 01:14:45AM +0100, Andre Klärner wrote: Hi Suvayu, On Tue, Feb 19, 2013 at 09:46:25PM +0100, Suvayu Ali wrote: On Tue, Feb 19, 2013 at 06:57:41PM +, Michael Elkins wrote: If are interested in it as a programming exercise, I would recommend trying to fiddle with readline. But if you did find a way for them to coexist, I'd be interested in the result as well. I was hoping to look at both and finally go with whichever is cleaner/simpler. My problem is I do not know where to start in the mutt source; as in, which methods/files to look at. Any help regarding the starting point would be awesome. just for my interest: what exact features are your missing? I for myself did not notice any missing parts. Just a quick list: 1. Although history browsing works, search doesn't 2. I couldn't find undo 3. Cut works, but I can paste it any more 4. Transpose word or transpose characters is missing I guess I'm too used to these from bash and emacs. :) Another unrelated issue, I found inputing unicode characters from the entry field is not possible although mutt displays those characters in other views like the pager. Cheers, -- Suvayu Open source is the future. It sets us free.
