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:
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
Note there’s actually a bug currently…
opened 05:02PM - 13 Mar 22 UTC
bug
channel
verified
can't reproduce
mail processing
<!--
Hi there - thanks for filing an issue. Please ensure the following things … before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: verified on stable 5.0 and develop 5.1 as of 13th March
* Installation method (source, package, ..): any
* Operating system: any
* Database + version: any
* Elasticsearch version: any
* Browser + version: any
### Expected behavior:
Zammad suggests an archive import when you have mails older than two weeks in your mail box.

### Actual behavior:
Zammad warns you about a heckton of mails but doesn't care to suggest archive mode.
I've used an email account with 2 year old mails

Even my other personal, bigger mailbox does not apply for archive import.
### Steps to reproduce the behavior:
* have a mailbox with old mails
* try to add it to Zammad, before you're shown the SMTP dialogue, Zammad should suggest archive importing
Yes I'm sure this is a bug and no feature request or a general question.
system
Closed
April 8, 2023, 10:23am
4
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.