Release overview
Release Date: 22 May 2018
Servers: atmail cloud EU servers
Release Versions: atmail suite - 8.3.12 / atmail API server - 8.3.12 / atmail dav server - 8.3.12 / atmail mail server - 8.3.12
atmail suite summary
Release Highlights
- Security Fix
Security
- CheckUserProvisioning debug log no longer displays passwords if
SHOW_PASSWORDS
is off
Known Issues
- API call getContacts → blank {} properties is treated as NULL
- atmail suite → When receiving a thread update, the avatar is not updated to latest replied user
- Some mail is not visible due to virtual folder configuration
- RPM script doesn't output the right configure command as shown in help center
- Deleting a folder will move the email to inbox rather then deleting the mail within the folder
- Calendar entries that are not parsable by the dav server will not be displayed in the webmail UI
- Transient password accounts will not work if the domain is switch back to normal logins and visa versa
atmail mail server summary
Release highlights
- You can now white label from address for customised forgotten password emails
Bugs
- Assigned user roles no longer become unavailable after creator is deleted
Known Issues
- On first installation, if a domain is created before services are published the domain will be unavailable to the API.
Changelog
T | Key | Summary | Description | Status | Component(S) |
---|---|---|---|---|---|
AT8-719 | Incorrect webmail sent folder being used |
Along with Sent, other conflicting folder names will need to be investigated as well. |
RESOLVED | WEBMAIL UI, DOVECOT | |
AT8-713 | ITSec security failures |
Multiple identified security issues resolved. |
RESOLVED | MAIL SERVER | |
AT8-709 | API List should accept params for filtering |
http://domain.com/admin/index.php/api/aliases/list currently only returns an accounts full list of aliases. |
RESOLVED | MAIL SERVER, MAIL SERVER API | |
AT8-698 | CheckUserProvisioning security in debug log |
API security issues resolved. |
RESOLVED | JMAP API | |
AT8-687 | Whitelabel noreply@* address |
In accordance with our white labelling functionalities, the noreply@ account defined in api.conf should have the ability to be defined on a per domain basis for password recovery and any other noreply@ functionality. |
RESOLVED | JMAP API | |
AT8-686 | Assign user roles become unavilable after creator is deleted |
Roles do not move back up the hierarchy when the creator of the role is deleted. If an subadmin is deleted who has created and assigned roles to a subsubadmin, then the role disappears from the webadmin interface. The role appears to still exist in the db, but is no longer available as the cloudadmin does not have permissions to view/edit the role created by the subadmin. Ideally, the role should move back up the hierarchy if the creator is deleted so the role can be maintained by the cloud admin and the user with that assigned role can retain it. |
RESOLVED | MAIL SERVER |
Comments