On Tue, 18 Jun 2002 16:22:57 +0200 (CET) Vadim Zeitlin 
<[EMAIL PROTECTED]> wrote:

VZ> On Tue, 18 Jun 2002 09:43:17 -0400 (Eastern Daylight Time) "Eric S.
VZ> Johansson" <[EMAIL PROTECTED]> wrote:
VZ> 
VZ> ESJ> I've got a couple more annoying bugs for you.
VZ> ESJ> 
VZ> ESJ> 1) when you use an external editor instead of the internal composer,
VZ> ESJ>    my root directory is getting littered with files.  Please cleanup
VZ> ESJ>    after yourself...
VZ> 
VZ>  These files are deleted when the external editor terminates -- at least on
VZ> my machine. It would be better to create them in the Mahogany directory
VZ> than in the root, though, and I'll change this, but in any case they
VZ> shouldn't stay and, if deleting them failed, you should get a warning from
VZ> Mahogany.

you are right, it does.  I was not seeing that behavior because of all
the backup files that get left behind.

VZ> ESJ> 2) I use Emacs as my editor and it leaves behind little ~ terminated
VZ> ESJ>    files.  Please clean those up as well.
VZ> 
VZ>  No, I can't do this (think a bit about how am I supposed to know how the
VZ> custom editor calls its external files?). Tell Emacs to not create the
VZ> backups.

easier said than done.  I think I'll probably just create a wrapper shell script and 
have it delete the ~file.

VZ> 
VZ> ESJ> 3) temporary file names end in an extremely wide range of extensions.
VZ> ESJ>    Emacs uses this information to auto select the editor mode.  Some
VZ> ESJ>    messages I'm editing assembler, others Fortran, C, objective c, and
VZ> ESJ>    so on.  Please if you are going to have an extension, make it just
VZ> ESJ>    .txt so that "I'm smarter than you are" editors won't get confused.
VZ> 
VZ>  I know this doesn't help you much but with vim I use the following command
VZ> line:
VZ> 
VZ>         gvim -c "so ~/vim/mail.vim" %s
VZ> 
VZ> and the mail.vim script sets the file type to mail overriding the default
VZ> extension detection. I'm sure Emacs has some equivalent feature (it can do
VZ> everything, right? ;-).

it does.  It's just a matter of finding it...  ;-)

VZ> 
VZ> ESJ> I'd like to hear a bit more about the antispam features.  
VZ> 
VZ>  Nothing fancy -- unfortunately so, but it turned out that the existing
VZ> filters framework was very inflexible and so to do what I originally wanted
VZ> I'd have to change almost everything :-(
VZ> 
VZ>  So finally I've just added the features I need myself:
VZ> 
VZ> - the test for 8 bit subjects: I'm sick and tired from Korean spam and
VZ>   this should catch 90% of it
VZ> 
VZ> - the test for having my address among the recipients or a mailing list
VZ>   header as most of the spam is not addresses directly to me -- of course,
VZ>   I won't get any messages via bcc neither like this but so be it

Spam filtering is difficult to do right.  Spamassassin has quite a
nice model for filtering that's good enough to take out 70 percent of
my spam (I still get 10 pieces per day) and a false positives are low
enough that I just ignore them.  getting the same level of filtering
into a mail client will be difficult.

VZ> 
VZ> ESJ> if I can run some python code after a message has been received but
VZ> ESJ> before it's been filtered/stuck in any local mailboxes, I can test out
VZ> ESJ> my antispam system.
VZ> 
VZ>  It should be possible -- you [are supposed to] have access to all the
VZ> Message class methods from Python so you can examine all the headers and
VZ> what not.

OK, that sounds worth investigating.

VZ> 
VZ> ESJ> On the output side, I need the ability to insert headers into a mail
VZ> ESJ> message and potentially modify the body (i.e. substitute encrypted
VZ> ESJ> text for plain text)
VZ> 
VZ>  I don't think Mahogany will ever do this -- it's a MUA, not an MTA.

you should think twice about this.  It's the kind of capability that
would be necessary for pgp plug-ins.  We just need to tap the mail
stream just before you inject it into the MTA.

VZ> 
VZ> ESJ> one of these days, someone should try out the cygwin environment for
VZ> ESJ> compiling mahogany.
VZ> 
VZ>  Compiling under cygwin should be trivial as you should be able to use
VZ> configure and the Unix makefiles without any changes.

that's good to know.

---eric


----------------------------------------------------------------------------
                   Bringing you mounds of caffeinated joy
                      >>>     http://thinkgeek.com/sf    <<<

_______________________________________________
Mahogany-Users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mahogany-users

Reply via email to