Re: [SOGo] Re: Problem with imap and SOGoMailAuxiliaryUserAccountsEnabled = YES

2014-02-26 Thread sr

Ok, thanks!
Have a good day!

Le 25/02/2014 18:43, Janis Hamme a écrit :
Yes that field is missing. Your SOGo password is used for IMAP 
Authentication. When external imap servers are used (as primary imap 
account), a user must change his sogo password manually when the IMAP 
password has changed.


For the other parameters (login name, imap server) you can add 
database fields or set them globally for a user source.


On 02/25/2014 05:59 PM, sr wrote:

Thanks for the answer,

Ok  it's seems to be a little hard to do, specially for the imap 
password ( it's missing the feature IMAPPasswordFieldName ) ...

Tell me if I'm wrong but I think that it could be resolved by:
- create new fields in Sogo postgresql database ( IMAPname, IMAPpass )
- enter with sql commands of each user imap login and password
- In sogo.conf, use IMAPLoginFieldName = IMAPname;
   etc...

Sam



Le 25/02/2014 12:55, Janis Hamme a écrit :





--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Re: Problem with imap and SOGoMailAuxiliaryUserAccountsEnabled = YES

2014-02-25 Thread Janis Hamme
Yes you need to configure a primary email account first.
You can just configure an external mail accounts as primary account. If
required you can make individual settings per users: check
IMAPHostFieldName and IMAPLoginFieldName in the documentation.

 - Janis

On 02/25/2014 10:23 AM, sr wrote:
 Hello,
 I have try the ZEG just to see and the auxiliary email account is
 working...
 Maybe my sogo auxiliary email don't work because there is no primary
 IMAP account that is set and work???
 ( I have set Active directory for user authentification and for now we
 only have an external mail provider )
 Any ideas? :)
 here is my sogo.conf
 Thanks!

 {
 OCSEMailAlarmsFolderURL =
 postgresql://sogo:sogo@localhost:5432/sogo/sogo_alarms_folder;
 OCSFolderInfoURL =
 postgresql://sogo:sogo@localhost:5432/sogo/sogo_folder_info;
 OCSSessionsFolderURL =
 postgresql://sogo:sogo@localhost:5432/sogo/sogo_sessions_folder;
 SOGoACLsSendEMailNotifications = YES;
 SOGoAppointmentSendEMailNotifications = YES;
 SOGoDraftsFolderName = Drafts;
 SOGoEnableEMailAlarms = YES;
 SOGoFoldersSendEMailNotifications = YES;
 //  SOGoIMAPServer = localhost;
 //NGImap4ConnectionStringSeparator = .;
 //SOGoIMAPAclConformsToIMAPExt = YES;
 //SOGoIMAPAclStyle = rfc2086;
 //SOGoIMAPAclStyle = rfc4314;
 //SOGoMailShowSubscribedFoldersOnly = YES;
 //SOGoForceExternalLoginWithEmail = YES;
 //ImapDebugEnabled = YES;
 //NGImap4DisableIMAP4Pooling = YES;
 SOGoLanguage = French;
 SOGoLoginModule = Calendar;
 SOGoMailAuxiliaryUserAccountsEnabled = YES;
 SOGoMailDomain = job.fr;
 SOGoMailingMechanism = smtp;
 SOGoProfileURL =
 postgresql://sogo:sogo@localhost:5432/sogo/sogo_user_profile;
 SOGoSMTPServer = smtp.job.fr;
 SOGoSearchMinimumWordLength = 0;
 SOGoSentFolderName = Sent;
 SOGoSuperUsernames = (
 s.r@ariane.intra,
 );
 SOGoTimeZone = Europe/Paris;
 SOGoTrashFolderName = Trash;
 SOGoUserSources = (
 {
 CNFieldName = cn;
 IDFieldName = cn;
 UIDFieldName = userPrincipalName;
 baseDN = OU=job,DC=ariane,DC=intra;
 bindDN = CN=ldap,CN=Users,DC=ariane,DC=intra;
 bindPassword = ldappw;
 bindFields = (
 sAMAccountName,
 userPrincipalName
 );
 hostname = ldap://172.20.2.3:389;;
 canAuthenticate = YES;
 isAddressBook = YES;
 displayName = Active Directory;
 // mapping AD du champ Service et Societe
 mapping = {
 ou = (department,ou);
 o = (company,o);
 };

 id = ariane.intra;
 type = ldap;
 }
 );
 WOWorkersCount = 3;
 }

 Le 19/02/2014 15:03, sr a écrit :


-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Re: Problem with imap and SOGoMailAuxiliaryUserAccountsEnabled = YES

2014-02-25 Thread sr

Thanks for the answer,

Ok  it's seems to be a little hard to do, specially for the imap 
password ( it's missing the feature IMAPPasswordFieldName ) ...

Tell me if I'm wrong but I think that it could be resolved by:
- create new fields in Sogo postgresql database ( IMAPname, IMAPpass )
- enter with sql commands of each user imap login and password
- In sogo.conf, use IMAPLoginFieldName = IMAPname;
   etc...

Sam



Le 25/02/2014 12:55, Janis Hamme a écrit :

Yes you need to configure a primary email account first.
You can just configure an external mail accounts as primary account. 
If required you can make individual settings per users: check 
IMAPHostFieldName and IMAPLoginFieldName in the documentation.


 - Janis

On 02/25/2014 10:23 AM, sr wrote:

Hello,
I have try the ZEG just to see and the auxiliary email account is 
working...
Maybe my sogo auxiliary email don't work because there is no primary 
IMAP account that is set and work???
( I have set Active directory for user authentification and for now 
we only have an external mail provider )

Any ideas? :)
here is my sogo.conf
Thanks!

{
OCSEMailAlarmsFolderURL = 
postgresql://sogo:sogo@localhost:5432/sogo/sogo_alarms_folder;
OCSFolderInfoURL = 
postgresql://sogo:sogo@localhost:5432/sogo/sogo_folder_info;
OCSSessionsFolderURL = 
postgresql://sogo:sogo@localhost:5432/sogo/sogo_sessions_folder;

SOGoACLsSendEMailNotifications = YES;
SOGoAppointmentSendEMailNotifications = YES;
SOGoDraftsFolderName = Drafts;
SOGoEnableEMailAlarms = YES;
SOGoFoldersSendEMailNotifications = YES;
//  SOGoIMAPServer = localhost;
//NGImap4ConnectionStringSeparator = .;
//SOGoIMAPAclConformsToIMAPExt = YES;
//SOGoIMAPAclStyle = rfc2086;
//SOGoIMAPAclStyle = rfc4314;
//SOGoMailShowSubscribedFoldersOnly = YES;
//SOGoForceExternalLoginWithEmail = YES;
//ImapDebugEnabled = YES;
//NGImap4DisableIMAP4Pooling = YES;
SOGoLanguage = French;
SOGoLoginModule = Calendar;
SOGoMailAuxiliaryUserAccountsEnabled = YES;
SOGoMailDomain = job.fr;
SOGoMailingMechanism = smtp;
SOGoProfileURL = 
postgresql://sogo:sogo@localhost:5432/sogo/sogo_user_profile;

SOGoSMTPServer = smtp.job.fr;
SOGoSearchMinimumWordLength = 0;
SOGoSentFolderName = Sent;
SOGoSuperUsernames = (
s.r@ariane.intra,
);
SOGoTimeZone = Europe/Paris;
SOGoTrashFolderName = Trash;
SOGoUserSources = (
{
CNFieldName = cn;
IDFieldName = cn;
UIDFieldName = userPrincipalName;
baseDN = OU=job,DC=ariane,DC=intra;
bindDN = CN=ldap,CN=Users,DC=ariane,DC=intra;
bindPassword = ldappw;
bindFields = (
sAMAccountName,
userPrincipalName
);
hostname = ldap://172.20.2.3:389;;
canAuthenticate = YES;
isAddressBook = YES;
displayName = Active Directory;
// mapping AD du champ Service et Societe
mapping = {
ou = (department,ou);
o = (company,o);
};

id = ariane.intra;
type = ldap;
}
);
WOWorkersCount = 3;
}

Le 19/02/2014 15:03, sr a écrit :





--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Re: Problem with imap and SOGoMailAuxiliaryUserAccountsEnabled = YES

2014-02-25 Thread Janis Hamme
Yes that field is missing. Your SOGo password is used for IMAP
Authentication. When external imap servers are used (as primary imap
account), a user must change his sogo password manually when the IMAP
password has changed.

For the other parameters (login name, imap server) you can add database
fields or set them globally for a user source.

On 02/25/2014 05:59 PM, sr wrote:
 Thanks for the answer,

 Ok  it's seems to be a little hard to do, specially for the imap
 password ( it's missing the feature IMAPPasswordFieldName ) ...
 Tell me if I'm wrong but I think that it could be resolved by:
 - create new fields in Sogo postgresql database ( IMAPname, IMAPpass )
 - enter with sql commands of each user imap login and password
 - In sogo.conf, use IMAPLoginFieldName = IMAPname;
etc...

 Sam



 Le 25/02/2014 12:55, Janis Hamme a écrit :


-- 
users@sogo.nu
https://inverse.ca/sogo/lists