Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some who self triggering loop of Ticket Update Notifications #15

Closed
marco-aa opened this issue Aug 23, 2017 · 5 comments
Closed

Some who self triggering loop of Ticket Update Notifications #15

marco-aa opened this issue Aug 23, 2017 · 5 comments

Comments

@marco-aa
Copy link
Contributor

marco-aa commented Aug 23, 2017

My mailbox was filling it self with "Ticket updated: #15:" over and over ;)

Not sure why - it looks like the messages send for update trigger them self a the next cron.

I was using the dev branch.

https://github.com/BadChoice/handesk/blob/dev/app/Notifications/NewComment.php

maybe related to

@BadChoice
Copy link
Owner

the ticket updated email is sent to the requester, to team and to admins, so if you are all, you'll get three emails with the same, could it be the thing?

The other thing is that your mail fetcher is not deleting the messages once downloaded (can you check that?)

Or are you using the same mailbox to send the update and to fetch?

@marco-aa
Copy link
Contributor Author

marco-aa commented Aug 23, 2017

The sender is someuser@somedomain.com

MAIL_USERNAME=support@ourserver.com
MAIL_FETCH_USERNAME=support@ourserver.com

Admin Email is support@ourserver.com
Team Email is support@ourserver.com

Do you think this setup is bad ?

I looked into the INBOX of support@ourserver.com and the email form user someuser@somedomain.com was deleted - the Ticket Update Emails not

Or are you using the same mailbox to send the update and to fetch?#

Yes

@BadChoice
Copy link
Owner

Yes, since it will enter a infinite loop, ticket updated mail, its fetched and sends another mail, fetched again... and so on, you ahould have a email user just for incoming tickets, so all your support is done trough handesk

@marco-aa
Copy link
Contributor Author

marco-aa commented Aug 23, 2017

Ah ok - gracias! (well this is more clean / straid forward than filter out the own tickets)

Should we mention this in the read.me as best practice ? If yes i can put it in the next PR ;)
I'll setup it up and ticket can be closed :)

@BadChoice
Copy link
Owner

Sure if you want, there is no harm in adding this note
Thank you so much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants