Bug 49869

Summary: Problem creating a fetchmail account with OX
Product: Z_Internal OX development Reporter: Christina Scheinig <scheinig>
Component: MailAssignee: Mail maintainers <mail-maintainers>
Status: REOPENED --- QA Contact:
Severity: normal    
Priority: P5 CC: best, schwardt, troeder
Version: UCS 4.4 / 7.10.2   
Target Milestone: ---   
Hardware: Other   
OS: Linux   
What kind of report is it?: Bug Report What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.229 Enterprise Customer affected?: Yes
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: 2019071821000228 Bug group (optional):
Max CVSS v3 score:

Description Christina Scheinig univentionstaff 2019-07-18 13:47:13 CEST 
The customer described the following problem:

If you create a Fetchmail account (in this case Single Drop) on a UCS with OX via the OX Mail Module, the LDAP object is stored in the top level directly under dc=domain,dc=de. The Listener script ox-fetchmail only looks for objects under cn=mail,dc=domain,dc=de when building the fetchmailrc. So of course no mails are retrieved for all new fetchmail accounts.

If you move the entry, the listener script will apply again

UCS: 4.4-0 errata168
Installed: mailserver=12.0 open-xchange-guard=2.10.2-ucs1 open-xchange-text=7.10.2-ucs1 oxseforucs=7.10.2-ucs1 self-service=4.0

This is quite urgend, because this applies to all of his customers. The major problem is to recognize the problem in the first place
Comment 1 Florian Best univentionstaff 2019-07-18 13:56:47 CEST 

*** This bug has been marked as a duplicate of bug 49826 ***
Comment 2 Florian Best univentionstaff 2019-07-18 14:01:36 CEST 
Sorry, wrong bug number. This is the correct one.

*** This bug has been marked as a duplicate of bug 49849 ***
Comment 3 Sönke Schwardt-Krummrich univentionstaff 2019-07-18 14:07:05 CEST 
RESOLVED-DUPLICATE → REOPENED

I think, these are 2 different bugs:
49849) define default position in UDM module
49869) the listener module should not rely on a specific position