Resolved AFTER MIGRATION - email do not exist or cannot receive mail

[femotvaff]

Server operating system version

Debian

Plesk version and microupdate number

18.0.60 Update #1

AFTER MIGRATION - email do not exist or cannot receive mail

After migration,
DNS was setted
but mail are bounced with the message

"
Recipient address rejected: Us=
er unknown in virtual mailbox table "

Any suggestion?

 

[femotvaff]

sudo plesk repair mail domain.com

no effect
zero to repair ...

 

[Bitpalast]

Did you verify the mail server DNS settings with a tool like mxtoolbox.com? Did you verify that the mailboxes exist on the new server? Did you check the maillog what happens when a mail is received?

 

[femotvaff]

Yes of course.

DNS is ok
MX record was ok
Mail are bouced because they appear to not exist in the server...
but of course they exist.

Recipient address rejected: Us=
er unknown in virtual mailbox table "

it is a problem of plesk

 

[femotvaff]

In mail log we can see mail arrive...

Jun 12 04:29:01 SERVERNAME postfix/smtpd[3985]: NOQUEUE: milter-reject: MAIL from de-smtp-delivery-223.mimecast.com[194.104.111.223]: 451 4.3.5 Server configuration problem - try again later; from=<> proto=ESMTP helo=<de-smtp-delivery-223.mimecast.com>
Jun 12 04:29:01 SERVERNAME postfix/smtpd[3985]: disconnect from de-smtp-delivery-223.mimecast.com[194.104.111.223] ehlo=1 starttls=0/1 mail=0/1 quit=1 commands=2/4
Jun 12 04:29:27 SERVERNAME postfix/smtpd[3985]: connect from sw.managed-otrs.com[159.69.61.96]
Jun 12 04:29:27 SERVERNAME postfix/smtpd[3985]: warning: milter inet:127.0.0.1:12768: bad protocol information: socks
Jun 12 04:29:27 SERVERNAME postfix/smtpd[3985]: NOQUEUE: milter-reject: CONNECT from AlfredKeller.managed-otrs.com[159.69.61.96]: 451 4.3.5 Server configuration problem - try again later; proto=SMTP
Jun 12 04:29:27 SERVERNAME postfix/smtpd[3985]: NOQUEUE: milter-reject: MAIL from AlfredKeller.managed-otrs.com[159.69.61.96]: 451 4.3.5 Server configuration problem - try again later; from=< > proto=ESMTP helo=<sw.managed-otrs.com>


it is something wrong in PLESK
but as we use the migration tool, we should have the same configurations

 

[Kaspar@Plesk]

I am not sure about 451 4.3.5 Server configuration problem - try again later error.

For the Recipient address rejected: User unknown in virtual mailbox table error you can try to run the mail repair utility: plesk repair mail example.com -y or if the issue occurs to many domains plesk repair mail -y

 

[femotvaff]

Thank you
it was already done 2 times, no errors.
and no solution.

Someone have idea how to check "virtual mailbox table" ?

 

[Kaspar@Plesk]

Did you check if the Mail service is enabled for the domain (which can be set in the mail settings of the domain)?

You can use the postmap -s /var/spool/postfix/plesk/virtual | grep [email protected] command the search for and email address in the virtual mailbox table (replace [email protected] with the email address of the mailbox).

 

[femotvaff]

yes of course,
and mails go out,
but cannot came in
and email yes is in the table

 

[Kaspar@Plesk]

I recommend opening a ticket with Plesk support for an investigation of the issue on your server. To sign-in to support please go to https://support.plesk.com

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk

 

[femotvaff]

it will be an endless story...
Anyway thank you!

 

[femotvaff]

The problem seems to be a A Milter program (content filtering software) rejected the email.
Now I have to understand which and why...

NOQUEUE: milter-reject: CONNECT from authsmtp38.domain.it[33.12.8.101]: 451 4.3.5 Server configuration problem - try again later; proto=SMTP

 

[femotvaff]

no is not that one the problem...

 

[femotvaff]

Jun 14 17:18:24 domainserver postfix/cleanup[5995]: 4DE242AF71: message-id=<CAATQh1rVVW4+rgu+ZGRH=A0nsP5P6QkYA=[email protected]>
Jun 14 17:18:24 domainserver psa-pc-remote[31098]: 4DE242AF71: py-limit-out: stderr: INFO:__main__:No SMTP AUTH and not running in sendmail context (incoming or unrestricted outgoing mail). SKIP message.

Sapete interpretare questo messaggio?
omeglio perchè plesk chiede un'autenticazione per le mail in arrivo ???
Grazie

 

[Kaspar@Plesk]

Jun 14 17:18:24 domainserver psa-pc-remote[31098]: 4DE242AF71: py-limit-out: stderr: INFO:__main__:No SMTP AUTH and not running in sendmail context (incoming or unrestricted outgoing mail). SKIP message.

The log entry is informative, it indicates that the message was not blocked. The SKIP message at the end of the line indicates that filters are being bypassed. Likely because of an bounceback message.

 

[femotvaff]

The problem was opendkim, as plesk has his DKIM native, romoving that and reverting postfix configuration solved the problem.