Re: deleted box

1999-02-17 Thread Randall J. Million

 What are the problems that you have with this?  It would take just a
 tiny bit of code to add a "trash_folder" variable, which when set, would
 receive a copy of deleted messages.  But I'm not sure what doesn't work
 about the above?

1. You cannot undelete messages and have them removed from the Trash
   folder.
2. It is possible to delete a message multiple times (and svae it to the
   Trash folder multiple times). Limited accoutn space made the
   duplicated messages hard to deal with.
3. No good way I found (without cron privs) to automatically delete
   messages without entering the Trash folder.
4. Takes relatively long time and puts a Saving... Message up.
5. Does not work with the tag-prefix or with thread-delete.

randy

-- 
Five hundred, twenty-five thousand six hundred minutes, how do you measure...?
 
[EMAIL PROTECTED]  http://www.louisville.edu/~rjmill01/
Triangle Fraternity   http://www.louisville.edu/rso/triangle/
Golden Key National Honor Society http://www.louisville.edu/rso/goldenkey/



Re: deleted box

1999-02-17 Thread Daniel Eisenbud

On Wed, Feb 17, 1999 at 02:52:36AM -0500, Randall J. Million [EMAIL PROTECTED] 
wrote:
  What are the problems that you have with this?  It would take just a
  tiny bit of code to add a "trash_folder" variable, which when set, would
  receive a copy of deleted messages.  But I'm not sure what doesn't work
  about the above?
 
 1. You cannot undelete messages and have them removed from the Trash
folder.
 2. It is possible to delete a message multiple times (and svae it to the
Trash folder multiple times). Limited accoutn space made the
duplicated messages hard to deal with.

Hmm.  I guess the time to save the mesags to the trash folder would be
when actually synchronizing the mailbox, then.

 3. No good way I found (without cron privs) to automatically delete
messages without entering the Trash folder.

This is (IMHO) beyond the scope of what mutt should be able to do.  It
will be easy to delete messages from cron with a find command if you
make the folder a maildir or MH folder, but it will also be easy to do
the same thing from your .login, or from a shell script wrapper around
mutt, or any number of things.

 4. Takes relatively long time and puts a Saving... Message up.

Hmm.  My method would make deleting messages instant, but then
resynchronizing the folder might take a moment longer.  But I think this
will be nicer.

 5. Does not work with the tag-prefix or with thread-delete.

I don't see why it wouldn't work with tag-prefix if your macro is
"s=deleted\n" or whatever.  But thread-delete is a good point.  This
will all be moot if we do it my way.

Hmm, I wonder how hard this would be to code?  Looking at the code a
bit, I come to the conclusion that it would be trivial to do this, but
such an implementation would have the problem that we would sometimes
save a copy of the message to the trash mailbox but then fail to
synchronize the folder.  By the time we successfully synchronized the
folder, we would have several copies of the message in the trash.  This
is not so bad, since this is just a backup mechanism, and too many is
much better than too few.  But it is still a bit ugly.  Alternatives are
to do this from within the routines specific to different types of
mailboxes, after we have checked for new messages and dealt with
locking.  That would be a bit ugly too.  A third alternative would be to
split up the various sync functions into two parts, but I don't know if
this change justifies that.  I will think about this a little bit more.

-Daniel

-- 
Daniel Eisenbud
[EMAIL PROTECTED]



Re: mutt -v (was: old home page URL in mutt.man from 0.95.3i)

1999-02-17 Thread Franklin R. Jones

On Tue, Feb 16, 1999 at 09:56:48PM +, Steve Kennedy wrote:
 On Tue, Feb 16, 1999 at 02:54:51PM -0700, Franklin R. Jones wrote:
 
  while on the subject of mailing addresses and such. It would
  also be useful to change the subscription information in the
  FAQ/manual. Every copy I found including those touted as "current"
  state:
  "To subscribe to one of the following mailing lists, send a message
  with the word subscribe in the subject to [EMAIL PROTECTED]"
  the list is run by majordomo and it *ignores* the subject line, and
  requires the subscribe command to be in the body.
 
 Err, that's how it works ...
 
 you can also use mail to [EMAIL PROTECTED] with
 subscribe mutt-list (where list is the one you want)
 in the body ...

Not. When I attempted to follow those directions I got the following.
I sent the e-mail to [EMAIL PROTECTED] once I realized it
was a 'domo server I turned around and sent a standard subscribe
request. So, if that is the intent (subject subscription) it's
currently broken.

fj.. 

==Date: 12 Feb 1999 16:26:42 -   
==To: [EMAIL PROTECTED]  
==From: [EMAIL PROTECTED]  
==Subject: Majordomo results: subscribe
==Reply-To: [EMAIL PROTECTED]  
==
==--  
==
==
== No valid commands found.  
== Commands must be in message BODY, not in HEADER.
==
== Help for [EMAIL PROTECTED]: 
==
==
==This help message is being sent to you from the Majordomo mailing list
==management system at [EMAIL PROTECTED]
==
==This is version 1.94.4 of Majordomo.
==
==If you're familiar with mail servers, an advanced user's summary of
==Majordomo's commands appears at the end of this message.  
==
==Majordomo is an automated system which allows users to subscribe
==and unsubscribe to mailing lists, and to retrieve files from list
==archives.   
==
==You can interact with the Majordomo software by sending it commands
==in the body of mail messages addressed to "[EMAIL PROTECTED]".
==Please do not put your commands on the subject line; Majordomo does
==not process commands in the subject line.
==
==You may put multiple Majordomo commands in the same mail message.
==Put each command on a line by itself.
==
==If you use a "signature block" at the end of your mail, Majordomo may
==mistakenly believe each line of your message is a command; you will 
==then receive spurious error messages.  To keep this from happening,
==either put a line starting with a hyphen ("-") before your signature,
==or put a line with just the word   



Re: mutt -v (was: old home page URL in mutt.man from 0.95.3i)

1999-02-17 Thread Steve Kennedy

On Tue, Feb 16, 1999 at 03:33:11PM -0700, Franklin R. Jones wrote:

 On Tue, Feb 16, 1999 at 09:56:48PM +, Steve Kennedy wrote:
  On Tue, Feb 16, 1999 at 02:54:51PM -0700, Franklin R. Jones wrote:
 while on the subject of mailing addresses and such. It would
   also be useful to change the subscription information in the
   FAQ/manual. Every copy I found including those touted as "current"
   state:
   "To subscribe to one of the following mailing lists, send a message
   with the word subscribe in the subject to [EMAIL PROTECTED]"
   the list is run by majordomo and it *ignores* the subject line, and
   requires the subscribe command to be in the body.
  Err, that's how it works ...
  you can also use mail to [EMAIL PROTECTED] with
  subscribe mutt-list (where list is the one you want)
  in the body ...
 I sent the e-mail to [EMAIL PROTECTED] once I realized it
 was a 'domo server I turned around and sent a standard subscribe
 request. So, if that is the intent (subject subscription) it's
 currently broken.

Err, you're right - the above is wrong - subscribe must be in the body.

You can send mail to [EMAIL PROTECTED] with
subscribe listname
in the body ...

Steve

-- 
NetTek Ltdtel +44-171 483 1169 fax +44-181 444 6103
Flat 2,  43 Howitt Road,  Belsize Park,  London NW3 4LU
   Epage [EMAIL PROTECTED] [body of text only]



Re: deleted box

1999-02-17 Thread David DeSimone

Brian Bray [EMAIL PROTECTED] wrote:

 just wondering about the easiest way to go about makeing deleted mail
 transfer to a"trash" folder before for later retrival/deletion.

I have been using this patch to get a trash-folder effect; unfortunately
I have lost the author's name.

It was created for Mutt 0.94.3, but seems to work very well with 0.95,
since it is not very obtrusive.

-- 
David DeSimone   | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED]   |  that there is no man really clever who has not
Hewlett-Packard  |  found that he is stupid." -- Gilbert K. Chesterson
Convex Division  |PGP: 5B 47 34 9F 3B 9A B0 0D  AB A6 15 F1 BB BE 8C 44


diff -u mutt-0.94.3i/Muttrc.in mutt-0.94.3i-trash/Muttrc.in
--- mutt-0.94.3i/Muttrc.in  Fri Jun 26 06:31:19 1998
+++ mutt-0.94.3i-trash/Muttrc.inSun Aug 23 22:02:42 1998
@@ -144,6 +144,7 @@
 # set timeout=600
 # set tmpdir=""
 # set to_chars="+TCF"
+# set trash=""
 # unset use_8bitmime
 # set use_domain
 # set use_from
Common subdirectories: mutt-0.94.3i/doc and mutt-0.94.3i-trash/doc
diff -u mutt-0.94.3i/globals.h mutt-0.94.3i-trash/globals.h
--- mutt-0.94.3i/globals.h  Fri Jul 17 03:47:13 1998
+++ mutt-0.94.3i-trash/globals.hSun Aug 23 22:02:42 1998
@@ -77,6 +77,7 @@
 WHERE char *Status;
 WHERE char *Tempdir;
 WHERE char *Tochars;
+WHERE char *Trash;
 WHERE char *Username;
 WHERE char *Visual;
 
diff -u mutt-0.94.3i/init.h mutt-0.94.3i-trash/init.h
--- mutt-0.94.3i/init.h Mon Aug 10 11:28:31 1998
+++ mutt-0.94.3i-trash/init.h   Sun Aug 23 22:02:42 1998
@@ -255,6 +255,7 @@
   { "timeout", DT_NUM,  R_NONE, UL Timeout, 600 },
   { "tmpdir",  DT_PATH, R_NONE, UL Tempdir, 0 },
   { "to_chars",DT_STR,  R_BOTH, UL Tochars, UL " +TCF" },
+  { "trash",   DT_PATH, R_NONE, UL Trash, UL "" },
   { "use_8bitmime",DT_BOOL, R_NONE, OPTUSE8BITMIME, 0 },
   { "use_domain",  DT_BOOL, R_NONE, OPTUSEDOMAIN, 1 },
   { "use_from",DT_BOOL, R_NONE, OPTUSEFROM, 1 },
diff -u mutt-0.94.3i/mx.c mutt-0.94.3i-trash/mx.c
--- mutt-0.94.3i/mx.c   Tue Jul 28 04:16:01 1998
+++ mutt-0.94.3i-trash/mx.c Sun Aug 23 22:02:42 1998
@@ -23,7 +23,7 @@
 #include "mailbox.h"
 #include "copy.h"
 #include "keymap.h"
-
+#include "globals.h"
 
 #ifdef _PGPPATH
 #include "pgp.h"
@@ -666,9 +666,41 @@
   BUFFY *tmp = NULL;
 #endif
   int rc = -1;
+  int i, nosave = 0;
+  CONTEXT trash;
+  struct stat st;
+  char tmp[_POSIX_PATH_MAX+20];
 
   if (!ctx-quiet)
 mutt_message ("Writing %s...", ctx-path);
+
+  /* Only save messages to trash if there are deleted messages, 
+ the Trash variable has been set,
+ and the current folder isn't the trash. */
+  if (ctx-deleted  strlen(Trash)  strncmp(ctx-path, Trash, _POSIX_PATH_MAX)) {
+errno = 0;
+stat(Trash, st);
+if (errno == ENOENT  option (OPTCONFIRMCREATE)) {
+  snprintf (tmp, sizeof (tmp), "Create trash mailbox, %s?", Trash);
+  if (mutt_yesorno (tmp, 1)  1) {
+if (mutt_yesorno("Purge deleted messages without saving?",1)  1)
+ return (-1);
+   else
+ nosave = 1;
+  }
+}
+if (!nosave) {
+  if (mx_open_mailbox (Trash, M_APPEND | M_QUIET, trash) == NULL) {
+dprint (1, (debugfile, "sync_mailbox(): unable to open mailbox %s in 
+append-mode, aborting.\n", Trash));
+return (-1);
+  }
+  for (i = 0; i  ctx-msgcount; i++)
+if (ctx-hdrs[i]-deleted)
+  mutt_append_message(trash, ctx, ctx-hdrs[i], 0, CH_UPDATE_LEN);
+  mx_close_mailbox(trash);
+}
+  }
+
   switch (ctx-magic)
   {
 case M_MBOX:
Common subdirectories: mutt-0.94.3i/rx and mutt-0.94.3i-trash/rx



Re: Archive of mailing lists?

1999-02-17 Thread Jeremy Blosser

Warning
Could not process message with given Content-Type: 
multipart/signed; boundary=nFreZHaLTZJo0R7j; micalg=pgp-md5;protocol="application/pgp-signature"




Re: deleted box

1999-02-17 Thread Mun Johl

Hi all,

I believe the author's name is Jeff Dubrule.  I use the patch too, and
it works great!  I've included Jeff's text that went along with the
patch:


 Ok, a long time ago I griped about the lack of a "trash" mailbox to which
 deleted messages would get moved.  I was directed to:
 
 unset confirmappend
 folder-hook . "macro index d 's=trash\n'"
 folder-hook . "macro pager d 's=trash\n'"
 folder-hook trash "bind index d delete-message"
 folder-hook trash "bind pager d delete-message"
 
 This annoyed me because it was slow, didn't handle ^D (delete-thread), and
 could cause me to make 1 copy of something if I hit 'd' on it more than
 once.  Finally, this is distinctly non-obvious to the casual user.  As a
 solution, I present this patch, which saves deleted messages to a designated
 mail-folder.
 
 While this feature is not traditionally included with Unix MUAs, I find it
 invaluable: I get too much mail to pay great attention to each one I delete.
 If I make a mistake, I'll never be able to recover that message.  This way,
 I can move 'em all to a 'trash' folder, have a cron-job clean up the old
 messages, so I have a week to realize that I screwed up.
 
 OK, the details:
 
 Include "set trash = +trash" (or whatever) in your .muttrc, and when the
 mailbox syncs, it'll copy all the deleted messages to the trash mailbox
 before zapping it.  This behaviour does not occur, however, if the trash
 mailbox itself is selected.
 
 This patch works with all mailbox types.
 
 -igor


-- 
Mun



Re: deleted box

1999-02-17 Thread Daniel Eisenbud

On Wed, Feb 17, 1999 at 10:15:19AM -0600, David DeSimone [EMAIL PROTECTED] wrote:
 Brian Bray [EMAIL PROTECTED] wrote:
 
  just wondering about the easiest way to go about makeing deleted mail
  transfer to a"trash" folder before for later retrival/deletion.
 
 I have been using this patch to get a trash-folder effect; unfortunately
 I have lost the author's name.

Looks pretty good.  There are a few little nits, like including
globals.h.  And can a string variable ever be a NULL pointer?  I wasn't
sure, so I checked anyway in my patch.  At least using safe_strlen would
be good, I think.  Also, the patch doesn't check the exit status from
actually writing the messages to the mailbox, which is kind of bad.  It
does check whether the user is in the trash mailbox, which is good.
However, besides this, it has all the same problems as my patch.  I've
decided that maybe the problem of saving a copy of messages to the trash
when you don't actually delete them but just save them to another
folder, is OK.  I just looked at my MH docs, and this is how the rmmproc
functionality that I used to use there works.  However, the potential
saving of messages multiple times is annoying, still, and will not be
infrequent in really busy mailboxes.  However, I don't want to do this
whole operation with signals blocked.  But I gather that we're not
supposed to keep the mailbox locked with signals unblocked, right?
Aargh!  Can someone enlighten me on the issues involved with that?

-Daniel

 diff -u mutt-0.94.3i/Muttrc.in mutt-0.94.3i-trash/Muttrc.in
 --- mutt-0.94.3i/Muttrc.inFri Jun 26 06:31:19 1998
 +++ mutt-0.94.3i-trash/Muttrc.in  Sun Aug 23 22:02:42 1998
 @@ -144,6 +144,7 @@
  # set timeout=600
  # set tmpdir=""
  # set to_chars="+TCF"
 +# set trash=""
  # unset use_8bitmime
  # set use_domain
  # set use_from
 Common subdirectories: mutt-0.94.3i/doc and mutt-0.94.3i-trash/doc
 diff -u mutt-0.94.3i/globals.h mutt-0.94.3i-trash/globals.h
 --- mutt-0.94.3i/globals.hFri Jul 17 03:47:13 1998
 +++ mutt-0.94.3i-trash/globals.h  Sun Aug 23 22:02:42 1998
 @@ -77,6 +77,7 @@
  WHERE char *Status;
  WHERE char *Tempdir;
  WHERE char *Tochars;
 +WHERE char *Trash;
  WHERE char *Username;
  WHERE char *Visual;
  
 diff -u mutt-0.94.3i/init.h mutt-0.94.3i-trash/init.h
 --- mutt-0.94.3i/init.h   Mon Aug 10 11:28:31 1998
 +++ mutt-0.94.3i-trash/init.h Sun Aug 23 22:02:42 1998
 @@ -255,6 +255,7 @@
{ "timeout",   DT_NUM,  R_NONE, UL Timeout, 600 },
{ "tmpdir",DT_PATH, R_NONE, UL Tempdir, 0 },
{ "to_chars",  DT_STR,  R_BOTH, UL Tochars, UL " +TCF" },
 +  { "trash", DT_PATH, R_NONE, UL Trash, UL "" },
{ "use_8bitmime",  DT_BOOL, R_NONE, OPTUSE8BITMIME, 0 },
{ "use_domain",DT_BOOL, R_NONE, OPTUSEDOMAIN, 1 },
{ "use_from",  DT_BOOL, R_NONE, OPTUSEFROM, 1 },
 diff -u mutt-0.94.3i/mx.c mutt-0.94.3i-trash/mx.c
 --- mutt-0.94.3i/mx.c Tue Jul 28 04:16:01 1998
 +++ mutt-0.94.3i-trash/mx.c   Sun Aug 23 22:02:42 1998
 @@ -23,7 +23,7 @@
  #include "mailbox.h"
  #include "copy.h"
  #include "keymap.h"
 -
 +#include "globals.h"
  
  #ifdef _PGPPATH
  #include "pgp.h"
 @@ -666,9 +666,41 @@
BUFFY *tmp = NULL;
  #endif
int rc = -1;
 +  int i, nosave = 0;
 +  CONTEXT trash;
 +  struct stat st;
 +  char tmp[_POSIX_PATH_MAX+20];
  
if (!ctx-quiet)
  mutt_message ("Writing %s...", ctx-path);
 +
 +  /* Only save messages to trash if there are deleted messages, 
 + the Trash variable has been set,
 + and the current folder isn't the trash. */
 +  if (ctx-deleted  strlen(Trash)  strncmp(ctx-path, Trash, _POSIX_PATH_MAX)) {
 +errno = 0;
 +stat(Trash, st);
 +if (errno == ENOENT  option (OPTCONFIRMCREATE)) {
 +  snprintf (tmp, sizeof (tmp), "Create trash mailbox, %s?", Trash);
 +  if (mutt_yesorno (tmp, 1)  1) {
 +if (mutt_yesorno("Purge deleted messages without saving?",1)  1)
 +   return (-1);
 + else
 +   nosave = 1;
 +  }
 +}
 +if (!nosave) {
 +  if (mx_open_mailbox (Trash, M_APPEND | M_QUIET, trash) == NULL) {
 +dprint (1, (debugfile, "sync_mailbox(): unable to open mailbox %s in 
append-mode, aborting.\n", Trash));
 +return (-1);
 +  }
 +  for (i = 0; i  ctx-msgcount; i++)
 +if (ctx-hdrs[i]-deleted)
 +  mutt_append_message(trash, ctx, ctx-hdrs[i], 0, CH_UPDATE_LEN);
 +  mx_close_mailbox(trash);
 +}
 +  }
 +
switch (ctx-magic)
{
  case M_MBOX:
 Common subdirectories: mutt-0.94.3i/rx and mutt-0.94.3i-trash/rx


-- 
Daniel Eisenbud
[EMAIL PROTECTED]



Re: deleted box

1999-02-17 Thread Stefan `Sec` Zehl

On Wed, Feb 17, 1999 at 12:39:20PM -0800, Daniel Eisenbud wrote:
However, the potential
 saving of messages multiple times is annoying, still, and will not be
 infrequent in really busy mailboxes.  However, I don't want to do this
 whole operation with signals blocked.  But I gather that we're not
 supposed to keep the mailbox locked with signals unblocked, right?
 Aargh!  Can someone enlighten me on the issues involved with that?

I'd just set a flag in each message to true when it was successfully
saved to trash. That way you can skip them on the second try.
That then gives you the possibility to have an 'delete to trash' and an
'really delete' op.

CU,
Sec
-- 
It's so nice to be insane, nobody asks you to explain.



send-hook bug?

1999-02-17 Thread Paul Visscher

I have [EMAIL PROTECTED]'s mail forwarding to this account(via a .forward). I
need mutt to make it look like I am replying to a mail that hasn't been
forwarded. I have the following send-hooks in my ~/.muttrc:

send-hook '~t [EMAIL PROTECTED]'  'my_hdr From: foobar [EMAIL PROTECTED]'
send-hook '~t [EMAIL PROTECTED]'  'set signature="~/.foobar.sig"'

This(AFIAK) says "when I reply to something sent to [EMAIL PROTECTED], it
should be from [EMAIL PROTECTED], and it should change my .signature
accordingly." Is this correct? If it is, I believe that I have found a
bug. If it is not, can someone please explain why? 

Here is how I reproduce the bug:

When I reply to a message sent to [EMAIL PROTECTED], the header changes and
says that I'm not me, I'm [EMAIL PROTECTED], and the signature changes to
[EMAIL PROTECTED]'s signature. The mail sends fine, and has the correct
information in it. Then(with out quitting mutt) I reply to a message
sent to [EMAIL PROTECTED], but the From: header and the signature remain
for [EMAIL PROTECTED] I did not see anything in the manual about this, nor
could I find anything on the web pages. There is, however, this note in
the manual:

Note: the send-hook's are only executed ONCE after getting the initial
list of recipients. Adding a recipient after replying or editing the
message will NOT cause any send-hook to be executed.

The way this is stated, my message shouldn't be affected. Can anyone
provide clarification? mutt -v is attached.
-- 
Paul Visscher
[EMAIL PROTECTED]
--
#include disclaimer.h
"I am definitely a tropical fish." -- Joseph Blaylock


Mutt 0.95.3i (1999-02-12)
Copyright (C) 1996-8 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 2.0.36 [using ncurses 1.9.9e]
Compile options:
-DOMAIN
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +USE_FCNTL  -USE_FLOCK
-USE_IMAP  -USE_POP  +HAVE_REGCOMP  -USE_GNU_REGEX  +HAVE_COLOR
+HAVE_PGP2  -BUFFY_SIZE 
-EXACT_ADDRESS  +ENABLE_NLS
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/spool/mail"
SHAREDIR="/usr/local/share/mutt"
SYSCONFDIR="/usr/local/etc"
ISPELL="/usr/bin/ispell"
_PGPPATH="/usr/local/bin/pgp"
_PGPV2PATH="/usr/local/bin/pgp"
To contact the developers, please mail to [EMAIL PROTECTED]. 



Re: send-hook bug?

1999-02-17 Thread Stefan `Sec` Zehl

Warning
Could not process message with given Content-Type: 
multipart/signed; boundary=Kj7319i9nmIyA2yE; micalg=pgp-md5;protocol="application/pgp-signature"




Re: disable X-Mailer:?

1999-02-17 Thread Claus Assmann

On Tue, Feb 16, 1999, Randall Hopper wrote:
 Claus Assmann:

  |Question: how can I disable the X-Mailer: header?

 I wonder if this would work:
 
unmy_hdr X-Mailer
 
 Haven't tried it, but it seems like it should.

Unless I did something wrong, it doesn't work.
I use the suggestion

CFLAGS="-DNO_XMAILER"

which seems to be the simplest way.

Thanks to all who responded!