I'm converting an environment from mandrake to centos, and always try to use the applications standard on the distribution. This means a switch from courier to cyrus.
A bit of reading uncovered a potential problem - the site uses firstname.lastname@domain, and I have come across references that Cyrus does not support this. I couldn't find this limitation in the Cyrus documentation.
Is it true?
regards Dave www.hornfordassociates.com
Dave Hornford wrote:
I'm converting an environment from mandrake to centos, and always try to use the applications standard on the distribution. This means a switch from courier to cyrus.
A bit of reading uncovered a potential problem - the site uses firstname.lastname@domain, and I have come across references that Cyrus does not support this. I couldn't find this limitation in the Cyrus documentation.
Is it true?
Hmm. Do you need it as >username<? You could create usernames as firstname_lastname@domain and use the virtusertable to map firstname.lastname@domain to the loginname using the '_'.
Another posibility would be to use LDAP... Harder...
And yet another posibility (taken from man imapd.conf):
unixhierarchysep: 0 Use the UNIX separator character '/' for delimiting levels of mailbox hierarchy. The default is to use the netnews separator character '.'.
I never tried it myself, but it should work fine...
Best, Oliver
Oliver Falk wrote:
Dave Hornford wrote:
I'm converting an environment from mandrake to centos, and always try to use the applications standard on the distribution. This means a switch from courier to cyrus.
A bit of reading uncovered a potential problem - the site uses firstname.lastname@domain, and I have come across references that Cyrus does not support this. I couldn't find this limitation in the Cyrus documentation.
Is it true?
Hmm. Do you need it as >username<? You could create usernames as firstname_lastname@domain and use the virtusertable to map firstname.lastname@domain to the loginname using the '_'.
Another posibility would be to use LDAP... Harder...
And yet another posibility (taken from man imapd.conf):
unixhierarchysep: 0 Use the UNIX separator character '/' for delimiting levels of mailbox hierarchy. The default is to use the netnews separator character '.'.
Oliver, Thanks All I need to do is maintain email address format firstname.lastname@domain, I do not need these as either unix/windows(samba) usernames. Currently these are a mixed bag of firstname, initiallastname & lastname. One step on the migration is to at least standardize the new ones.
Any suggestions on whether we'd be better off operationally using ldap to control the mapping or the virtusertable. It is a smallish site (<50 users), who are looking for a very automated administrative/operations environment.
This is my first cyrus so what I don't know is everything :-)
Dave
On Sun, October 30, 2005 19:51, Dave Hornford wrote:
Oliver, Thanks All I need to do is maintain email address format firstname.lastname@domain, I do not need these as either unix/windows(samba) usernames. Currently these are a mixed bag of firstname, initiallastname & lastname. One step on the migration is to at least standardize the new ones.
Any suggestions on whether we'd be better off operationally using ldap to control the mapping or the virtusertable. It is a smallish site (<50 users), who are looking for a very automated administrative/operations environment.
This is my first cyrus so what I don't know is everything :-)
Dave
Hi Dave,
I suggest the usage of web-cyradm (http://web-cyradm.org/). There are SQL scripts for installing MySQL tables for the virtual user management. On the site you will also find the configuration instructions for postfix.
I did a new installation just last week and everything worked straight on.
BTW: Cyrus is a really good choice. Shared folders and quotas without any problems. And the performance is great.
Greets, Sebastian
Dave Hornford wrote:
All I need to do is maintain email address format firstname.lastname@domain, I do not need these as either unix/windows(samba) usernames. Currently these are a mixed bag of firstname, initiallastname & lastname. One step on the migration is to at least standardize the new ones.
Than simply use virtusertable (if you use sendmail, or whatever is postfix equivalent if you use postfix) to map email addresses in first.last@domain format to actual usernames. This is kind of standard thing to do, and I'm surprised you haven't done it that way while you were on courier too.
Aleksandar Milivojevic wrote:
Dave Hornford wrote:
All I need to do is maintain email address format firstname.lastname@domain, I do not need these as either unix/windows(samba) usernames. Currently these are a mixed bag of firstname, initiallastname & lastname. One step on the migration is to at least standardize the new ones.
Than simply use virtusertable (if you use sendmail, or whatever is postfix equivalent if you use postfix) to map email addresses in first.last@domain format to actual usernames. This is kind of standard thing to do, and I'm surprised you haven't done it that way while you were on courier too.
Aleksandar Milivojevic wrote:
Dave Hornford wrote:
All I need to do is maintain email address format firstname.lastname@domain, I do not need these as either unix/windows(samba) usernames. Currently these are a mixed bag of firstname, initiallastname & lastname. One step on the migration is to at least standardize the new ones.
Than simply use virtusertable (if you use sendmail, or whatever is postfix equivalent if you use postfix) to map email addresses in first.last@domain format to actual usernames. This is kind of standard thing to do, and I'm surprised you haven't done it that way while you were on courier too.
Aleksandar, Its the result of reading something about an app I know nothing about and attempting to head-off a problem before I get there. In retrospect what I read, and the follow-up google searches that showed there might be a problem, were from people who knew less than I did. But that is the internet - help files and directions written for people who know what to do, and help queries from the lost, who don't even know what terminology to use when asking for help.
Dave
Quoting Dave Hornford OSD@HOrnfordAssociates.com:
Its the result of reading something about an app I know nothing about and attempting to head-off a problem before I get there. In retrospect what I read, and the follow-up google searches that showed there might be a problem, were from people who knew less than I did. But that is the internet - help files and directions written for people who know what to do, and help queries from the lost, who don't even know what terminology to use when asking for help.
My guess is that what you found on the web were problems with usernames containing dots. Not email addresses containing dots. If users have usernames as you described (with no dots), you should be fine. Translation from first.last@domain to usernames is most likely done at MTA level, whatever they used for MTA. If they used sendmail or postfix, you probably won't have any additional work to do. If they used Courier's MTA module, you'd need to replace that with either sendmail or postfix and create table with mappings between email addresses and usernaems (either using aliases or virtusertables).
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
On Sun, 2005-10-30 at 14:22, Aleksandar Milivojevic wrote:
All I need to do is maintain email address format firstname.lastname@domain, I do not need these as either unix/windows(samba) usernames. Currently these are a mixed bag of firstname, initiallastname & lastname. One step on the migration is to at least standardize the new ones.
Than simply use virtusertable (if you use sendmail, or whatever is postfix equivalent if you use postfix) to map email addresses in first.last@domain format to actual usernames.
Alises will work if all the names are unique. You only need virtusertable if there are identical first.last with different @domain portions that map to different actual destinations.
Dave Hornford wrote:
Oliver Falk wrote:
Dave Hornford wrote:
I'm converting an environment from mandrake to centos, and always try to use the applications standard on the distribution. This means a switch from courier to cyrus.
A bit of reading uncovered a potential problem - the site uses firstname.lastname@domain, and I have come across references that Cyrus does not support this. I couldn't find this limitation in the Cyrus documentation.
Is it true?
Hmm. Do you need it as >username<? You could create usernames as firstname_lastname@domain and use the virtusertable to map firstname.lastname@domain to the loginname using the '_'.
Another posibility would be to use LDAP... Harder...
And yet another posibility (taken from man imapd.conf):
unixhierarchysep: 0 Use the UNIX separator character '/' for delimiting levels of mailbox hierarchy. The default is to use the netnews separator character '.'.
Oliver, Thanks All I need to do is maintain email address format firstname.lastname@domain, I do not need these as either unix/windows(samba) usernames. Currently these are a mixed bag of firstname, initiallastname & lastname. One step on the migration is to at least standardize the new ones.
Any suggestions on whether we'd be better off operationally using ldap to control the mapping or the virtusertable. It is a smallish site (<50 users), who are looking for a very automated administrative/operations environment.
This is my first cyrus so what I don't know is everything :-)
Sebastian allready said what there is to say 'bout Cyrus. :-)
There's no need to use LDAP for such a small site, if you don't want to grow very much or there are really good reasons. :-)
If you don't need the loginnames as first.last@domain, then you're better off with not using unixhierarchysep, as the normal way using the netnews seperator is really good tested. :-)
So long, Oliver
Dave Hornford wrote:
A bit of reading uncovered a potential problem - the site uses firstname.lastname@domain, and I have come across references that Cyrus does not support this. I couldn't find this limitation in the Cyrus documentation.
Do they use them for usernames and email, or just email? If they use them for usernames, simply create such mailboxes. If they use them for email only (and use normal usernames), than it is MTA thing, not Cyrus thing. If you use sendmail as MTA, you can use virtusertable feature to map firstname.lastname@domain to usernames.