Selva
Run it on a hypervisor which offers high availability. Currently there is no way of clustering it in a supported configuration.

    11 days later

    Hi,

    I installed and setup the Mailcow mail server. I also set up split delivery for my email server.
    However, when I send an email from Mailcow, it ends up in the spam folder in the recipient’s mailbox.
    How to resolve it?

    2 months later

    Hi I have installed mailcow mail server in my own server, And I have configured the split delivery with outlook. All is working fine,

    But now I am facing issue, that is If I send the mail to my outlook domain, my message goes in spam folder.

    Another issue is If I send the mail to my personal mail like gmail.com, it is not send the mail to my mail account. It shows the following error.

    The IP you’re using to send mail is not
    authorized 550-5.7.1 to send email directly to our servers. Please use the
    SMTP relay at 550-5.7.1 your service provider instead. For more
    information, go to 550 5.7.1
    'The IP you're using to send email is not authorized...' - Gmail Help

    support.google.com
    'The IP you're using to send email is not authorized...' - Gmail Help
    Troubleshoot delivery issues with Postmaster Tools Gmail Postmaster Tools provides senders with metrics on parameters such as reputation, spam rate, feedback loop, etc. It can help you prevent your em

    l11-20020a17090ac58b00b002a2e545eac4si9940168pjt.87 - gsmtp (in reply to
    end of DATA command)

    Kindly help us to resolve the issue.

    Spam categorization happens at the “local” level, you need to check why that happens on your Outlook server.
    For the 5.7.1 is impossible to tell, but I’d guess you don’t have proper SPF/DKIM/DMARC configuration in place.
    Make sure you followed all of the configuration steps, Google has a pretty strict policy on blocking incoming messages

    Hi @maddler,

    Thanks for the update. Can you give a example of which records we have to add in our mail server. Kindly share the details.

    Because it will very helpful for us. Thanks.

    That’s all in the Mailcow installation docs (which is in fairness among the best ones I’ve ever seen in ages), and/or a quick Google search will give the answer for just anything else. That’s all pretty much standard configuration you’re looking at.

    22 days later

    Hi,

    I have installed mailcow mail server and also configure the split delivery with outlook.

    Everything is fine, But the issue I am not able to send the mail to gmail. I have checked all the records everything is goood,

    Kindly help us.

      Selva I have checked all the records everything is goood,

      Just checking the records is not enough.
      Have you checked the postfix logs, when sending a mail?

        Selva But the issue I am not able to send the mail to gmail.

        Is it still this error?

        The IP you’re using to send mail is not
        authorized 550-5.7.1 to send email directly to our servers. Please use the
        SMTP relay at 550-5.7.1 your service provider instead. For more
        information, go to 550 5.7.1

        If you are sending the mails from your private ISP IP address then you won’t be able to fix it, ISP pools are used by SPAMmers and therefore blocked by almost all mailservers. You have to use a relay service as the Google message indicated

          How to configure the smtp relay service in mailcow.

          Because I have already enabled the smtp relay service in mailcow configuration.

            I have looked the document, But I have one doubt, as above the document they given a mailgun example,

            I dont have any idea of that my question is I have installed mailcow in docker using mailcow document So what I have to give the transport address instead of mailgun and what will I give the username and password?

            Selva I have already enabled the smtp relay service

            Well, which relay service are you using? They provide you with username/password and the transport address

              No one is typing