firstname.lastname@example.org very helpfully documented the odd behavior Outlook shows when dealing with line breaks in a most useful manner:
"Every message starts with continuation off.
Lines less than 40 characters long do not trigger continuation, but if continuation is on, they will have their line breaks removed.
Lines 40 characters or longer turn continuation on. It remains on until an event occurs to turn it off.
Lines that end with a period, question mark, exclamation point or colon turn continuation off. (Outlook assumes it's the end of a sentence?)
Lines that turn continuation off will start with a line break, but will turn continuation back on if they are longer than 40 characters.
Lines that start or end with a tab turn continuation off.
Lines that start with 2 or more spaces turn continuation off.
Lines that end with 3 or more spaces turn continuation off.
Please note that he tried all of this with Outlook 2007.
So if possible, you can end messages with a sentence-terminating punctuation mark, or even a tab."
Big yourself up mtruesdell this has been doing my head in the last 2 hours!
Tuesday, 9 March 2010
Monday, 8 March 2010
I have been seeing what I thought was a botnet virus on my network trying to talk to it's command and control server via constant UDP to everyone on port 34447! I had two laptop clients doing it and their owners where none the wiser. I reported this to HP's internal security teams to see if it was known to them and for them to get solving. One just stopped with no info from it's owner and the other was eventually rebuilt. Now I look at the users machine I note it runs a print server! A HP wireless print server! I smell the potential FAIL as most these products are made in India and Eastern Europe like their drivers, so I disable it. Bingo no more UDP broadcasts!
This is what the client running the print server sends:
438.407640 x.x.x.x -> 255.255.255.255 UDP Source port: 49906 Destination port: 34447
The source port moves but is sometimes reused the rest is static.