Re: imap syntax error bad return option status

Axel Rau writes: Arnt did not honor the pull request until now, which may have to do with architectural concerns. Axel's second pull request seems intuitively too complex for the problem... I believe that a solution should not be more complex than the problem, and that PR makes me feel

Re: imap syntax error bad return option status

GP writes: I like your software and it's true that it's gotten into the hosted mail era so it doesn't have the recognition it deserves, but never the less it's still very useful to some folks myself included. I apologise if my tone was bad. So thank you for building it, even if it's not

Re: imap syntax error bad return option status

> Am 12.06.2016 um 23:25 schrieb NSS Ltd : > > Admittedly, the website has some things which make it look very dated, > such as references to old version as if they were current and the fact > the last release is from a few years ago. Although the GIT

Re: imap syntax error bad return option status

On 06/13/2016 12:25 AM, NSS Ltd wrote: In short, AOX looks to me like the sort of IMAP server that people should be considering, especially if they want an open source stack and the advantage of database backed storage on a database which can scale and supports things like online backup and

Re: imap syntax error bad return option status

On 12/06/2016 08:41, Arnt Gulbrandsen wrote: > > I'm not concerned about database space, but requiring an extension > feels ungood. However, the number of aox users is now in two digits > and probably dropping, and they all are capable of adding an > extension, so IMO it's fine either way. > It

Re: imap syntax error bad return option status

On 12/06/2016 08:41, Arnt Gulbrandsen wrote: However, the number of aox users is now in two digits and probably dropping, and they all are capable of adding an extension, so IMO it's fine either way. That's a shame. I wonder if it would be worthwhile considering a 'salvage job' to see what

Re: imap syntax error bad return option status

Stephen R. van den Berg writes: The common way to solve this which does not cost extra database space would be to store a unique but permanent identifier per aox instance, and then use a one-way-hash (e.g. MD5) to make your UUIDs difficult to guess (it only needs to fill in part of the UUID this

Re: imap syntax error bad return option status

NSS Ltd wrote: >----0123 >This could be OK but, for me, I actually have 4 AOX servers I have >accounts on, so I would end up with the situation where I have identical >UUIDs for different mailboxes on different servers and that breaks the >concept of a UUID which

Re: imap syntax error bad return option status

Hi, why did you use the UUID type and a column instead of constructing a UUID at read time based on mailboxes.id and mailboxes.uidvalidity? Arnt

Re: imap syntax error bad return option status

Hi Stephen, I hadn't thought it could be the cause, but when you mention it, it could be possible. Essentially, a STATUS command is embedded in the LIST to try and be more efficient, and it could be Thunderbird is trying that. Although, a sensible client should then see the error and run

Re: imap syntax error bad return option status

After some further testing, there is a small change required to the new SQL - it requires a LEFT OUTER JOIN rather than a simple join as some of the sub-tables may be empty and that causes erroneous empty results. I've re-created the patch sets which can be applied against the git master. Jim

Re: imap syntax error bad return option status

Oops, typo : alter table mailboxes add constraint uniq_guid unique (guid); (removed 'check' which is wrong syntax) On 09/06/2016 16:14, NSS Ltd wrote: > It looks like my earlier patch does address this and also adds the > x-guid to the status command as well. > > I have 2 patch files plus a

Re: imap syntax error bad return option status

It looks like my earlier patch does address this and also adds the x-guid to the status command as well. I have 2 patch files plus a necessary change to the database tables : -- add uuid extension into PostgreSQL database CREATE EXTENSION "uuid-ossp"; -- alter mailboxes table to add a guid and

Re: imap syntax error bad return option status

OK, I knew this was familiar. I sent a patch in April 2015 but it's not merged (some others I sent for some different things are merged). I need to check the code to become familiar again, but is it possible to get this merged in? It may need some cleanup, but I believe it was working on my

imap syntax error bad return option status

Hi, I've just updated to the latest git master and see a number of back-off due to imap syntax error messages. The offending command seems to be : list "" "*" return (status (x-guid) children) And the 'status' seems to be the problem. 114 BAD Unknown return option: status Before digging into