[1488] in Moira
RE: IMAP question
daemon@ATHENA.MIT.EDU (Tom Coppeto)
Sat Mar 25 14:23:57 2000
From: "Tom Coppeto" <tom@MIT.EDU>
To: "Garry Zacheiss" <zacheiss@mit.edu>, "Qing Dong" <dongq@mit.edu>
Cc: <moiradev@mit.edu>
Date: Sat, 25 Mar 2000 14:35:36 -0500
Message-ID: <NDBBKHCHPJDKBDPHJLDAAEMJCIAA.tom@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <200003250202.VAA18922@bobbi-harlow.mit.edu>
I agree.. should be a way to set the pobox to an existing imap filesys and
the filesys may or not be their own filesys. It's kind of unfortunate we
have the .po extension hack which might make this concept less cluttered.
Admin access should be required for controlling the filesys pointers, not
what filesys the users record points to. This lines up with your first
option and change to access_spob().
At some point, there are no POP types in the mail system although it appears
to be used in a few places where mail is being forwarded outside the system
but a hesiod pointer is desired. I wonder how much trouble its worth to
worry about the transitions between IMAP and POP in moira. It could simplify
things if hesiod pointers were just generated for mit.edu smtp mailboxes.
- Tom
-----Original Message-----
From: Garry Zacheiss [mailto:zacheiss@MIT.EDU]
Sent: Friday, March 24, 2000 9:02 PM
To: Qing Dong
Cc: moiradev@MIT.EDU
Subject: Re: IMAP question
>> I set my P.O Box to IMAP, then I set it to POP. The app then will never
>> let me set myself back to IMAP again. It complains "record already
>> exists creating IMAP filesys in CreateImapBox" and it just quits. Is it
>> how it should function? Should I prevent the user from changing from
>> IMAP to POP since it can not be undone?
Hmm. That's the error message you should get if you're running the
query from the moira client with user-admin bits; otherwise, you'll get
"Insufficient permission..." because moirad won't let you set_pobox
yourself to type IMAP without bits (more on that later). The reason for
this, of course, is that right now, "moira" always does an add_filesys
when you use it to set someone's pobox to type IMAP. I'd argue this is
a misfeature. There are a couple ways to fix this:
1.) Make the client ask "Create IMAP filesystem (y/n)? [y]" and only
afil if the user says yes. This would be nice because it gives you a
way of saying "qy spob username IMAP username.po" without needing to use
mrtest. I implemented this earlier today while thinking about this.
2.) Make the client do a get_filesys_by_label for an appropriate
filesystem and use it if it finds it, and otherwise always try to create
it. I don't particularly like this.
That said, neither of these solutions help the average user, since
set_pobox won't let anyone not on the capacl put themselves on an IMAP
pobox. This is fixable in the server if we change access_spob() to only
let you spob yourself to an IMAP pobox only if the filesystem you
specify exists, is owned by you, is lockertype "USER" and type "IMAP".
The other solution to say "don't do that" and not allow people not on
the capacl to change themselves from type IMAP to type POP, so they
can't get in this state.
Tom, this is your call. Implementing any of this isn't especially
hard; which options do you prefer?
Garry
