Thanks for all these great suggestions. I'm sure one of them will work. It seems like the best and least complicated route would be to use perl to simply extract contents and dump into Mysql for later analysis and manipulation.
Perl has libraries for doing exactly what I want and although I'm not a perl coder, I'm sure I could hire someone to do that for us. Any takers? Thanks! On 04/25/2014 04:38 AM, Thomas Raschbacher wrote: > Just one thing i was thinking while reading this thread: > > Do you even need 'root' imap access? > For me this sounded like lots of users send mails to one receiver? so > you could just use IMAP to access the data? > (even if you have more than one receiving address you can just create > aliases and then use SIEVE to sort it into IMAP folders if you want to). > > Anyway if you want (read-only) access to the SQL data directly you > might in any case want to use SQL VIEWs so that in case of a DB change > you can - most likely- just update your VIEW instead of rewrite all > your code. > > though what others suggested about just writing your own > milter/lmtp/whatever code might be more suitable for you. > One thing that popped into my head was using e.g. twisted's SMTP > server (if the performance is ok for you) and then instead of saving > the messages somewhere as maildir,.. just parse them and put the info > you want into your own tables .. you'd need to do quite a bit of > python coding then though -- i am sure there are several different > options for this approach too) > > Regards > > On 2014-04-24 15:05, Mark Winslow wrote: >> I think Mimedefang would be the Milter approach. It's probably the >> easiest thing to do. You'll need to look into Perl's Mysql libraries >> to dump into the database. I think there's a way to configure Sendmail >> or Postfix so it doesn't deliver mail, so you're not duplicating >> messages. >> >> On 4/23/2014 5:41 PM, Jeffrey Starin wrote: >> >>> These all sound like great ideas. I've also been looking into >>> mimedefang. >>> >>> On 04/23/2014 06:49 PM, Mark Winslow wrote: >>> >>>> I was thinking that maybe you have an app that decides how to >>>> send messages to your server. If you're exposing an email address, >>>> then clearly you need to have an smtp server, which is probably >>>> going to be Postfix. >>>> >>>> There was a suggestion to just have the server dump into user >>>> Maildirs. It's probably the easiest thing. Bear in mind, though, >>>> that user management for Maildir setups can be quite complex if >>>> you have a lot of users. >>>> >>>> If you want to use a database, there are least 3 methods. >>>> >>>> 1. Use DBMail through IMAP/API. I'm still not sure if there's an >>>> api/protocol that will allow you to query/manipulate at a >>>> global/root level. >>>> >>>> 2. Use DBMail directly through SQL. It's been discouraged here, >>>> so at the very least you're not going to get any help doing it. >>>> >>>> 3. Implement LMTP yourself or else use a Milter to store you >>>> messages. I've seen simple examples of LMTP code around. Milters >>>> are easier to implement, but not as clean doing it through LMTP. >> >> >> _______________________________________________ >> DBmail mailing list >> [email protected] >> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail > _______________________________________________ > DBmail mailing list > [email protected] > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail > _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
