I am observing the following behaviour when logging to syslog from an external application: if I send a well-formed syslog message to a UDP socket, rsyslog correctly parses it, however if the very same message is sent to a UNIX domain socket (/dev/log), it is not parsed at all (rsyslog basically assumes, that everything, that he received, is a message, so no timestamp, no anything).
The message in question is
<142>1 2010-12-29T11:11:11Z foo bar 123 baz - A Message
which is parsed as
Dec 29 11:11:11 foo bar A Message
unless it isn't.