View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004283 | SOGo | Backend Calendar | public | 2017-09-11 00:41 | 2018-03-13 19:36 |
Reporter | davrom | Assigned To | |||
Priority | high | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | Dell/Asus | OS | x86_64 | OS Version | 6.5 |
Product Version | 3.2.0 | ||||
Summary | 0004283: Underlying server domain used when sending calendar entries and/or invites | ||||
Description | The customer has noted that when using either SOGo web interface or e-mail clients such as Thunderbird or iPad e-mail, any events sent from the Linux server show as a domain of the default domain on the server rather than the one configured in SOGo. This is a multi-domained server for e-mail. | ||||
Steps To Reproduce | Go into a calendar event and send an invite or notification to a third party. | ||||
Additional Information | The default domain name of the server was set so that should any domain name be 'visible' to a recipient/third party, the other domains on the server would never be visible and the default server domain has no 'real' presence as an e-mail/web entity in itself, it is purely a domain name with the relevant Zone file setup - kind of like an unassociated unrelated domain name was chosen years ago. Example, server domain name is: xyz.net.au, but the sending domain name setup in SOGo is: customer.com.au Also side question, this server is using the older GNU Default setup as a user rather than /etc/sogo/sogo.conf - should this be migrated? I ask this to see if this might be part of the issue and also looking at moving MySQL setup to ldap for multiple domain name issues in SOGo. (per 0004222) | ||||
Tags | No tags attached. | ||||