Tiki sends emails for several things (watches, password reset, newsletters, etc.) in addition to end users via Cypht webmail.
System emails should be sent with a valid sender email. Many will put a bogus no-reply at example.org but that is bad practice. We should be using a real email account, accessible via Cypht.
See also Transactional Email Providers
There will be manual replies. There will be bounces. This should be monitored, and handled accordingly. When you have hundreds or thousands of bounces in a Cypht-accessible account, it's tricky and time-consuming to manage.
If you don't handle this, and repeatedly send out emails to invalid accounts, you risk being flagged as a spammer.
Tiki should help detect types of bounces. Ex.:
There should be a dashboard of all bounces, with a way to see
And help Tiki admin handle this
See https://packagist.org/?query=bounce for potential libs.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |