Stuck on 97% changing mailboxes
Hi, following on from problems getting a new Exchange 2010 server to play nice with mutt's SMTP support (http://marc.info/?l=mutt-usersm=128493280217503w=2), I have now encountered a problem with IMAP access to the same server. This problem is unique to mutt and is not displayed by other mail clients (which proves that I haven't missed something completely basic, but does not necessarily mean the problem is mutt and not the server!) I can connect fine, and read the INBOX fine, and I seem to be able to change into small mailboxes 2000 messages. By change I mean, I can select the mailbox in mutt and after a delay while it downloads the message headers, the mutt list view shows the contents of the folder. However, for larger mailboxes, when I attempt to change, mutt only gets as far as saying Fetching message headers... 3320/3391 (97%) which remains unchanged for ~5 minutes before I give up. Curiously, the .muttdebug log looks normal. The last few lines are Date: Mon, 20 Sep 2010 10:18:35 +0100 4 ) parse_parameters: `charset=US-ASCII; format=flowed; delsp=yes' parse_parameter: `charset' = `US-ASCII' parse_parameter: `format' = `flowed' parse_parameter: `delsp' = `yes' 4 a0011 OK FETCH completed. IMAP queue drained (where that Date is the date of the most recent email in that mailbox). The other data point is the fact that Thunderbird has no problem reading these mailboxes: it downloads the headers, displays the full message list, and reads the contents of the emails to generate its search index, all without any unusual delay. The problem seems to be 97% every time. And there does seem to be something significant about mailbox size -- I haven't found a mailbox with fewer than 2000 messages with this problem, and I haven't found a mailbox larger than that without it. But this is obviously based on limited statistics and it's difficult to test. I have disabled header and body caching in mutt. No change. Any ideas? Is there a switch I can throw in mutt? -- Mike
Re: How to match all theaded emails excluding the first one?
On Sun, Sep 19, 2010 at 09:18:40AM +0200, Marco Giusti wrote: On Sun, Sep 19, 2010 at 09:23:15AM +0800, Yue Wu wrote: Hi list, As title, I want to keep all of the topics, but delete all of the others. You can tag/search/delete responses using an heuristic expression, the simpler comes in my mind: ~s Re: If the emails are not too much, tag them using this expression and then perform a manually check. Thanks Marco, seems it's what I want. P.S., how does mutt dertermine threads? Maybe it's better and more reliable than the ~s Re: way? -- Regards, Yue Wu Key Laboratory of Modern Chinese Medicines Department of Traditional Chinese Medicine China Pharmaceutical University No.24, Tongjia Xiang Street, Nanjing 210009, China
Re: some color definitions dont work
I don't know if it helps or applies to you, but I was unable to get the colors to work, but the devil is in the details. I was running on Solaris 10/x86 and installed mutt from the sunfreeware pre-built. No luck with colors under 1.5.17 but no problems at all with 1.5.20 with a lot of the issues being the load library dependencies. On Sat, Sep 18, 2010 at 02:16:53PM +0200, Matthias Apitz wrote: Hello, I'm really with no clue and sorry if this stupid or a FAQ, but I can't get some of the color settings to work in mutt 1.15.9 :-( What does work is: set color_after_eol=no color status brightgreen blue color indicator brightyellow red color normal black white What does not work is, for example: color header brightyellow red ^(To|From|Subject): The effect is with the above statement like 'brightgris white'. Same happens with color signature brightgreen blue setting this gives the signature in 'brightgris white'. What do I stupidly wrong? Thanks for a pointer. And yes. I have read the manual, already for some hours, and it is not my xterm, because it worked with 1.14.x Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: How to match all theaded emails excluding the first one?
On 10.09.20, Yue Wu wrote: P.S., how does mutt dertermine threads? Maybe it's better and more reliable than the ~s Re: way? For correct threads, i.e. if the user hasn't chosen to use just the subject line, it uses References: which refer to the message-id of the mail(s) to which it is responding. Do H and look at the headers and you'll see under References: 20100919012315.gc36...@fbsd.t60.cpu 20100919071840.ga26...@murdoc etc. Kind regards Michael
Re: How to match all theaded emails excluding the first one?
On Mon, Sep 20, 2010 at 03:02:06PM +0200, mjsseppl-m...@yahoo.de wrote: On 10.09.20, Yue Wu wrote: P.S., how does mutt dertermine threads? Maybe it's better and more reliable than the ~s Re: way? For correct threads, i.e. if the user hasn't chosen to use just the subject line, it uses References: which refer to the message-id of the mail(s) to which it is responding. Do H and look at the headers and you'll see under References: 20100919012315.gc36...@fbsd.t60.cpu 20100919071840.ga26...@murdoc etc. I got it, matching Re: in subject field is easier, though not reliable, but it works in almost cases. Thank you :) -- Regards, Yue Wu Key Laboratory of Modern Chinese Medicines Department of Traditional Chinese Medicine China Pharmaceutical University No.24, Tongjia Xiang Street, Nanjing 210009, China
Re: How to match all theaded emails excluding the first one?
On Mon, Sep 20, 2010 at 08:36:02PM +0800, Yue Wu wrote: [...] P.S., how does mutt dertermine threads? Maybe it's better and more reliable than the ~s Re: way? I got another idea that uses mutt's thread capability. I test it but i didn't create a macro (because I'm lazy) and I leave it to you as exercise. Uncollapse all threads (Esc+V), tag all messages (T and '.' as pattern), collapse all threads (Esc+V again) tag all messages (T and '.' again). What you get is that all messages excluded the first ones in every thread are tagged. At this point I don't know if you need to uncollapse all threads again to delete the messages or not (I didn't tryed this :). m. -- C'è un'ape che se posa su un bottone di rosa: lo succhia e se ne va... Tutto sommato, la felicità è una piccola cosa. -- Trilussa, Felicità
Re: How to match all theaded emails excluding the first one?
On 10.09.20, mjsseppl-m...@yahoo.de wrote: On 10.09.20, Yue Wu wrote: Do H and look at the headers and you'll see under References: 20100919012315.gc36...@fbsd.t60.cpu 20100919071840.ga26...@murdoc etc. In-Reply-To: is also used. Kind regards Michael
Re: How to match all theaded emails excluding the first one?
On Mon, Sep 20, 2010 at 03:29:37PM +0200, Marco Giusti wrote: On Mon, Sep 20, 2010 at 08:36:02PM +0800, Yue Wu wrote: [...] P.S., how does mutt dertermine threads? Maybe it's better and more reliable than the ~s Re: way? I got another idea that uses mutt's thread capability. I test it but i didn't create a macro (because I'm lazy) and I leave it to you as exercise. Uncollapse all threads (Esc+V), tag all messages (T and '.' as pattern), collapse all threads (Esc+V again) tag all messages (T and '.' again). What you get is that all messages excluded the first ones in every thread are tagged. At this point I don't know if you need to uncollapse all threads again to delete the messages or not (I didn't tryed this :). Wow. So smart tip! Thank you. -- Regards, Yue Wu Key Laboratory of Modern Chinese Medicines Department of Traditional Chinese Medicine China Pharmaceutical University No.24, Tongjia Xiang Street, Nanjing 210009, China
Re: sending mail directly to MX based on To: addr
El día Friday, September 17, 2010 a las 04:44:46PM +0200, Luciano Rocha escribió: which put the mail to the local queue and the sendmail queue runner later to the SMTP smarterhost (of my ISP). So far so good. In some cases I would send the mail directly with SMTP to the destination, based on the To: addr. Any idea how I could configure this in mutt? Thanks in advance I use a send-hook: send-hook . unset smtp_url send-hook @example.com set smtp_url=smtp://example.com/ Luciano, Do you know if mutt logs somewhere the SMTP dialog with the remote server? I found nothing in the docs about... Thx matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/
Re: sending mail directly to MX based on To: addr
On 20 Sep 2010, at 16:36, Matthias Apitz wrote: Do you know if mutt logs somewhere the SMTP dialog with the remote server? I found nothing in the docs about... Run mutt -d2. Server chat is then logged in ~/.muttdebug*. Increase the number 2 to larger numbers for more detail. (This assumes mutt was compiled with --enable-debug, i.e. mutt -v includes +DEBUG.)
Re: How to match all theaded emails excluding the first one?
* On 20 Sep 2010, Marco Giusti wrote: I got another idea that uses mutt's thread capability. I test it but i didn't create a macro (because I'm lazy) and I leave it to you as exercise. I have used this technique before. It works well. Uncollapse all threads (Esc+V), tag all messages (T and '.' as pattern), collapse all threads (Esc+V again) tag all messages (T and '.' again). ITYM untag for the second pass :) The tricky part of macrofying it is that collapse-all is a toggle, so you have to assume the initial state of your folder. Assuming you start out uncollapsed: macro index =tS tag-pattern.entercollapse-alluntag-pattern.entercollapse-all tag all non-initial messages in threads You can of course extend this technique to work on the current thread. macro index =ts enter-commandset my_resolve=$resolve; set resolve=noentertag-threadcollapse-threadtag-messagecollapse-threadenter-commandset move=$my_resolveenter tag non-initial messages in current thread -- David Champion * d...@uchicago.edu * IT Services * University of Chicago
Re: How to match all theaded emails excluding the first one?
On Mon, Sep 20, 2010 at 03:38:16PM +0200, mjsseppl-m...@yahoo.de wrote: On 10.09.20, mjsseppl-m...@yahoo.de wrote: On 10.09.20, Yue Wu wrote: Do H and look at the headers and you'll see under References: 20100919012315.gc36...@fbsd.t60.cpu 20100919071840.ga26...@murdoc etc. In-Reply-To: is also used. In-Reply-To: is standard, while References: is a Usenet-ism. Good MUAs will thread based on both. Some MUAs break threading (by including neither of those two headers), so sometimes it's necessary to match replies via subject matching. Mutt supports all of this, and uses asterisks to mark mails which break threading. (MUAs could go so far as to match quoting in mail bodies, but that's really hard.) See: http://www.jwz.org/doc/threading.html Nico --
$tunnel and $smtp_url
Hi, I try to use $tunnel with $smtp_url, but can't manage to do it. I don't trust my wifi Internet connection, so I want my mail to pass through a ssh tunnel to a server I own, before reaching the smtp server. ME ---(smtp inside ssh)--- my_server ---(smtp)--- smtp_server. I don't own smtp_server (in fact it is gmail). For incoming mail, I've added a plugin line in my fetchmailrc and it's perfect : poll imap.gmail.com with proto IMAP timeout 20 plugin ssh my_server nc %h %p user me there is ... So fetchmail launches ssh to my_server, then nc (netcat) remotely. nc connects to the imap server (%h:%p), sends what it gets on stdin and writes to its stdout what the imap server answers. I guess it goes back to fetchmail the same way, using ssh' stdin and stdout. I'm trying to do it for outgoing mail, and I want to use mutt (because $smtp_url depends on hooks, and I want to deal with it inside mutt). I've found the tunnel variable, but can't make it work as I'd like. « Setting this variable will cause mutt to open a pipe to a command instead of a raw socket. You may be able to use this to set up preauthenticated connections to your IMAP/POP3/SMTP server. Example: set tunnel=ssh -q mailhost.net /usr/local/libexec/imapd » I can't use ssh to connect to the smtp server (since it's gmail). I have smtp_url=smtps://m...@gmail.com@smtp.gmail.com:465 and smtp_pass defined (works fine when connecting directly). I tried setting tunnel=ssh my_server nc smtp.gmail.com 465, but it doesn't work and I don't manage to find why. The only thing I can see is that a ssh connection is opened and data is sent. I also tried smtp instead of smtps, but it doesn't work either. How does $tunnel work? Is $smtp_url ignored when $tunnel is set?
