Home » Kerio User Forums » Kerio Connect » Advice on best way of handling "department" email
  •  
macjimbo

Messages: 52
Karma: 6
Send a private message to this user
Hi

As our business has grown, we have lots of people working different shifts and when they send an email to a customer, they might not be around to receive and respond to replies straight away.

We use a generic info<_at_> email address to receive incoming mail for our reception department, and this goes to a public folder. All the reception team have access to this folder but, when they reply, it comes from their own email address instead of info@

I know that I could ask them to put a 'reply-to' field in but this is time consuming and will sometimes get forgotten. If I automate it, I run the risk of confidential emails going out with 'reply to info@'

Please can anyone share their strategies for dealing with this? One approach is to set up a dedicated user named 'info' and give all users access to it - but that would only work using a mail client. For a variety of reasons, we are often using the Kerio Connect Webmail client - and that doesn't let you sign in to more than one account at a time.

We run the latest Kerio Connect, and a network of Macs running 10.13.

Hope someone can offer guidance/experience.

Thanks!
  •  
Maerad

Messages: 210
Karma: 38
Send a private message to this user
An idea for that, that is also in line with the data protection.

Configuration > Message Filter

- Change the header to the message that goes to the info@ address with those rules to something like "IM: (Old Subject)" or any other kind of code you can track
- Add another filter, so any mail with this code in the subject will be redirected to the info mail address.

You can also add another options with this, like a notification to the real "to:" address or something like that. So unless the user removes the code from the header, it will always go to the info account.

The other way would be, that you change the header like I mentioned before and the user adds a rule in his kerio settings, that any mail with that code gets moved to the public folder.

So if he leaves the office, he needs to enable the rule and be done. Sure, they could forget it, but if they do it for some days with a daily remainder, they get used to it.
  •  
macjimbo

Messages: 52
Karma: 6
Send a private message to this user
that's a really helpful reply, thank you. I will have a think about the first option, which I think would work well


thanks again

James
  •  
macjimbo

Messages: 52
Karma: 6
Send a private message to this user
For posterity, to make it work I had to make a couple of changes to prevent outgoing replies being diverted straight to info<_at_> instead of the intended customer.

The rules are:

1. Tag info emails:

IF 'To' contains info@company
AND Subject does not contain [IN]:

THEN Change header (Subject) - [IN]: ${Subject}


2. Redirect replies to info:

IF Subject contains [IN]:
AND Sender does not contain @company

THEN Redirect to info@company


Hope this helps someone Smile

[Updated on: Mon, 21 May 2018 13:55]

Previous Topic: Happy With GFI Handling of Kerio Connect
Next Topic: Microsoft System Center Endpoint Anti-malware scanning
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Sat Oct 20 09:03:03 CEST 2018

Total time taken to generate the page: 0.68650 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.