Andreas Seltenreich wrote:
> Hi dbmail-dev,
> 
> I just discovered that imapd doesn't take "*" everywhere in message
> sets where the grammar in rfc 2060 allows it. Gnus
> (<http://www.gnus.org>) tries to find the min and max UID using a
> "fetch 1,* uid", which fails.

You're quit right. That is valid.

> I was about to fix imapd in svn-trunk to send a patch, but imapd of
> svn-trunk didn't even let me login because of issues with the
> PostgreSQL schema. 

wtf? The svn repository doesn't require a login afaik. You can also
access my GIT repository if you like. It's what I use as my primary vc.

http://nfg3.nfgs.net/cgi-bin/gitweb.cgi

for webaccess, or clone the master tree using the cogito tools:

cg-clone http://nfg3.nfgs.net/git/dbmail-2.1.git dbmail-2.1

Patches are very welcome!

> The pgsql schema of the 2.1.3 release didn't work
> either, does this mean PostgreSQL is a 2nd class citizen during
> development?

Be specific, please. What didn't work. Did you load all the add_XX.psql
files after creating the database and setting up the basic schemas with
create_tables.pgsql?

Yes, main development is on mysql (it's just what I started using when I
started off on dbmail), but I do try to keep the postgres sql files in
sync, and do run postgres tests now and then. Indeed, QA is not my main
priority; finishing 2.2 *is*. Once I'm ready for a release candidate
(around the end of november, knock on wood), we can all start working on
testing all the different use case, platforms, db engines, etc...

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

Reply via email to