Re: Problem with attachments sent through NeoMail interface

Jason Marshall schrieb:
...
> > If you want to find it better, make:
> >
> > warn ("The size of the upload before encoding");
> > warn (length($attcontents));
> > $attcontents = encode_base64($attcontents);
> > warn ("The size of the upload after encoding");
> > warn (length($attcontents));
> >
> > and search for 'The size of the upload' in your
> > apache error logfile.
> >
> > Torsten
> >
> 
> Torsten,
> 
> The warn() output was just not making it to any of the
> error files that my web server (Resin) outputs to. I
> ended up opening a new file to output the length of
> $attcontents to.
> 
> After doing so, I got the interesting result of a size
> of zero before and after the call to encode_base64().
> 
> I guess this would mean that the problem is outside of
> neomail at this point, and perhaps in the way Resin is
> handling CGI?

Again:
Please do not reply in PM, use the mailinglist.

Yes, i would assume the same.
However, we isolated the problem a little bit with
checking the upload size.
As i read http://www.caucho.com/quercus/faq/question.xtp?question_id=469
it seems, that CGI support is done by a Servlet.

At this point i can't help you more, as i don't have
any experiences with this servlet.

Possibly you can ask at their mailinglist (Resin)
how other users handle fileuploads with the CGI servlet.

If you find an answer / or not, drop a note on this list too,
that the archive has an answer for future users of
Resin/neomail.

Torsten


-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/