"FETCH failed: Storage corrupted" while trying to add Email channel

Info

  • Used Zammad version: 3.3.0-19
  • Used Zammad installation docker
  • Operating system: CentOS

Expected behavior:

  • Add a new channel

Actual behavior:

Details

I had a channel previously, but because of the email server issue we delete it from Zammad and now we are trying to add it back.
We have 5 other channels and everything is working Ok except that while I’m trying to add the new channel with the same email address that was used before I’ve got the error “FETCH failed: Storage corrupted”.
Added any other email is working.

Logs from rails-server when I’m clicking “Continue”

I, [2020-09-01T12:12:59.330469 #124-47447327215740]  INFO -- : Started POST "/api/v1/channels_email_inbound" for 192.168.1.19 at 2020-09-01 12:12:59 +0000
I, [2020-09-01T12:12:59.336641 #124-47447327215740]  INFO -- : Processing by ChannelsEmailController#inbound as JSON
I, [2020-09-01T12:12:59.336718 #124-47447327215740]  INFO -- :   Parameters: {"adapter"=>"imap", "options"=>{"host"=>"mail.kkts.com.au", "user"=>"quotes@kkts.com.au", "password"=>"[FILTERED]", "ssl"=>true, "port"=>"993", "folder"=>"", "keep_on_server"=>true}}
I, [2020-09-01T12:12:59.344808 #124-47447327215740]  INFO -- : fetching imap (mail.kkts.com.au/quotes@kkts.com.au port=993,ssl=true,starttls=false,folder=INBOX,keep_on_server=true)
I, [2020-09-01T12:12:59.566306 #124-47447327215740]  INFO -- : check only mode, fetch no emails
I, [2020-09-01T12:12:59.613496 #124-47447327215740]  INFO -- : Completed 200 OK in 277ms (Views: 0.3ms | ActiveRecord: 3.4ms)
I, [2020-09-01T12:13:01.965600 #22-47447327245980]  INFO -- : Started GET "/api/v1/channels_email?_=1598960280672" for 192.168.1.19 at 2020-09-01 12:13:01 +0000
I, [2020-09-01T12:13:01.974172 #22-47447327245980]  INFO -- : Processing by ChannelsEmailController#index as JSON
I, [2020-09-01T12:13:01.974230 #22-47447327245980]  INFO -- :   Parameters: {"_"=>"1598960280672"}
I, [2020-09-01T12:13:02.147876 #22-47447327245980]  INFO -- : Completed 200 OK in 174ms (Views: 54.1ms | ActiveRecord: 5.5ms)

These error messages usually come from your mail server.
Did you try to login to the affected account with e.g. a Thunderbird? If so, does it work?

If this is a selfhosted mail server, checking it’s logfiles for the word corrupted may help.
For me personally I’ve never seen such an error message, but well, you always learn new stuff. :wink:

For me personally I’ve never seen such an error message, but well, you always learn new stuff. :wink:

Yes, me too.

Mailbox is working. We use it from a web interface every day. I checked the mail server (we use Axigen) logs and didn’t find any errors. Restarted everything just in case and nothing…
So I made a workaround. Created a new email box and set up a forward rule from the original box to the new one. Then added the new one to the Zammad.

Really odd.
Glad you could somehow solve it.