Icewarp Mail Server Configuration

[Rode Strawther]

Throughconnection to standard e-mail servers . IceWarp Desktop Client will attempt to automatically retrieve the server settings (this works for the most frequently used email servers i.e. Gmail, Yahoo etc.)

AutoDiscover technology. If IceWarp Desktop Client is unsuccessful with the first attempt, it will try to use the so called autodiscover technology, which basically tries to identify the predefined credentials of email servers. This service is fully automatic and it can autonomously detect the settings if the correct email information is provided.

Predicting less usual email servers. In this case, IceWarp Desktop Client tries searching access to your account details on the Internet, it works on predicting how the address of your email provider is realized. (For example, this service will be utilized in the cases when a private company's email addresses will be prompted to set up).

If automatic setup fails you will be prompted to specify the settings manually. Click Other to set up other email account. Click Next to continue.

In this case, the setup be a little more complex, performed in six steps - you will be asked to fill in all the e-mail settings.

I'm trying to configure my Ice Warp mail server to work with our Google Cloud DNS. A lot of our emails are ending up in the spam folders after we send them I've configured google cloud with the required

Ran a test on Google Toolbox and received this outcome. Can anyone give me some info as to what needs to be setup on the server or in DNS to get it right? I don't want to guess at things...just want to get it right

The warning message that you are getting in the screenshot that you have sent is because you are allowing only a specific ip address in your spf record. It will basically allow the emails from that particular ip to come in. If you are using a google domain, then please follow 1 to setup spf records, otherwise please ignore that warning message. For setting up the DKIM and DMARC record, please follow 2.Please note that the article 2 has further sub links once you click on DKIM and DMARC. You can take the help of 3 to verify if your domain is properly setup to configure DKIM and DMARC records. This has to be done once you have completed the steps in article 2You can find information about managing records in Cloud DNS in article 3

To have properly working mail server you need to add A, MX, SPF, DKIM, and DMARC records to Cloud DNS for your domain (as it was suggested by @Ernesto U) and PTR record which maps the IP address to the name of your mail server (and resolved name of your mail server should maps to the same IP). Don't forget to setup DKIM in configuration of your mail server in addition to DNS record.

The integration is finished. LiveAgent ticketing system will now fetch all of your email communication from the IceWarp Mail Server. In the meantime, you can have a look at our Academy page or features page to discover more about help desks, customer support, and LiveAgent capabilities. LiveAgent Product Tour Live Agent02:25Live AgentMarch 10, 2021 ILooking for an effective way to streamline your customer support process and enhance the productivity of your team? Enhance your customer support by integrating with IceWarp Mail Server using LiveAgent's seamless integration. Try LiveAgent Schedule a Demo Frequently Asked QuestionsWhat is IceWarp Mail Server?IceWarp is a collaboration software and mail server. Aside from mail, the application provides document editing capabilities, calendar sharing, instant messaging, and collaboration features. In addition to its groupware capabilities, it offers spam protection modules as well as an antivirus protection module. Linux and Windows versions of the application are available.How can you use IceWarp Mail Server?Collaboration is made easy with IceWarp. Since it can handle any number of users, it is suitable for businesses of any size. All the members can collaborate, chat, or manage documents together. It can be used as a useful email solution for help desks. For enhanced customer support capabilities and toolset, it can also be integrated with LiveAgent help desk system.What are benefits of IceWarp Mail Server integration?The benefits are: email server with a custom domain, collaborative editing capabilities, shared calendar and documents, handles any number of users.How to integrate IceWarp Mail Server with LiveAgent?Go to LiveAgent and open Configuration > Email > Mail Accounts. Create a new email and select Other. Select IMAP/POP3, provide your details and click Save.How do I change my IceWarp password?In WebClient settings, go to Accounts (My details - Options). Click the Change password button. You will be asked to enter your old password once and then your new password twice (New Password, Confirm Password). Click on OK and you're finished. Back to Integrations Create account for FREE Related Articles MailEnableMailEnable is the most popular email server available for Microsoft Windows. It seamlessly integrates with Outlook and LiveAgent.

Click the "+ Add account" button to open the New Account window. The account wizard window will appear. Now simply enter your IceWarp email address and confirm. Automatic setup will then use the AutoDiscover feature to detect your server settings. Enter your password and click Continue.

I have also used Merak for about the same amount of time as you. Originally it was our only company mail server. We now use it as the gateway for filtering for our Exchange and it works pretty good for what I use it for.

Oh yes the SMTP service - Icewarp support says it is working just fine. I would agree except the sessions back up into the hundreds with the inbound and outboound message queues holding the email until I reboot the server. I just had one user report that an email she sent was received 36 times. Seems the senders outbox keeps trying to send the email even when a partial session is established. However, if you look at the SMTP logs everything looks normal.

Mystery solved! The issue was related to a server used for archiving email settings. This server was used for several years as a dedicated share for the mail server. After moving the archive to a local directory on the email server the problem abated.

Company Overview:

IceWarp,Inc. is one of the world's largest unified messaging, collaboration, mobility and security solutions. It originally focused on development of high powered Email server in 1999, which transformed over time into the full messaging solution by 2011. IceWarp's solutions meet the needs of businesses of all sizes -- from SMBs to enterprises. Customers include Cisco,Chipotle, Toyota, Burger King and Marriott.

Description:

IceWarp. Inc.'s messaging server is built for today's mobile workforce; delivering email, instant messaging, VoIP, text messaging, spam and virus protection, and a robust collaboration suite on a single platform. The IceWarp server scales as a business grows, resulting in lower total cost of ownership than its competitors. IceWarp's communications platform is trusted by the world's largest brands.

This all started last Sat when, out of the blue, Thunderbird (latest version) start complaining about invalid certs that had been working flawlessly. Had to tell Tbird to accept a security exception. IW could not update certs.

No webserver. IW kept telling me that port 80 had to available from outside. Finally killed MS Branch Cache that was hooked into 80. As it is only a mail server, I don't want any web/http running on it but now IW is telling me the LE needs a web service running.

Is there a succinct explanation of how to use DNS to validate but, more importantly, how will IW know to use DNS to validate. I understand that IW is using the ACME protocol - will it know to use DNS if it can't hit an http?

From your description, Icewarp is currently only presenting your domain certificate (leaf/end-entity) cert, not the intermediate certificate(s) that the certificate chain is made up of, so the cert fails in Thunderbird because it used to know about the old Let's Encrypt intermediate and doesn't know about the new one, so it expects to find it in your certificate chain instead: Note regarding transition to R3 intermediate with Firefox or Thunderbird

If the actual cert is renewing OK then the task is to find out how to get Icewarp to use the correct intermediate certificates, this can sometime be done on other servers by giving it a 'chain' file containing the intermediates and the root.

For ACME certs, http validation works by presenting a specific http response file to Let's Encrypt when they ask for it. If validation has stopped working then something has change in your configuration or the server simply needs a restart. A lot of windows ACME clients (such as the one I maintain: ) start a temporary http listener in port 80, so you don't have to have IIS running, or it can even sit in front of IIS and just answer the acme challenges. I don't know if Icewarp has that feature.

DNS validation (also called dns-01) involves automatically asking Let's Encrypt for a challenge, this then roughly means your system has to add/update the TXT record _acme-challenge.yourdomain.com with the value specified by Let's Encrypt. To do this can involve any number of DNS APIs and whether you will be able to use that feature depends on Icewarps acme support for DNS validation, and your DNS service.

3a8082e126