[Mimedefang] Re: sql integration of quarentine and others

[Robert Dudley]

> Hmmm base64 might be a better solution.

FWIW - I've come across this problem several times in the past with  
several different apps and have found that the quickest, most  
portable (used in both MS-SQL and MySQL 4 - 5) solution is to store  
the mail Base64 encoded.

It is wasteful but saves so much time and worry it's almost worth the  
disk overhead.

Of course if you come up with a viable alternative then I'd be  
intrigued to hear it.

Cheers and good luck

Rob

---

Robert Dudley
rob.dudley at gmail.com



On 18 Apr 2007, at 12:43, Danny Kjærgaard wrote:

>
>> What database are you using?  Maybe it has a database encoding  
>> that it wants
>> the e-mail to be in?
> Mysql 5.0
>
>>
>> We solved the problem by Base64-encoding the entire e-mail before  
>> stuffing
>> it into the database.  It wastes space, but is guaranteed not to  
>> cause
>> encoding problems.
>
> Hmmm base64 might be a better solution.
>
>>
>> (Actually, our upcoming solution is a dedicated storage-manager  
>> daemon
>> for storing e-mail bodies; it's not efficient to stuff large  
>> chunks of random
>> text into most databases.)
>
> Yeah that's my problem right now. The next step might be to reduce  
> then
> longtext, to mediumtext, but still this have insane search times,  
> and it's
> not the positive insane.
>
> Cheers.
> -Danny
>
>
> _______________________________________________
> NOTE: If there is a disclaimer or other legal boilerplate in the above
> message, it is NULL AND VOID.  You may ignore it.
>
> Visit http://www.mimedefang.org and http://www.roaringpenguin.com
> MIMEDefang mailing list MIMEDefang at lists.roaringpenguin.com
> http://lists.roaringpenguin.com/mailman/listinfo/mimedefang