Zimbra

sholden · #1 (**permalink**) 11-12-2007, 10:31 AM

The error mail contains in the body:

Error: This message could not be sent.

Subject: [THE SUBJECT]
To: [the to person]
CC: [the cc person]

Note: File Upload Fault. Please contact your system administrator regarding maximum message and attachment sizes.

Error Code: 401
Error Text: 401,'null'
<<...>>

The zco.log contains:

Code:

12-11-2007 10:59:11.609 [2576]: TRACING => ProgressTask::ProgressTask this(0x3bea900)
12-11-2007 10:59:11.609 [2576]: TRACING => Zimbra::Rpc::Connection::GetNewProgressTask - _pProgressTask(0x3bea900)
12-11-2007 10:59:11.609 [2576]: *5* Enter Zimbra::Rpc::Connection::DoFileUpload ...
12-11-2007 10:59:11.609 [2576]: *5* <<<<-------- HTTP stream Start (Request) ----------------------------------------------->>>>
12-11-2007 10:59:11.609 [2576]: *5* AuthToken =
12-11-2007 10:59:11.609 [2576]: *5* Url = /service/upload?fmt=raw
12-11-2007 10:59:11.609 [2576]: *5* FilePreamble: (null)
12-11-2007 10:59:11.609 [2576]: *5* Original file contents with length of 53686 bytes:
12-11-2007 10:59:11.609 [2576]: *5* Enter Zimbra::Rpc::Rfc1876Helper::DoFileUpload ...
12-11-2007 10:59:12.62 [2576]: *5* Rfc1876Helper::DoFileUpload - Done with read from file stream, total bytes to read: 53686, total bytes read: 53686
12-11-2007 10:59:12.62 [2576]: *5* HTTP body:
----B-00=_NQHEB220$i40$S00aR00
Content-Disposition: form-data; name="requestId"

lsrpc32-client-id
----B-00=_NQHEB220$i40$S00aR00
Content-Disposition: form-data; name="lslib32"; filename="lslib32.bin"
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary

[INSERT THE EMAIL HERE]

12-11-2007 10:59:12.62 [2576]: *5*
12-11-2007 10:59:12.625 [2576]: *5* DEBUG: Zimbra::Rpc::Connection::WriteToHttp, Byte written so far in current segment: 54006
12-11-2007 10:59:12.625 [2576]: *5* Rfc1876Helper::DoFileUpload - Done with written to Http, total bytes to write: 54006, total bytes written: 54006
12-11-2007 10:59:12.625 [2576]: *5* HTTP Headers:
12-11-2007 10:59:12.625 [2576]: POST /service/upload?fmt=raw HTTP/1.1
Cookie: ZM_AUTH_TOKEN=
Content-Type: multipart/form-data; boundary=--B-00=_NQHEB220$i40$S00aR00
User-Agent: Zimbra-ZCO/5.0.306 (5.1.2600 Service Pack 2; en-US)
Host: zimbra.steeprockinc.com
Content-Length: 54006
Connection: Keep-Alive
Cache-Control: no-cache
Pragma: no-cache
12-11-2007 10:59:12.625 [2576]: *5* Exit Zimbra::Rpc::Rfc1876Helper::DoFileUpload ...
12-11-2007 10:59:12.625 [2576]: *5* <<<<-------- HTTP stream End (Request) ----------------------------------------------->>>>
12-11-2007 10:59:12.625 [2576]: *5* <<<<-------- HTTP stream Start (Response) ----------------------------------------------->>>>
12-11-2007 10:59:12.625 [2576]: *5* DEBUG: in Zimbra::Rpc::Connection::ReadResponseFully - content-length in http response header: 12
12-11-2007 10:59:12.625 [2576]: *5* HTTP Headers:
12-11-2007 10:59:12.625 [2576]: HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/html;charset=ISO-8859-1
Content-Length: 12
Date: Mon, 12 Nov 2007 15:59:18 GMT
12-11-2007 10:59:12.625 [2576]: *5* HTTP body:
401,'null'

12-11-2007 10:59:12.625 [2576]: *5*
12-11-2007 10:59:12.625 [2576]: *5* DEBUG: in Zimbra::Rpc::Connection::ReadResponseFully - Total bytes read from wire: 12
12-11-2007 10:59:12.625 [2576]: *5* <<<<-------- HTTP stream End (Response) ----------------------------------------------->>>>
12-11-2007 10:59:12.625 [2576]: *5* Exit Zimbra::Rpc::Connection::DoFileUpload ...
12-11-2007 10:59:12.640 [2576]: ERROR: in Zimbra::Rpc::ZimbraConnection::DoFileUpload - no server token returned, error status: 401
12-11-2007 10:59:12.656 [2576]: ZimbraXPLogon::SubmitMessage: FileUploadFaultException => status code: '401', error text: '401,'null'
'

Another send in the same log file has

Cookie: ZM_AUTH_TOKEN=0_HEXSTRING_HEXSTRING

in its version of the above transaction.

ZCO is ZimbraOlkConnector-4.5.6_GA_1023_4.5.288.msi and the zimbra server is 4.5.5 (at least that's what searching for version in the help in the webmail UI tells me).

sam · #2 (**permalink**) 11-12-2007, 10:59 AM

Do you get the same behavior with the latest connector (4.5.9) ?

sholden · #3 (**permalink**) 11-12-2007, 11:04 AM

I haven't managed to convince the user in question and his 8GB mailbox to try upgrading it.

Nutz · #4 (**permalink**) 11-27-2007, 05:59 AM

I have been getting similar messages in 4.5.9...

sholden · #5 (**permalink**) 11-27-2007, 07:12 AM

Turns out the user in question for us, is running a BETA connector:

Zimbra Connector for Outlook 5.0.306
File Path: C:\WINDOWS\Explorer.EXE
File Version: 6.0.2900.3156

is in the log, so he's running:
ZimbraOlkConnector-5.0.0_BETA3_1277_5.0.306.msi

Which I guess might be the problem, except someone else mentioned seeing it on 4.5.9 above.

sholden · #6 (**permalink**) 01-18-2008, 08:18 AM

I'm getting this for a couple of users now.

In outlook they get an undeliverable message a screenshot of which is attached.

alee · #7 (**permalink**) 01-18-2008, 09:09 AM

Quote:

Originally Posted by sholden

The error mail contains in the body:

Error: This message could not be sent.

Subject: [THE SUBJECT]
To: [the to person]
CC: [the cc person]

Note: File Upload Fault. Please contact your system administrator regarding maximum message and attachment sizes.

Error Code: 401
Error Text: 401,'null'
<<...>>

The zco.log contains:

Code:

12-11-2007 10:59:11.609 [2576]: TRACING => ProgressTask::ProgressTask this(0x3bea900)
12-11-2007 10:59:11.609 [2576]: TRACING => Zimbra::Rpc::Connection::GetNewProgressTask - _pProgressTask(0x3bea900)
12-11-2007 10:59:11.609 [2576]: *5* Enter Zimbra::Rpc::Connection::DoFileUpload ...
12-11-2007 10:59:11.609 [2576]: *5* <<<<-------- HTTP stream Start (Request) ----------------------------------------------->>>>
12-11-2007 10:59:11.609 [2576]: *5* AuthToken =
12-11-2007 10:59:11.609 [2576]: *5* Url = /service/upload?fmt=raw
12-11-2007 10:59:11.609 [2576]: *5* FilePreamble: (null)
12-11-2007 10:59:11.609 [2576]: *5* Original file contents with length of 53686 bytes:
12-11-2007 10:59:11.609 [2576]: *5* Enter Zimbra::Rpc::Rfc1876Helper::DoFileUpload ...
12-11-2007 10:59:12.62 [2576]: *5* Rfc1876Helper::DoFileUpload - Done with read from file stream, total bytes to read: 53686, total bytes read: 53686
12-11-2007 10:59:12.62 [2576]: *5* HTTP body:
----B-00=_NQHEB220$i40$S00aR00
Content-Disposition: form-data; name="requestId"

lsrpc32-client-id
----B-00=_NQHEB220$i40$S00aR00
Content-Disposition: form-data; name="lslib32"; filename="lslib32.bin"
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary

[INSERT THE EMAIL HERE]

12-11-2007 10:59:12.62 [2576]: *5*
12-11-2007 10:59:12.625 [2576]: *5* DEBUG: Zimbra::Rpc::Connection::WriteToHttp, Byte written so far in current segment: 54006
12-11-2007 10:59:12.625 [2576]: *5* Rfc1876Helper::DoFileUpload - Done with written to Http, total bytes to write: 54006, total bytes written: 54006
12-11-2007 10:59:12.625 [2576]: *5* HTTP Headers:
12-11-2007 10:59:12.625 [2576]: POST /service/upload?fmt=raw HTTP/1.1
Cookie: ZM_AUTH_TOKEN=
Content-Type: multipart/form-data; boundary=--B-00=_NQHEB220$i40$S00aR00
User-Agent: Zimbra-ZCO/5.0.306 (5.1.2600 Service Pack 2; en-US)
Host: zimbra.steeprockinc.com
Content-Length: 54006
Connection: Keep-Alive
Cache-Control: no-cache
Pragma: no-cache
12-11-2007 10:59:12.625 [2576]: *5* Exit Zimbra::Rpc::Rfc1876Helper::DoFileUpload ...
12-11-2007 10:59:12.625 [2576]: *5* <<<<-------- HTTP stream End (Request) ----------------------------------------------->>>>
12-11-2007 10:59:12.625 [2576]: *5* <<<<-------- HTTP stream Start (Response) ----------------------------------------------->>>>
12-11-2007 10:59:12.625 [2576]: *5* DEBUG: in Zimbra::Rpc::Connection::ReadResponseFully - content-length in http response header: 12
12-11-2007 10:59:12.625 [2576]: *5* HTTP Headers:
12-11-2007 10:59:12.625 [2576]: HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/html;charset=ISO-8859-1
Content-Length: 12
Date: Mon, 12 Nov 2007 15:59:18 GMT
12-11-2007 10:59:12.625 [2576]: *5* HTTP body:
401,'null'

12-11-2007 10:59:12.625 [2576]: *5*
12-11-2007 10:59:12.625 [2576]: *5* DEBUG: in Zimbra::Rpc::Connection::ReadResponseFully - Total bytes read from wire: 12
12-11-2007 10:59:12.625 [2576]: *5* <<<<-------- HTTP stream End (Response) ----------------------------------------------->>>>
12-11-2007 10:59:12.625 [2576]: *5* Exit Zimbra::Rpc::Connection::DoFileUpload ...
12-11-2007 10:59:12.640 [2576]: ERROR: in Zimbra::Rpc::ZimbraConnection::DoFileUpload - no server token returned, error status: 401
12-11-2007 10:59:12.656 [2576]: ZimbraXPLogon::SubmitMessage: FileUploadFaultException => status code: '401', error text: '401,'null'
'

Another send in the same log file has

Cookie: ZM_AUTH_TOKEN=0_HEXSTRING_HEXSTRING

in its version of the above transaction.

ZCO is ZimbraOlkConnector-4.5.6_GA_1023_4.5.288.msi and the zimbra server is 4.5.5 (at least that's what searching for version in the help in the webmail UI tells me).

can you check the max message size on the server and see if this problem only happens when users send messages that are larger than the allowed message size? this problem looks familiar.

sholden · #8 (**permalink**) 01-18-2008, 10:12 AM

Quote:

Originally Posted by alee

can you check the max message size on the server and see if this problem only happens when users send messages that are larger than the allowed message size? this problem looks familiar.

$ zmprov gacf | grep -i max
zimbraFileUploadMaxSize: 50000000
zimbraGalMaxResults: 100
zimbraMtaMaxMessageSize: 30720000
zimbraNotebookMaxCachedTemplatesPerFolder: 256
zimbraTableMaintenanceMaxRows: 1000000

The attachment on the mail the screenshot is from was 83 KB.

Nutz · #9 (**permalink**) 01-18-2008, 10:24 AM

For me this was happening when trying to send a meeting invite, which really can't be over our limit of 100 Mb.

alee · #10 (**permalink**) 01-18-2008, 10:35 AM

Quote:

Originally Posted by Nutz

For me this was happening when trying to send a meeting invite, which really can't be over our limit of 100 Mb.

yeah..i didn't catch the authtoken problem until right now.
the ZM_AUTH_TOKEN header in the file upload request needs an auth token.

this sounds like a familiar issue and i'm trying to hunt down the bug.

if i can't find it, i'll file a new one.