SuiteCRM 8.10.1 IMAP config problem - Port number inserts a comma - Locale settings to blame?

I can’t configure my inbound email in SuiteCRM 8.10.1. (running in Docker on MacOs 15.7.7.

The port for my email needs to be 1143, but it always adds a comma (1,143) when I save.

I changed my Locale settings to remove the comma, Quick Repair and Rebuild, changed the IMAP settings, but the comma always returns.

I had this problem with SuiteCRM 7, but removing the comma in Locale setting worked. Mot this time.

Does anyone have any suggestions, please?

Thanks in advance.

Did you check Admin -> Locale or the config.php file?

Maybe related: Php imap module no longer available in php8.4 - #2 by rsp

Thanks for your response.

I tried Admin → Locale and deleted the comma from the 1000s separator box, leaving it empty.

I’m a novice, so forgive the question, are you suggesting that I try the CLI commands in your link copied below? I will need time to adapt them since my instance of SuiteCRM is in a Docker environment:

For Ubuntu/Debian

sudo apt update

sudo apt install -y \
    libc-client-dev \
    libkrb5-dev \
    php8.4-dev \
    php-pear \
    build-essential

sudo pecl install imap

Then enable it:

echo "extension=imap.so" | sudo tee /etc/php/8.4/mods-available/imap.ini

sudo phpenmod imap

Restart your web server and PHP!

What is your PHP version? You don’t need it unless it is PHP 8.4.

It’s PHP 8.3.31. Hope that helps?

Okay, also locale → comma separator is for currency value. It should not affect your port number.


Try this:

Locate and open config.php (and check config_override.php) using a text editor.

Find the $sugar_config['valid_imap_ports'] array.

$sugar_config['valid_imap_ports'] = array (
  0 => '143',
  1 => '993',
  2 => '995',
  3 => '1143', 
);

Save the file and clear your cache via Admin > Repair > Quick Repair and Rebuild.

:white_check_mark: Solution: Updating to 7.14.2 causes issues with any imap port longer than 3 digits - #5 by ezon


Because you are running Docker on MacOS, container network isolation may prevent SuiteCRM from routing directly to a service on your host or external network over port 1143.

Make sure your custom email container is actually exposing or forwarding 1143

Thank you, I tried this and it didn’t work. I have SMTP working and may just have to give up on IMAP.

I think my problem is that I am using Proton Mail Bridge in Docker. The logs say that it’s working and connected, but nothing appears in the CRM. Obviously something is wrong there. It works with another CRM I use, but I want to use SuiteCRM for myself and two clients I have in my contract work.

I’ll give up for myself now. For my clients it should be straightforward as they use Gmail and Outlook business email accounts.

Hey @rcword! Thank you for getting in touch with this!

(and thank you @rsp for looking into this)

I’ve given this some testing locally myself and I believe this is a valid bug.

It appears as though this field, (on Inbound Email Accounts), is currently being treated as a number/integer field, so values over 3 digits long will have a thousands separator added.

Whereas the equivalent field on Outbound Email Accounts is a varchar(5), so this is handled as entered and does not add the thousands separator.

(Which is why SMTP works with your port number, and IMAP does not)

I wanted to let you know I have raised it on the Suite7 Github Repo, as I can replicate this issue in 7.15.1: Inbound Email -> "Mail Server Port" uses Thousand Separators if value is more than 4 digits long · Issue #10848 · SuiteCRM/SuiteCRM · GitHub

So any fixes/updates on this issue can be tracked there.

Thank you again for identifying and raising this!

1 Like

Thank you, this is good to know. I’ll track up dates there.

I’ve recommended SuiteCRM to a client and they’ll start using it by next week.