# Trouble successfully configuring an inbound email account

**URL:** https://community.zammad.org/t/trouble-successfully-configuring-an-inbound-email-account/915
**Category:** Technical assistance
**Created:** [July 1, 2018, 10:01pm UTC](https://community.zammad.org/t/trouble-successfully-configuring-an-inbound-email-account/915 "2018-07-01T22:01:53Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![FOGDrew](https://community.zammad.org/letter_avatar_proxy/v4/letter/f/5fc32e/32.png) [@FOGDrew](https://community.zammad.org/u/FOGDrew)
#### Post date: [July 1, 2018, 10:01pm UTC](https://community.zammad.org/t/trouble-successfully-configuring-an-inbound-email-account/915/1 "2018-07-01T22:01:53Z")

</div>

### Infos:

I am having trouble successfully configuring an inbound email account. This is a completely fresh installation of Ubuntu 16.04.4 and Zammad 2.5.x from the official repository.

- Used Zammad version: 2.5.x
- Used Zammad installation source: DEB
- Operating system: 16.0.4.4
- Browser + version: Chrome 67.0.3396.99 and Firefox 60.0.2

### Expected behavior:

Enter the settings after clicking on “New” under the Email Accounts under Channels, and then have zammad query the email server.

### Actual behavior:

After entering the correct server settings I receive the error “incompatible encoding regexp match (ASCII-8BIT regexp with UTF-8 string)”

If I try to submit multiple times I will occasionally see an additional error of “closed stream”

### Steps to reproduce the behavior:

Add a new email account of type IMAP using either SSL/STARTTLS or none with port 143 or 993.

I am using Dovecot as my IMAP server and have 100s of clients using these settings without incident.

---

<div class="post-metadata">

### Author: ![tlook](https://community.zammad.org/letter_avatar_proxy/v4/letter/t/ecd19e/32.png) [@tlook](https://community.zammad.org/u/tlook)
#### Post date: [July 12, 2018, 1:09pm UTC](https://community.zammad.org/t/trouble-successfully-configuring-an-inbound-email-account/915/2 "2018-07-12T13:09:22Z")

</div>

Just to confirm I am experiencing this issue as well. Running Debian 9, fresh install based on the Zammad docs.

> timothy@debian:~$ locale  
> LANG=en\_US.UTF-8  
> LANGUAGE=en\_US:en  
> LC\_CTYPE=“en\_US.UTF-8”  
> LC\_NUMERIC=“en\_US.UTF-8”  
> LC\_TIME=“en\_US.UTF-8”  
> LC\_COLLATE=“en\_US.UTF-8”  
> LC\_MONETARY=“en\_US.UTF-8”  
> LC\_MESSAGES=“en\_US.UTF-8”  
> LC\_PAPER=“en\_US.UTF-8”  
> LC\_NAME=“en\_US.UTF-8”  
> LC\_ADDRESS=“en\_US.UTF-8”  
> LC\_TELEPHONE=“en\_US.UTF-8”  
> LC\_MEASUREMENT=“en\_US.UTF-8”  
> LC\_IDENTIFICATION=“en\_US.UTF-8”  
> LC\_ALL=en\_US.UTF-8

---

<div class="post-metadata">

### Author: ![FOGDrew](https://community.zammad.org/letter_avatar_proxy/v4/letter/f/5fc32e/32.png) [@FOGDrew](https://community.zammad.org/u/FOGDrew)
#### Post date: [September 9, 2018, 4:34pm UTC](https://community.zammad.org/t/trouble-successfully-configuring-an-inbound-email-account/915/3 "2018-09-09T16:34:41Z")

</div>

I have just upgraded the previous version to 2.6.x and this problem still persists. Any idea of what to try?

---

<div class="post-metadata">

### Author: ![FOGDrew](https://community.zammad.org/letter_avatar_proxy/v4/letter/f/5fc32e/32.png) [@FOGDrew](https://community.zammad.org/u/FOGDrew)
#### Post date: [September 9, 2018, 5:17pm UTC](https://community.zammad.org/t/trouble-successfully-configuring-an-inbound-email-account/915/4 "2018-09-09T17:17:25Z")

</div>

Well after further troubleshooting… PLAIN authentication must be enabled on the server. A worthwhile note for anyone else experiencing this issue.

---

<div class="post-metadata">

### Author: ![system](https://community.zammad.org/uploads/default/original/1X/5c5afaea2d23f811dbec33cd4edb02fa29d3262f.png) [@system](https://community.zammad.org/u/system)
#### Post date: [January 7, 2019, 5:17pm UTC](https://community.zammad.org/t/trouble-successfully-configuring-an-inbound-email-account/915/5 "2019-01-07T17:17:26Z")

</div>

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