• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Resolved bounced mails from third mailserver won't be delivered to sender

Sellighsphire

New Pleskian
Hello,

we tried to send an email from my_mailadress@domain.com to non_existant_mail_address@example.com. The mailserver at example.com rejected the mail and we see this information in our maillog.
But there is no message send to my_mailadress@domain.com and therefore we didn't know that this mailadress doesn't exist.
What should we change to get those messages?
We use postfix on Ubuntu 16.04.4 LTS‬ and Plesk Onyx Version 17.5.3 Update #71

Kind regards
Jens
 
Hello. I've been away for some days. See following log:

Apr 15 12:58:32 lvps83-169-22-195 postfix/smtpd[25031]: connect from ip5b43876b.dynamic.kabel-deutschland.de[91.67.135.107]
Apr 15 12:58:32 lvps83-169-22-195 postfix/smtpd[25031]: D2F16101214: client=ip5b43876b.dynamic.kabel-deutschland.de[91.67.135.107], sasl_method=LOGIN, sasl_username=versand@xxxxxxxxxxxx.de
Apr 15 12:58:32 lvps83-169-22-195 greylisting filter[25143]: Starting greylisting filter...
Apr 15 12:58:32 lvps83-169-22-195 /usr/lib/plesk-9.0/psa-pc-remote[389]: _mh_fork(): unrecognized status code '5'
Apr 15 12:58:32 lvps83-169-22-195 /usr/lib/plesk-9.0/psa-pc-remote[389]: Error during 'grey' handler
Apr 15 12:58:32 lvps83-169-22-195 postfix/cleanup[23194]: D2F16101214: message-id=<807c9f92f4234d828760aee731dd955d@exchange.xxxxxxxxxxxx.local>
Apr 15 12:58:32 lvps83-169-22-195 check-quota[25144]: Starting the check-quota filter...
Apr 15 12:58:32 lvps83-169-22-195 /usr/lib/plesk-9.0/psa-pc-remote[389]: handlers_stderr: SKIP
Apr 15 12:58:32 lvps83-169-22-195 /usr/lib/plesk-9.0/psa-pc-remote[389]: SKIP during call 'check-quota' handler
Apr 15 12:58:32 lvps83-169-22-195 postfix/qmgr[23822]: D2F16101214: from=<local_mailadress@xxxxxxxxxxxx.de>, size=13553, nrcpt=1 (queue active)
Apr 15 12:58:33 lvps83-169-22-195 postfix/smtpd[25031]: disconnect from ip5b43876b.dynamic.kabel-deutschland.de[91.67.135.107] ehlo=2 starttls=1 auth=1 mail=1 rcpt=1 data=1 quit=1 commands=8
Apr 15 12:58:33 lvps83-169-22-195 postfix/smtp[25039]: D2F16101214: to=<invalid_remote_mailadress@yyyyyyyyyyyy.com>, relay=mx0.yyyyyyyyyyyy.com[80.237.138.5]:25, delay=0.23, delays=0.11/0/0.1/0.02, dsn=5.0.0, status=bounced (host mx0.yyyyyyyyyyyy.com[80.237.138.5] said: 550 Address invalid (ID:550:1:1 (mi027.mc1.hosteurope.de)) (in reply to RCPT TO command))
Apr 15 12:58:33 lvps83-169-22-195 postfix/cleanup[23194]: 1999A101576: message-id=<20190415105833.1999A101576@ns50-mainz.de>
Apr 15 12:58:33 lvps83-169-22-195 postfix/bounce[25074]: D2F16101214: sender non-delivery notification: 1999A101576
Apr 15 12:58:33 lvps83-169-22-195 postfix/qmgr[23822]: 1999A101576: from=<>, size=15511, nrcpt=1 (queue active)
Apr 15 12:58:33 lvps83-169-22-195 postfix/qmgr[23822]: D2F16101214: removed
Apr 15 12:58:33 lvps83-169-22-195 postfix-local[25146]: postfix-local: from=MAILER-DAEMON, to=local_mailadress@xxxxxxxxxxxx.de, dirname=/var/qmail/mailnames
Apr 15 12:58:33 lvps83-169-22-195 postfix/pipe[25075]: 1999A101576: to=<local_mailadress@xxxxxxxxxxxx.de>, relay=plesk_virtual, delay=0.02, delays=0/0/0/0.01, dsn=2.0.0, status=sent (delivered via plesk_virtual service)
Apr 15 12:58:33 lvps83-169-22-195 postfix/qmgr[23822]: 1999A101576: removed


Regards
Jens
 
Apr 15 12:58:33 lvps83-169-22-195 postfix/pipe[25075]: 1999A101576: to=<local_mailadress@xxxxxxxxxxxx.de>, relay=plesk_virtual, delay=0.02, delays=0/0/0/0.01, dsn=2.0.0, status=sent (delivered via plesk_virtual service)
says it has been delivered.
 
Hello. Thanks for clarfiying. We encountered the problem at our firewall, after your hint.
The firewall doesn't accepted any mail that couldn't be resolved to any domain.
The plesk server was sending mails with his ip, so we got following error at our firewall:
Domain of sender address MAILER-DAEMON@83.169.22.195 does not exist

After that, we changed configuration of our firewall to allow recieving this mails and everything was fine.

Regard
Jens
 
Back
Top