# Single mail not being fetched
**URL:** https://community.zammad.org/t/single-mail-not-being-fetched/3382
**Category:** Technical assistance
**Created:** [November 6, 2019, 8:41am UTC](https://community.zammad.org/t/single-mail-not-being-fetched/3382 "2019-11-06T08:41:14Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@maxxer](https://community.zammad.org/u/maxxer)
#### Post date: [November 6, 2019, 8:41am UTC](https://community.zammad.org/t/single-mail-not-being-fetched/3382/1 "2019-11-06T08:41:14Z")
### Infos:
- Used Zammad version: 3.0
- Used Zammad installation source: docker
- Operating system: Ubuntu 18.04
- Browser + version: any
### Expected behavior:
- All mails being fetched
### Actual behavior:
- We found **one** email in the mailbox not being downloaded
Unfortunately we didn’t notice the mail until the customer called. Now the message is left unread on the server, and it’s not being downloaded. How can I have it fetched?
---
### Author:  [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [November 6, 2019, 12:27pm UTC](https://community.zammad.org/t/single-mail-not-being-fetched/3382/2 "2019-11-06T12:27:13Z")
`Channel.fetch`
check the output, Zammad will tell you the issue.
You can also find the issue in the log.
Quick guess: The mail is too big.
---
### Author:  [@maxxer](https://community.zammad.org/u/maxxer)
#### Post date: [November 15, 2019, 7:18am UTC](https://community.zammad.org/t/single-mail-not-being-fetched/3382/3 "2019-11-15T07:18:49Z")
Indeed that is. I found this in the _Email channel_ page:
This can be problematic… Isn’t it better to trigger a notification for such errors? I mean, this is a missed ticket. Ok the user didn’t receive a confirmation email, but this can be disabled in certain environments.
I haven’t found an open issue for this, shall I open one? Thanks
---
### Author:  [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [November 15, 2019, 6:23pm UTC](https://community.zammad.org/t/single-mail-not-being-fetched/3382/4 "2019-11-15T18:23:04Z")
> [@maxxer](#):
>
> This can be problematic… Isn’t it better to trigger a notification for such errors? I mean, this is a missed ticket. Ok the user didn’t receive a confirmation email, but this can be disabled in certain environments.
>
> I haven’t found an open issue for this, shall I open one? Thanks
This isn’t an open issue, as this has been adressed already (internally) and will be coming with Zammad 3.2. This is the issue you’re looking for:
>
>
> \### Infos:
>
> \* Used Zammad version: 2.5
> \* Installation method (source, package…, ..): any
> \* Operating system: any
> \* Database + version: any
> \* Elasticsearch version: any
> \* Browser + version: any
> \* Ticket-ID: #1031354, #1025102, #1021533, #1029932, #1049679
>
>
> \### Expected behavior:
>
> \* If an email is too big for Zammad (at least for Zammad max email size setting), send an bounce email (like an postmaster email) to the sender.
>
>
> \### Actual behavior:
>
> \* Zammad is just skipping too big emails. The emails will stay in the mailbox as untouched.
Upgraded instances will stick to not send any mail, but will put up a information within the monitoring. You can, at any point, change this to a postmaster notification that informs the user about the issue. Again, soonish available with Zammad 3.2
---
### Author:  [@system](https://community.zammad.org/u/system)
#### Post date: [March 14, 2020, 6:23pm UTC](https://community.zammad.org/t/single-mail-not-being-fetched/3382/5 "2020-03-14T18:23:07Z")
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.