> I tried changing the type from bytea to oid, PostgreSQL's blob type. This
> doesn't help much since James now failed to store the message to the
spool.
I haven't looked. Matching change needed on the store side?
> The thing could be fixed easily by a try/catch construction wich first
> tries the blob and when it fails tries the byte array wich the old
> version used, but it's not really a very clean solution.
No it isn't, but I'd like to support the wider range if we can.
> Another, somewhat related thing i noticed is the fact that Exceptions
during
> mail storage are output to the mail session. This causes a multiline
> response in way that is irrc in violation of the SMTP rfc.
Please submit a bug report, preferably with a short patch.
> Just out of curiosity, do you have any insight in what databases people
> use with james and wheter they are all tested with the RCs?
They get tested on whatever people run them on. I, personally, use MySQL in
production and testing. I think that some others use MSSQL. Your guess is
as good as mine for which databases are getting tested each time. We don't
have any formal testing volunteers. Apparently, Oracle, DB2 and PostgreSQL
do get tested because Steve Short posted the fix for the first two, and two
of you have since run into a problem with PostgreSQL due to the fix.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
