Bug 690348

Summary:	yast2-mail fails to modify mail domain type
Product:	[openSUSE] openSUSE 11.4	Reporter:	Wolfgang Rosenauer <wolfgang>
Component:	YaST2	Assignee:	Peter Varkoly <varkoly>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	openSUSE 11.4
Whiteboard:
Found By:	Community User	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Wolfgang Rosenauer 2011-04-27 19:23:09 UTC

I'm using LDAP configuration set up with YaST.

After setting up the basic ldap tree and also creating a DNS zone for the local network I've tried to use yast2-mail to setup the mailserver.

The module complained about no main maildomain being set and I would need to fix it. The zone configured earlier was visible in the module with type "none". I've changed that to "main" and quit the module.
During saving of the configuration it failed to write the mail domain configuration.

The YaST log shows:

2011-04-27 21:02:09 <3> oxlive(20427) [agent-ldap] LdapAgent.cc(debug_exception):485 ldap error while modifying zoneName=ox.rosenauer.org,ou=DNS,dc=ox,dc=rosenauer,dc=org (21
): Invalid syntax
2011-04-27 21:02:09 <3> oxlive(20427) [agent-ldap] LdapAgent.cc(debug_exception):487 additional info: objectClass: value #1 invalid per syntax
2011-04-27 21:02:09 <3> oxlive(20427) [-e] SCR_INIT_FAILED[2394:/usr/share/YaST2/modules/YaPI/MailServer.pm] LDAP modify failed
2011-04-27 21:02:09 <3> oxlive(20427) [-e] Description: 21 : Invalid syntax
2011-04-27 21:02:09 <2> oxlive(20427) [YCP] Report.ycp:470 Cannot write the mail server domains.

Comment 1 Wolfgang Rosenauer 2011-04-27 20:38:08 UTC

Now I've tried it differently. I didn't create the zone with yast2 dns-server before but immediately configured a "main" zone within the mail module.

That failed with a similar error "invalid DN".

Then I went back to yast2 ldap-server and added "dnszone" and "suse-mailserver" schemata to the ldap configuration and tried again to configure the main domain.
Then it worked.

Comment 2 Peter Varkoly 2011-08-22 09:39:55 UTC

The reason is the same like in bnc#690345

*** This bug has been marked as a duplicate of bug 690345 ***