|
»
« Return to Thread: Questions about initial DBmail setup
Re: Questions about initial DBmail setup
by Paul J Stevens
::
Rate this Message:
Josh Berkus wrote:
> Paul,
>
>>> Keen! Hopefully I'll be able to do a write up on replicated e-mail
>>> with dbmail ...
>> On postgresql perhaps?
>
> What, like I'd use something else? ;-)
THing is people talk a lot about pros and cons of running dbmail on a
mysql-replication setup. But I havent heard from anyone doing
replication on postgresql.
>
>> In 2.3+ attachments are indeed stored as atomic blobs in the mimeparts
>> table. The rfc822 header part of the complete message, and the
>> headerpart of attached mimeparts is also stored as blob in the mimeparts
>> table. Mimeparts are linked into actual messages by the partlists table.
>> Retrieval put the right blobs in the right order and depth, separated by
>> the correct boundary.
>
> Are you using BYTEA or LO for PostgreSQL? The former is vastly easier to
> manage.
bytea.
>
>> More to the point: it looks like I
>> have to rewrite the whole mime parser from scratch. GMime is not
>> threadsafe, and adding mutex locks appears to completely kill
>> performance. But then again, things may be not quite that bad after all.
>> I havent figured it out quite yet. Which makes it just one of those
>> things: they take time to work themselves out.
>
> Hmmm. I don't know mime parsers *at all*. Are you storing the attachments
> in MIME form, or in original format?
Mimepart headers and body are stored as-is in the original message, but
separately to maintain atomicity of the bodyparts even when used in
different attachments. Decoding base64 wouldn't add much benefit other
than somewhat better coverage for text searches in message bodies.
Marginal at best.
--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail@...
https://mailman.fastxs.nl/mailman/listinfo/dbmail
> Paul,
>
>>> Keen! Hopefully I'll be able to do a write up on replicated e-mail
>>> with dbmail ...
>> On postgresql perhaps?
>
> What, like I'd use something else? ;-)
THing is people talk a lot about pros and cons of running dbmail on a
mysql-replication setup. But I havent heard from anyone doing
replication on postgresql.
>
>> In 2.3+ attachments are indeed stored as atomic blobs in the mimeparts
>> table. The rfc822 header part of the complete message, and the
>> headerpart of attached mimeparts is also stored as blob in the mimeparts
>> table. Mimeparts are linked into actual messages by the partlists table.
>> Retrieval put the right blobs in the right order and depth, separated by
>> the correct boundary.
>
> Are you using BYTEA or LO for PostgreSQL? The former is vastly easier to
> manage.
bytea.
>
>> More to the point: it looks like I
>> have to rewrite the whole mime parser from scratch. GMime is not
>> threadsafe, and adding mutex locks appears to completely kill
>> performance. But then again, things may be not quite that bad after all.
>> I havent figured it out quite yet. Which makes it just one of those
>> things: they take time to work themselves out.
>
> Hmmm. I don't know mime parsers *at all*. Are you storing the attachments
> in MIME form, or in original format?
Mimepart headers and body are stored as-is in the original message, but
separately to maintain atomicity of the bodyparts even when used in
different attachments. Decoding base64 wouldn't add much benefit other
than somewhat better coverage for text searches in message bodies.
Marginal at best.
--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail@...
https://mailman.fastxs.nl/mailman/listinfo/dbmail
« Return to Thread: Questions about initial DBmail setup
| Free embeddable forum powered by Nabble | Forum Help |
