Hi
It seems dbmail-smtp uses wrong quoting.
Since we started using postgresql-8.2 it started logging:
WARNING: nonstandard use of \\ in a string literal
LINE 1: ..., messageblk,blocksize, physmessage_id) VALUES (1,'Return-
Pa...
^
H
Paul J Stevens wrote:
Matthew O'Connor wrote:
Paul J Stevens wrote:
Matt,
Could plz you run this through valgrind? I'll look into this later today
if i can.
hmm... I can try, I don't have valgrind setup at the moment. BTW, I
fixed the gdb backtrace problem (I had a ulimit set for core files
Paul J Stevens wrote:
For a very long time postgresql users have complained about charset
incompatibilities in dbmail.
This is only a problem for PostgreSQL users that have an encoding other
than SQL_ASCII, the PostgreSQL SQL_ASCII encoding basically ignores
encoding completely, which is a go
Charsets are a Nightmare!!
We know one thing for sure, converting between charsets is very ugly,
this lesson was learned when trying
to synchronise a swedish (latin9) cvs with svn which is UTF8
The above problem was in the fact, that svn was implemented UTF8
without backsight to the possib
Hi all,
For a very long time postgresql users have complained about charset
incompatibilities in dbmail.
Typically errors like "invalid byte sequence for encoding ..." would
break delivery of messages when the string being inserted in the
database was differently encoded than postgres was expec
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=426
==
Reported By:yuen
Assigned To:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
DBMail 1.2.12 is out. This is a bugfix release only, which is
recommended for all DBMail 1.2 users:
* Security bugfix for proper escaping of sender and recipient
addresses while forwarding to external addresses
* Some memory le
