Mail import as archive not working

[floriankessler]

Infos:

• Used Zammad version: 5.2.x
• Used Zammad installation type: docker-compose
• Operating system: Docker Desktop App on OSX
• Browser + version: Chrome, 105.0.5195.52 (Current as of today)

Expected behavior:

• show the option to “Import as archive” as per Account Setup — Zammad documentation

Actual behavior:

• Mails get imported as regular mails

Steps to reproduce the behavior:

• Create a new email channel; make sure
• messages in your inbox are more than two weeks old
• you selected Keep messages on server: No
• you selected Type: IMAP

---

First of all, thank you for that product of yours. Nicely done! Now to the issue at hand:

Whilst I can’t get the import to work, can anyone explain the reasoning behind the way imports are handled?

A few things I would love to see done:

• don’t rely on an opaque/arbitrary (two weeks) heuristic to trigger an import. Instead, let the user decide to do in import as archive, ie fetch mails and don’t change the timestamp and don’t trigger any actions.
• don’t force an email outbound check

This way, I could

• create an inbound-only archive-per-default channel
• pointing to an email folder called, say, IMPORT
• where I move/copy mails into I would want to archive

Thanks in advance,
Florian

[MrGeneration]

Note there’s actually a bug currently…

Import as / email archive import no longer triggered