Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-20-2016 09:58 AM
A ticket was opened to remove a users email address. Ticket was opened by the user himself. When ticket is closed, it will send email to just removed email address. Server answers "Delivery failed blah blah" and ticket activates again and gets In Progress state.
So I added regular expression \Delivery\sfailed.* to ignore subjects. Test field tells match found. But in fact this doesn't work.
So I added regular expression \Delivery\sfailed.* to ignore subjects. Test field tells match found. But in fact this doesn't work.
Labels:
- Labels:
-
General Discussion
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-23-2016 09:00 PM
This is causing us huge headache, it needs to be addressed, we have tried several rules on our exchange online to combat this but doesn't work either.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-26-2016 02:54 PM
spallison wrote:
This is causing us huge headache, it needs to be addressed, we have tried several rules on our exchange online to combat this but doesn't work either.
I had a short email conversation with support. Turned out Lansweeper mail rules apply only to new incoming tickets. Rules set at https://<yourserver>:<port>/configuration/HelpdeskEmail/ won't help.
Michael V. suggested ignoring mail on mailbox/server level. I logged to email with our Lansweeper mailbox credentials and added some rules to delete mail delivery error messages. So far this is working.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-24-2016 04:51 PM
spallison wrote:
This is causing us huge headache, it needs to be addressed, we have tried several rules on our exchange online to combat this but doesn't work either.
Ignoring these messages on mailbox/server level is the way to go.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-25-2016 08:47 AM
Michael.V wrote:spallison wrote:
This is causing us huge headache, it needs to be addressed, we have tried several rules on our exchange online to combat this but doesn't work either.
Ignoring these messages on mailbox/server level is the way to go.
Ticket tells "state changed by Microsoft Outlook". Clicking unspecified user Microsoft Outlook allows to create a new lansweeper user: for starters there is name and email address "MicrosoftExchange<identification number>@domain.com". This is the mailbox I should ignore?
What about relevant mails coming via the same server if ignore the server totally?
