Hi list,
I've got SOGo running on ubuntu precise with postfix, dovecot and mysql as
backends.
It's been working nice and reliable for the last 18 months, handling about
8-10k mails per day.
Postfixadmin is used to manage all users, aliases, forwardings and
maildomains.
The server hosts several domains (for smtp and imap), sogo however serves
only one of the domains on the server.
The sogo usersource "sogo_auth" is a view on the mail database (that
postfixadmin created), like so:
select `mail`.`mailbox`.`username` AS `c_uid`,`mail`.`mailbox`.`username`
AS `c_name`,`mail`.`mailbox`.`password` AS
`c_password`,`mail`.`mailbox`.`name` AS `c_cn`,`mail`.`mailbox`.`username`
AS `mail`,`mail`.`mailbox`.`maildir` AS `home` from `mail`.`mailbox`
/etc/sogo/sogo.conf contains the lines:
SOGoUserSources = (
{
IMAPLoginFieldName = "c_uid";
MailFieldNames = (
mail
);
canAuthenticate = YES;
displayName = "sogo_auth";
id = directory;
isAddressBook = YES;
type = sql;
userPasswordAlgorithm = "md5-crypt";
viewURL = "mysql://user:secretpassword@localhost
:3306/sogo/sogo_auth";
}
All other sogo information is kept in a separate database "sogo", which is
configured just like the sogo installation manual says
This seemed to be a good idea at the time...
Now, the need for room- and other resources has popped up :-|
The sogo wiki http://wiki.sogo.nu/ResourceConfiguration tells me that
"SOGo user source (in SOGo config) must be defined with KindFieldName and
MultipleBookingsFieldName"
Right.
How could i extend my sql-db to offer the fields "kind" and
"multiple_bookings"?
Would it be save to add these fields to the postfixadmin db "mailbpx" and
modify the view, or would it be possible (or even safer) to add another
table (e.g. resource_things) to the "sogo" database, create the fields
"kind" and "multiple_bookings" there and modify the above stated view to
suit, linking the tables with some primary key?
i'm not too much of a sql pro, so i am quite at a loss with this.
Would it be ok to simply add the statements KindFieldName = kind;
MultipleBookingsFieldName = multiple_bookings; to the SOGoUserSources as
defined above?
BTW. can i change the "displayName" from sogo_auth to something more
intellegible without detrimental side-effects? Or would all the
thunderbirds go coughing all over the place? I didn't realize "back then"
that the displayName would actually be seen by clients ...
Thanks for your ideas,
Jochen
--
[email protected]
https://inverse.ca/sogo/lists
