# Preventing multiple imports of the same message

**URL:** https://community.zammad.org/t/preventing-multiple-imports-of-the-same-message/19231
**Category:** No implementation planned
**Tags:** missing-template
**Created:** [December 9, 2025, 9:36am UTC](https://community.zammad.org/t/preventing-multiple-imports-of-the-same-message/19231 "2025-12-09T09:36:57Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![DieFormel](https://community.zammad.org/letter_avatar_proxy/v4/letter/d/77aa72/32.png) [@DieFormel](https://community.zammad.org/u/DieFormel)
#### Post date: [December 9, 2025, 9:36am UTC](https://community.zammad.org/t/preventing-multiple-imports-of-the-same-message/19231/1 "2025-12-09T09:36:57Z")

</div>

The fact that changing the status of an already imported message to “ **unread** ” triggers a new import is, in my opinion, not ideal.  
We weren’t even aware of this until a cautious employee manually changed the status of several emails to “unread,” thus triggering a whole series of multiple imports.

My suggestion would be to train zammad’s logging system to import a message and log it based on clear criteria, so that multiple imports are impossible.

For example, it would be sensible to log the following values ​​for an email:

- **Timestamp**
- **Sender**
- **Subject**

**If all three values ​​match a protocol entry** for a new/unread message, the message should **not be imported** by default.

This behavior could then be offered as an on/off option to accommodate different scenarios.

---

<div class="post-metadata">

### Author: ![DieFormel](https://community.zammad.org/letter_avatar_proxy/v4/letter/d/77aa72/32.png) [@DieFormel](https://community.zammad.org/u/DieFormel)
#### Post date: [December 12, 2025, 2:18pm UTC](https://community.zammad.org/t/preventing-multiple-imports-of-the-same-message/19231/2 "2025-12-12T14:18:26Z")

</div>

Please send a like (❤) if you support this idea!  
Otherwise, zammad will not take action and begin implementation.

---

<div class="post-metadata">

### Author: ![richie\_77](https://community.zammad.org/user_avatar/community.zammad.org/richie_77/32/5964_2.png) [@richie\_77](https://community.zammad.org/u/richie_77)
#### Post date: [December 15, 2025, 3:40pm UTC](https://community.zammad.org/t/preventing-multiple-imports-of-the-same-message/19231/3 "2025-12-15T15:40:12Z")

</div>

Why you don’t delete messages after import? Where is the need for setting mails in a mailbox for a ticket system manually to “unread”?

---

<div class="post-metadata">

### Author: ![DieFormel](https://community.zammad.org/letter_avatar_proxy/v4/letter/d/77aa72/32.png) [@DieFormel](https://community.zammad.org/u/DieFormel)
#### Post date: [December 15, 2025, 3:58pm UTC](https://community.zammad.org/t/preventing-multiple-imports-of-the-same-message/19231/4 "2025-12-15T15:58:44Z")

</div>

We are in a multi-user environment here, where several people are querying and editing the same IMAP mailbox.

That`s why I said: We weren’t even aware of this until a cautious employee manually changed the status of several emails to “unread,” thus triggering a whole series of multiple imports.

But yes, deleting the mail directly after importing would be the normal way.

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [December 15, 2025, 3:59pm UTC](https://community.zammad.org/t/preventing-multiple-imports-of-the-same-message/19231/5 "2025-12-15T15:59:25Z")

</div>

There shouldn‘t be anyone else using and reading in a mailbox of Zammad at all.

---

<div class="post-metadata">

### Author: ![richie\_77](https://community.zammad.org/user_avatar/community.zammad.org/richie_77/32/5964_2.png) [@richie\_77](https://community.zammad.org/u/richie_77)
#### Post date: [December 15, 2025, 5:24pm UTC](https://community.zammad.org/t/preventing-multiple-imports-of-the-same-message/19231/6 "2025-12-15T17:24:13Z")

</div>

> [@DieFormel](#):
>
> We are in a multi-user environment here, where several people are querying and editing the same IMAP mailbox.

This is imho the normal behaviour for a ticket system - multiple users watching/using the same inbound chanel. Use a functional mailbox instead of personal ones.

---

<div class="post-metadata">

### Author: ![YetAnotherGerrit](https://community.zammad.org/user_avatar/community.zammad.org/yetanothergerrit/32/8413_2.png) [@YetAnotherGerrit](https://community.zammad.org/u/YetAnotherGerrit)
#### Post date: [December 16, 2025, 9:56am UTC](https://community.zammad.org/t/preventing-multiple-imports-of-the-same-message/19231/7 "2025-12-16T09:56:30Z")

</div>

Thank you for your input. We currently don’t plan to introduce a duplicate detection on mail fetching, as the benfit does not outweight the performance costs.

---

<div class="post-metadata">

### Author: ![YetAnotherGerrit](https://community.zammad.org/user_avatar/community.zammad.org/yetanothergerrit/32/8413_2.png) [@YetAnotherGerrit](https://community.zammad.org/u/YetAnotherGerrit)
#### Post date: [December 16, 2025, 9:56am UTC](https://community.zammad.org/t/preventing-multiple-imports-of-the-same-message/19231/8 "2025-12-16T09:56:42Z")

</div>


