Support

Akeeba Ticket System

#23115 ATS not picking up email tickets

Posted in ‘Akeeba Ticket System for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Ticket System version
n/a

Latest post by nicholas on Wednesday, 19 August 2015 03:56 CDT

user88056
 Have checked docs, help and videos.

Setup ATS per document with 2 categories. Added email address to one of the categories and setup CRON fetching script. Script says it completed successfully but no emails appearing as tickets. Are there logs to indicate where the failure may be occurring.

Tickets can be entered manually via the frontend.

nicholas
Akeeba Staff
Manager
Are both email categories aliases to same email inbox? If they are not aliases but individual email inboxes or forwards then the email fetch won't work. In these cases the inbox to which ATS connects does not have any emails or has emails with the wrong sender address.

The same goes for the senders of the emails. The email addresses must match exactly the email address in the user record on the Joomla! site. This can get a bit complicated. For example a user registers with [email protected] but his email sender address is always [email protected]. There is an address mismatch so the email is ignored. Or more typically you get someone subscribe with [email protected] and then send you emails from [email protected]. Also email address mismatch, also no go.

Please note that only unread messages will be parsed. If the message has been marked as read it will be ignored. If you have another email client / web mail reading those messages that could be it.

If you have switched to a different email inbox or mail server please note that messages may be ignored. The only way to prevent double posts / double tickets from the same email message is keeping track of the message IDs. Unfortunately, these are NOT globally unique. They are unique in a mailbox. When you move to another mailbox or mail server it is absolutely certain that new emails will have the same message IDs as older emails on the old server / mailbox. As such they will be ignored. Unfortunately there is no work around this. It will either be the way it is now or you'll end up with the same email message resulting in multiple tickets / posts being created in ATS. We genuinely chose the lesser of two evils.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user88056
Ok you referenced two items that I did not see explained in the documentation with regards to aliases and matching Joomla users. What is the best setup approach for allowing anyone to email a question that is recorded as a ticket by ATS? Sounds like a dedicated mailbox is needed that is not monitored by another other clients to ensure that it remains unread. Aliases here could allow multiple flows but for the moment, let concentrate on the single flow from any user. I need this to work for unregistered users.

If I have 2 categories setup, what happens if I only define an email address for one of them?

nicholas
Akeeba Staff
Manager
They are mentioned in the documentation but not in the same place. There are bits in the category configuration, bits in the component Options and other bits in the plugin/CRON job documentation. Hm, I'll have to fix that.

What is the best setup approach for allowing anyone to email a question that is recorded as a ticket by ATS? Sounds like a dedicated mailbox is needed that is not monitored by another other clients to ensure that it remains unread. Aliases here could allow multiple flows but for the moment, let concentrate on the single flow from any user. I need this to work for unregistered users.


First create a single, new mailbox for ATS. One that's not used by anyone or anything else. For example [email protected]

Then create one or more aliases for this mailbox, e.g. [email protected] and [email protected].

Edit each support category. There's the "Category email" option in the "Akeeba Ticket System - General" tab. Enter the email alias you want to use for this category, e.g. [email protected] for Category 1, [email protected] for Category 2.

I need this to work for unregistered users.


This is not possible with ATS. It requires a Joomla! user account to be already present. Each ticket is owned by a Joomla! user. An unregistered "user" is not a user, it's a guest who has no user ID. If we allowed tickets to be filed by guests we'd have two problems:
1. It would be impossible to apply access control to a category allowing guests to post tickets and replies. Everybody would be able to read everyone else's ticket. And no, email address based authentication is not authentication at all. Email addresses are not passwords, they are usernames.
2. Anybody could edit everyone else's tickets and reply to them. Also, everyone would appear as "Guest" making it impossible for you to know who you're talking to. Not to mention that it would be nigh impossible for ATS to know who to email.

If we allowed user creation on guest ticket creation you'd end up with a massive backdoor for spammers. So no go either.

For these (and many more) reasons we are not going to ever implement a guest "user" ticket feature.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!