Re: 2.3.2. users heads up

Paul J Stevens wrote:
> Jorge Bastos wrote:
>   
>> I changed mine to 50M, wich will mean an attach of
50M, per message,
>> correct?.
>>     
>
> No. That means a maximum of 50M per attachment, not per
message.
>   
Are you storing the data straight in to a blob? or is it
still base64 
encoded? Is it is still encoded might need to allow large
than 50M to 
allow a 50M attachment.

S
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

Simon Gray wrote:
> Paul J Stevens wrote:
>> Jorge Bastos wrote:
>>  
>>> I changed mine to 50M, wich will mean an attach
of 50M, per message,
>>> correct?.
>>>     
>>
>> No. That means a maximum of 50M per attachment, not
per message.
>>   
> Are you storing the data straight in to a blob? or is
it still base64
> encoded? Is it is still encoded might need to allow
large than 50M to
> allow a 50M attachment.

It is the attachment size that matters. The attachment
as-is. No
decoding is done during storage. Dbmail doesn't care if
you're using
base64, uuencoding, or raw 8bit data. Just as long as it's
MIME compliant.


-- 
 
____________________________________________________________
____
  Paul Stevens                                      paul at
nfg.nl
  NET FACILITIES GROUP                     GPG/PGP:
1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail