| Author |
|
adrian
Newbie
Joined: 22 April 2008
Online Status: Offline
Posts: 1
|
| Posted: 22 April 2008 at 5:37am | IP Logged
|
|
|
Hi,
I'm investigating integrating MailBee Pro with our hosted CRM application, and I have a few pre-sales questions. We'd be installing MailBee on a Linux server, with a separate qmail/courier-imap server acting as the mail server.
Your features list says that emails are stored in a database. Is this used as a cache to prevent MailBee having to get all emails from the IMAP server upon every login? Could it be used to provide a MySQL FullText search on emails? I read a previous post which suggested that using IMAP's native "SEARCH" method would not be appropriate in most situations because most imap implementations don't decode the message source from base64/etc before searching. If this is the case, we'd need the emails in a searchable format.
Assuming the MailBee table stores useful information about each email, we'd also like to summarise contact history outside of MailBee, so interrogating that email table directly would be ideal for this. Would this be possible?
What (broadly speaking) is the structure of the contacts database - we'd be interested in setting up a view, or pre-populating MailBee's address book table, so that users of our CRM automatically have a full address book.
Thank you for your time,
Adrian
|
| Back to Top |
|
| |
Andrew
AfterLogic Support
Joined: 28 April 2006
Location: United States
Online Status: Offline
Posts: 1189
|
| Posted: 22 April 2008 at 6:23am | IP Logged
|
|
|
Quote:
| Your features list says that emails are stored in a database. |
|
|
By default e-mail messages are stored on filesystem as standard .eml files, but there is an option to store them in a database (configurable).
Quote:
| Is this used as a cache to prevent MailBee having to get all emails from the IMAP server upon every login? |
|
|
Yes. Moreover, three types of sync mode are supported:
- Direct Mode - messages are accessed directly on mail server without storing in WebMail storage;
- Headers Only - only message headers are downloaded to the WebMail Pro storage, messages bodies and attachments are downloaded when you try to access them;
- Entire Messages - entire messages are stored in the WebMail storage.
These modes allow distributing load between mail server and the WebMail local storage.
Quote:
| Could it be used to provide a MySQL FullText search on emails? I read a previous post which suggested that using IMAP's native "SEARCH" method would not be appropriate in most situations because most imap implementations don't decode the message source from base64/etc before searching. If this is the case, we'd need the emails in a searchable format. |
|
|
Even if entire messages are stored on filesystem, their headers and decoded plain text bodies are cached in the database. This allows quick searching in message headers and bodies. Search in bodies works in Entire Messages sync mode only.
The database contains fully readable text which can be searched via SQL. WebMail Pro search engine uses LIKE clause, MySQL FullText search is not used because WebMail Pro can operate on various database engines, but each database provides specific FullText search architecture. With regard to MySQL, it's easy to customize WebMail Pro to use MySQL FullText search.
Quote:
| Assuming the MailBee table stores useful information about each email, we'd also like to summarise contact history outside of MailBee, so interrogating that email table directly would be ideal for this. Would this be possible? |
|
|
Yes.
Quote:
| What (broadly speaking) is the structure of the contacts database - we'd be interested in setting up a view, or pre-populating MailBee's address book table, so that users of our CRM automatically have a full address book. |
|
|
We'll contact you regarding this via e-mail.
Best regards,
Andrew
|
| Back to Top |
|
| |
MailBee.NET Objects 
MailBee.NET Queue 
MailBee Objects 
WebMail Pro PHP 
AfterLogic Aurora 
MailSuite Pro for Linux 
Unified Messaging Solution 
Search
Register
Login
Topic: MailBee Pro Search/Database
Privacy policy |
Refund policy