A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=430
==
Reported By:bjohnson
Assigned To:
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=430
==
Reported By:bjohnson
Assigned To:
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=430
==
Reported By:bjohnson
Assigned To:
The following issue has been RESOLVED.
==
http://www.dbmail.org/mantis/view.php?id=430
==
Reported By:bjohnson
Assigned To:
Hello
I've just landed a change that will convert all strings inserted into
the headervalue and subjectfield columns into UTF8 encoded strings using
a gmime's iconv facilities. The subject and address parts of the
envelope are encoded as utf7 (rfc2047) also makes it safe to insert them
into
Oleg Lapshin wrote:
Hello
I've just landed a change that will convert all strings inserted into
the headervalue and subjectfield columns into UTF8 encoded strings using
a gmime's iconv facilities. The subject and address parts of the
envelope are encoded as utf7 (rfc2047) also makes it
That's unrelated. The envelope cache should always be 7bit clean.
Subjects should be utf7 encoded to begin with, and if they are not they
are utf7 encoded by dbmail during the construction of the imap envelope
string. There's no utf8 conversion done along the way.
Could you provide me with a
I just download revision 2347
Configure options:
./configure --with-mysql --with-sieve --enable-shared
The last lines from strace output of my command
$ cat message | strace /usr/local/sbin/dbmail-smtp -u loe :
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_DFL}, 8) = 0
socket(PF_FILE, SOCK_STREAM, 0)
Oleg please try rev 2348
I've reverted the utf7 encoding on subject in envelope. Apparently it
wan't encoded right anyway.
I've also pushed the utf8 encoding to the postgres driver, so it won't
affect mysql/sqlite users.
--
Oleg,
I need a backtrace. Use valgrind or gdb if you can.
--
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The
Oleg,
I need a backtrace. Use valgrind or gdb if you can.
I've attache output from:
cat message |
valgrind --leak-check=full -v --show-reachable=yes /usr/local/sbin/dbmail-smtp
-u
loe
(can't check your changes for utf7 encoding in subject)
--
Oleg Lapshin
out.gz
Description: GNU Zip
When the module search path had one less item, the for loop was still
counting up to four. Fixed.
Aaron
On Thu, 2006-11-02 at 16:05 +0300, Oleg Lapshin wrote:
Oleg,
I need a backtrace. Use valgrind or gdb if you can.
I've attache output from:
cat message |
valgrind --leak-check=full
Hi
since last upgrade to a recent dbmail, I get some problems with my
staff because dbmail-users -l shows a
second created alias both as forward and as alias.
This is a transcript:
hercules ~# dbmail-users -a [EMAIL PROTECTED] -s [EMAIL PROTECTED]
Adding INBOX for new user
[EMAIL
For the record, I would agree 110% that a 2.1.8 would be in order.
There have been *many* changes made since 2.1.7, and svn has been
especially unstable lately. I think getting 2.2 release fever right now
is likely to go about as well as the 2.0 release did (ie. immediate
patches to fix a few
The following issue has been SUBMITTED.
==
http://www.dbmail.org/mantis/view.php?id=431
==
Reported By:bjohnson
Assigned To:
The following issue has been SUBMITTED.
==
http://www.dbmail.org/mantis/view.php?id=432
==
Reported By:bjohnson
Assigned To:
16 matches
Mail list logo
