Re: Outlook, we do love to hate you....
On 01/09/14 04:33, Dave Warren wrote: As I understand that, that's specifically for messages that originated within Exchange itself and had no SMTP transmission or RFC5321 or 5322 components in the first place. This dates back to Exchange's history, at which point it wasn't primarily a SMTP server, SMTP was just one possible transport. Ah - no. I sorta thought of that. Nope - it stripped existing Received headers out. Stoopid, stooopud, stped If Exchange sends the message via SMTP, or exposes it via IMAP, it constructs something more standards compliant, it's only when you export directly from Outlook that you get this mess. Yes - it's probable a MAPI thing (not IMAP). I bet Received headers are kept in some MAPI metadata blob and don't follow the main message blob when drag-n-dropped into an IMAP folder. Still - no excuse for such heinous behaviour. -- Cheers Jason Haar Corporate Information Security Manager, Trimble Navigation Ltd. Phone: +1 408 481 8171 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
Re: Outlook, we do love to hate you....
while we're having a grizzle... how about the Outlook/MAPI feature where if you copy/move an Exchange mail message onto an IMAP folder, what arrives can barely be described as a legitimate mail message: it has no Received: headers, and it's To/From lines consist of Jason Haar instead of Jason Haar email@address. You can imagine what spamassassin thinks about such messages... Words fail me... -- Cheers Jason Haar Corporate Information Security Manager, Trimble Navigation Ltd. Phone: +1 408 481 8171 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
Re: Outlook, we do love to hate you....
On 27.08.14 18:32, Matteo Dessalvi wrote: Is anybody else got in trouble due to this 'fantastic' auto responder feature? Especially when these email are generated by an Exchange server. Just curious, since the last week one of our mail server (for outbound traffic) got listed in one black list due to this 'out of office'|'vacation' messages. I am aware of the RFC3834 but not sure if our Exchange server is following it. Of course is does not. Microsoft does not follow standards. It does violate them, break them, misinterpret them... -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. They say when you play that M$ CD backward you can hear satanic messages. That's nothing. If you play it forward it will install Windows.
Outlook, we do love to hate you....
*sigh* Just got a FP report... ... about an Out of Office message... ... generated by Outlook 15... ... which, among other things, seems to go to great lengths to look like spam, by way of the HTML formatting overkill that hits a local rule for HTML comments over 32K long. *headdesk* Someone please tell me, how is it Necessary for a three-line OOO message to include more than 32K of CSS gibberish? -kgd
Re: Outlook, we do love to hate you....
On 8/27/2014 11:56 AM, Kris Deugau wrote: *sigh* Just got a FP report... ... about an Out of Office message... ... generated by Outlook 15... ... which, among other things, seems to go to great lengths to look like spam, by way of the HTML formatting overkill that hits a local rule for HTML comments over 32K long. *headdesk* Someone please tell me, how is it Necessary for a three-line OOO message to include more than 32K of CSS gibberish? -kgd Outlook shares code with MS Word for its dealings with HTML. It's usually pretty easy to detect and make exceptions for in rules.
Re: Outlook, we do love to hate you....
Since you are mentioning 'Out of office' messages Is anybody else got in trouble due to this 'fantastic' auto responder feature? Especially when these email are generated by an Exchange server. Just curious, since the last week one of our mail server (for outbound traffic) got listed in one black list due to this 'out of office'|'vacation' messages. I am aware of the RFC3834 but not sure if our Exchange server is following it. -Matteo On 27.08.2014 17:56, Kris Deugau wrote: *sigh* Just got a FP report... ... about an Out of Office message... ... generated by Outlook 15... ... which, among other things, seems to go to great lengths to look like spam, by way of the HTML formatting overkill that hits a local rule for HTML comments over 32K long. *headdesk* Someone please tell me, how is it Necessary for a three-line OOO message to include more than 32K of CSS gibberish? -kgd
