Obsolete Releases > SME 8.x Contribs

blank screen at SMTP with attachments

<< < (2/5) > >>

CharlieBrady:

--- Quote from: detlevp on October 15, 2012, 05:35:11 PM ---Thanks for your help. The problem lies in the SME Server, not the clients.  :-(

--- End quote ---

No, the problem lies with eGroupware or SoGo, neither of which is SME server software. Or perhaps the problem is with your expectation, that you can safely send humungous attachments via email.

CharlieBrady:

--- Quote from: detlevp on October 15, 2012, 06:06:25 PM ---In addition, the e-mail attachment is 10.5 MB in size. Strange that the error occurs at something around 12 MB.

--- End quote ---

That's not strange at all. Binary files always grow when they become email attachments, as they are encoded in base64 ascii and then encapsulated with MIME and SMTP headers.

detlevp:
Hello Charlie,


--- Quote from: CharlieBrady on October 15, 2012, 09:47:28 PM ---That's not strange at all. Binary files always grow when they become email attachments, as they are encoded in base64 ascii and then encapsulated with MIME and SMTP headers.

--- End quote ---
Yes, this is familiar to me. It is due to my poor English that my texts are partially taken out of context. Sorry.

detlevp:
Hello again,

I'm very grateful for the SOGo-Implementation and -guidance for SME-Server.

I still, however, a communication problem.  I send a mail with a file attachment with the size of 8271 KB on SOGo.  Unfortunately, I get the message "Warning can not send message: (smtp) failure when sending data." The file is 11.1 MB in size when sending. In SOGo log I find the following information:

================================================================
C: connect to <0x0x8dd9418[NGInternetSocketAddress]: host=localhost not-filled>
S: <SMTP-Reply: code=220 line='domsrv01.domain.com ESMTP'>
C: EHLO localhost
S: <SMTP-Reply: code=250 line='STARTTLS'>
S: pipelining extension supported.
S: size extension supported.
C: MAIL FROM:<admin@domain.com>
C: RCPT TO:<user@arcor.de>
C: DATA
S: <SMTP-Reply: code=354 line='go ahead'>
C: data(135430288 bytes) ..
2012-10-16 01:22:40.785 sogod[4307] WARNING(-[NGBufferedStream writeBytes:count:]): got passed in length 129MB (135430288 bytes, errcode=2147$
S: <SMTP-Reply: code=552 line='Message too big!'>
2012-10-16 01:22:48.932 sogod[4307] SMTP(DATA): mail input failed, got code 552 ..
C: QUIT
S: <SMTP-Reply: code=221 line='teske-schwiede.de closing connection. Have a wonderful day.'>
================================================================
I do not understand why in the log file, the mail is given as 129 MB, though the file is only 11.1 MB in size. Says the NGBufferedStream that here regardless of the size of the mail is sent in an entire block size memory_limit? Can anyone help me here. I have try it with Outlook (not my favorite), same result.

Greeting
Detlev

janet:
detlevp

Is that related to the setting in php ie
memory_limit 128M 128M

You were told earlier in this thread by Stefano to look at the wiki etc for the answer, did you ?
"I'm quite sure the solution is available here in the forums and in the wiki/FAQ, so please use the search link above, thank you"

Have you specified more appropriate values in sme server for large files (uploads) & emails (attachment size), see the following for likely possibilities
http://wiki.contribs.org/SME_Server:Documentation:FAQ#Set_max_email_size
and
http://wiki.contribs.org/SME_Server:Documentation:FAQ#Large_attachments_not_displaying_in_webmail
and
http://wiki.contribs.org/DB_Variables_Configuration#Database_variables
and
http://wiki.contribs.org/DB_Variables_Configuration#Php
and
http://wiki.contribs.org/DB_Variables_Configuration#Clam_AntiVirus_.28clamav.29
and
http://wiki.contribs.org/Useful_Commands#PHP_Related_Commands

If the above is not enough info, then search the Forums for specific examples, eg search on webmail attachment size limit

Navigation

[0] Message Index

[#] Next page

[*] Previous page