Why?1. Ray Bilyk22/01/2008 11:46:26
Homepage: http://www.thepridelands.com
Could it be a bulk message that is requiring a X.509 certificate, but is seeing 'Undisclosed Recipient' instead of a real name?
Just a shot in the dark... because right now in Michigan, it's dark.
2. Chris Linfoot22/01/2008 12:30:55
No x.509 cert.
It was caused by:
- To field contained "<Undisclosed-Recipient:;> (real recipient was bcc)
- There was a remotely served image in the HTML part (img src="http...").
- I'm using Notes 8 and have "do not show remote images without my permission" set
- After I loaded the remote image, the errant dialog shown above was not displayed again.
Seems that Notes is doing some form of validation of the sender of the email while rendering HTML parts containing remote images.
3. Dan Murphy10/11/2008 17:36:37
I would like a work around to this. I don't want to enable ALL remote images... just some. So, I thought maybe I should re-read the message "do not show remote images without my permission" ... That makes me wonder -- what are LOCAL images? Does anyone know? Maybe by putting the images in the right place (client's notes directory???) they would display??? 
4. Chris Linfoot11/11/2008 09:04:54
Remote images are images referred to by http:// locations in the HTML part of an email. That is, the HTML will say something like
<img src="http://...>
The benefit of remote images is that only the HTML needs to be transported with the message, which makes the email much smaller. The drawback, and the reason that remote images are often blocked, is that these can be used to track who has read an email.
The opposite of remote image is therefore not strictly local. It might be more accurate to call it in-line or something like that.
In-line images in email are contained in a multipart/related MIME wrapper where the first related part is usually the HTML part of the email. They are thus transported with the email, increasing its size, but cannot be used to track who has read an email and are often regarded as safe to load without user intervention.
In-line images are generally base64 encoded MIME parts and have a MIME attribute called a content id tag. The HTML part of the email refers to them thus:
<img src="cid:...">
This will not help you if you want to be able to select which http locations are considered safe and from which images should be loaded without user intervention.
However, adding the sender to a local address book should help.
Unable to post a comment? Please read this for a possible explanation...
- 