Fwd: Re: [Imap-uw] LIST / hidden files

[Oliver Block]

--- Begin Message ---
Am Dienstag, 24. Februar 2009 19:43:57 schrieben Sie:
> UW imapd once suppressed listing of dot files.  I was made to remove that
> feature, for the reason stated in the previous paragraph.
>
> I look at the prospect of revisiting that decision with about the same as
> I view a colonoscopy.

You mean it's preferable to follow example 2 of CONFIG, don't you?
--- End Message ---
___
Imap-uw mailing list
Imap-uw@u.washington.edu
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Re: [Imap-uw] LIST / hidden files

[Mark Crispin]

On Tue, 24 Feb 2009, Oliver Block wrote:

The ls command of unix will not show those files
or directories unless you use the -a option.
On the other hand uw-imapd does show the hidden files.


That is correct.  If the IMAP server did not list those files, it would be 
impossible for the IMAP client to show them to the user under any of those 
circumstances.


UW imapd once suppressed listing of dot files.  I was made to remove that 
feature, for the reason stated in the previous paragraph.


I look at the prospect of revisiting that decision with about the same as 
I view a colonoscopy.


-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
___
Imap-uw mailing list
Imap-uw@u.washington.edu
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Re: [Imap-uw] sharing mailboxes

[Neil Hoggarth]

On Tue, 24 Feb 2009, Oliver Block wrote:


I've read the short desciption in the imap faq and would like to know one
thing. When you follow the instructions on top of anwer 4.6
  [...]
If user A sets the permission like above, how will user B find that folder,
shared by A?


. Familiarise yourself 
with naming.txt and drivers.txt. There are lots of interesting ways to 
access files under various pathnames using imapd. Once know how to use 
IMAP namespaces to access different parts of the filesystem tree on the 
mail server then you use the normal Unix permission mechnisms to allow 
access to things that you want to allow (and disallow things that you 
don't).


Common methods would be B accessing files under A's home directory:

0001 SELECT ~A/path/to/mailbox

or the sysadmin creating an "imapshared" psuedo-user, along with a 
subdirectory of that psuedo-user's home directory which both A and B can 
access (using groups and setgid directories, or inheritable ACLs, or a 
similar mechanism) and then the clients using the "#shared" namespace:


0002 SELECT #shared/groupdir/mailbox

Regards
--
Neil Hoggarth -- Department of Physiology, Anatomy and Genetics
Head of IT --- University of Oxford, UK

___
Imap-uw mailing list
Imap-uw@u.washington.edu
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

[Imap-uw] sharing mailboxes

[Oliver Block]

Hello everybody,

I've read the short desciption in the imap faq and would like to know one 
thing. When you follow the instructions on top of anwer 4.6

> At the simplest level, a shared mailbox is one which has UNIX file and
> directory protections which permit multiple users to access it. What this 
> means is that your existing skills and tools to create and manage shared 
> files on your UNIX system apply to shared mailboxes; e.g.
>
>  chmod 666 mailbox

If user A sets the permission like above, how will user B find that folder, 
shared by A?

Best Regards,

Oliver Block
___
Imap-uw mailing list
Imap-uw@u.washington.edu
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

[Imap-uw] LIST / hidden files

[Oliver Block]

Hello everybody,

I have a question regarding the LIST command and about how it is handled by 
UW-IMAPD.

The "default" installation of imapd returns the following result for an 
average user on ubuntu linux:

0004 LIST "" "*"
* LIST (\NoInferiors \UnMarked) "/" .bash_logout
 / .bash_logout, no inferiors, unmarked
* LIST (\NoSelect \HasChildren) "/" mail
 / mail, no select
* LIST (\NoInferiors \UnMarked) "/" mail/postponed-msgs
 / mail/postponed-msgs, no inferiors, unmarked
* LIST (\NoInferiors \UnMarked) "/" mail/sent-mail
 / mail/sent-mail, no inferiors, unmarked
* LIST (\NoInferiors \UnMarked) "/" mail/saved-messages
 / mail/saved-messages, no inferiors, unmarked
* LIST (\NoInferiors \UnMarked) "/" .pinerc
 / .pinerc, no inferiors, unmarked
* LIST (\NoInferiors \UnMarked) "/" .profile
 / .profile, no inferiors, unmarked
* LIST (\NoInferiors \UnMarked) "/" .bashrc
 / .bashrc, no inferiors, unmarked
* LIST (\NoSelect \HasNoChildren) "/" .ssh
 / .ssh, no select
* LIST (\NoInferiors) NIL INBOX
 NIL INBOX, no inferiors
0004 OK LIST completed

You can easily recognize the alpine part underneath mail/. But what's the best 
way to handle the mailboxes at hierarchy level 1? Here you 
see .pinerc, .profile, etc. The ls command of unix will not show those files 
or directories unless you use the -a option.

On the other hand uw-imapd does show the hidden files. 

1. Is this a configuration issue or is it a protocol issue?

2. Has that ever been discussed in the imap-wg weither ot show hidden hidden 
files or not?

Best Regards,

Oliver Block
___
Imap-uw mailing list
Imap-uw@u.washington.edu
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw