thanks for the fast reply !

well, my biggest fear here is that my boss (or better : the project leader... he's not really in charge) is no idea at all about where this project is going... And the client allready signed the contract, fortunately (for me (the PHP-programmer)) without a deadline on paper

so i really really need the most *open* solution. I can handle some complexity, but i would really find my head in my ass if one day i find out that the tech-side solution proposed by me turns out to be a dead-end

are there other mail-processing back-ends that you would suggest considering ? so far, DBMail seemed to be quite appropriate. Much more than trying to get postfix do the job with a ton of patches & hooks... I looked into cyrus too, but it seems to very hard to integrate in database-driven website...

ah well, it's late (over here). I'll talk to the boss tomorrow

thanks again !

Jeroen


jeroen clarysse wrote:
Hi all,
a rather generic question from a newcomer to this list. Please forgive me if i'm way off topic ! My boss asked me to do some research on an upcoming project which will mainly revolve around a website which serves as a central messaging point among what is best described through an analogy with the publishing world : article authors, article reviewers and journal editors come together on a website on which the editors will send and receive messages to and from authors and reviewers. These messages must be answerable by mail, but also searchable via a web front end which includes a lot more than only messages (for instance it will include article-status or reviewer history, etc etc) my first job is to figure out which backend to use on the server so that we can have a system that nicely archives all messages and can talk via POP/IMAP, but is also smoothly integrated into a bigger content. So here goes the question : is DBMail fit for this ? Or is DBMail not intended as a backend for a web-frontend (what a scentence...) ? Would DBmail be an overkill ? Or perhaps not easy enough to integrate into a website ?
Well that wasn't the orig idea behind DBMail, but I would think that it would be pretty well suited to that simply because of the database backend. So long as your app had database access, you could query the DB directly or generate static pages to index from the content.

On the flip side an email system like courier or cyrus could also be indexed... although you might have more issues with cleaning out header information.

DBmail developers might be able to give you a better sense of how to index the body of each message....

Good luck with that, cool idea!


sorry if this is a silly question, but the documentation on the website isn't really clear to me on this matter...
many thanks in advance !
Jeroen
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail


_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail


Reply via email to