• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. H

    Issue Reason: 2022-11-27 02:16:33 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']

    All solution proposaIs I could find didn't help. 2022-11-27 02:16:36 ERROR: E:The repository 'http://security.debian.org/debian-security bullseye/updates Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default...
  2. H

    Issue pum is called with arguments

    Don't know wether this relates to anything already discussed under "pum is called with arguments ..." here in the forum, but Here is what I get Reason: 2022-03-30 02:16:56 INFO: pum is called with arguments: ['--update', '--json'] 2022-03-30 02:17:05 INFO: no packages to update 2022-03-30...
  3. H

    Resolved Problens with SSL/TLS certificate in client mail

    Corrected master.cf (myhostname) and the mistake in the "full-chain.pem". Works now. Thanks a lot again for the effort
  4. H

    Resolved Problens with SSL/TLS certificate in client mail

    Many thanks and I'm getting closer commented out the thing you suggested. Results tried openssl s_client -CApath /etc/postfix/keys -starttls smtp -crlf -connect ... // on port 25/465/587 with different results port 25 CONNECTED(00000003) // with loads of information port 465 CONNECTED(00000003)...
  5. H

    Resolved Problens with SSL/TLS certificate in client mail

    got fatal: bind 127.0.0.1 port 25: Address already in use with the configuration above. if I out-comment all localhost settings and try it again I get the same error message for one the IP Adresses.
  6. H

    Resolved Problens with SSL/TLS certificate in client mail

    Okay. IMAP/POP3 are up and running. Trying to connect to domain1.de with openssl s_client -CApath /etc/postfix/keys -starttls smtp -crlf -connect domain1.de:25 connects but shows the certificate for domain2.de report and master.cf follows ------------------ report ---------------------...
  7. H

    Resolved Problens with SSL/TLS certificate in client mail

    Mmh. A bit lost. At the moment I have in /etc/dovecot/private a - dovecot.pem (private key, cert, CA cert) and - ssl-cert-and-key.pem (seems to be some default plesk one) Q: Shall I put my config in /etc/dovecot/conf.d? I didn't get the point with the number in #26 For every domain (in my case...
  8. H

    Resolved Problens with SSL/TLS certificate in client mail

    for "openssl s_client -CApath /etc/postfix/keys -connect mail.YOUR-DOMAIN.COM:smtps" getservbyname failure for smtps for the command openssl s_client -CApath /etc/postfix/keys -starttls pop3 -crlf -connect mail.domain1.de:110 openssl s_client -CApath /etc/postfix/keys -starttls smtp -crlf...
  9. H

    Resolved Problens with SSL/TLS certificate in client mail

    Thanks. Here is what is now in my master.cf file (the bold lines the ones I've added). For better reading I'v put every option on a separate line. Before it was one line. plesk-domain1.de-xx.xxx.xxx.xxx- unix - n n - - smtp -o smtpd_tls_key_file=/etc/postfix/keys/domain1t.de.key -o...
  10. H

    Resolved Problens with SSL/TLS certificate in client mail

    I still struggle to get it working for 2 domains too. Thought there would be more support in plesk for this kind of operation but .. Anyway. I found that the default is now dovecot for IMAP/POP3. @UFHH01 are the links you mentioned #2/#11 are still valid or is there anything one should...
  11. H

    Problem to have postfix/courier work with two domains (separate ip addresses)

    I'm running Debian 7.5 (wheezy) and have 2 domains connected. I managed to get postfix/courier to work with dedicated ssl certificate for one domain but not for both. What I did as far as Courier is concerned Replace the pop3d.pem/imapd.pem (both having the private key/certificate/ca...
Back
Top