List Info

Thread: Re: (patch) Another case of duplicate keys (via dbmail-smtp)




Re: (patch) Another case of duplicate keys (via dbmail-smtp)
country flaguser name
Netherlands
2008-03-05 06:06:21
attaching the old and a new patch. The last patch should fix
the memory
corruption issue.

Please apply both against 2.2.9 and let me know if it
helps.



John Fawcett wrote:
> John Fawcett wrote:
>> However, the existing code cannot handle the
>>  case of multiple X- headers which have the same
value: that would
>> generate a Duplicate key.
> 
>> John
> Following up to my own post, ignore this, it's wrong.
> Multiple headers are handled without producing an
error
> when they are read in from the original message, but
> they result in a single entry in the dbmail_headervalue
cache.
> 
> That makes sense I think, since dbmail_headervalue is a
cache
> it won't benefit from multiple entries with the same
values.
> 
> John
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

-- 
 
____________________________________________________________
____
  Paul Stevens                                      paul at
nfg.nl
  NET FACILITIES GROUP                     GPG/PGP:
1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

  
  
AW: (patch) Another case of duplicate keys (via dbmail-smtp)
user name
2008-03-05 06:27:24
Using these both patches on 2.2.9 i get compile errors:
primary:~/newmta/dbmail-2.2.9 # make
make  all-recursive
make[1]: Entering directory `/root/newmta/dbmail-2.2.9'
Making all in modules
make[2]: Entering directory
`/root/newmta/dbmail-2.2.9/modules'
if /bin/sh ../libtool --tag=CC --mode=compile gcc
-DHAVE_CONFIG_H -I. -I. -I.. -I..   -I/usr/include/mysql
-fmessage-length=0 -D_FORTIFY_SOURCE=2 -g -DPIC -fPIC
-DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing   
-I/usr/lib/include -g -O2 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/usr/include/gmime-2.0 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include   -W -Wall
-Wpointer-arith -Wstrict-prototypes -MT sortnull.lo -MD -MP
-MF ".deps/sortnull.Tpo" -c -o sortnull.lo
sortnull.c; 
then mv -f ".deps/sortnull.Tpo"
".deps/sortnull.Plo"; else rm -f
".deps/sortnull.Tpo"; exit 1; fi
mkdir .libs
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include/mysql
-fmessage-length=0 -D_FORTIFY_SOURCE=2 -g -DPIC -fPIC
-DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing
-I/usr/lib/include -g -O2 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include -I/usr/include/gmime-2.0
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include -W -Wall -Wpointer-arith
-Wstrict-prototypes -MT sortnull.lo -MD -MP -MF
.deps/sortnull.Tpo -c sortnull.c  -fPIC -DPIC -o
.libs/sortnull.o
/bin/sh ../libtool --tag=CC --mode=link gcc
-I/usr/include/mysql -fmessage-length=0 -D_FORTIFY_SOURCE=2
-g -DPIC -fPIC -DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing 
  -I/usr/lib/include -g -O2 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/usr/include/gmime-2.0 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include   -W -Wall
-Wpointer-arith -Wstrict-prototypes -module
-L/opt/gnome/lib64 -lglib-2.0   -Wl,--export-dynamic
-L/opt/gnome/lib64 -lgmodule-2.0 -ldl -lglib-2.0  
-L/opt/gnome/lib64 -lgmime-2.0 -lz -lnsl -lgobject-2.0
-lglib-2.0   -o libsort_null.la   sortnull.lo
ar cru .libs/libsort_null.a .libs/sortnull.o
ranlib .libs/libsort_null.a
creating libsort_null.la
(cd .libs && rm -f libsort_null.la && ln -s
../libsort_null.la libsort_null.la)
if /bin/sh ../libtool --tag=CC --mode=compile gcc
-DHAVE_CONFIG_H -I. -I. -I.. -I..   -I/usr/include/mysql
-fmessage-length=0 -D_FORTIFY_SOURCE=2 -g -DPIC -fPIC
-DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing   
-I/usr/lib/include -g -O2 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/usr/include/gmime-2.0 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include   -W -Wall
-Wpointer-arith -Wstrict-prototypes -MT dbmysql.lo -MD -MP
-MF ".deps/dbmysql.Tpo" -c -o dbmysql.lo
dbmysql.c; 
then mv -f ".deps/dbmysql.Tpo"
".deps/dbmysql.Plo"; else rm -f
".deps/dbmysql.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include/mysql
-fmessage-length=0 -D_FORTIFY_SOURCE=2 -g -DPIC -fPIC
-DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing
-I/usr/lib/include -g -O2 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include -I/usr/include/gmime-2.0
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include -W -Wall -Wpointer-arith
-Wstrict-prototypes -MT dbmysql.lo -MD -MP -MF
.deps/dbmysql.Tpo -c dbmysql.c  -fPIC -DPIC -o
.libs/dbmysql.o
/bin/sh ../libtool --tag=CC --mode=link gcc
-I/usr/include/mysql -fmessage-length=0 -D_FORTIFY_SOURCE=2
-g -DPIC -fPIC -DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing 
  -I/usr/lib/include -g -O2 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/usr/include/gmime-2.0 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include   -W -Wall
-Wpointer-arith -Wstrict-prototypes -module
-L/opt/gnome/lib64 -lglib-2.0   -Wl,--export-dynamic
-L/opt/gnome/lib64 -lgmodule-2.0 -ldl -lglib-2.0  
-L/opt/gnome/lib64 -lgmime-2.0 -lz -lnsl -lgobject-2.0
-lglib-2.0   -o libmysql.la -rpath /usr/lib/dbmail 
dbmysql.lo -L/usr/lib64/mysql -lmysqlclient -lz -lcrypt
-lnsl -lm
gcc -shared  .libs/dbmysql.o  -Wl,--rpath
-Wl,/usr/lib64/mysql -Wl,--rpath -Wl,/usr/lib64/mysql
-L/opt/gnome/lib64 /opt/gnome/lib64/libgmodule-2.0.so -ldl
/usr/lib64/libgmime-2.0.so
/opt/gnome/lib64/libgobject-2.0.so
/opt/gnome/lib64/libglib-2.0.so -L/usr/lib64/mysql
/usr/lib64/mysql/libmysqlclient.so -lz -lcrypt -lnsl -lm 
-Wl,--export-dynamic -Wl,-soname -Wl,libmysql.so.0 -o
.libs/libmysql.so.0.0.0
(cd .libs && rm -f libmysql.so.0 && ln -s
libmysql.so.0.0.0 libmysql.so.0)
(cd .libs && rm -f libmysql.so && ln -s
libmysql.so.0.0.0 libmysql.so)
creating libmysql.la
(cd .libs && rm -f libmysql.la && ln -s
../libmysql.la libmysql.la)
if /bin/sh ../libtool --tag=CC --mode=compile gcc
-DHAVE_CONFIG_H -I. -I. -I.. -I..   -I/usr/include/mysql
-fmessage-length=0 -D_FORTIFY_SOURCE=2 -g -DPIC -fPIC
-DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing   
-I/usr/lib/include -g -O2 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/usr/include/gmime-2.0 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include   -W -Wall
-Wpointer-arith -Wstrict-prototypes -MT sortsieve.lo -MD -MP
-MF ".deps/sortsieve.Tpo" -c -o sortsieve.lo
sortsieve.c; 
then mv -f ".deps/sortsieve.Tpo"
".deps/sortsieve.Plo"; else rm -f
".deps/sortsieve.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include/mysql
-fmessage-length=0 -D_FORTIFY_SOURCE=2 -g -DPIC -fPIC
-DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing
-I/usr/lib/include -g -O2 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include -I/usr/include/gmime-2.0
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include -W -Wall -Wpointer-arith
-Wstrict-prototypes -MT sortsieve.lo -MD -MP -MF
.deps/sortsieve.Tpo -c sortsieve.c  -fPIC -DPIC -o
.libs/sortsieve.o
/bin/sh ../libtool --tag=CC --mode=link gcc
-I/usr/include/mysql -fmessage-length=0 -D_FORTIFY_SOURCE=2
-g -DPIC -fPIC -DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing 
  -I/usr/lib/include -g -O2 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/usr/include/gmime-2.0 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include   -W -Wall
-Wpointer-arith -Wstrict-prototypes -module
-L/opt/gnome/lib64 -lglib-2.0   -Wl,--export-dynamic
-L/opt/gnome/lib64 -lgmodule-2.0 -ldl -lglib-2.0  
-L/opt/gnome/lib64 -lgmime-2.0 -lz -lnsl -lgobject-2.0
-lglib-2.0   -o libsort_sieve.la -rpath /usr/lib/dbmail 
sortsieve.lo -L/usr/lib/lib -lsieve
gcc -shared  .libs/sortsieve.o  -L/opt/gnome/lib64
/opt/gnome/lib64/libgmodule-2.0.so -ldl
/usr/lib64/libgmime-2.0.so -lz -lnsl
/opt/gnome/lib64/libgobject-2.0.so
/opt/gnome/lib64/libglib-2.0.so -L/usr/lib/lib
/usr/lib/libsieve.so  -Wl,--export-dynamic -Wl,-soname
-Wl,libsort_sieve.so.0 -o .libs/libsort_sieve.so.0.0.0
(cd .libs && rm -f libsort_sieve.so.0 && ln
-s libsort_sieve.so.0.0.0 libsort_sieve.so.0)
(cd .libs && rm -f libsort_sieve.so && ln -s
libsort_sieve.so.0.0.0 libsort_sieve.so)
creating libsort_sieve.la
(cd .libs && rm -f libsort_sieve.la && ln -s
../libsort_sieve.la libsort_sieve.la)
if /bin/sh ../libtool --tag=CC --mode=compile gcc
-DHAVE_CONFIG_H -I. -I. -I.. -I..   -I/usr/include/mysql
-fmessage-length=0 -D_FORTIFY_SOURCE=2 -g -DPIC -fPIC
-DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing   
-I/usr/lib/include -g -O2 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/usr/include/gmime-2.0 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include   -W -Wall
-Wpointer-arith -Wstrict-prototypes -MT authsql.lo -MD -MP
-MF ".deps/authsql.Tpo" -c -o authsql.lo
authsql.c; 
then mv -f ".deps/authsql.Tpo"
".deps/authsql.Plo"; else rm -f
".deps/authsql.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include/mysql
-fmessage-length=0 -D_FORTIFY_SOURCE=2 -g -DPIC -fPIC
-DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing
-I/usr/lib/include -g -O2 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include -I/usr/include/gmime-2.0
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include -W -Wall -Wpointer-arith
-Wstrict-prototypes -MT authsql.lo -MD -MP -MF
.deps/authsql.Tpo -c authsql.c  -fPIC -DPIC -o
.libs/authsql.o
authsql.c: In function âauth_getclientidâ:
authsql.c:118: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c:123: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c: In function âauth_getmaxmailsizeâ:
authsql.c:146: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c:151: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c: In function âauth_getencryptionâ:
authsql.c:179: warning: format â%lldâ expects type âlong
long intâ, but argument 7 has type âguint64â
authsql.c:183: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c:188: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c: In function âauth_change_passwordâ:
authsql.c:331: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 9 has type âguint64â
authsql.c:337: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c: In function âauth_change_clientidâ:
authsql.c:346: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c:346: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 8 has type âguint64â
authsql.c:352: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c: In function âauth_validateâ:
authsql.c:403: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âlong unsigned
intâ
authsql.c: In function âauth_md5_validateâ:
authsql.c:484: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c: In function âauth_get_useridâ:
authsql.c:537: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c: In function âauth_check_useridâ:
authsql.c:570: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c:580: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c:585: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c: In function âauth_get_users_from_clientidâ:
authsql.c:601: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c:605: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c: In function âauth_addaliasâ:
authsql.c:635: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 8 has type âguint64â
authsql.c:635: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 9 has type âguint64â
authsql.c:648: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 8 has type âguint64â
authsql.c:656: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 8 has type âguint64â
authsql.c:656: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 9 has type âguint64â
authsql.c: In function âauth_addalias_extâ:
authsql.c:692: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 9 has type âguint64â
authsql.c:724: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 9 has type âguint64â
authsql.c: In function âauth_removealiasâ:
authsql.c:749: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
authsql.c: In function âauth_get_user_aliasesâ:
authsql.c:802: warning: format â%lluâ expects type âlong
long unsigned intâ, but argument 7 has type âguint64â
/bin/sh ../libtool --tag=CC --mode=link gcc
-I/usr/include/mysql -fmessage-length=0 -D_FORTIFY_SOURCE=2
-g -DPIC -fPIC -DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing 
  -I/usr/lib/include -g -O2 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include  
-I/usr/include/gmime-2.0 -I/opt/gnome/include/glib-2.0
-I/opt/gnome/lib64/glib-2.0/include   -W -Wall
-Wpointer-arith -Wstrict-prototypes -module
-L/opt/gnome/lib64 -lglib-2.0   -Wl,--export-dynamic
-L/opt/gnome/lib64 -lgmodule-2.0 -ldl -lglib-2.0  
-L/opt/gnome/lib64 -lgmime-2.0 -lz -lnsl -lgobject-2.0
-lglib-2.0   -o libauth_sql.la -rpath /usr/lib/dbmail 
authsql.lo -lcrypt
gcc -shared  .libs/authsql.o  -L/opt/gnome/lib64
/opt/gnome/lib64/libgmodule-2.0.so -ldl
/usr/lib64/libgmime-2.0.so -lz -lnsl
/opt/gnome/lib64/libgobject-2.0.so
/opt/gnome/lib64/libglib-2.0.so -lcrypt 
-Wl,--export-dynamic -Wl,-soname -Wl,libauth_sql.so.0 -o
.libs/libauth_sql.so.0.0.0
(cd .libs && rm -f libauth_sql.so.0 && ln -s
libauth_sql.so.0.0.0 libauth_sql.so.0)
(cd .libs && rm -f libauth_sql.so && ln -s
libauth_sql.so.0.0.0 libauth_sql.so)
creating libauth_sql.la
(cd .libs && rm -f libauth_sql.la && ln -s
../libauth_sql.la libauth_sql.la)
make[2]: Leaving directory
`/root/newmta/dbmail-2.2.9/modules'
Making all in man
make[2]: Entering directory `/root/newmta/dbmail-2.2.9/man'
asciidoc -b docbook -d manpage dbmail.txt
xmlto man dbmail.xml 2>/dev/null
make[2]: *** [dbmail.1] Error 127
rm dbmail.xml
make[2]: Leaving directory `/root/newmta/dbmail-2.2.9/man'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/newmta/dbmail-2.2.9'
make: *** [all] Error 2

without patches, it compiles successful.
Some new requirements?!

Simon

-----Ursprüngliche Nachricht-----
Von: dbmail-bouncesdbmail.org [mailto:dbmail-bouncesdbmail.org] Im Auftrag von Paul J Stevens
Gesendet: Mittwoch, 5. März 2008 13:06
An: DBMail mailinglist
Betreff: Re: [Dbmail] (patch) Another case of duplicate keys
(via dbmail-smtp)


attaching the old and a new patch. The last patch should fix
the memory corruption issue.

Please apply both against 2.2.9 and let me know if it
helps.



John Fawcett wrote:
> John Fawcett wrote:
>> However, the existing code cannot handle the  case
of multiple X- 
>> headers which have the same value: that would
generate a Duplicate 
>> key.
> 
>> John
> Following up to my own post, ignore this, it's wrong.
> Multiple headers are handled without producing an error
when they are 
> read in from the original message, but they result in a
single entry 
> in the dbmail_headervalue cache.
> 
> That makes sense I think, since dbmail_headervalue is a
cache it won't 
> benefit from multiple entries with the same values.
> 
> John
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

--
 
____________________________________________________________
____
  Paul Stevens                                      paul at
nfg.nl
  NET FACILITIES GROUP                     GPG/PGP:
1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

AW: (patch) Another case of duplicate keys (via dbmail-smtp)
user name
2008-03-05 06:32:02
Well, now it compiles. Seems that a make clean is not as it
clean as it should be 

Im testing.

-----Ursprüngliche Nachricht-----
Von: dbmail-bouncesdbmail.org [mailto:dbmail-bouncesdbmail.org] Im Auftrag von Paul J Stevens
Gesendet: Mittwoch, 5. März 2008 13:06
An: DBMail mailinglist
Betreff: Re: [Dbmail] (patch) Another case of duplicate keys
(via dbmail-smtp)


attaching the old and a new patch. The last patch should fix
the memory corruption issue.

Please apply both against 2.2.9 and let me know if it
helps.



John Fawcett wrote:
> John Fawcett wrote:
>> However, the existing code cannot handle the  case
of multiple X- 
>> headers which have the same value: that would
generate a Duplicate 
>> key.
> 
>> John
> Following up to my own post, ignore this, it's wrong.
> Multiple headers are handled without producing an error
when they are 
> read in from the original message, but they result in a
single entry 
> in the dbmail_headervalue cache.
> 
> That makes sense I think, since dbmail_headervalue is a
cache it won't 
> benefit from multiple entries with the same values.
> 
> John
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

--
 
____________________________________________________________
____
  Paul Stevens                                      paul at
nfg.nl
  NET FACILITIES GROUP                     GPG/PGP:
1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

Re: (patch) Another case of duplicate keys (via dbmail-smtp)
country flaguser name
Italy
2008-03-05 06:47:57
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul J Stevens wrote:
> attaching the old and a new patch. The last patch
should fix the memory
> corruption issue.
> 
> Please apply both against 2.2.9 and let me know if it
helps.
> 
> 
Paul
thanks for these. It solves memory corruption and duplicate
Return-Path headers cases I posted.
John

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org


iD8DBQFHzpZ8d4I3jTtt9EIRAnevAKCggVbqYuPDUEPTMx9e2110/5BQSgCg
sG2K
91/Y1MgKOY0EjpwcNzSdNic=
=LtD1
-----END PGP SIGNATURE-----
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

Re: (patch) Another case of duplicate keys (via dbmail-smtp)
country flaguser name
United States
2008-03-05 10:09:23
Hi Paul,

I see that the fix made it to the repository. Do you have an
ETA for a 2.10 
debian package? The 2.9 version has rolled into official
debian testing and I 
need to figure out how to proceed with my upgrade plans
(i.e. to mark the 
packages as held, or just wait a couple of days if a new
release comes soon). 
Either way is fine, I just wanted to stay informed 

Thanks
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

[1-5]

about | contact  Other archives ( Real Estate discussion Medical topics )