Aaron Stone | 1 Jan 02:40 2007

Mailbox namespaces

In researching bug #474, I realized that we currently allow arbitrary
mailboxes to begin with #. According to RFC 3501, section 5.1:

   5)    Two characters, "#" and "&", have meanings by convention, and
         should be avoided except when used in that convention.

and then:

5.1.2.  Mailbox Namespace Naming Convention

   By convention, the first hierarchical element of any mailbox name
   which begins with "#" identifies the "namespace" of the remainder of
   the name.  This makes it possible to disambiguate between different
   types of mailbox stores, each of which have their own namespaces.

        For example, implementations which offer access to USENET
        newsgroups MAY use the "#news" namespace to partition the
        USENET newsgroup namespace from that of other mailboxes.
        Thus, the comp.mail.misc newsgroup would have a mailbox
        name of "#news.comp.mail.misc", and the name
        "comp.mail.misc" can refer to a different object (e.g., a
        user's private mailbox).

It occurs to me that we should be preventing such mailboxes from being
created. This may have to happen in 2.2. In fact, I may have recently
un-disallowed such mailboxes. I'll have to check back on this.

I also wonder if there isn't some cleaner abstraction that could be made,
so that any mailbox beginning with # is passed through a single set of
functions that figure out what to do with it. This is more 2.3 work.
(Continue reading)

bugtrack | 1 Jan 02:47 2007

[DBMail 0000474]: LIST with other users folder not working correctly


A NOTE has been added to this issue. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=474 
====================================================================== 
Reported By:                lkneschke
Assigned To:                
====================================================================== 
Project:                    DBMail
Issue ID:                   474
Category:                   IMAP daemon
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
target:                      
====================================================================== 
Date Submitted:             14-Dec-06 10:18 CET
Last Modified:              01-Jan-07 02:47 CET
====================================================================== 
Summary:                    LIST with other users folder not working correctly
Description: 
Have a look at this imap conversation:

all folders i have access too

a002 list "" "*"
* LIST (\hasnochildren) "/" "#Users/cweiss/INBOX"
* LIST (\hasnochildren) "/" "Drafts"
* LIST (\hasnochildren) "/" "INBOX"
(Continue reading)

bugtrack | 1 Jan 02:53 2007

[DBMail 0000234]: Shared lib relocate R_X86_64_32 amd64


The following issue has been RESOLVED. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=234 
====================================================================== 
Reported By:                mike
Assigned To:                aaron
====================================================================== 
Project:                    DBMail
Issue ID:                   234
Category:                   installation scripts
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
target:                      
Resolution:                 unable to reproduce
Fixed in Version:           
====================================================================== 
Date Submitted:             28-Jul-05 16:18 CEST
Last Modified:              01-Jan-07 02:53 CET
====================================================================== 
Summary:                    Shared lib relocate R_X86_64_32 amd64
Description: 
gmake install will fail on AMD64 SMP kernels linking objects to libs *see
additional for temp fix*
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0000215 Configure warning and other compilation...
(Continue reading)

bugtrack | 1 Jan 02:54 2007

[DBMail 0000452]: Allow aliases with unknown subdomains.


The following issue has been RESOLVED. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=452 
====================================================================== 
Reported By:                dirixmjm
Assigned To:                aaron
====================================================================== 
Project:                    DBMail
Issue ID:                   452
Category:                   General
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     resolved
target:                      
Resolution:                 fixed
Fixed in Version:           2.2.2
====================================================================== 
Date Submitted:             19-Nov-06 23:02 CET
Last Modified:              01-Jan-07 02:54 CET
====================================================================== 
Summary:                    Allow aliases with unknown subdomains.
Description: 
as do other MDA, it would be very convenient if dbmail understands aliases
in form:  <at> .foo.com
and then accepts mails for  <at> bar.foo.com,  <at> test.foo.com and so fort.

====================================================================== 

(Continue reading)

Lars Kneschke | 1 Jan 16:41 2007
Picon

Re: Three things on my plate for 2.2.2

"Aaron Stone" <aaron@...> schrieb:
> Hasn't been changed yet. Did we conclude that this was the right thing
> to do?
I got that impression from paul's response.

http://www.mail-archive.com/dbmail-dev-taRh+z1m2xodnm+yROfE0A <at> public.gmane.org/msg08100.html

--
Lars Kneschke
Metaways Infosystems GmbH
Pickhuben 4
20457
Hamburg
Germany

eGroupWare Training & Support ==>
http://www.egroupware-support.net

E-Mail:
mailto:l.kneschke@...
Web: http://www.metaways.de
Tel: +49 (0)40
317031-21
Fax: +49 (0)40 317031-81
Mobile: +49 (0)175 9304324
Paul J Stevens | 1 Jan 17:02 2007
Picon

Re: Three things on my plate for 2.2.2


rev. 2408

Lars Kneschke wrote:
> "Aaron Stone" <aaron@...> schrieb:
>> Hasn't been changed yet. Did we conclude that this was the right thing
>> to do?
> I got that impression from paul's response.
> 
> http://www.mail-archive.com/dbmail-dev-taRh+z1m2xodnm+yROfE0A <at> public.gmane.org/msg08100.html
> 
> 
> --
> Lars Kneschke
> Metaways Infosystems GmbH
> Pickhuben 4
> 20457
> Hamburg
> Germany
> 
> eGroupWare Training & Support ==>
> http://www.egroupware-support.net
> 
> E-Mail:
> mailto:l.kneschke@...
> Web: http://www.metaways.de
> Tel: +49 (0)40
> 317031-21
> Fax: +49 (0)40 317031-81
> Mobile: +49 (0)175 9304324
(Continue reading)

bugtrack | 1 Jan 17:05 2007

[DBMail 0000482]: use ANALYZE TABLE instead of OPTIMIZE TABLE in mysql driver


The following issue has been SUBMITTED. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=482 
====================================================================== 
Reported By:                paul
Assigned To:                paul
====================================================================== 
Project:                    DBMail
Issue ID:                   482
Category:                   Database layer
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
target:                      
====================================================================== 
Date Submitted:             01-Jan-07 17:05 CET
Last Modified:              01-Jan-07 17:05 CET
====================================================================== 
Summary:                    use ANALYZE TABLE instead of OPTIMIZE TABLE in mysql
driver
Description: 

Optimize table does a full table lock while copying the whole table. This
is overkill given the intended purpose. Analyze table serves the same
purpose taking less time and requires only a read lock.
====================================================================== 

Issue History 
(Continue reading)

bugtrack | 1 Jan 17:05 2007

[DBMail 0000482]: use ANALYZE TABLE instead of OPTIMIZE TABLE in mysql driver


The following issue has been RESOLVED. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=482 
====================================================================== 
Reported By:                paul
Assigned To:                paul
====================================================================== 
Project:                    DBMail
Issue ID:                   482
Category:                   Database layer
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
target:                      
Resolution:                 fixed
Fixed in Version:           2.2.2
====================================================================== 
Date Submitted:             01-Jan-07 17:05 CET
Last Modified:              01-Jan-07 17:05 CET
====================================================================== 
Summary:                    use ANALYZE TABLE instead of OPTIMIZE TABLE in mysql
driver
Description: 
Optimize table does a full table lock while copying the whole table. This
is overkill given the intended purpose. Analyze table serves the same
purpose taking less time and requires only a read lock.
====================================================================== 

(Continue reading)

bugtrack | 1 Jan 17:06 2007

[DBMail 0000481]: wrong repsonse on failed login


The following issue has been ASSIGNED. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=481 
====================================================================== 
Reported By:                lkneschke
Assigned To:                paul
====================================================================== 
Project:                    DBMail
Issue ID:                   481
Category:                   Authentication layer
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
target:                      
Resolution:                 fixed
Fixed in Version:           2.2.2
====================================================================== 
Date Submitted:             30-Dec-06 15:15 CET
Last Modified:              01-Jan-07 17:06 CET
====================================================================== 
Summary:                    wrong repsonse on failed login
Description: 
This is the output of a imap session, where the login failed:

lkneschke <at> laptoplk:~$ telnet dbmail-server 143
Trying 1.2.3.4...
Connected to dbmail-server.
Escape character is '^]'.
(Continue reading)

Justin McAleer | 2 Jan 14:00 2007

Re: Three things on my plate for 2.2.2

Has any progress been made on the imapd memory leak? http://www.dbmail.org/mantis/view.php?id=462 On Sat, 30 Dec 2006 14:59:05 -0800 Aaron Stone wrote: > I didn't think much about DBMail through holidays, but > I've got three > things that I want to commit for the next release: > > o Failed forwards drop mail without a trace. > o LDAPi patch from Uemura Tetsuya. > o Sub-domain alias matches. > > Any objections to the above? Other things someone would > like me to take > a look at in the immediate future? > > Aaron > > _______________________________________________ > Dbmail-dev mailing list > Dbmail-dev-taRh+z1m2xodnm+yROfE0A@public.gmane.org > http://twister.fastxs.net/mailman/listinfo/dbmail-dev >

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

Gmane