squirrelmail cannot decode budystructure of email?

[Tenaka]

hi there,

I have a problem with tthe following message:

viewed with outlook:

From: Mail Delivery System [MAILER-DAEMON@h898552.serverkompetenz.net]
Subject: Undelivered Mail Returned to Sender

Your message did not reach some or all of the intended recipients.

Subject: www.Hai-Hui.net - Confirmarea inregistrarii
Sent: 29.08.2006 11:43

The following recipient(s) could not be reached:

andreeea@yahoo.com on 29.08.2006 11:43
The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.
< h898552.serverkompetenz.net #5.0.0 X-Postfix; host mx1.mail.yahoo.com[4.79.181.14] said: 554 delivery error: dd This user doesn't have a yahoo.com account (andreeea@yahoo.com) [-5] - mta181.mail.mud.yahoo.com (in reply to end of DATA command)>

trying to view it from squirrelmail:

SquirrelMail could not decode the bodystructure of the message
The bodystructure provided by your IMAP server:

(("text" "plain" NIL NIL "Notification" "8bit" 631 15 NIL NIL NIL)("message" "delivery-status" NIL NIL "Delivery report" "8bit" 519 NIL NIL NIL)("message" "rfc822" NIL NIL "Undelivered Message" "8bit" 1905 ("Tue, 29 Aug 2006 10:43:01 +0200" "www.Hai-Hui.net - Confirmarea inregistrarii" (("\\www.Hai-Hui.net\\" NIL "info" "hai-hui.net")) (("\\www.Hai-Hui.net\\" NIL "info" "hai-hui.net")) (("\\www.Hai-Hui.net\\" NIL "info" "hai-hui.net")) ((NIL NIL "andreeea" "yahoo.com")) NIL NIL NIL "<d9446ec18f48c2c15a5549847e96b4db@www.hai-hui.net>") (("text" "plain" ("charset" "iso-8859-2") NIL NIL "8bit" 374 14 NIL NIL NIL)("text" "html" ("charset" "iso-8859-2") NIL NIL "8bit" 454 15 NIL NIL NIL) "alternative" ("boundary" "b1_d9446ec18f48c2c15a5549847e96b4db") NIL NIL) 59 NIL NIL NIL) "report" ("report-type" "delivery-status" "boundary" "6A13E6281DA.1156840991/h898552.serverkompetenz.net") NIL NIL)

any ideas? I found some hints with google, but those problems were mostly concerned with decoding us_ascii encoded mails coming from yahoo, but this is a self generated mail by my system, so I was wondering.....

[falko]

Maybe this helps you: http://www.squirrelmail.org/wiki/Sup...tipleLanguages

[Tenaka]

thx.

before I go ahead an read all that huuuuge text, one more question:

the text is mostly concerned with a problem of squirrelmail, and aims at installing all possible locales, what I was wondering is why do I have problems displaying a self generated mail by my own system???

I mean I can read mails I send to myself with squirrelmail, so why can't I read mails from Mail Delivery System [MAILER-DAEMON@h898552.serverkompetenz.net] which is my server?

Are you sure I have to look for the source of the problem at squirrelmail?

###edit###

I would like to squeeze another squirrelmail question in here, recently I realized I have display problems with messages bigger than aprox. 10 or 12MB - I see a mail in my inbox with 15 MB click on it and the page stays white? where to look for trouble? the usual php.ini values are all >32MB....

[falko]

Originally Posted by Tenaka

I would like to squeeze another squirrelmail question in here, recently I realized I have display problems with messages bigger than aprox. 10 or 12MB - I see a mail in my inbox with 15 MB click on it and the page stays white? where to look for trouble? the usual php.ini values are all >32MB....

What's in Apache's error log?

[Tenaka]

hi there - same problem with roundcube so its not the webmailer.

do not find anything inside the error logs, tried looking inside the /var/log/httpd/ispconfig_access_log there should be any apache log inside there?

by the way I checked mail logs too seems tehre is no error there....

[Tenaka]

ok, I just tried squirrelmail development version: 1.5.1 and I can open mails bigger than 5-6MB so its back to checking whats wrong with sq instead of looking at log files...

still the bodystructure of those strange mails cannot be displayed...

I am digging deeper now ;-)

[falko]

Originally Posted by Tenaka

do not find anything inside the error logs, tried looking inside the /var/log/httpd/ispconfig_access_log there should be any apache log inside there?

I think the error log is in /var/log/apache2.

[Tenaka]

ok this is how I understood ispcfg was working: all logs go to /var/log/httpd/ispconfig_access_log so this is the place to check in realtime, after the nightly provessing the access log and error log are split and put in the coresponding /var/www/webxx/log folders?

am I wrong here?

[Tenaka]

ok I finally found the error here, by doing a tail -f /var/log/error.log

this is an excerpt:

[Thu Sep 07 23:09:53 2006] [notice] child pid 7947 exit signal Segmentation fault (11)
Allowed memory size of 33554432 bytes exhausted (tried to allocate 140 bytes)
[Thu Sep 07 23:10:29 2006] [notice] child pid 8074 exit signal Segmentation fault (11)

I tried clicking on a 5MB mail and it opened, I tried clicking on a 15MB mail and got this error...

can you tell me more about these settigns:

max_execution_time = 30
max_input_time = 60
memory_limit = 32M

from my php.ini - are these 32MB the limit for one php process? or is it sitewide? why would a 15MB mail exhaust 32MB ?

what settings would you recommend on a AMD 3000MHZ 1GB Ram 2x80gb software raid server running mail,web,dns, etc. services for severall small sites, not a lot of sites hosted here...

###edit###

there must be something wrong with squirrelmail, like I said with version 1.5.1 it worked with the 32MB limit, I set it to 64MB now and look what I got:

Allowed memory size of 67108864 bytes exhausted (tried to allocate 140 bytes)
[Thu Sep 07 23:16:35 2006] [notice] child pid 8597 exit signal Segmentation fault (11)

[falko]

Originally Posted by Tenaka

ok this is how I understood ispcfg was working: all logs go to /var/log/httpd/ispconfig_access_log so this is the place to check in realtime, after the nightly provessing the access log and error log are split and put in the coresponding /var/www/webxx/log folders?

That's right, but not for the error log. The error log is still written in /var/log/apache2/error.log (or similar).