unixhierarchysep: 1 (Was: Re: Web based administration interfaces ...)

[Marc G. Fournier]

Okay, I tried this out, on an existing mail spool ... two words: ACK ACK!

'k, looking at the file system, to start, I'm seeing changes:

The first mailbox is 'before' and the second is 'after':

12524   ./s/user/seminars/sent-mail
12532   ./s/user/seminars
12534   ./s/user
12536   ./s
8       ./u/user^sakellariou
8       ./u/user^sakellariou^sent-mail
18      ./u

Does the mailbox creation stuff have have to change also?  We create all 
ours as 'user.<userid>', so do we have to change it all to user/userid? :(

If so, is there a way in PHP of finding out whether the seperator is a '.' 
or a '/'?

Thx ...

On Tue, 4 Apr 2006, David Lang wrote:

> On Tue, 4 Apr 2006, Marc G. Fournier wrote:
>
>> On Tue, 4 Apr 2006, Carl P. Corliss wrote:
>> 
>>> Ow Mun Heng wrote:
>>>> On Sun, 2006-04-02 at 03:17 -0300, Marc G. Fournier wrote:
>>>> 
>>>>> you can't easily have first.last at domain within Cyrus ... so, I have 
>>>>> clients create first_last, and create an alias that delivers to that 
>>>>> "central mailbox" ... I just have to extend mailadmin to allow for 
>>>>> adding aliases to the virtuals table next ...
>>>>> 
>>>> 
>>>> And why not? I have it working. (although I'm not 100% sure since I only
>>>> have it as user at domain and I didn't try user.name at domain.com, but I'm
>>>> sure it's do-able
>>>> 
>>> 
>>> It is 100% possible and not difficult at all to use... so long as 
>>> unixhierarchysep is turned on.
>> 
>> 'k, I haven't investigated that one too closely, but ... how does that 
>> affect sub-folders and mail readers?  If I change unixhierarchysep to 1, 
>> how does that affect outlook?  are clients going to need to somehow 
>> reconfigure their mail reader?  Or is this totally transparent?
>
> one of the things that the server tells the client when it connects is what 
> the seperator character is, cyrus uses '.' some other imap servers usr '/' 
> while others use '\'. the client is supposed to honor what the server tells 
> it, and if it doesn't it will have problems with some servers (or the user 
> will have to configure it on the client per server)
>
>> And, if totally transparent, just curious as to why it defaults to '.'?
>
> historical reasons. it has to default to something, and back when there 
> really weren't that many people useing e-mail (when the cyrus project 
> started) e-mail addresses tended to be short, alphanumeric words so '.' 
> wasn't any worse (or nessasarily much better) then any other option.
>
> now, I wasn't around at that time, I'm sure that others can give better 
> reasons (or at least more insight into the project), but I could see the 
> argument that since . isn't a directory seperation character for any OS 
> nativly, it's somewhat safer to user that so that any mistakes in validating 
> (and converting) the folder names would result in an error rather then access 
> to unexpected things.
>
> David Lang
>
> -- 
> There are two ways of constructing a software design. One way is to make it 
> so simple that there are obviously no deficiencies. And the other way is to 
> make it so complicated that there are no obvious deficiencies.
> -- C.A.R. Hoare
>
>
>

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy at hub.org           Yahoo!: yscrappy              ICQ: 7615664