K
kiwi88

  • Mar 15, 2021
  • Joined Jul 7, 2020
  • 7 discussions
  • 13 posts
  • 1 best answer
  • Post posted... wait what?
  • Hi there,

    I was just wondering why I am getting this error “This certificate has expired or is not yet valid” in Outlook and Thunderbird.
    My mailcow runs smoothly and I am using a reverse proxy nginx. I use a certificate from letsencrypt.

    Why am I getting this error every time I am receiving or sending email in outlook or thunderbird?

    I would really appreciate your help.

    THX

    Kiwi88

  • Hi there,

    I would like to logon to mailcow with my own webui. So I am sending off a post request with my credentials and can logon only, if I disable web security on chrome. If I try to logon without disabling web security, I am not geeting in and it seems that a cookie was blocked! I am using an nginx reverse proxy and tried several settings like proxy_cookie_path ~^/(.+)$ ‘/$1; SameSite=None;Secure’; , but nothing works! can someone please help?

    Cheers

    Kiwi

  • Hi Pkernstock,

    Thx for your reply. Do you know where I can find a proper API docu about sogo? I already found this “ Developer’s Guide

    ”, but it doesn’t help a lot! I would like to login from my own GUI via a post request. It’ll be nice if you could give me a hint :-).

    Cheers

    Kiwi

  • Hi there,

    I was just wondering how to logon with the username only, instead of user@myemail.com. Does anyone have a clue?

    Cheers

    Kiwi

  • Hi there,

    I am using mailcow with a regular domain www.myserver.com an a nginx reverse proxy. I was gonna use mail.myserver.com as well and notized, no matter which prefix I use “cowmail.myserver.com” etc, everything is working. So I can access my webui with any prefix!!! How can I change this? Furthermore, how can I get a valid ssl certificate for mail.myserver.com and myserver.com? It would be great if someone can help :-)

    Cheers

    kiwi

  • Hi Magic,

    thx for your reply. I read the articel in the link, but still I am not sure where to set mx up? Which file do I have to modify?

    Cheers

    Kiwi

  • Hi there, yesterday I wanted to register at a service with my mailcow email adress and got the response, that my email doesn’t have a mx record??? How and where can I set this up on mailcow?

    Cheers

    Kiwi

  • Hi Magic,

    I made it work by changing the themes.js in /var/lib/docker/volumes/mailcowdockerized_sogo-web-vol-1/_data/WebServerResources/js. But if you restart sogo, it overwrites my custom settings again with the default ones.
    Cheers

    Kiwi

  • Hi Magic,

    thx, it worked :-). Do you also know, how to change the color of the logon screen on the right side?

  • Hi there, I would like to change the sogo logo. I tried to change the sogo-logo.png in /var/lib/docker/volumes/mailcowdockerized_sogo-web-vol-1/_data/WebServerResources/img, but nothing happened after a restarting with “docker-compose restart memcached-mailcow sogo-mailcow”. Can someone please help?
    Cheers Kiwi

      • Best Answerset by MAGIC

      Hello,

      You need to put your logo as .svg in /data/conf/sogo/ and name it sogo-full.svg as seen here

      Then a down + up should be enough

  • Hello diekuh,

    I guess you don’t know what I mean, so we aren’t on the same page. Anyway, I developed my own api, now I can access.
    THX

    Kiwi

  • Hi,

    thx for the reply. The API call only works, as long as I am using the “Allow CORS: Access-Control-Allow-Origin” plugin in my Chrome browser. As soon as I deactivate it, I am getting this: (Reason: CORS header “Access-Control-Allow-Origin” missing).

    You have to set this either in nginx, or directly in the programming code! Where can I set this? For instance in nodejs I would handle it like this:
    var cors = require(‘cors’)
    app.use(cors())

    Sending an ajax request from one domain to another without setting Access-Control-Allow-Origin, would be a security issue. Therefore it’s blocked. So does anyone know how to allow this in mailcow???

    Regards

    Kiwi

  • Hi there,

    I would like to use the API in mailcow to create a mailbox. If I send off a request I am keep getting the following error:

    “Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.”

    I know this is a cross domain issue, therefor I have adapted the settings in

    /opt/mailcow-dockerized/data/conf/nginx/site.conf

    server {
    root /web;
    listen 80 default_server;
    listen [::]:80 default_server;
    include /etc/nginx/conf.d/server_name.active;
    if ( $request_uri ~* “%0A|%0D” ) { return 403; }
    location ^~ /.well-known/acme-challenge/ {
    allow all;
    default_type “text/plain”;
    }

    location /.well-known/host-meta {
    default_type ‘application/json’;
    add_header Access-Control-Allow-Origin ‘*’ always;
    }

    location / {
    return 301 https://$host$uri$is_args$args;
    }
    }

    server_tokens off;
    proxy_cache_path /tmp levels=1:2 keys_zone=sogo:10m inactive=24h max_size=1g;

    // file end

    Anyway it doesn’t work!!! Can someone please tell me, how to allow posts from another server?

    Regards

    Kiwi

    • Hello diekuh,

      I guess you don’t know what I mean, so we aren’t on the same page. Anyway, I developed my own api, now I can access.
      THX

      Kiwi