Bug 49869 - Problem creating a fetchmail account with OX
Problem creating a fetchmail account with OX
Product: Z_Internal OX development
Classification: Unclassified
Component: Mail
UCS 4.4 / 7.10.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: Mail maintainers
Depends on:
  Show dependency treegraph
Reported: 2019-07-18 13:47 CEST by Christina Scheinig
Modified: 2019-08-21 09:08 CEST (History)
3 users (show)

See Also:
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:


Note You need to log in before you can comment on or make changes to this bug.
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

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