On 07/20/2013 01:17 PM, Axel Rau wrote:
Recording of utf-8 characters from headers in mainlog and PostgreSQL DB via
lookup usually works flawlessly.
Occasionally PostgreSQL complains during INSERT of header items or main log
events (our log host uses PostgreSQL as bakend) about invalid byte sequence,
like here:
[1\3] 1V085d-00067H-9X H=mail03.noris.net [62.128.1.223] Warning: ACL "warn" statement
skipped: condition test deferred: PGSQL: query failed: ERROR: invalid byte sequence for encoding
"UTF8": 0xfc
2013-07-19T10:39:10.005396+00:00 db1 rsyslogd: db error (22021): invalid byte sequence
for encoding "UTF8": 0xfc
2013-07-19T10:39:10.005415+00:00 db1 rsyslogd: db error (event):
|2013-07-19t10:39:09.991124+00:00|6|2|mx4|exim| [2\3] (PGRES_FATAL_ERROR) (SELECT *
FROM record_Reception( '1525916', '1V085d-00067H-9X', 'Staatstheater Nürnberg
<[email protected]>', 'Newsletter Staatstheater Nürnberg',
'none', 'N/A'))
Does this come from bad encoding of original mail headers?
It seems likely from the complaint coming from pgsql,
but you've not shown us any relevant bit of your exim config.
Can you duplicate the situation manually?
Can you identify the lines in your exim config that are responsible?
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim
details at http://www.exim.org/ ##
