Re: How are people using Mail::Box?

> 
> I'm wondering how people are using Mail::Box.  Personally, I've been 
> planning to use it to enhance a set of CGI scripts I have which act as a 
> mail reader on localhost.  I've been developing this on Windows, but I 
> hope to make it pretty platform-neutral.
> 
> Do people already have mail readers based on Mail::Box working?  I'd be 
> happy not to repeat work that's already done.
> 
> Thanks,
> 

Currently I use Mail::Box at work in an application that processes mail
that includes encrypted file attachments (the encryption is not handled
by Mail::Box, at least for us).  In the other direction we use
Mail::Message (part of MB distro) to handle the sending of messages,
production messages that include an encrypted attachment, or help desk
e-mails when something goes wrong in processing of one of the files
(inbound or outbound).  In the former case we have a very simple Perl
script (not MB related) that reads what sendmail gives it on a pipe and
stores the message to the filesystem in a plain text file with our
naming conventions, etc. A separate daemon watches for the new files and
processes them using 'MB->read' checking various headers, and stripping
off the attachments which then get further processing (aka decryption).
We don't use many of the actual 'box' handling features of MB, but parse
mail from 200+ organizations and have yet to hit a snag based on the
various mail clients, etc.  We process roughly 900 inbound messages a
day and send roughly 3500.

In my spare time I use MM again for sending messages in the CGI
application I use to run my various sites. It is still not in a high
traffic mode, but I haven't had any problems yet with it in that
environment.  Eventually I intend to write a mail client into the
framework of the rest of the application and wouldn't have considered it
without knowing about MB's capabilities (I did this once before and it
wasn't pretty, though did work (somewhat)).  I would love to distribute
it and will certainly contribute back code I get from it that is generic
enough, but I have a feeling it will be tied so closely to the rest of
my code that it may not be that beneficial to anyone (unless I
distribute the rest of the app which I may ((only reason I wouldn't is
because it might suck :-)))).

As part of the above application I am thinking about writing a daemon
that will allow managing and delaying sending of bulk e-mail (not spam
don't worry) and would use MB for sending those messages as well.
Essentially it is a traffic throttling app to allow a CGI to write
messages quickly to the local filesystem without contacting sendmail, so
that a return response can be provided quickly, before the messages
actually go out, the app would then send the messages as it has time.
This may already exist too, not sure....

Just some rambles, all code developed on *nix...

http://danconia.org