Sent e-mails aren't actually sent (Outlook 2003, ZCO 4.5.5)

[ILLCOMM]

Outlook 2003
ZCO 4.5.5_GA_831_4.5.230

Logging (including Http) is attached.

I opened Outlook, sent an e-mail (it went into the sent folder in Outlook), and then closed Outlook. That is the extent of the log. The e-mail was never received.

In advance, thanks for your help!

[mmauleon]

I reported the same thing, one thing can you look at your /tmp partition is full. I have a few gigs of tmp partition and zimbra just like to eat it and not do a cleanup. Might be the cause of our problems. I'm still investigating this.

[henry]

There is a bug in the bugzilla related to this problem
Bug 20168 - ZCO failed to send a message

just a tip.
make sure that you have enough space on the disk where
zdb file is located and where temporary files are being created (%TEM% %TMP% variables)

[ILLCOMM]

Originally Posted by henry

There is a bug in the bugzilla related to this problem
Bug 20168 - ZCO failed to send a message

just a tip.
make sure that you have enough space on the disk where
zdb file is located and where temporary files are being created (%TEM% %TMP% variables)

That bug applies to 5.0.0 and Outlook 2007. I figured since I was running another code base and Outlook version it didn't apply.

There is room in %TMP%

Thanks!

I am open to any other suggestions. Were the logs helpful?

[alee]

Originally Posted by ILLCOMM

That bug applies to 5.0.0 and Outlook 2007. I figured since I was running another code base and Outlook version it didn't apply.

There is room in %TMP%

Thanks!

I am open to any other suggestions. Were the logs helpful?

the logs were helpful bit it seems that you are having different issues than what we've seen in the past for this issue. the send failed for your message and there was another failure in trying to generate an NDR (non-delivery report) in your inbox. the questions that need to be addressed by our engineering team is "why did the send fail?" (there is nothing in the logs) and "why did the NDR fail to be generated?" (maybe enough information).

the bug that is being used to track this issue is a top priority bug so we are going to try to resolve this issue right away.

[ILLCOMM]

Originally Posted by alee

the logs were helpful bit it seems that you are having different issues than what we've seen in the past for this issue. the send failed for your message and there was another failure in trying to generate an NDR (non-delivery report) in your inbox. the questions that need to be addressed by our engineering team is "why did the send fail?" (there is nothing in the logs) and "why did the NDR fail to be generated?" (maybe enough information).

the bug that is being used to track this issue is a top priority bug so we are going to try to resolve this issue right away.

Thank you Anthony. Please let me know what I can do to get you the information you need (additional logging, etc).

[alee]

Originally Posted by ILLCOMM

Thank you Anthony. Please let me know what I can do to get you the information you need (additional logging, etc).

actually, i just saw a mime conversion failure in the logs. this is the answer to "why did the message not send?".

29-09-2007 13:00:11 [7340]: DEBUG: Zimbra::Rpc::UserSession::GetSupportObject - m_pMapiSup = 0x01342ba8
29-09-2007 13:00:11 [7340]: ZimbraXPLogon::SubmitMessage - mime conversion failed, hr: 80004005

[ILLCOMM]

Originally Posted by alee

actually, i just saw a mime conversion failure in the logs. this is the answer to "why did the message not send?".

29-09-2007 13:00:11 [7340]: DEBUG: Zimbra::Rpc::UserSession::GetSupportObject - m_pMapiSup = 0x01342ba8
29-09-2007 13:00:11 [7340]: ZimbraXPLogon::SubmitMessage - mime conversion failed, hr: 80004005

forgive my ineptitude, but how do I correct the MIME issue?

[alee]

Originally Posted by ILLCOMM

forgive me ineptitude, but how to I correct the MIME issue?

if it is truly a mime conversion issue, than there is nothing that you can do and the onus would be on us to figure out what our mime conversion code doesn't like the mime for the message being sent. its also possible that the mime conversion failure is a red herring. the real problem might lie someplace in the mime conversion routine but not the actual mime conversion.