Email flood after enabling POP3 Fetching

[subsonic68]

New install of Hesk and we got an email flood after enabling POP3 fetching. We aren't allowed to delete email from our helpdesk email account, so after enabling POP3 it starting creating tickets for very old emails of issues resolved long ago, and the worst part was that it starting flooding our users inboxes with messages.

I had SMTP piping as well as POP3 fetching enabled if it makes any difference. Our Hesk user email addresses are not the same as our admin email or help desk email address that POP3 was connecting to. We do not have any auto replies or autoresponders.

All we want Hesk to do in regards to email is create a ticket when any NEW emails are received. Our help desk email account has thousands of read messages that we don't want to be imported or replied to.

[Klemen]

Your mail server is the one sending emails to HESK, HESK will just process anything that comes in. So you need to stop the server from sending old mails over POP3.

This is something you will need to configure at the server-side. POP3 protocol has no way of marking emails as "read" though. Gmail for example has an option to only send emails over POP3 for "emails that arrive from now on", but this is their custom solution.

And this is exactly why step 1 in the POP3 fetching instructions says

Preferably this should be a new (unused) email account

[subsonic68]

I guess that I won't be turning POP3 back on. I'm not allowed to delete the old email out of the inbox, and can't create a new email address as management wants to keep the email and doesn't want the users to have to learn something other than helpdesk@domain.com.

Thanks for the reply.