Profile Details

Toggle Sidebar
Recent updates
  • In GoogleDNS you should have a subdomain set as YYYYMM._domainkey and the TXT record should contain:

    Now you need to update your DNS records. Open the file '/etc/opendkim/keys/mydomain.com/YYYYMM.txt'. In your DNS records, create a new TXT record with a subdomain as the first field in the file which you can just copy. In this case it is “YYYYMM._domainkey”. For TXT Data copy and paste everything between the first and last set of quotes, excluding the first and last quotes and removing the middle quotes and whitespace between them.
    You also need to adjust YYYYMM to whatever you chose.

    If you dig command is not working then you've got something wrong. If, from other posts ages ago, you have tweaked your dnsmasq so iy does not local queries onto the internet? You may have added:To your dnsmasq configuration. If so, you will need an extra line:
    This will allow the domainkey lookup to go out to the internet.

    Do you have a funny DNS set up? If I google your error it refers to other DNS utilities running. W hat is the output to:

    BTW, can I say that your DKIM record is public knowledge to anyone receiving your e-mails so there is not too much point in munging it.

  • ClearOS (alonf with a lot of firewalls) is not brilliant at redirecting traffic from the LAN to its WAN interface and back in. Whatever is used as the DNS resolver on your LAN should resolve mail.mydomain.com to a LAN IP.

  • That all looks OK. SPF checks out and everything seems to be legitimate in the header so I can't see why it is being sent to spam unless other recipients have flagged this sort of mail as spam. You could try DKIM, but honestly, at the moment, I don't know. Also check Google's bulk senders guidelines.

  • I don't follow your mail routing for the moment. Can you tell me the route a main takes from your church to the internet? What domain do they use? Have you got hold of an email which has been nent to Junk? If so, can you post the header?

    Generally DKIM is not needed. I know I've done a how to for it, but given the opportunity, I would not read it. Instead I'd use SpamAssassin to do the DKIM. There are plenty of instructions on the internet and I hope to give it a go and write it up. It saves installing anything.

  • ProxyPass is a one-off payment.

    For IMAP for external access, you should just port forward at the gateway. Do not open the incoming port on the gateway. You can track the packets with tcpdump with something like:You can have multiple windows, one running on your WAN port one on your LAN port and one on your mail server. For internal access, in your DNS server, you need to set your mail server name to point to your mailserver LAN IP. E.g if you have you e-mail client configured to point to mail.mydomain.com, externally it should resolve to your WAN IP and internally you put it in your DNS server so it resolves to your mail server's LAN IP.

    I have little idea about Owncloud and may need the exact message. I am a Nextcloud user but is is on my gateway.

  • I've just tried going into mine and the webconfig screen is broken. Very odd.

    Anyway, you should not need to reset the password. Click on the documentation icon (the sloping book). If there is none, have a look at the Owncloud for Home documentation. The Business documentation is not so up to date. The admin password should be available with:

    I'll have to see if I can get mine working then ping the dev about the documentation. Historically, Nextcloud evolved from the OwnCloud app and the documentation may heve been overlooked.

  • Nick Howitt
    Nick Howitt's reply was accepted as an answer

    Re: Paid for install, won't install

    I think this stems from an irrecoverable error during the 7.7beta trial. You will have to do the simple fix yourself as the error broke yum. Please see this sticky.

  • Nick Howitt
    Nick Howitt's reply was accepted as an answer

    Re: Paid for install, won't install

    I think this stems from an irrecoverable error during the 7.7beta trial. You will have to do the simple fix yourself as the error broke yum. Please see this sticky.

  • Nick Howitt

    I think this stems from an irrecoverable error during the 7.7beta trial. You will have to do the simple fix yourself as the error broke yum. Please see this sticky.

  • I'm not so sure. In ClearOS the folder is created when the user is created. The solutions that Google came up with create the folder on first login.