automatically delete duplicate email ... is it possible ? [SEC=UNCLASSIFIED]
Hi all, I often find my self using D ~= $ (manually) to delete duplicate email from my mailing lists mailboxes. Can anyone recommend a way to have this automagically done for me ? Thanks! -Alex IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: mutt and some GMail features [SEC=UNCLASSIFIED]
0n Sun, Jun 05, 2011 at 04:19:10PM -0400, Chris Brennan wrote: * Ionel Mugurel Ciobica tga...@chem.tue.nl [2011-06-05 21:37:13 +0200]: If you use vim for other than editing e-mails, you may want not to add that limit in your .vimrc. Instead add this to your .muttrc: set editor=/usr/bin/vim -c 'set ft=mail et tw=72' Perfect, I will add that over textwidth in my .vimrc, thanks Something else that is brilliant is binding a key as such: Add this to your $HOME/.vimrc -- fix formatting -- * F1 to re-format the current paragraph correctly * F2 to format a line which is too long, and go to the next line * F3 to merge the previous line with the current one, with a correct nmapF1gqap nmapF2gqqj nmapF3kgqj map!F1ESCgqapi map!F2ESCgqqji map!F3ESCkgqji Enjoy! -Alex IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: accessing shared mailboxes on exchange server [SEC=UNCLASSIFIED]
0n Mon, Jun 06, 2011 at 12:10:52PM +0100, John wrote: You can also set up your mutt to point imap connection at the davmail server and check if that works. wow, thanks for this. I hope I can make it run on freebsd with linux emulation. I wonder if it will run on windows as a portable app? I run thunderbird as a portable app on windows boxes) Its in ports: /usr/ports/mail/davmail -Alex IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: mairix search [SEC=UNCLASSIFIED]
0n Fri, Apr 29, 2011 at 01:56:51PM +0200, Sebastian Tramp wrote: Is searching / indexing with mairix state of the art or is there a better solution available? I am quite happy with that, just wanted to ask ;-). There is also nmzmail (only for Maildir though) - I actually thought many users switched from mairix to nmzmail. nmzmail is a tool to use the namazu2 search engine from within a mail reader such as mutt to search mail stored in maildir folders. Based on the result of the namazu query, nmzmail generates a maildir folder containing symbolic links to the mails matching the query. Mutt and other mail readers can make it easy to use nmzmail with a simple macro. Features: * fast mail searching even with large number of mails * incremental index building * rich query language including regular expressions (see the namazu documentation) * integrates nicely into mutt * query history WWW: http://www.ecademix.com/JohannesHofmann/nmzmail.html -Alex IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: Wrapping non-wrapped e-mail when replying [SEC=UNCLASSIFIED]
0n Thu, Apr 28, 2011 at 02:51:32PM -0500, David Champion wrote: * On 27 Apr 2011, Trey Sizemore wrote: I'd like to find out how to wrap long lines in e-mails that I'm replying to. My mutt is setup to automatically wrap lines when I compose, but I'd like to be able to also lap long lines in e-mails when I reply. I use with gqap functionality within vim (.vimrc) (F1 being the key one you want): * F1 to re-format the current paragraph correctly * F2 to format a line which is too long, and go to the next line * F3 to merge the previous line with the current one, with a correct nmapF1gqap nmapF2gqqj nmapF3kgqj map!F1ESCgqapi map!F2ESCgqqji map!F3ESCkgqji Works wonderfully! -Alex IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: Wrapping non-wrapped e-mail when replying [SEC=UNCLASSIFIED]
0n Thu, Apr 28, 2011 at 02:51:32PM -0500, David Champion wrote: * On 27 Apr 2011, Trey Sizemore wrote: I'd like to find out how to wrap long lines in e-mails that I'm replying to. My mutt is setup to automatically wrap lines when I compose, but I'd like to be able to also lap long lines in e-mails when I reply. Besides vim, you can use a program called 'par'. It is brilliant. I set $display_filter to use it so that I get the neat line wrap for reading as well. I also have several vi macros that use it for reflowing text in different styles. (Even if I did use vim, par is more flexible.) David, any chance you can post any examples of your config for par ? -Alex IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: removing signatures from incoming mails [SEC=UNCLASSIFIED]
0n Thu, Feb 24, 2011 at 08:01:26PM +0100, Thorsten Scherf wrote: some mailinglists using freemail providers put an automatic signature to all mails from the lists. How do I have to configure mutt to get rid of the signature from all mails within a specfic folder? t-prot is good. This program is a filter which shall improve the readability for messages (emails and posts) by *hiding* some annoying parts, including: - mailing list footers - excessive quoting - overlong signatures - Outlook-style TOFU (text above - full quote below) - squeeze sequences of blank lines or punctuation Its primary mode of operation is a display filter in MUA (it has special support for Mutt), but it can also be used in MTA/MDA - e.g. for immediately bouncing improper messages. Author: Jochen Striepe t-p...@tolot.escape.de WWW:http://www.escape.de/~tolot/mutt/ -Alex IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: setting mutt to charset UTF-8 ? [SEC=UNCLASSIFIED]
0n Wed, Oct 06, 2010 at 10:00:27AM -0500, Nicolas Williams wrote: It is, since Matthias must be using Solaris (given the reference to truss(1)), #uname -s which truss FreeBSD /usr/bin/truss :P -Alex IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: forwarding mail with attachments [SEC=UNCLASSIFIED]
0n Thu, Feb 25, 2010 at 08:35:53AM +0100, Vegard Svanberg wrote: * Daniel Dalton d.dal...@iinet.net.au [2010-02-25 07:27]: How can I make mutt forward all attachments as well as the original email when using 'f' the forward command? I would also like the original text from the email to be included in the body of the message as it is now. You could also set up a macro as such: macro index,pager F :set mime_forward=yes\n:set mime_forward_decode=no\nforward-message -- -- /* Please Dont Blame Me For The Below Text */ IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. -- --
Certain (mailing list) emails NOT being threaded ... trying to work out why ? [SEC=UNCLASSIFIED]
Hi all,
I am subscribed to email alerts from:
From: Sysinternals Forums fo...@forum.sysinternals.com
However, threading never ever has seemed to work. I am finally
wanting to investigate why and if possible how to fix it.
Here is an example of a series of emails that should have been threaded:
03 N Jan 08 Sysinternals Fo (2.6K) Sysinternals Forums Topic Reply
Notification : dxgkrnl.sys and usbport.sys hardware interrupts
- 0 141 N Jan 07 Sysinternals Fo (4.0K) Sysinternals Forums Topic Reply
Notification : dxgkrnl.sys and usbport.sys hardware interrupts
0 165 N Jan 07 Sysinternals Fo (4.4K) Sysinternals Forums Topic Reply
Notification : dxgkrnl.sys and usbport.sys hardware interrupts
0 166 N Jan 07 Sysinternals Fo (4.4K) Sysinternals Forums Topic Reply
Notification : dxgkrnl.sys and usbport.sys hardware interrupts
0 184 N Jan 07 Sysinternals Fo (4.7K) Sysinternals Forums Topic Reply
Notification : dxgkrnl.sys and usbport.sys hardware interrupts
0 188 N Jan 07 Sysinternals Fo (6.6K) Sysinternals Forums Topic Reply
Notification : dxgkrnl.sys and usbport.sys hardware interrupts
Here is my folder-hook to implement threading:
folder-hook . \
set sort=reverse-threads ;\
set sort_aux=last-date-received ;\
set duplicate_threads=yes ;\
push 'delete-pattern~=enter' ;\
push 'collapse-all' ;\
set index_format='%3N %4C %S %{%b %d} %-15.15F (%4c) %?M?%M
?%s' ;\
set display_filter='t-prot -acelmtS -Mmutt --spass'
Can anyone suggest why the aforementioned Sysinternals Forums Topic Reply
Notification emails would not be threaded or methods to try investigate why.
Thanks
-Alex
IMPORTANT: This email remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT
1914. If you have received this email in error, you are requested to contact
the sender and delete the email.
Re: Certain (mailing list) emails NOT being threaded ... trying to
0n Thu, Jan 07, 2010 at 10:48:37PM -0600, Kyle Wheeler wrote:
On Friday, January 8 at 12:38 PM, quoth Wilkinson, Alex:
However, threading never ever has seemed to work. I am finally
wanting to investigate why and if possible how to fix it.
Do you have strict threading enabled? If so, try turning it off (unset
strict_threads). It's possible that that mailing list is stripping out
the usual email headers that establish threads (such as In-Reply-To
and References).
I added unset strict_threads to my folder-hook e.g.
folder-hook . \
set sort=reverse-threads ;\
set sort_aux=last-date-received ;\
set duplicate_threads=yes ;\
unset strict_threads ;\
push 'delete-pattern~=enter' ;\
push 'collapse-all' ;\
set index_format='%3N %4C %S %{%b %d} %-15.15F (%4c) %?M?%M
?%s' ;\
set display_filter='t-prot -acelmtS -Mmutt --spass'
However still no threading :(
I looked at the headers and you are correct - there is no In-Reply-To header.
However there are these two:
thread-index: AcqPygfdiA/1vWBTRGqs/6xP5Fmwtw==
Thread-Topic: Sysinternals Forums Topic Reply Notification : dxgkrnl.sys and
usbport.sys hardware interrupts
Is there any way in mutt to add a custom rule for threading ? e.g Thread msg's
based on the Thread-Topic: header ?
-Alex
IMPORTANT: This email remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT
1914. If you have received this email in error, you are requested to contact
the sender and delete the email.
Re: Problems with a2ps/enscript and printing in mutt
0n Tue, Jan 05, 2010 at 11:30:17PM -0500, Joseph Ishac wrote: I'm looking to adjust the way mutt prints. I had just been piping things to lpr, but I decided to try and get a little fancier. You may want to look at: Muttprint pretty-prints mail messages for any mail client which can output plain text with the mail headers included. It uses the typesetting system LaTeX, which is normally installed on a Unix/Linux system. WWW: http://muttprint.sourceforge.net/ -Alex IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: accent problem replying mails
0n Thu, Apr 02, 2009 at 12:21:53PM -0500, Kyle Wheeler wrote: in the .muttrc I have tried with different carset options: - set charset=iso-8859-1 - set charset=utf-8 - and with charset not defined. mmm ... i have set in my $HOME/.mutt/settings set charset=//TRANSLIT But i cant even remember what that means :( -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
[message scoring] Is it possible to ... ?
Hi all, I would like to score any thread that i have replied to i.e. the entire thread. Is this possible ? If yes, any pointers ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: Mutt crashing on exit or replying (sometimes)
0n Fri, Mar 06, 2009 at 03:44:45PM -0600, Kyle Wheeler wrote: On Friday, March 6 at 02:15 PM, quoth Joshua Tinnin: This may have nothing to do with your problem, but: setting the $charset variable manually is ALMOST NEVER a good idea! I've only ever seen *one* situation where it's even *useful*. I typically need more than just 7-bit text, however. So do I! But that means you have to establish an 8-bit environment, not just force your programs to spit out 8-bit characters and hope that everything makes good guesses about what's going on. I'm really not sure how to get it to use unicode without my specifying it. Is there something I'm missing? I wish the documentation had warned me. The *correct* way of informing programs like mutt (so that all of the system libraries they rely on behave properly) is to use environment variables, specifically LANG (and, if you need them, the LC_* variables as well). Step 1 of establishing a UTF-8 environment is getting a terminal program that supports it. Most of them do these days, but you need to run them with the right flags. For example, xterm supports UTF-8, but requires a bunch of flags to enable it, so they usually provide the `uxterm` script in order to launch xterm in UTF-8 mode. The rxvt terminal has a similar script (I think it's `urxvt`). Step 2 is making sure you have UTF-8 fonts. This all depends on your OS, and I don't know the specifics of doing it with FreeBSD (with luck, you already have them). Step 3 is exporting the right environment variables - you can read the `locale` man page for details. Personally, I set LANG to be en_US.UTF-8, but you have to use `locale -a` (or something similar) to find out what encodings are available on your machine. (en means english, US means american, and UTF-8 means the character set) For example, on my OSX box... $ locale -a | grep en_US en_US en_US.ISO8859-1 en_US.ISO8859-15 en_US.US-ASCII en_US.UTF-8 Often times, the uxterm/urxvt terminal scripts will set up your environment variables correctly for you, so you don't have to muck with them. However, many terminals do NOT set these things up for you (e.g. I don't believe gnome-terminal does, and I *know* Apple Terminal doesn't either). Chances are you want to add some logic to your ~/.bashrc (or equivalent for your shell) to set the LANG environment variable correctly for your machine. (There are lots of tricks to detecting the correct locale setting for your terminal, depending on the environment. For example, in an X11 environment, as long as you have a $WINDOWID environment variable, you can use the xprop program to find out what locale that window is using.) The tricky part of this is that in many cases the wrong settings can produce acceptable results *most* of the time. It IS, however, important to use environment variables. For example, mutt may use system library calls like isalpha(), which base their answers on what locale they think they're in. Usually, they default to US-ASCII, and since that's the basis for most character sets, it usually produces acceptable results. But when someone sends you a message that uses a character that isn't in US-ASCII, those functions can get it wrong UNLESS they and mutt are both aware of the right character set. It'd probably be more helpful if you ran mutt inside a debugger and gave us a backtrace. How do you do that? Again, I'm not a programmer. I'm running it compiled with debug flags and with the debug level set at 5. Usually, just load up mutt with the following command: gdb /usr/local/bin/mutt And then at the prompt, type run. When mutt crashes, it will return you to the prompt, at which point you can type backtrace. (To get out of it, type quit.) What version of libiconv do you use? There's some buggy ones out there (esp. on FreeBSD) that are known to cause crashes. You may just need to update your iconv library. Well, right now it's libiconv-1.11_1. I'll run an update and see if a newer version is available. Hmmm. 1.11 should be good. See about that backtrace; that'll give a much better idea of what's going on and where it's crashing. An insanely useful email! Thanks for sharing this with the community kyle! -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: How can I change the from header of my email?
0n Wed, Oct 01, 2008 at 09:56:24AM +0800, Kun Niu wrote: I'm trying to change the from email address of my mutt client. I've tried to change hostname which failed. And I alse tried change my_hdr which also failed. How can I change mutt to use the from email I want? Any hints will be appreciated and thanks in advance. my_hdr From: [EMAIL PROTECTED] -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: delete duplicated mails
0n Tue, Sep 23, 2008 at 08:19:27AM -0500, Kyle Wheeler wrote:
On Tuesday, September 23 at 02:20 PM, quoth Wilkinson, Alex:
mmm, i liked the idea of this folder-hook so i tried it out.
Is it meant to automagically delete duplicate threads ? If so
the following folder-hook did sweet-fa for me :(
sweet-fa? That's a new one to me...
folder-hook . \
set sort=reverse-threads ;\
set sort_aux=last-date-received ;\
set duplicate_threads=yes ;\
push 'collapse-all' ;\
push 'delete-pattern~=enter' ;\
set index_format='%3N %4C %Z %{%b %d} %-15.15F (%4c) %?M?%M
?%s' ;\
set display_filter='t-prot -acelmtS -Mmutt --spass'
Well, one problem I see is that delete-pattern only works on messages
you can *see*. After you collapse-all, the pattern won't match
anything that has been collapsed. So swap those two lines: delete
things before you collapse-all.
Will test. Thanks!
-aW
IMPORTANT: This email remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT
1914. If you have received this email in error, you are requested to contact
the sender and delete the email.
Re: short-keys
0n Wed, Jun 18, 2008 at 09:26:25PM -0700, Ravi Uday wrote: Does anyone has a comprehensive list of short cut keys while navigating/composing/deleting mails when using mutt 1.5.17 I mean I have so many similar apps(xterm/emac/vi/sendmail etc) opened and I kind of get confused with different keyboard key combo's. Maybe I can take a printout and stick it up the wall :) Responses appreciated in advance http://www.sys-concept.com/Mutt-Quick-Reference-A4.pdf -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Sorting messages by score AND keeping threading - is it possible ?
Hi all,
* I have mutt score every message that it reads.
* I then use the scores to sort my messages in order of importance (to me).
Problem: I loose my threading :(
Question: Is it possible to maintain the following threading whilst viewing
messages in sorted by score mode ?
folder-hook . \
set sort=reverse-threads ;\
set sort_aux=last-date-received ;\
set duplicate_threads=yes ;\
push 'collapse-all' ;\
set index_format='%3N %4C %Z %{%b %d} %-15.15F (%4c) %?M?%M ?%s'
;\
set display_filter='t-prot -acelmtS -Mmutt --spass'
-aW
IMPORTANT: This email remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT
1914. If you have received this email in error, you are requested to contact
the sender and delete the email.
Re: [Mutt 1.5.18] /usr/local/share/doc/mutt/manual.txt is XML!
0n Wed, May 28, 2008 at 10:11:08AM +0200, Rocco Rutte wrote: Did you compile mutt yourself? If yes, from what source (e.g. tarball or mercurial)? Do you have any of these installed: lynx, links, w3m? From FreeBSD ports [/usr/ports/mail/mutt-devel]. Yes, I have all 3 lynx, links, w3m. -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: set time_inc= ?
Pure gold kyle! Thanks stacks for such a detailed explanation. forgive my top-posting -aW 0n Tue, May 27, 2008 at 10:49:29PM -0500, Kyle Wheeler wrote: On Wednesday, May 28 at 09:56 AM, quoth Wilkinson, Alex: Ok so in the manual time_inc says: this variable controls the frequency with which progress updates are displayed. It suppresses updates less than ``time_inc'' milliseconds apart. This can improve throughput on systems with slow terminals, or when running mutt on a remote system. Ok so what is meant by progress updates ? Whenever mutt does something that can take a while (such as download a large message, open a very large mailbox, send a large message, etc.), it displays status information about that task at the bottom of the terminal. That status information is a progress update. I'm still trying to work out what time_inc gives me :( time_inc is a solution to a problem that some people have had. Here's how things used to work: Progress updates used to be on a once every N things basis (this is the $read_inc setting). For example, when opening a large mailbox, you could tell mutt to post a new progress update every 10 messages (ten is the default, but it could be any number). Thus, after parsing ten messages, mutt would change the message at the bottom of the terminal (update it) to tell you that another ten messages had been parsed. Now, generally speaking, mutt can read messages out of a mailbox pretty darn fast. Let's say, just for discussion purposes, that on you computer, mutt can read 1000 messages every second. With a $read_inc setting of 10, that means mutt will attempt to update the terminal's contents 100 times per second, or once every 1/100th of a second. That's pretty darn fast---you can't even read that fast---and some terminals just aren't that fast. If your terminal is slow and can't change it's display that quickly, you're spending a lot of time (comparatively speaking) updating your terminal and you aren't even getting anything useful out of it because the terminal can't display updates that quickly. It can even slow down how quickly mutt opens a mailbox, because mutt can't change the display until the previous display has finished. If your terminal has a reaction time of 1/25th of a second, that means updating the terminal 100 times takes 4 seconds! That's no good, because that forces mutt to take four times as long to open a 1000 message mailbox (which it could have opened in 1 second, if it didn't have to wait for the terminal). With me so far? Previously, to compensate, you would do something like increase the read_inc setting to, say, 100. Thus, mutt would attempt to update the terminal's contents only 10 times per second. That's still plenty fast, on your 1/25th second terminal, it only takes 0.4 seconds, which means mutt can easily meet its deadline of opening the 1000 message mailbox in 1 second. But now imagine that in addition to opening a local mailbox, which mutt can open quickly, you also want to open a remote IMAP mailbox, which mutt can only pull down much more slowly. Let's say, just for argument's sake, that mutt can only read 20 IMAP messages every second. If your $read_inc setting is 100, that means mutt has to read 100 messages before it tells you how far along it is, which means that in the IMAP situation, it'll only tell you what it's doing every five seconds. That's annoying! It's also very imprecise! You don't know if mutt is just chugging along, or if there's one really big message that's causing a problem, or quite what's going on. What you'd really like mutt to do is to tell you what it's up to every so often, so that you know it's still alive, but at a pace that doesn't slow down its operation. That's where $time_inc comes in. You can set $read_inc to something absurdly small, like 1, and then set $time_inc to something reasonable, like 250. That means that it'll update the terminal to tell you what it's up to 4 times per second, NO MATTER how quickly or slowly it's doing its job. That way you can ensure that mutt keeps you informed (even if the task is really slow) without slowing itself down (even if the task is really fast). Does that make sense? AFAICT with time_inc=10 included in my $HOME/.mutt/settings I see no change, yet I see people on this list raving about it ? What am I missing ? A $time_inc=10 setting is absurdly low. That's telling mutt that you need updates every 1/100th of a second. You can't read that fast, and your terminal can't update that fast. The real joy of $time_inc is that you can make your increments (read_inc
[Mutt 1.5.18] /usr/local/share/doc/mutt/manual.txt is XML!
Erm, was this intended: #file /usr/local/share/doc/mutt/manual.txt /usr/local/share/doc/mutt/manual.txt: XML #head -3 !$ head -3 /usr/local/share/doc/mutt/manual.txt ?xml version=1.0? !DOCTYPE html PUBLIC //W3C//DTD XHTML 1.0 Transitional//EN ttp://www.w3.org/ TR/xhtml1/DTD/xhtml1-transitional.dtd I want my plain TXT manual back :( -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
set time_inc= ?
Ok so in the manual time_inc says: this variable controls the frequency with which progress updates are displayed. It suppresses updates less than ``time_inc'' milliseconds apart. This can improve throughput on systems with slow terminals, or when running mutt on a remote system. Ok so what is meant by progress updates ? I'm still trying to work out what time_inc gives me :( AFAICT with time_inc=10 included in my $HOME/.mutt/settings I see no change, yet I see people on this list raving about it ? What am I missing ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: sending email - mutt waiting for long periods of time on Sending
0n Wed, May 21, 2008 at 03:30:42AM -0500, Kyle Wheeler wrote: Well, to *debug* it is easy, just use mutt's debugging mode, and have `tail -F ~/.muttdebug0` running in another terminal. Generally, though, that's probably an issue with your sendmail, and you can just ignore it by setting $sendmail_wait to be something small, like 2 (it'll complete in the background and you won't have to be bothered by it). Thanks Kyle. I just added $sendmail_wait=1. -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: extract_url.pl - version 1.3
0n Tue, May 20, 2008 at 07:14:21PM -0500, Kyle Wheeler wrote: The original reason for this script was because urlview doesn't correctly handle format=flowed email or any other email encodings, so URLs are often mishandled or simply broken. This script handles all known encodings *correctly* (when fed the raw email). It can be used either as a standalone script (which requires the Curses::UI perl module) or as a pre-filter for urlview. Ahh, now this is what i like to hear. I have a few questions: 1. What is meant by format=flowed email ? 2. What are the known encodings ? I often have broken links in the body of my emails and I don't know why e.g. The link is meant to look like: http://odinr.dcb.defence.gov.au/uhtbin/cgisirsi/MhOktEUDHs/DSTOE/242330010/60/54/X But I will always see it like this in mutt: http://odinr.dcb.defence.gov.au/uhtbin/cgisirsi/MhOktEUDHs/DSTOE/2423300 10/60/54/X When I look at the raw spool file (independent of mutt) I see: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 3.2//EN HTML HEAD META HTTP-EQUIV=3DContent-Type CONTENT=3Dtext/html; = charset=3Dus-ascii META NAME=3DGenerator CONTENT=3DMS Exchange Server version = 6.5.7652.24 TITLELink to catalogue/TITLE /HEAD BODY !-- Converted from text/rtf format -- BR PA = HREF=3Dhttp://odinr.dcb.defence.gov.au/uhtbin/cgisirsi/MhOktEUDHs/DSTOE/= 242330010/60/54/XUFONT COLOR=3D#FF SIZE=3D2 = FACE=3DArialhttp://odinr.dcb.defence.gov.au/uhtbin/cgisirsi/MhOktEUDHs= /DSTOE/242330010/60/54/X/FONT/U/A /P Would your script deal with this annoying problem (which I still don't understand). If it would ... I am going to use it permanently :) -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
sending email - mutt waiting for long periods of time on Sending message...
Hi all, When sending messages in mutt (Mutt 1.5.17 (2007-11-01), mutt seems to spend anywhere between 8 and 30 seconds trying to send the message. All i see is Sending message... And then 20 seconds latter it sends and returns me to my INBOX. This is on an adhoc basis ... maybe 1 out of every 5 messages. How does one go about debugging why this is happening ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: tagurl.pl
0n Mon, May 19, 2008 at 08:29:16PM -0500, Kyle Wheeler wrote: Make sense? Yeah for sure. But life is already simple with: macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' And #grep -i firefox /usr/local/bin/url_handler.sh https_prgs=/usr/local/bin/firefox-remote:XW /usr/local/bin/lynx:XT /usr/local/bin/w3m:XT http_prgs=/usr/local/bin/firefox-remote:XW /usr/local/bin/lynx:XT /usr/local/bin/w3m:XT /usr/local/bin/links:XT And /usr/ports/www/firefox-remote/pkg-descr reads: Wrapper script for firefox web browser to add the open-in-new-tab functionality missing in the original startup script. Im not sure what your solution really gives extra than what is already achived via the aforementioned ? (im probably missing something obvious :)) -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: tagurl.pl
0n Mon, May 19, 2008 at 03:45:12PM -0500, Kyle Wheeler wrote: I put up a webpage for my tagurl.pl script: http://www.memoryhole.net/~kyle/tagurl/ After having a quick read of the page I still dont really get what this script does :( -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: sendmail_wait for smtp ?
0n Sat, May 17, 2008 at 12:01:38PM -0500, Kyle Wheeler wrote: Yes and no. Mutt is not multithreaded, so you can't have it handle the SMTP connection in the background, so, NO. But if you really want it backgrounded, why not use a simple SMTP sender (like msmtp or nullmailer or something similar) instead of have mutt do it? That way you *can* background email sending. Is msmtp completely independent of a local MTA ? i.e. I would no longer need to use my local sendmail for smart-relay anymore ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: New mail - 'un-collapses' thread ... Can I stop this ?
0n Tue, Apr 29, 2008 at 06:04:28PM +0200, Rado S wrote: =- Wilkinson, Alex wrote on Tue 29.Apr'08 at 9:01:45 +0800 -= Is it possible to stop threads un-collaping as new mail arrives ? Yes, check vars with collapse in them. Ok, filtering on the word collapse in the manual all I come up with is: 3.28. collapse_unread 3.29. uncollapse_jump 3.45. digest_collapse And none of these control what the desired behaviour. Can you enlighten me with what you where thinking ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
New mail - 'un-collapses' thread ... Can I stop this ?
Hi all,
I have the following folder-hook:
folder-hook . \
set sort=reverse-threads ;\
set sort_aux=last-date-received ;\
push 'collapse-all' ;\
set index_format='%3N %4C %Z %{%b %d} %-15.15F (%4c) %?M?%M
?%s' ;\
set display_filter='t-prot -acelmtS -Mmutt --spass'
As well as this I have the following defined:
set collapse_unread=yes
My problem:
My INBOX will be open all day within a terminal as per usual and as soon as a
new message for a particular thread arrives the thread un-collapses.
Is it possible to stop threads un-collaping as new mail arrives ?
-aW
IMPORTANT: This email remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT
1914. If you have received this email in error, you are requested to contact
the sender and delete the email.
Re: push 'collapse-all' - Question ...
0n Wed, Jan 30, 2008 at 09:33:16AM -0600, Kyle Wheeler wrote:
To expand on what Michael said, this would work:
folder-hook . \
set sort=reverse-threads ;\
set sort_aux=last-date-received ;\
push 'collapse-all' ;\
set index_format='%3N %4C %Z %{%b %d} %-15.15F (%4c) %?M?%M
?%s' ;\
set display_filter='t-prot -acelmtS -Mmutt --spass'
Note the double-quote at the beginning and end of the hook (and that I
replaced your index_format double-quotes with single-quotes).
Yes, yes! This works perfectly now. Thanks once again master kyle :)
One quick question to wrap it up. Why does index_format need single quotes ?
-aW
IMPORTANT: This email remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT
1914. If you have received this email in error, you are requested to contact
the sender and delete the email.
[NCLASSIFIED]push 'collapse-all' - Question ...
Hi all,
I have the following default folder-hook:
folder-hook . \
set sort=reverse-threads ;\
set sort_aux=last-date-received ;\
push 'collapse-all' ;\
set index_format=%3N %4C %Z %{%b %d} %-15.15F (%4c) %?M?%M ?%s ;\
set display_filter='t-prot -acelmtS -Mmutt --spass'
When I first exec mutt(1) all threads are collapsed (intended behaviour).
However, if I 'c' +another_folder and then 'c' ! (back to my INBOX) all threads
will be _always_ expanded (not intended behaviour).
So, how can I make push 'collapse-all' persist regardless of whether or not
what folder(s) I change into and how many times I change into them ? I just want
all my threads to be collapsed at all times unless I explicitly expand them.
Any hot tips would be much appreciated!
-aW
IMPORTANT: This email remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT
1914. If you have received this email in error, you are requested to contact
the sender and delete the email.
Re: Which spam filter do you use?
0n Fri, Oct 05, 2007 at 08:06:55AM +0200, M. Fioretti wrote: On Fri, Oct 05, 2007 00:23:06 AM +0200, Eyolf Østrem ([EMAIL PROTECTED]) wrote: So, should I switch? I'm quite happy with bogo, especially with the current setup with some macros I borrowed from an article in linux journal (I think it was), but I would very much like to hear what your experiences are in this respect. Besides some MTA-level filtering, I am using bogo instead of spamassassin because of one simple reason: lack of maintenance. Have you got any documents describing the process of integrating bogofilter with mutt ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: viewing pdf jpgeg etc attachment
0n Thu, Sep 27, 2007 at 01:33:53PM -0600, Joseph wrote: Somebody from Gentoo mailing list gave me a hint on how to generate/edit mailcap file. There is a file called globs on Gentoo in /usr/share/mime/globs Just trimming this file and adding your favorite editor will do the trick. You can also get a prewritten mailcap file by installing MetaMail: [http//ftp.funet.fi/pub/unix/mail/metamail/] -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: Problem printing doc-attachments
0n Tue, Sep 18, 2007 at 12:43:42AM -0700, Gary Johnson wrote: I need the mutt_rem_bgrun command because I run mutt on a Solaris machine and run viewers for MS attachments remotely on the Linux box. In your case, this might work: Where does one find details on mutt_rem_bgrun ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: SEC:UOutlook 2003 splits URLs over multiple lines when viewed in
0n Fri, Sep 07, 2007 at 03:21:43PM +0800, Wilkinson, Alex wrote: Hi all, Something that has bugged me for a long time is that when people send me URLs from Outlook-2003, mutt sees the URL split over 2 lines e.g. http://www.mathworks.com/support/sysreq/current_release/?parenttopic=Sys tem%20Compatibility If I send the same URL from mutt to myself I get the URL on a single line as such: http://www.mathworks.com/support/sysreq/current_release/?parenttopic=System%20Compatibility In the raw Maildir spool file the URL is split also e.g. http://www.mathworks.com/support/sysreq/current_release/?parenttopic=3DSy= s tem%20Compatibility So it looks like the URL gets split over a series of lines in transit. Does anyone know why ? And how to make this stop happening ? Ok, so I have investigated more. I have sent the URL from both mutt and outlook-2003 and then I have proceeded to connect to the POP service on the Exchange server to view the messaage _before_ fetchmail fetches it. The results: Email sent from mutt -~-~-~-~-~-~-~-~-~-~ A single pristine URL: [http://www.mathworks.com/support/sysreq/current_release/?parenttopic=System%20Compatibility] This is how it should be. Email sent from Outlook-2003 -~-~-~-~-~-~-~-~-~-~-~-~-~-~ So this proves that outlook marks it up in HTML and does some seriosuly weird stuff to the email when it gets sent. How the hell does an MTA such as mutt deal with the below crap ? This is a multi-part message in MIME format. --_=_NextPart_001_01C7F124.1170E94F Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable http://www.mathworks.com/support/sysreq/current_release/?parenttopic=3DSy= s tem%20Compatibility --_=_NextPart_001_01C7F124.1170E94F Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 3.2//EN HTML HEAD META HTTP-EQUIV=3DContent-Type CONTENT=3Dtext/html; = charset=3Dus-ascii META NAME=3DGenerator CONTENT=3DMS Exchange Server version = 6.5.7652.24 TITLEURL from Outlook .../TITLE /HEAD BODY !-- Converted from text/rtf format -- BR PA = HREF=3Dhttp://www.mathworks.com/support/sysreq/current_release/?parentto= pic=3DSystem%20CompatibilityUFONT COLOR=3D#FF SIZE=3D2 = FACE=3DCourier = Newhttp://www.mathworks.com/support/sysreq/current_release/?parenttopic= =3DSystem%20Compatibility/FONT/U/A /P /BODY /HTML --_=_NextPart_001_01C7F124.1170E94F-- -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Outlook 2003 splits URLs over multiple lines when viewed in mutt ... why ?
Hi all, Something that has bugged me for a long time is that when people send me URLs from Outlook-2003, mutt sees the URL split over 2 lines e.g. http://www.mathworks.com/support/sysreq/current_release/?parenttopic=Sys tem%20Compatibility If I send the same URL from mutt to myself I get the URL on a single line as such: http://www.mathworks.com/support/sysreq/current_release/?parenttopic=System%20Compatibility In the raw Maildir spool file the URL is split also e.g. http://www.mathworks.com/support/sysreq/current_release/?parenttopic=3DSy= s tem%20Compatibility So it looks like the URL gets split over a series of lines in transit. Does anyone know why ? And how to make this stop happening ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
mutt+vim+putty ... long delay in opening vim(1) ?
Hi all, I use vim as $editor with Mutt 1.5.16. When I use vim with eterm(1) on FreeBSD CURRENT it opens instantaneously, however, occasionally I use Putty on Windows and ssh(1) into FreeBSD and vim literally takes 20 seconds to open. $TERM is set to xterm. Can anyone recommend what could be wrong ($TERM??) and or how to debug this ? Cheers -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: mutt+vim+putty ... long delay in opening vim(1) ?
0n Thu, Jul 05, 2007 at 10:00:12PM -0600, Vincent Beffara wrote: Try adding the following line to your .muttrc (or replacing the ppropriate line): set editor=vim -X Long version: vim by default (or not) tries to connect to the X server to enable client/server behavior. Through putty there is no X server, so that fails - after a timeout (X11 is network-oriented, one needs to wait for network lag). I am guessing that the timeout on your system is set to 20 seconds ... You are *exactly* right ! vim -X opens vim instantaneously now! Thanks! -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Waiting for flock attempt ... ?
Hi all, Mutt 1.5.15 (2007-04-06) System: FreeBSD 7.0-CURRENT (i386) These days when I open mutt I am seeing the following printed: Waiting for flock attempt ... And a count-down e.g. Waiting for flock attempt ... count-down of seconds After the count-down period (about 5 seconds) I do eventually get my INBOX. I have no clue what this is. I assume flock is file lock ? INBOX is coming from a Maildir via IMAP using Dovecot. Any clues people ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: Send replies to ISP smtp server
0n Tue, Jun 12, 2007 at 06:57:30PM -0700, Brendan Cully wrote: On Wednesday, 13 June 2007 at 01:54, [EMAIL PROTECTED] wrote: I need to set up mutt to send replies through the smtp server of my ISP. Can I do this in .muttrc or do I need to modify the mutt source code? Thanks, Dave Feustel set smtp_url=smtp://my.isp.server/ Cool, so this means I no longer have to use sendmail ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: Best way to handle DOS newlines
0n Tue, Jun 05, 2007 at 12:34:52AM +0200, Alain Bench wrote: Hello Michelle, On Saturday, May 26, 2007 at 15:06:43 +0200, Michelle Konzack wrote: But it seems, your MTA/MUA has eaten the backslashrbackslashn It should be [...] \r\n Alex has no problem. The thing eating certain characters is on your incoming path, Michelle. True, true. -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: Best way to handle DOS newlines
0n Sat, May 12, 2007 at 12:54:20PM +0200, Michelle Konzack wrote: # FLT_dos_coded :0 fw * ^1^ \r\n * ? which dos2unix /dev/null 21 |/usr/bin/dos2unix Michelle, Can you please interpret the following line in English for me: * ^1^ \r\n Cheers -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: Charset issue?
0n Sun, May 13, 2007 at 05:30:03PM +0200, Alain Bench wrote: ...an heresy. Modern PuTTY supports 256 colors, the best setting is TERM=putty-256color. More precisely, set this value to the terminal type string in PuTTY config, so it gets auto-exported. You'll also need there to set translation to UTF-8, to match your locale's charset. I tried this connecting to FreeBSD -CURRENT and see the following errors: tcsh: Cannot open /etc/termcap. tcsh: using dumb terminal settings. #grep -i putty-256 /etc/termcap Outputs nothing. Is this termcap entry only available OOTB on Linux ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
no visible messages ... mutt hung ...
Hi all, On an adhoc basis mutt will hang and not let me browse my INBOX telling me No visable messages. A screenshot so you know what I am talking about: http://users.on.net/~lex/mutt_error.png I am using Maildirs with the following: Mutt 1.5.15 (2007-04-06) dovecot-1.0.r28_1 FreeBSD 7.0-CURRENT #2: Wed May 2 09:28:13 WST 2007 Any hot tips to debug this ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: Folder Format for my setup
0n Thu, May 10, 2007 at 05:03:38PM -0600, Kyle Wheeler wrote: On Thursday, May 10 at 07:48 PM, quoth Cleverson: Thank you very much for all of infos. I have yet another question: Whatever format I choose, is it easy to convert the folders to the other one in case I want to give it a try? http://batleth.sapienti-sat.org/projects/mb2md/ http://sageshome.net/oss/mbox2mdir.php -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: Extract URL's from message
0n Wed, May 09, 2007 at 07:38:39PM -0400, Trey Sizemore wrote: I remember a while back I had a setup with mutt that allowed me to extract all URL's from a message and display them (numbered) in a separate window. I could then choose a URL to open by selecting its number and it would open in my browser of choice. I've been googling to find the proper 'recipe' for my .muttrc. Anyone have what I'm talking about? urlview is a screen oriented program for extracting URLs from text files and displaying a menu from which you may launch a command to view a specific item. urlview uses a regular expression to extract URLs from the specified text files. $HOME/.mutt/keybindings macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
[t-prot] display_filter not getting exec()'d ...
Hi all, I am *really* wanting to use t-prot [http://www.escape.de/~tolot/mutt/]. However, addng the following to my mutt config seems have no effect what so ever on any messages. set display_filter='t-prot -acelmtS -Mmutt --spass' Can someone please assist me with confirming whether mutt is actually executing t-prot. Chers -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: [t-prot] display_filter not getting exec()'d ...
0n Sun, May 06, 2007 at 02:34:42PM +0200, M. Fioretti wrote: Very likely, it is a path problem. Instead of just t-prot, try to use: set display_filter='/the/complete/path/where/you/placed/t-prot... etc set display_filter='/usr/local/bin/t-prot -acelmtS -Mmutt --spass' Still does nothing :( And by the way the version is: Mutt 1.5.14 (2007-02-12) I'm not sure if this is the best way to test from the CLI, but as you can see t-prot doesn't seem to alter the message at all. This was a fake message a created for testing: #cat /var/tmp/test.txt | /usr/local/bin/t-prot -acelmtS -Mmutt --spass Date: Fri, 4 May 2007 13:20:07 +0800 From: Wilkinson, Alex [EMAIL PROTECTED] To: Wilkinson, Alex [EMAIL PROTECTED] Subject: Re: FW: Gotta love this girl GOLD ! -aW 0n Fri, May 04, 2007 at 01:14:35PM +0800, Leibhardt, Bruce wrote: For all Who Work With Rude Customers. An award should go to the Virgin Airlines gate attendant in Sydney some months ago for being smart and funny, while making her point, when confronted with a passenger who probably deserved to fly as cargo. A crowded Virgin flight was cancelled after Virgin's 767s had been withdrawn from service. A single attendant was re-booking a long line of inconvenienced travellers Suddenly an angry passenger pushed his way to the desk. He slapped his ticket down on the counter and said, I HAVE to be on this flight and it HAS to be FIRST CLASS. IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to [EMAIL PROTECTED] Can I run mutt in 'debugging mode' somehow to see what it is actually doing ? -aW
Re: [t-prot] display_filter not getting exec()'d ...
0n Sun, May 06, 2007 at 08:38:43AM -0600, Kyle Wheeler wrote: On Sunday, May 6 at 08:44 PM, quoth Wilkinson, Alex: I'm not sure if this is the best way to test from the CLI, It is. but as you can see t-prot doesn't seem to alter the message at all. Aha! Well, there you have it; not a mutt config problem, but a t-prot config problem. This was a fake message a created for testing: #cat /var/tmp/test.txt | /usr/local/bin/t-prot -acelmtS -Mmutt --spass I use t-prot like this: t-prot -cemtwk -M=mutt Things I observe about how you're using t-prot: - You're using -a, but you're not using -A, which t-prot requires (see its documentation) - You're using -l, but you're not using -L, which t-prot requires (see its documentation) Yup, you're right. t-prot is actually doing something. I have changed my t-prot settings to: set display_filter='/usr/local/bin/t-prot -cemtwkS -M=mutt --spass And all is now good. -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
alias question ...
Hi all, If I have an email address in the body of an email such as: [EMAIL PROTECTED] Is there a magic function that can add this email address to my $alias_file ? I am only aware of being able to add aliases' from the From: header. -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Re: alias question ...
0n Mon, Apr 30, 2007 at 05:20:48PM +1200, Roland Hill wrote: On Mon, 30 Apr 2007 or thereabouts, Wilkinson, Alex came forth with: If I have an email address in the body of an email such as: [EMAIL PROTECTED] Is there a magic function that can add this email address to my $alias_file ? I am only aware of being able to add aliases' from the From: header. Hi, I use mail2muttalias.py for this. It is available here: http://pyropus.ca/software/mail2muttalias/ It is call from a macro such as: macro index A |'mail2muttalias.py ~/.mutt/aliases'\n \ Create new alias from the actual message Hope this helps. This helps a tone. I tested and it works perfectly fine ! Cheers -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Trying to explain mutt+ssl to myself :(
Hi all, I have recently migrated my mail from courier-imap to dovecot. In doing so, I finally configured mutt to connect to imaps (SSL). In the end I got it all working. I then sat back and thought: I kinda don't understand the SSL/TLS part even though it works. And I hate setting stuff up and not truely understanding the mechanics of it. So I started to write about it and am stuck. Can those that _understand_ mutt+ssl have a read of what I wrote to myself and give me your $00.02 worth (corrections etc). Trying to explain mutt+ssl and getting it all wrong --- * mutt(with openssl support built in) initiates with a SSL-Client-Hello to SSL on port 993 i.e. mutt's capabilities (algorithms, SSL version etc). * dovecot:993 compares mutt's CipherSuites with its own. Of the CipherSuites mutt and dovecot have in common, dovecot:993 chooses the _most_ secure algorithm. * Dovecot:993 will then tell mutt what it has decided to use and assigns a Unique session ID. From now on all communication is via this ID. * Now that the CipherSuite is set between mutt and dovecot, dovecot sends its SSL certificate to mutt [/usr/local/share/dovecot/certs/dovecot.pem]. mutt then uses dovecot's corresponding public key [/usr/local/share/dovecot/private/dovecot.pem] to verify that the ceritificate is authentic. * once mutt has verified that the certificate is authentic ... and here I got unstuck. Cheers -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
