search for: utc_mktime

http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz.sig Some small fixes and changes to v2.2.14. This release is mainly in the hope that it could still make it into the next Debian stable instead of v2.2.14 - mainly because of a couple of new assert crashes that started happening in v2.2.14 and should be fixed now. * Plugins can now print

http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz.sig Some small fixes and changes to v2.2.14. This release is mainly in the hope that it could still make it into the next Debian stable instead of v2.2.14 - mainly because of a couple of new assert crashes that started happening in v2.2.14 and should be fixed now. * Plugins can now print

Hi all, I compiled a 64-bit Dovecot stable (13-03-2005) version on a Solaris 9 box with gcc 3.4.2. OpenSSL and libiconv are compiled 64-bit also. The configure I use: export CPPFLAGS="-m64 -I/var/tmp/openssl/include" export LDFLAGS="-m64 -L/var/tmp/openssl/lib" ./configure \ --prefix=/opt/dovecot \ --sysconfdir=/etc/opt/dovecot

...ices * at Carnegie Mellon University (http://www.cmu.edu/computing/)." And something similar in utc-mktime.c for Berkeley university as well. I think I'd really like to get rid of those base64.c and utc-mktime.c exceptions.. There's probably also an easier/faster way to implement utc_mktime(). Anyway.. Currently these copyrights or acknowledgments aren't listed anywhere else than in the source files. I don't know if binary packagers have added those, but somehow I doubt it. So I think I should add these to COPYING file somehow. Any suggestions? Perhaps appending something l...

...t;> On 21.10.2007, at 3.58, Jeff Grossman wrote: >> >>> 2 search since 6-Sep-2007 >> .. >>> Oct 20 17:54:47 apple IMAP(jeff): : since: 1190593264 vs 2147483647 >>> Oct 20 17:54:47 apple IMAP(jeff): : since: 1190829893 vs 2147483647 >> >> I guess utc_mktime() doesn't work correctly for some reason. What >> are TIME_T_MAX_BITS and TIME_T_SIGNED in your config.h? You've >> 32bit system? >> > Yes, this is a 32-bit system. I did test it with TIME_T_MAX_BITS=32, but looks like I never tested it with actual 32bit systems....

...'0') * 3600; + s += 3; + + /* MM */ + if (!i_isdigit(s[0]) || !i_isdigit(s[1]) || s[2] != '\0') + return 0; + tm.tm_gmtoff += ((s[0] - '0') * 10 + s[1] - '0') * 60; + + if (tzsign == '-') + tm.tm_gmtoff = -tm.tm_gmtoff; + } else + return 0; + + t = utc_mktime(&tm); + if (t < 0) + return 0; + return t - tm.tm_gmtoff; +} + +// decode the parts of a URL +bool imap_url_decode(const struct imap_url_parts *enc_parts, + struct imap_url_parts *dec_parts, + const char **error) +{ + string_t *str = t_str_new(256); + +#define URL_DECODE(field,...