Domino Web Access - Attachments on sent email

Have had a search through the forum but can’t find anything that matches up with this issue.

Environment is as follows:

3 Domino 6.03 servers, 2 of which are in a cluster and provide webmail to our users.

Users are using either the inotes60.ntf or the inotes6.ntf template on their database.

Problem is as follows:

User creates an email, types in the body text, and attaches a file to the email, then sends. Recipient opens the email and it contains no text or an attachment - just the subject line.

Sender then checks the Sent folder and the sent email is the same - has a subject but has no bodytext and no attachment.

This doesn’t occur on all emails sent - just intermittently (I could call one of the affected people up a few minutes after they have logged the issue and it will work)

Originally I suspected the issue was with the inotes60.ntf template and my solution was to upgrade them to the inotes6.ntf template - this temporarily alleviated the problem but it is now affecting more people.

Anyone know of any settings on the Domino server which could cause this issue?

Thanks in advance,

Dave

Subject: I may have found a link between the affected users

Checking back through our logs regarding the issue, it looks like Internet Explorer IE 5.5 may be the browser used by all the affected users.

Subject: nope…not that

Affecting 5.5 and 6+ IE browsers :frowning:

Subject: RE: nope…not that

Check quota.

Perhaps user doesnt have quota to send that attachment. Try delete some emails…then empty garbage…then try again

Sorry this answer its after 1 year

Subject: Domino Web Access - Attachments on sent email

Dave,

We also have the same problem with are running Domino on OS/390.

This problem is also present if your iNotes (Domino Web Access) users have Quotas and limits set. If these users are approaching or over the limit set this problem happens.

We upgraded the server code only from Domino R6.0.1 CF1 but did not upgrade the iNotes template.

You may also find that the problem may be due to the encoding of text being in Base64 instead of Binary in previous release.

However,IBM have now informed us that this is a known SPR, in this release.