[KLUG Members] cyrus imap working

[Adam Williams]

> This week I've gotten two cyrus imap servers working, one at work on a
> slow old test box and another on my machine at home.  The performance is
> significantly better than UW imap an I am very pleased with that.  At

Excellent!

> work I just had two imap servers connected to one client and migrated
> with a mouse.  At home I used the migration scripts.  I had to hack them
> a little to change directories to match the rpm directories.  Also all
> of the mail folders that were not the inbox needed to be added to the
> user.sub files in /var/lib/imap/user/d to get them to be visible.  So
> I'll have to agree with Adam that migrating from UW is the most
> difficult part.

Did you try to pre-hacked migration scripts available from the KLUG FTP
server?

> Sieve is working but not behaving quite as expected so I will need to
> investigate.
> The thing I have not yet figured out yet is how to successfully have
> shared folders that I can see in my evolution client and my wife can see
> in her m$ outlook 2000 client.  Yes I could create a shared user and
> connect as that user, but doesn't that sort of defeat the purpose.

Users are "user.{username}"

But you can create as many other trees as you want.

For instance, we have - 

departments.actng
departments.actng.creditcards
departments.cis
departments.cis.projects
departments.cis.projects.internet
....
internet.morrison.orders
internet.morrison.harbour
internet.mor-value.orders
....

What makes it "shared" or not is solely the ACL, not the position in the
tree.  So just create whatever roots make sense based upon the
organization of your organization.

You can still send e-mail directly to these folders.  Just add anonymous
posting privilage to the folder.  Define a "postuser" in your imapd.conf
file.

For instance we have "postuser: shared", so one can e-mail to
"shared+departments.cis.projects@morrison-ind.com"  Or create an alias
like "cis-projects" that points to the real address.

> Also I have yet to get some anti spam package going.  I am assuming
> spam-assisin is the suggested.

I'm tempted to try Spam-Assasin, but have been really looking for an
alternative.  I really don't want a huge pile of perl crap on my mail
server.  (IMHO) SERVER SIDE PROCESSES SHOULD BE WRITTEN IN C\C++ (or at
least someone that compiles).   Hello; can they spell
S-C-A-L-A-B-I-L-I-T-Y.