Re: need advice on reply-to problem

2000-04-07 Thread Charles Cazabon

Darren Wyn Rees [EMAIL PROTECTED] wrote:
 [ Mutt 1.0i (1999-10-22 ]
 
 i'm having difficulty understanding how to
 reply to an e-mail from a list, which contains
 a set reply-to.

Basically the problem is that Reply-To: is being munged for mailing list
purposes.  This is in general a bad idea and causes these types of problems.

Any decent mail client, like Mutt, has Reply, Group reply, and List reply
functions.  Munging the Reply-To: overrides these functions.  Even this
list does it for whatever reason, which is why you won't get a copy of
this message in your personal mailbox, despite the fact that I chose
group-reply.

Charles
-- 
---
Charles Cazabon [EMAIL PROTECTED]
GPL'ed software available at:  http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
---



macro for ezmlm confirms

2000-04-07 Thread Dan Lipofsky

I administer an ezmlm mailing list.  I would like to make answering
YES to confirm requests easier.  Ezmlm encodes administrative commands
as part of the mail address, and you confirm by replying to a special
one time email address (placed into the Reply-To: field). I have never
made a macro before, but this is what I would like it to do
  * Reply to the Reply-To: address
  * do NOT pop up the editor
  * unset Fcc
  * construct a message with no subject and no body
  * do not ask me the usual questions about subjectless messages
  * actually, if it is easier to put in a dummy subject than deal
with subjectless messages, that is fine too.  Subject is ignored. 
  * all effects should last just for that message
Can anyone help me build this macro?  Or tell me something better
than a macro (hooks?).
Thanks,
Dan



[HOWTO] compiling Mutt for Windows NT

2000-04-07 Thread Jim Graham

Ok, ok  I can already hear the heckling starting, and this e-mail
hasn't even left my system yet  :-) But for those of us who
have to use a windoze box at work, this might be useful information,
so it's time to de-lurk and post what I've gotten done so far.

This is a preliminary look at what I've gotten done so far.  As I get
more done on this, I'll post updates (if needed) at
http://www.gnt.net/~n5ial/mutt/building_mutt_on_win.html (which is
linked from http://purl.org/net/n5ialmutt).

Btw, I haven't added this to the web page, because I've forgotten all of
the relevant info, but I do remember seeing a POP/IMAP/etc. client that
can fetch mail from an exchange server...so those who are able to may
want to combine that with this (for mostly political reasons, I'm not
likely to even think about it).

---  CUT HERE  ---

 Building and Using Mutt on Windows NT

   To compile (and use!) Mutt on Windoze NT (yeah, I know...but if you
   have to use 'doze at work, you can at least make it look like a real
   computer---I plan to use it here to catch up on Bugtraq, which I read
   only for work, but receive at home (long story)...and don't have time
   to read at home):

1. If you don't have Cygwin installed, do so now. You can get it from
   The Cygwin Project (http://www.cygnus.com/misc/cygwin/).

2. If you haven't installed ncurses for Cygwin (B20), do so now. You
   can get it in binary or source form from ftp.franken.de in
   /pub/win32/develop/gnuwin32/cygwin/porters/Hirmke_Michael/B20. The
   binary is ncurses-4.2-cygwin-b20-bin.tar.gz OR
   ncurses-4.2-cygwin-b20-bin.zip.

3. Once you've installed ncurses, you will need to cd to
   /usr/local/lib and remove what is supposed to be a symbolic link
   from ../share/terminfo to terminfo, and copy ../share/terminfo to
   /usr/local/lib (cp -R ../share/terminfo .).

4. Get the source for Mutt 1.0.1 from the Mutt site (everything from
   here on is based loosely on that version, but should be easily
   adapted to other versions).

5. run configure as (adjust args to match your system):

   sh configure --with-mailpath=d:/jdg \
  --with-exec-shell=c:/cygnus/cygwin-b20/H-i586-cygwin32/bin/sh.exe

6. Edit addrbook.c in the source distribution. Move the #includes for
   the three standard headers (string.h, stdlib.h, and ctype.h) and
   put them ABOVE the four headers for Mutt (mutt.h, mutt_menu.h,
   mapping.h, and sort.h). If you don't, compiling addrbook.c will
   bomb.

7. Edit protos.h in the source distribution. Search for the line

   #ifndef STDC_HEADERS

   and add the following three lines above it:

   #ifndef STDC_HEADERS
   #define STDC_HEADERS
   #endif

8. make

9. Set a couple of environment variables (see note [1] below):

   TERM=vt100 ; export TERM
   USER=username ; export USER

   10. copy your normal .muttrc and make sure Mutt can find it.

   11. Run mutt (see notes [1] and [2] below)

STATUS

   As of 7 April 2000, I've gotten Mutt to compile and run. I didn't have
   any mbox files, and didn't have time to create one, so I couldn't go
   beyond that point. More details later

 _

   NOTES:

   [1] Note that normally, you want TERM=cygwin. I suggest using an alias
   or shell function for mutt, as I do.

   [2] If you plan to do something like what I'm doing, and send yourself
   an mbox file from home, be sure you send it in a format that Outlook
   won't recognize. If it realizes that it's an attached e-mail, it
   reads your mind incorrectly and assumes (and you know what they say
   about assuming things!) that you want the e-mail saved in Outlook
   format, instead of as an mbox. Gzip it, etc., but make sure it doesn't
   appear to be any e-mail format.

---  CUT HERE  ---

Later,
   --jim

-- 
73 DE N5IAL (/4)| Peter da Silva:  No, try "rm -rf /"
[EMAIL PROTECTED]   | Dave Aronson:As your life flashes before
ICBM / Hurricane:   |  your eyes, in the unit of time known as an
   30.39735N 86.60439W  |  ohnosecond (alt.sysadmin.recovery)