• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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.

Resolved Mails cannot be sent

Thera

Regular Pleskian
Server operating system version
Debian 11.6
Plesk version and microupdate number
18.0.52
Hi,

if i try to sent a mail to my new server (dienetzcloud.de). Neither sender Mail Domain or other domains listed on spamhaus (31.25.152.138, 178.20.100.105). if i try to sent a mail from mailserver dienetzcloud.de nothing happens, not error, no mail on reciepient. in plesk holding pattern also nothing.

dienetzcloud.de hat diesen Fehler ausgegeben:
Decision Engine classified the mail item was rejected because of IP Block (from outbound normal IP pools) -> 554 5.7.1 Service unavailable; Client host [40.107.20.109] blocked using sbl.spamhaus.org; Error: open resolver; DNSBL Error Code - Open/public resolver - The Spamhaus Project

has anybody got n idea?
Thank you so much
 
The open resolver issue occurs for some resolvers such as 1.1.1.1 (Cloudflare) when these are used as resolvers in /etc/resolv.conf. Could you check what is used there and maybe change it to 8.8.8.8 and 8.8.4.4 (Google).
 
Have you checked the /var/log/maillog for further information what is happening when you send mail to the server or when you send mail from that server?
 
Apr 13 10:11:40 dienetzcloud postfix/smtp[109766]: 4185727822A3: to=<[email protected]>, relay=none, delay=8844, delays=8844/0.02/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Apr 13 10:12:25 dienetzcloud dovecot: imap-login: Login: user=<[email protected]>, method=PLAIN, rip=::1, lip=::1, mpid=109778, TLS, session=<paLkSDP5cJkAAAAAAAAAAAAAAAAAAAAB>
Apr 13 10:12:25 dienetzcloud dovecot: service=imap, user=[email protected], ip=[::1]. Disconnected: Logged out rcvd=50, sent=581
Apr 13 10:12:49 dienetzcloud postfix/smtpd[109531]: warning: hostname dtarax-brsi.oinkhow.net does not resolve to address 141.98.10.48
Apr 13 10:12:49 dienetzcloud postfix/smtpd[109531]: connect from unknown[141.98.10.48]
Apr 13 10:12:51 dienetzcloud plesk_saslauthd[109779]: listen=6, status=5, dbpath='/plesk/passwd.db', keypath='/plesk/passwd_db_key', chroot=1, unprivileged=1
Apr 13 10:12:51 dienetzcloud plesk_saslauthd[109779]: privileges set to (118:126) (effective 118:126)
Apr 13 10:12:51 dienetzcloud plesk_saslauthd[109779]: failed mail authentication attempt for user 'xx' (password len=xx)
Apr 13 10:12:51 dienetzcloud postfix/smtpd[109531]: warning: unknown[141.98.10.48]: SASL LOGIN authentication failed: authentication failure
Apr 13 10:12:51 dienetzcloud postfix/smtpd[109531]: disconnect from unknown[141.98.10.48] ehlo=1 auth=0/1 quit=1 commands=2/3
Apr 13 10:13:16 dienetzcloud postfix/smtpd[109531]: connect from mail-am6eur05on2121.outbound.protection.outlook.com[40.107.22.121]
Apr 13 10:13:16 dienetzcloud postfix/smtpd[109531]: 659132780596: client=mail-am6eur05on2121.outbound.protection.outlook.com[40.107.22.121]
Apr 13 10:13:16 dienetzcloud psa-pc-remote[612]: 659132780596: from=<[email protected]> to=<[email protected]>
Apr 13 10:13:16 dienetzcloud postfix/cleanup[109783]: 659132780596: message-id=<AM9PR01MB83478511E1C6B6767D36B7ADD3989@AM9PR01MB8347.eurprd01.prod.exchangelabs.com>
Apr 13 10:13:16 dienetzcloud psa-pc-remote[612]: 659132780596: py-limit-out: stderr: INFO:__main__:No SMTP AUTH and not running in sendmail context (incoming or unrestricted outgoing mail). SKIP message.
Apr 13 10:13:16 dienetzcloud psa-pc-remote[612]: 659132780596: py-limit-out: stderr: SKIP
Apr 13 10:13:16 dienetzcloud psa-pc-remote[612]: 659132780596: spf: stderr: PASS
Apr 13 10:13:16 dienetzcloud psa-pc-remote[612]: 659132780596: check-quota: stderr: SKIP
Apr 13 10:13:16 dienetzcloud postfix/qmgr[2602]: 659132780596: from=<[email protected]>, size=40255, nrcpt=1 (queue active)
Apr 13 10:13:16 dienetzcloud postfix/error[109789]: 659132780596: to=<[email protected]>, relay=none, delay=0.59, delays=0.59/0.01/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Apr 13 10:13:17 dienetzcloud postfix/smtpd[109531]: disconnect from mail-am6eur05on2121.outbound.protection.outlook.com[40.107.22.121] ehlo=2 starttls=1 mail=1 rcpt=1 bdat=1 quit=1 commands=7
 
The relevant part is
"(connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)"
It tells that for a yet unknown reason the local mail server cannot be used. Can you test whether you can send mails from one domain on your server to another domain also hosted on the server (and with correct MX record pointing to that same server)?
 
Back
Top