DBMail 2.2.7 release candidate 2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi all,

I'm releasing the second candidate for 2.2.7.

This release contains two changes with respect to rc1 (and
2.2.6-rc2).

The notify support in sieve, which was incomplete, is now
marked as
unsupported.

The annoying sieve error messages, that were triggered by
some broken
spam messages, resulting in cryptic messages in the
recipients mailbox
have now been disabled.

kind regards,

- --
 
____________________________________________________________
____
  Paul Stevens                                      paul at
nfg.nl
  NET FACILITIES GROUP                     GPG/PGP:
1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG+7998iITvBH4zTERAtuoAJ0aT5wKnnrfdDMaGWNYKUubX9pfsQCg
mJF6
j+PE2cebORaLHKFGspdx4wM=
=KUdv
-----END PGP SIGNATURE-----
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

On Sat, 2007-09-29 at 11:28 +0800, zamri wrote:

> I still got these 2 warnings as in previous versions
during
> compilation:
> 
>  warning: format '%llu' expects type 'long long
unsigned int', but
> argument 7 has type 'guint64' 
>  warning: format '%llu' expects type 'long long
unsigned int', but
> argument 4 has type 'long unsigned int'

These warnings are harmless, as the data types are in fact
the same.
Hopefully the glib and gcc folks will work these warnings
out; we're
just using the portable declarations that glib defines.

Aaron

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

On Sat, 2007-09-29 at 10:02 +0200, Paul J Stevens wrote: 
> Aaron Stone wrote:
> > On Sat, 2007-09-29 at 11:28 +0800, zamri wrote:
> > 
> >> I still got these 2 warnings as in previous
versions during
> >> compilation:
> >>
> >>  warning: format '%llu' expects type 'long
long unsigned int', but
> >> argument 7 has type 'guint64' 
> >>  warning: format '%llu' expects type 'long
long unsigned int', but
> >> argument 4 has type 'long unsigned int'
> > 
> > These warnings are harmless, as the data types are
in fact the same.
> > Hopefully the glib and gcc folks will work these
warnings out; we're
> > just using the portable declarations that glib
defines.
> 
> Are they the same? guint64 is guaranteed to be 64 bits
wide, but a long
> long unsigned int on a amd64 is 128 bits right?

Quick table:  http
://blogs.sun.com/nike/entry/ilp64_lp64_llp64

For way too much detail:  http://yarchiv
e.net/comp/longlong.html

There are no 128 bit numbers in the C standard yet.

Aaron

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