Re: Change in mutt behavior?
On 2001-02-20 22:47:11 -0600, Lance Simmons wrote: Am I losing my memory, or was this a recent change to Mutt? If so, is there some way I can change it back? Just wait for the next version. This has been fixed in the CVS. -- Thomas Roessler [EMAIL PROTECTED] This message may have been certified to be possibly virus-free.
Re: sending postponed messages
On Tue, Feb 20, 2001 at 12:54:21PM -0800, [EMAIL PROTECTED] wrote:
On Tue, Feb 20, 2001 at 08:11:22AM +0100, Pacholleck wrote:
I cannot afford long online times waiting that some sendmail
deceides to try delivery again or recalling every of all those
postponed in vi again.
If you're offline when you send messages (not postpone them),
sendmail should queue the messages. When you're online again, "sendmail -q"
should flush the queue, i.e., send all the messages in the queue.
Have a look at:
http://lists.suse.com/archives/suse-linux-e/2000-Jun/2112.html
http://cork.linux.ie/projects/install-sendmail/
I'd like to add another Sendmail tip:
So that Sendmail doesn't take long to return to Mutt when it runs
while sending a message, you might also consider using its -odd
option.
"-o" some configuration [o]ption
"d" the [d]elivery mode option
"d" delivery mode "[d]eferred", which is like queued, but also skips
initial DNS lookups.
This is what I do. In fact, my sendmail Mutt variable is set to a
shell script which looks through the numeric ("-n") output of
netstat(1) for the default ("0.0.0.0") route. Since I generally use
the "defaultroute" option to pppd(8), when I'm online, a default route
will be present, but will be absent while offline:
#!/bin/bash
sendm='/usr/sbin/sendmail -oem -oi'
if netstat -nr | grep '^0\.0\.0\.0' /dev/null 21
then # there is a default route; we're on the Internet
: # so do nothing extra
else # we aren't, so use the Sendmail defer option
sendm="$sendm -odd"
fi
exec $sendm "$@"
I hope you Mutt w/ Sendmail users like this :-)
--
Oo---o, Oo---o, O-weem-oh-wum-ooo-ayyy
In the jungle, the silicon jungle, the process sleeps tonight.
Joe Philipps [EMAIL PROTECTED], http://www.philippsfamily.org/Joe/
public PGP/GPG key 0xFA029353 available via http://www.keyserver.net
PGP signature
RFC: Maildir tmp clean patch
Hi,
I've put together a simple patch following mutt coding
style to implement older than 36 hours files' tmp cleaning.
Before the discussion arises, mutt should comply to the
maildir specification. It does not matter if your local installation
does not seem to mind the non-compliance. It is a simple requirement
and an easy one to implement. Why not comply, then?
I am proposing my patch but any other that does the trick
is fine by me. :)
Input and suggestions welcome. The patch applies against
mutt 1.2.5. It can be found at
http://people.freebsd.org/~lioux/mutt_maildir_tmp_clean-1.2.5-2001022100.tar.bz2
MD5 (mutt_maildir_tmp_clean-1.2.5-2001022100.tar.bz2) =
2c55edc5600f99cce077fb7ea712788a
or
http://people.freebsd.org/~lioux/mutt_maildir_tmp_clean-1.2.5-2001022100.tar.gz
MD5 (mutt_maildir_tmp_clean-1.2.5-2001022100.tar.gz) = 7b15031d918e09de35f1e13cc71c3ea5
The informative README.TXT packaged inside the tar follows
at the end of this email. There is also a TODO file, if you want
to contribute code to do any of those, please do.
A side issue. I packaged the main code files with a BSD
style license, if that is illegal, I'll gladly remove it. However,
before anyone says it is illegal, please check the files in question:
maildir_clean_dir.[ch]. They are files separate from the main mutt
distribution. Bear in mind that I am not a license expert.
I apologize for any trouble.
Thanks,
ps: I am not subscribed to this list, so please CC: me
when you reply.
--
Mario S F Ferreira - UnB - Brazil - "I guess this is a signature."
lioux at ( freebsd dot org | linf dot unb dot br )
flames to beloved [EMAIL PROTECTED]
--
# $Header: /home/lioux/cvsroot/mutt/maildir-patch/1.2.5/README.TXT,v 1.5 2001/02/21
06:23:47 lioux Exp $
Mutt 1.2.5 does not implement the complete maildir specification.
It ignores details regarding the handling of maildir tmp directories.
[begin of quote from maildir specification]
The reader is also expected to look through the tmp directory
and to clean up any old files found there. A file in tmp
may be safely removed if it has not been accessed in 36
hours.
[end of quote]
1) What the patch does?
o Implements thist last item of the specification which has
been left out of mutt maildir handling implementation
2) How? How the patch does it?
o Checks the tmp directory and stores the time stamp of the oldest
message below the 36 hours old watermark.
o If there are no messages, stores zero as the time stamp.
o Erases any messages older than 36 hours. This time watermark can
be selected within one minute precision through a configure file
option. If the watermark value is either equal or below zero, the
maildir specification value will be used instead.
o DEFAULTS:
- patch disabled
- time watermark: 36 hours = 36 * 60 minutes
o These are the muttrc options:
set maildir_tmp_clean=yes
set maildir_tmp_clean_interval=desire_time_watermark_in_minutes
o At each mh_check_mailbox cycle, this code does
if (difftime(rightnow,oldest_message)watermark)
checks_directory_for_over_watermark_files;
checks_directory_for_over_watermark_files() {
remove_any_files_over_watermark;
}
3) How do I install it?
o Copy both maildir_clean_dir.c and maildir_clean_dir.h to mutt
directory
o Apply each of the following patches:
- patch-Makefile.am
- patch-Makefile.in
- patch-globals.h
- patch-init.h
- patch-mh.c
- patch-mutt.h
o configure and build the port as usual
4) How do I test it?
o Just add a file to any tmp maildir directory. Then, use
an utility such as "touch" to set a date older than 36
hours (or, whatever the watermark is set).
o Open this maildir folder.
o Check to see if the file has been erased.
---
# $Header: /home/lioux/cvsroot/mutt/maildir-patch/1.2.5/TODO,v 1.2 2001/02/21 07:01:15
lioux Exp $
1) Consider what to do when a message date is in the future. Perhaps,
nothing.
2) Make it faster, perhaps replace all function variable copies
with relative references
3) Do the polling also when -Z is defined.
sorting and display options for list subscribers
Is it possible to sort by and/or display in the index the string in
the recipient list which is matched by the 'subscribe' command?
It is nice to be able to separate mail received from lists from those
which are individually sent to me. This is taken care of nicely with
the 'subscribe' command which causes the index to display the first
recipient of the mail preceded by a To or Cc rather than the sender
which is the default given "%Z %{%b %d} %-15.15L (%-10.10a) %s" as my
current display formatting. But often, this first recipient is not the
list to which I am subscribed because the mail has been sent to many
lists. If mutt, when it matches the recipient list to one of my
'subscribe' command arguments, could hold on to that match and display
it, that would be perfect.
Please let me know if this is already implemented and I don't know how
to enable it or if it is currently on the list for future
implementation.
Cheers,
John
--
--
John J. Niekrasz
2nd Floor, Flat 1
37 South Clerk Street
EDINBURGH work: (+44 131) 651 1769
EH8 9NZ home: (+44 131) 662 9465
United Kingdomfacs: (+44 131) 650 4587
--
Signature cut
Hi, With mutt I am using several accounts and signatures. What annoyes me a bit is, although my signatures aren't so long, they'll be saved on harddisk in every outgoing mail. I am looking for a simple solution to cut them after sending automatically. As far as I know there's no configuration variable for this built in mutt. Does anyone have an advice or even a script to solve this problem ? And: does anyone use abook with mutt ? I find it useful, but I don't know how to make queries for Cc and how to include several receipients. Best regards $ean = -- Please don't send e-mails to this account. __ Do You Yahoo!? Gesendet von Yahoo! Mail - http://mail.yahoo.de
Re: Making directories along the way.
You can use the "!" shortcut to create one before you save the message. If it is once created, one can use tab completion for ease use. Ciao, Andreas On Tue, Feb 20, 2001 at 11:50:16AM +0100, Scott A. McIntyre wrote: Hi, Is it possible to have mutt make directories at the same time it makes mailboxes? That is, if I want to save to =lists/interesting/mutt but the directory "interesting" doesn't exist, mutt will currently not save messages and whine about their being no such file or directory...I can't find an obvious way to force it to do it anyway. Thanks. -- Andreas Grytz | http://www.linux-user.de Stefan-George-Ring 24 | Tel: +49 (0) 89 993411-0 D-81929 Mnchen | Fax: +49 (0) 89 993411-99
Re: Change in mutt behavior?
* On Tue Feb 20 2001, Lance Simmons screamed: - There's been a change in the past few days in how Mutt - behaves--for me at least. I upgraded to 1.3 recently, and I - don't remember changing my .muttrc recently. - - Old behavior: when I'm in index, press "c" to change mailboxes, - and press "?" for list, I get a list of my ~/Mail directories - and files. - - New behavior: when I do the same thing, I get a list of my 6 - declared mailboxes, but _not_ a list of my other ~/Mail - directories and folders. - - Am I losing my memory, or was this a recent change to Mutt? If - so, is there some way I can change it back? - - Lance Simmons I have a similar problem...although for me it's the other way around. I only want to see the declared mailboxes. Is there a ./configure option or some line I need to add to my .muttrc? --- Nelson D. Guerrero| E-Mail: [EMAIL PROTECTED] Platinom.NET Dominicana | Phone: (809) 567-4600 Dialup / Web Hosting / E-Commerce |WWW: http://www.platinom.net/
color on Solaris 2.6
hi, Here is how I get mutt work on solaris: . compile it with spool pointed to user's directory (nothing special option about term with ./configure . compile xterm (http://www.clark.net/pub/dickey/xterm/) . download xterm-color terminfo (from mutt FAQ) and setenv TERM xterm-color problem . the color defined in muttrc is not shown correctly in mutt (you say this color, it gives you other) . BTW, the color in VIM is totally right. I think it is a problem about xterm or locale or related. Some one please shed some light on this so that I can experiment it more. thanks, jack
Re: color on Solaris 2.6
On Wed, 21 Feb 2001, Jack wrote: hi, Here is how I get mutt work on solaris: . compile it with spool pointed to user's directory (nothing special option about term with ./configure . compile xterm (http://www.clark.net/pub/dickey/xterm/) . download xterm-color terminfo (from mutt FAQ) and setenv TERM xterm-color xterm-free86 is correct... problem . the color defined in muttrc is not shown correctly in mutt (you say this color, it gives you other) are you talking about red/blue interchange? that's from an application using (terminfo) setf/setb where setaf/setab are appropriate. . BTW, the color in VIM is totally right. vim has tables that it consults (does not always use termcap/terminfo) I think it is a problem about xterm or locale or related. Some one please shed some light on this so that I can experiment it more. thanks, jack -- T.E.Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: Press any key to continue ...
Jeroen Valcke muttered: Mutt has this habit of always asking me to press a key to continue, for recently after an update mutt even asks me to press when I start it up. So how do I remove this behaviour, Most likely you updated from a rather old version. There were some changes to the muttrc options. Mutt finds an "error" in the config file and asks you press a key to confirm. See README.UPGRADE for further reference. HTH, Michael -- "Absolutely nothing should be concluded from these figures except that no conclusion can be drawn from them." (By Joseph L. Brothers, Linux/PowerPC Project) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
decrypt-pipe function
Hi, all -- Is there a decrypt-pipe function anywhere, perhaps in 1.3? I do not see one in my 1.2.5 version. If there isn't, I'd like to see one... I sometimes get attachments in encrypted email and have to decrypt-copy them to the mailbox before I can pipe them out to my handling script, when a decrypt-pipe function would handle it all for me... TIA HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! PGP signature
No Subject
Can mutt be configured to work over a firewall with a proxy server. thanks, craig
Re: Press any key to continue ...
Set this in your .muttrc so mutt won't prompt for a key after executing something in a shell: set wait_key=no Zach Jeroen Valcke said: Hello all, Mutt has this habit of always asking me to press a key to continue, for example when I want to view an attachment or an url (with urlview) recently after an update mutt even asks me to press when I start it up. So how do I remove this behaviour, So that I never see this phrase "Press any key to continue..." again. Searched the docs, but didn't find anything, somebody an idea??? Thankx -- Jeroen Valcke [EMAIL PROTECTED] ICQ# 30116911 Home page: http://www.valcke.com/jeroen Phone +32(0)56 32 91 37 Mobile +32(0)486 88 21 26 "Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come." -Matt Groening-
RFC: maildir tmp clean patch
Hi,
version:1.2.5
menu: n.a.
command:n.a.
new config options: set maildir_tmp_clean
set maildir_tmp_clean_interval
bug that it fixes: non-compliance to maildir specification
I've put together a simple patch following mutt coding
style to implement older than 36 hours files' tmp cleaning.
djb's maildir specification clearly states:
[begin of quote from maildir specification]
The reader is also expected to look through the tmp directory
and to clean up any old files found there. A file in tmp
may be safely removed if it has not been accessed in 36
hours.
[end of quote]
Before the discussion arises, mutt should comply to the
maildir specification. It does not matter if some local installation
does not seem to mind the non-compliance. It is a simple requirement
and an easy one to implement. Why not comply, then? Do not flame
me, I am just stating an opinion.
I am proposing my patch but any other that does the trick
is fine by me. :) I just would like to see this implemented.
Input and suggestions welcome. The patch applies against
mutt 1.2.5. It can be found at
http://people.freebsd.org/~lioux/mutt_maildir_tmp_clean-1.2.5-2001022100.tar.bz2
MD5 (mutt_maildir_tmp_clean-1.2.5-2001022100.tar.bz2) =
2c55edc5600f99cce077fb7ea712788a
or
http://people.freebsd.org/~lioux/mutt_maildir_tmp_clean-1.2.5-2001022100.tar.gz
MD5 (mutt_maildir_tmp_clean-1.2.5-2001022100.tar.gz) = 7b15031d918e09de35f1e13cc71c3ea5
The informative README.TXT packaged inside the tar follows
at the end of this email. There is also a TODO file, if you want
to contribute code to do any of those, please do.
Please, contribute with both suggestions and ideas on how
to improve this patch. Simply reviewing and helping proofing it
is already a great help. :)
A side issue. I packaged the main code files with a BSD
style license, if that is illegal, I'll gladly remove it. However,
before anyone says it is illegal, please check the files in question:
maildir_clean_dir.[ch]. They are files separated from the main mutt
distribution. Bear in mind that I am not a license expert.
I apologize for any trouble.
Thanks,
ps: I am not subscribed to this list, so please CC: me
when you reply.
--
Mario S F Ferreira - UnB - Brazil - "I guess this is a signature."
lioux at ( freebsd dot org | linf dot unb dot br )
flames to beloved [EMAIL PROTECTED]
--
# $Header: /home/lioux/cvsroot/mutt/maildir-patch/1.2.5/README.TXT,v 1.5 2001/02/21
06:23:47 lioux Exp $
Mutt 1.2.5 does not implement the complete maildir specification.
It ignores details regarding the handling of maildir tmp directories.
[begin of quote from maildir specification]
The reader is also expected to look through the tmp directory
and to clean up any old files found there. A file in tmp
may be safely removed if it has not been accessed in 36
hours.
[end of quote]
1) What the patch does?
o Implements thist last item of the specification which has
been left out of mutt maildir handling implementation
2) How? How the patch does it?
o Checks the tmp directory and stores the time stamp of the oldest
message below the 36 hours old watermark.
o If there are no messages, stores zero as the time stamp.
o Erases any messages older than 36 hours. This time watermark can
be selected within one minute precision through a configure file
option. If the watermark value is either equal or below zero, the
maildir specification value will be used instead.
o DEFAULTS:
- patch disabled
- time watermark: 36 hours = 36 * 60 minutes
o These are the muttrc options:
set maildir_tmp_clean=yes
set maildir_tmp_clean_interval=desire_time_watermark_in_minutes
o At each mh_check_mailbox cycle, this code does
if (difftime(rightnow,oldest_message)watermark)
checks_directory_for_over_watermark_files;
checks_directory_for_over_watermark_files() {
remove_any_files_over_watermark;
}
3) How do I install it?
o Copy both maildir_clean_dir.c and maildir_clean_dir.h to mutt
directory
o Apply each of the following patches:
- patch-Makefile.am
- patch-Makefile.in
- patch-globals.h
- patch-init.h
- patch-mh.c
- patch-mutt.h
o configure and build the port as usual
4) How do I test it?
o Just add a file to any tmp maildir directory. Then, use
an utility such as "touch" to set a date older than 36
hours (or, whatever the watermark is set).
o Open this maildir folder.
o Check to see if the file has been erased.
---
# $Header: /home/lioux/cvsroot/mutt/maildir-patch/1.2.5/TODO,v 1.2 2001/02/21 07:01:15
lioux Exp $
1) Consider what to do when a message date is in the future. Perhaps,
nothing.
2) Make it faster, perhaps replace all function variable
Re: sort=threads
Hi Jason! Jason Helfman muttered: On Tue, Feb 20, 2001 at 07:44:44PM +0100, Michael Tatge muttered: | Jason Helfman muttered: | For some reason, not quiet sure why, I am unable to sort by threads... | | set sort_aux | | | There's missing a value since $sort_aux is not boolean. I removed that option, and still same result. folder-hook . set sort=sent-date date-sent isn't it? Nevertheless you should be able to sort a folder manually. ':set sort=threads' ought to work! set strict_threads This *could* cause unwanted probs, but shouldn't effect sorting by threads in generell. HTH, Michael -- Why use Windows, since there is a door? (By [EMAIL PROTECTED], Andre Fachat) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Press any key to continue ...
Hello all, Mutt has this habit of always asking me to press a key to continue, for example when I want to view an attachment or an url (with urlview) recently after an update mutt even asks me to press when I start it up. So how do I remove this behaviour, So that I never see this phrase "Press any key to continue..." again. Searched the docs, but didn't find anything, somebody an idea??? Thankx -- Jeroen Valcke [EMAIL PROTECTED] ICQ# 30116911 Home page: http://www.valcke.com/jeroen Phone +32(0)56 32 91 37 Mobile +32(0)486 88 21 26 "Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come." -Matt Groening-
Re: How to do a regexp
On Mon, Feb 19, 2001 at 06:21:58PM -0500, Bruce A. Petro wrote: Many thanks! Can you point me to some book or doc or man that says things in fairly plain english as you did??? I'm finding a lot of docs on regexps that are hard to translate when you are just starting out like me. They don't seem to say things like: The "." means "any character", so ".*" means "any string of characters". Personally, I'd recommend the O'Reilly book, "Mastering Regular Expressions". If you don't want to buy that book, find someone who's got the "Programming Perl" book, and read the section on Regular Expressions. (warning: perl does have some nice extentions to the standard regex syntax) Also, question: I understand the leading .* based on your remark, but what about the trailing .* ?? The TO address should always end with t the ".com" - is there a need for it, or were you just being ultra cautious to get everything possible? The reasoning behind this is: * ^To: .*about.com.* ...often addresses are formatted in a way like: John Doe [EMAIL PROTECTED] or [EMAIL PROTECTED] (John Doe) but are not that often just the email address alone. Hope that helps, -- Josh Huber | [EMAIL PROTECTED] | PGP signature
Re: sending postponed messages
( Die, 20 Feb 2001 ) [EMAIL PROTECTED] -- : If you're offline when you send messages (not postpone them), sendmail should queue the messages. When you're online again, "sendmail -q" should flush the queue, i.e., send all the messages in the queue. ( Mit, 21 Feb 2001 ) BWise -- : Erika, don't throw Mutt out! I'm on a dial-up connection (as you are) and have a script run by a cron-daemon which connects me to my isp, checks my various mail accounts, and sends queued mail (using "sudo qsend" so that I do not have to be logged in as root) at regular intervals. And at this moment I have in the neighborhood of a half-dozen postponed messages in Mutt. Ok, in kmail I made myself a folder out.wait for drafts besides out. But you are right sendmail -q does the trick - for god sake this is not one of those postfix's sendmail commands whith (ignored:), so I only have to discipline myself that sent is nearly out and not longer a draft ... But better than this mousing around - and no I do not intend to throw Mutt out but kmail as soon as I got my headers correct. And of course I will end up with scripting the whole thing, that's at least what I exactely know how to do it ;) Thanks to all for that hint. Erika
Re: How to do a regexp
Many thanks!
Can you point me to some book or doc or man that says things in fairly
plain english as you did??? I'm finding a lot of docs on regexps that
are hard to translate when you are just starting out like me. They
don't seem to say things like:
The "." means "any character", so ".*" means "any string of characters".
Also, question: I understand the leading .* based on your remark, but
what about the trailing .* ?? The TO address should always end with t
the ".com" - is there a need for it, or were you just being ultra
cautious to get everything possible?
THANKS AGAIN!
Bruce.
On Sat, Feb 17 03:58AM, Nollaig MacKenzie wrote:
On 2001.02.16 23:23:57, you,
the extraordinary Bruce A. Petro, opined:
Hi - I'm new at regexp's and don't know how to do this...
The main question is from procmail regexp I did that is
not working. I want it to find all mail where the TO:
contains "@about.com" ("[EMAIL PROTECTED], [EMAIL PROTECTED]).
Any suggestions why its not working?
:0:
* ^[EMAIL PROTECTED]
about.com
Try:
:0:
* ^To: .*about.com.*
about.com
The "." means "any character", so ".*"
means "any string of characters".
Cheers, N.
--
Nollaig MacKenzie [EMAIL PROTECTED]
http://www.amhuinnsuidhe.cx
Oppose renaming Mt Logan!! http://www.savemtlogan.com
xterm titlebars and status_format or folder-hook
Hi -- I'd like to tell Mutt to echo the appropriate escape codes to change xterm's title bar to the name of the current mailbox. I tried adding them to folder_hook, but the literals "^[" and "^G" get displayed; I couldn't figure out how to tell a folder-hook to cant the magic. Has anyone solved this problem? -Rich -- -- Rich Lafferty --- Sysadmin/Programmer, Instructional and Information Technology Services Concordia University, Montreal, QC (514) 848-7625 - [EMAIL PROTECTED] --
Re: sending postponed messages
Erika Pacholleck proclaimed on mutt-users that: But better than this mousing around - and no I do not intend to throw Mutt out but kmail as soon as I got my headers correct. Try my howto at http://www.hserus.net/dlhowto.html (email on a dialup). That's a howto on how to configure sendmail + mutt on a dialup. There's also a copy of my .muttrc in case you are interested. -s -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
RFC: maildir tmp clean patch
Hi,
version:1.2.5
menu: n.a.
command:n.a.
new config options: set maildir_tmp_clean
set maildir_tmp_clean_interval
bug that it fixes: non-compliance to maildir specification
I've put together a simple patch following mutt coding
style to implement older than 36 hours files' tmp cleaning.
djb's maildir specification clearly states:
[begin of quote from maildir specification]
The reader is also expected to look through the tmp directory
and to clean up any old files found there. A file in tmp
may be safely removed if it has not been accessed in 36
hours.
[end of quote]
Before the discussion arises, mutt should comply to the
maildir specification. It does not matter if some local installation
does not seem to mind the non-compliance. It is a simple requirement
and an easy one to implement. Why not comply, then? Do not flame
me, I am just stating an opinion.
I am proposing my patch but any other that does the trick
is fine by me. :) I just would like to see this implemented.
Input and suggestions welcome. The patch applies against
mutt 1.2.5. It can be found at
http://people.freebsd.org/~lioux/mutt_maildir_tmp_clean-1.2.5-2001022100.tar.bz2
MD5 (mutt_maildir_tmp_clean-1.2.5-2001022100.tar.bz2) =
2c55edc5600f99cce077fb7ea712788a
or
http://people.freebsd.org/~lioux/mutt_maildir_tmp_clean-1.2.5-2001022100.tar.gz
MD5 (mutt_maildir_tmp_clean-1.2.5-2001022100.tar.gz) = 7b15031d918e09de35f1e13cc71c3ea5
The informative README.TXT packaged inside the tar follows
at the end of this email. There is also a TODO file, if you want
to contribute code to do any of those, please do.
Please, contribute with both suggestions and ideas on how
to improve this patch. Simply reviewing and helping proofing it
is already a great help. :)
A side issue. I packaged the main code files with a BSD
style license, if that is illegal, I'll gladly remove it. However,
before anyone says it is illegal, please check the files in question:
maildir_clean_dir.[ch]. They are files separated from the main mutt
distribution. Bear in mind that I am not a license expert.
I apologize for any trouble.
Thanks,
ps: I am not subscribed to this list, so please CC: me
when you reply.
--
Mario S F Ferreira - UnB - Brazil - "I guess this is a signature."
lioux at ( freebsd dot org | linf dot unb dot br )
flames to beloved [EMAIL PROTECTED]
--
# $Header: /home/lioux/cvsroot/mutt/maildir-patch/1.2.5/README.TXT,v 1.5 2001/02/21
06:23:47 lioux Exp $
Mutt 1.2.5 does not implement the complete maildir specification.
It ignores details regarding the handling of maildir tmp directories.
[begin of quote from maildir specification]
The reader is also expected to look through the tmp directory
and to clean up any old files found there. A file in tmp
may be safely removed if it has not been accessed in 36
hours.
[end of quote]
1) What the patch does?
o Implements thist last item of the specification which has
been left out of mutt maildir handling implementation
2) How? How the patch does it?
o Checks the tmp directory and stores the time stamp of the oldest
message below the 36 hours old watermark.
o If there are no messages, stores zero as the time stamp.
o Erases any messages older than 36 hours. This time watermark can
be selected within one minute precision through a configure file
option. If the watermark value is either equal or below zero, the
maildir specification value will be used instead.
o DEFAULTS:
- patch disabled
- time watermark: 36 hours = 36 * 60 minutes
o These are the muttrc options:
set maildir_tmp_clean=yes
set maildir_tmp_clean_interval=desire_time_watermark_in_minutes
o At each mh_check_mailbox cycle, this code does
if (difftime(rightnow,oldest_message)watermark)
checks_directory_for_over_watermark_files;
checks_directory_for_over_watermark_files() {
remove_any_files_over_watermark;
}
3) How do I install it?
o Copy both maildir_clean_dir.c and maildir_clean_dir.h to mutt
directory
o Apply each of the following patches:
- patch-Makefile.am
- patch-Makefile.in
- patch-globals.h
- patch-init.h
- patch-mh.c
- patch-mutt.h
o configure and build the port as usual
4) How do I test it?
o Just add a file to any tmp maildir directory. Then, use
an utility such as "touch" to set a date older than 36
hours (or, whatever the watermark is set).
o Open this maildir folder.
o Check to see if the file has been erased.
---
# $Header: /home/lioux/cvsroot/mutt/maildir-patch/1.2.5/TODO,v 1.2 2001/02/21 07:01:15
lioux Exp $
1) Consider what to do when a message date is in the future. Perhaps,
nothing.
2) Make it faster, perhaps replace all function variable
Re: your mail
Craig Neuwirt proclaimed on mutt-users that: Can mutt be configured to work over a firewall with a proxy server. Use fetchmail (or .forward files or whatever) to move mail to your box from the mailserver. Then use sendmail (which should be configured to go through the proxy) to send out mail. If you have a central pop and smtp server, set up fetchmail, and sendmail (or even ssmtp, masqmail etc) to smarthost through your central smtp server. -s -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
