HESK Email Piping with an existing account

[brandong]

My company is thinking of converting an existing email over to use with our new HESK installation for use with POP3 email piping. When I got it working with the test email, all of the emails in that account were converted to tickets, which was to be expected.

But now we are considering using an existing email account for use with HESK. There are hundreds if not thousands of emails already in this account. So I'm assuming that if I link HESK up to it, we're going to get thousands of tickets generated and people who emailed us years ago will be getting notifications that tickets were created. Definitely not the results we want.

I cannot seem to find any way to set HESK to only work from new emails or even unread emails. So it seems our only option would be to delete every email from this account, or of course use a new account.

Any advice?

[Klemen]

The problem is POP3 protocol doesn't have a way of marking emails as "read/unread" so your mail server will probably indeed send thousands of emails on the first run.

The solution is to use IMAP fetching instead of POP3 fetching. When using IMAP fetching, Hesk will only fetch and convert *unread* emails from the mail server.