ProtonMail -> Can't use Channel::Driver::Imap: #<Net::IMAP::NoResponseError: unsupported search query>

Info:

  • Used Zammad version: 3.5.0 + Elasticsearch
  • Used Zammad installation source: (source, package, ā€¦) RPM + also try on https://zammad.com
  • Operating system: CentOS 7
  • Browser + version: Firefox 80.0.1
  • ProtonMail Bridge 1.3.3

Expected behavior:

  • Email integration to work wormal as expected

Actual behavior:

  • After successfully add Email Accounts i get this error Can't use Channel::Driver::Imap: #<Net::IMAP::NoResponseError: unsupported search query>

Steps to reproduce the behavior:

  • On Premise or using https://zammad.com result is the same
  • Just follow UI steps for adding Email Accounts
  • Use ProtonMail email with setup ProtonMail bridge server

Others

  • As before i can provide credential for a test server with ProtonMail Bridge to Zammad team for test and debug purposes
1 Like

Hi everyone,

I got the same error. Zammad succesfully connects to protonmail-bridge, then throws the error after ~20sec

Info:

  • Used Zammad helm chart for kubernetes version: 2.6.1 (with zammad 3.5.0)
  • ProtonMail Bridge 1.3.3 (also on kubernetes)
  • Browser + version: Firefox 81.0
1 Like

Here is a more detailled output of the command rails r 'p Channel.fetch'

I, [2020-10-02T08:18:21.154654 #45-47250971769180]  INFO -- : Setting.set('models_searchable', ["Chat::Session", "KnowledgeBase::Answer::Translation", "Ticket", "User", "Organization"])
I, [2020-10-02T08:18:22.068032 #45-47250971769180]  INFO -- : fetching imap (10.3.151.4/**** port=143,ssl=false,starttls=false,folder=INBOX,keep_on_server=true,auth_type=LOGIN)
E, [2020-10-02T08:18:22.219760 #45-47250971769180] ERROR -- : Can't use Channel::Driver::Imap: #<Net::IMAP::NoResponseError: unsupported search query>
E, [2020-10-02T08:18:22.220014 #45-47250971769180] ERROR -- : unsupported search query (Net::IMAP::NoResponseError)
/usr/local/lib/ruby/2.6.0/net/imap.rb:1219:in `get_tagged_response'
/usr/local/lib/ruby/2.6.0/net/imap.rb:1273:in `block in send_command'
/usr/local/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
/usr/local/lib/ruby/2.6.0/net/imap.rb:1255:in `send_command'
/usr/local/lib/ruby/2.6.0/net/imap.rb:1420:in `block in search_internal'
/usr/local/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
/usr/local/lib/ruby/2.6.0/net/imap.rb:1416:in `search_internal'
/usr/local/lib/ruby/2.6.0/net/imap.rb:774:in `search'
/opt/zammad/app/models/channel/driver/imap.rb:148:in `rescue in block in fetch'
/opt/zammad/app/models/channel/driver/imap.rb:146:in `block in fetch'
/opt/zammad/app/models/channel/driver/imap.rb:544:in `block in timeout'
/usr/local/lib/ruby/2.6.0/timeout.rb:93:in `block in timeout'
/usr/local/lib/ruby/2.6.0/timeout.rb:33:in `block in catch'
/usr/local/lib/ruby/2.6.0/timeout.rb:33:in `catch'
/usr/local/lib/ruby/2.6.0/timeout.rb:33:in `catch'
/usr/local/lib/ruby/2.6.0/timeout.rb:108:in `timeout'
/opt/zammad/app/models/channel/driver/imap.rb:543:in `timeout'
/opt/zammad/app/models/channel/driver/imap.rb:144:in `fetch'
/opt/zammad/app/models/channel.rb:57:in `fetch'
/usr/local/bundle/gems/activerecord-5.2.4.4/lib/active_record/relation/delegation.rb:71:in `each'
/usr/local/bundle/gems/activerecord-5.2.4.4/lib/active_record/relation/delegation.rb:71:in `each'
/opt/zammad/app/models/channel.rb:32:in `fetch'
/usr/local/bundle/gems/railties-5.2.4.4/lib/rails/commands/runner/runner_command.rb:41:in `<main>'
/usr/local/bundle/gems/railties-5.2.4.4/lib/rails/commands/runner/runner_command.rb:41:in `eval'
/usr/local/bundle/gems/railties-5.2.4.4/lib/rails/commands/runner/runner_command.rb:41:in `perform'
/usr/local/bundle/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
/usr/local/bundle/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
/usr/local/bundle/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
/usr/local/bundle/gems/railties-5.2.4.4/lib/rails/command/base.rb:69:in `perform'
/usr/local/bundle/gems/railties-5.2.4.4/lib/rails/command.rb:46:in `invoke'
/usr/local/bundle/gems/railties-5.2.4.4/lib/rails/commands.rb:18:in `<main>'
/usr/local/bundle/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `require'
/usr/local/bundle/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `block in require_with_bootsnap_lfi'
/usr/local/bundle/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/loaded_features_index.rb:65:in `register'
/usr/local/bundle/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:20:in `require_with_bootsnap_lfi'
/usr/local/bundle/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in `require'
/usr/local/bundle/gems/activesupport-5.2.4.4/lib/active_support/dependencies.rb:291:in `block in require'
/usr/local/bundle/gems/activesupport-5.2.4.4/lib/active_support/dependencies.rb:257:in `load_dependency'
/usr/local/bundle/gems/activesupport-5.2.4.4/lib/active_support/dependencies.rb:291:in `require'
bin/rails:9:in `<main>'
[#<Channel id: 7, group_id: 3, area: "Email::Account", options: {"inbound"=>{"adapter"=>"imap", "options"=>{"host"=>"10.3.151.4", "user"=>"****", "password"=>"******", "ssl"=>false, "port"=>"143", "folder"=>"", "keep_on_server"=>true}, "channel_id"=>7}, "outbound"=>{"adapter"=>"smtp", "options"=>{"host"=>"10.3.4.12", "user"=>"*****", "password"=>"*****", "port"=>"587"}, "email"=>"*****", "channel_id"=>7}}, active: true, preferences: {"last_fetch"=>Fri, 02 Oct 2020 08:18:22 UTC +00:00}, last_log_in: "Can't use Channel::Driver::Imap: #<Net::IMAP::NoRe...", last_log_out: nil, status_in: "error", status_out: "ok", updated_by_id: 98, created_by_id: 6, created_at: "2020-07-09 14:12:52", updated_at: "2020-10-02 08:18:22">]
1 Like

Hi.
Here is opened issue at GitHub: https://github.com/zammad/zammad/issues/3233

1 Like

Would someone mind to provide a bridge with test credentials for us again?

Edit (If so, Iā€™d be gratefull for a PM so that your credentials are not public)

1 Like

I sent you needed credentials.
Best regards!

2 Likes

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.