• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved cannot get sender domain

Hi Brujo,
For further informations and suggestions, you should consider to provide MORE informations ( i.e. your FQDN and your depending mail - server configuration files ), so that people willing to help have the chance to investigate your issues/errors/problems. ;)

Sure here we go and I attached both both postfix files.
 

Attachments

  • main.cf.pdf
    96.5 KB · Views: 3
  • master.cf.pdf
    53.6 KB · Views: 2
Hi Brujo,

first, I would like to point out, that you secured your mail - server with a certificate of your hostname, which may cause issues/errros/problems with your domain "xxxxpionsxxxx.de".

DMARC + SPF - records for your hostname ( v3xxxx.xxxx.de ) are currently missing , which could as well cause issues/errors/problems.

As you redirect your IP to "mail.xxxxpionsxxxx.de", sendmail - eMails can cause issues/errors/problems on your server. Pls. consider to use only SMTP-AUTH for scripts ( contact-forms, etc. ) for your hosted domains on your server.

Pls. consider to change "Outgoing mail mode", as there are currently no domain/IP - specific settings at your "master.cf". This results in eMails being sent only over your IPv4 or IPv6, with the current SMTP - banner of your hostname, which will further result in a mismatch, if you for example sent eMails with the domain "xxxxpionsxxxx.de", as the recursive check will then be v3xxxx.xxxx.de = 1xx.2xx.XX.XX = mail.xxxxpionsxxxx.de , which is a misconfiguration.


My suggestions:
  1. Change the hostname of your server, to meet your reverse DNS - entry for your IP ( currently setup to reverse to: 1xx.2xx.XX.XX = mail.xxxxpionsxxxx.de ) .
  2. If you changed 1.), pls. don't forget to change the mail - server - certificate, as it is currently secured with a certificate for "CN=v3xxxx.xxxx.de".
  3. Change your "Outgoing mail mode" ( => HOME > Tools & Settings > Mail Server Settings ) to: Send from domain IP addresses and use domain names in SMTP greeting
  4. Change your domain - specific SPF - entries and include your hostname to avoid issues/errors/problems with sendmail - eMails. Example ( with your current hostname )
    Code:
    v=spf1 a:v3xxxx.xxxx.de +a +mx ip4:1xx.2xx.XX.XX ?all
  5. If you changed 1.), pls. don't forget to change the certificate to secure your Plesk Control Panel ( as it is currently secured with a certificate for "CN=v3xxxx.xxxx.de" ).
 
Hi UFHH01,
first awesome support from you I realy appreciate this that you take the time to answer in such detailed way.

Well I followed your Suggestion 1-5 and did the changes via Plesk Gui and not via command line.
I checked the result for example within mxtoolbox and spf check and in my opinion it looks fine.

Unfortunately it seems the errors still existing in the log but only for forwarded mails but as I already mentioned the mails are forwarded anyway.

Mail traffic from extern "[email protected]" > Mail address on the domain "[email protected]" > forward to an external Mailaddress "[email protected]"

Code:
Oct 20 20:56:19 mail postfix/smtpd[12882]: connect from mail-wm0-f51.google.com[74.125.82.51]
Oct 20 20:56:20 mail postfix/smtpd[12882]: 10385A08C3: client=mail-wm0-f51.google.com[74.125.82.51]
Oct 20 20:56:20 mail postfix/cleanup[12888]: 10385A08C3: message-id=<[email protected]>
Oct 20 20:56:20 mail /usr/lib64/plesk-9.0/psa-pc-remote[720]: handlers_stderr: SKIP
Oct 20 20:56:20 mail /usr/lib64/plesk-9.0/psa-pc-remote[720]: SKIP during call 'limit-out' handler
Oct 20 20:56:20 mail check-quota[12890]: Starting the check-quota filter...
Oct 20 20:56:20 mail /usr/lib64/plesk-9.0/psa-pc-remote[720]: handlers_stderr: SKIP
Oct 20 20:56:20 mail /usr/lib64/plesk-9.0/psa-pc-remote[720]: SKIP during call 'check-quota' handler
Oct 20 20:56:20 mail spf[12891]: Starting the spf filter...
Oct 20 20:56:20 mail spf[12891]: SPF result: pass
Oct 20 20:56:20 mail spf[12891]: SPF status: PASS
Oct 20 20:56:20 mail /usr/lib64/plesk-9.0/psa-pc-remote[720]: handlers_stderr: PASS
Oct 20 20:56:20 mail /usr/lib64/plesk-9.0/psa-pc-remote[720]: PASS during call 'spf' handler
Oct 20 20:56:20 mail postfix/qmgr[1512]: 10385A08C3: from=<[email protected]>, size=12131, nrcpt=1 (queue active)
Oct 20 20:56:20 mail postfix/smtpd[12882]: disconnect from mail-wm0-f51.google.com[74.125.82.51]
Oct 20 20:56:20 mail postfix-local[12893]: postfix-local: [email protected], [email protected], dirname=/var/qmail/mailnames
Oct 20 20:56:20 mail dk_check[12894]: Starting the dk_check filter...
Oct 20 20:56:20 mail dk_check[12894]: DKIM verify result: DKIM verification (d=senderdomain.de, 1024-bit key) succeeded
Oct 20 20:56:20 mail journal: plesk sendmail[12898]: handlers_stderr: PASS
Oct 20 20:56:20 mail journal: plesk sendmail[12898]: PASS during call 'limit-out' handler
Oct 20 20:56:20 mail check-quota[12900]: cannot get sender domain
Oct 20 20:56:20 mail check-quota[12900]: Unable to intialize check-quota mail handler
Oct 20 20:56:20 mail journal: plesk sendmail[12898]: Error during 'check-quota' handler
Oct 20 20:56:20 mail postfix/pickup[8078]: 5A2FAA08C5: uid=30 from=<[email protected]>
Oct 20 20:56:20 mail postfix/cleanup[12888]: 5A2FAA08C5: message-id=<[email protected]>
Oct 20 20:56:20 mail postfix/qmgr[1512]: 5A2FAA08C5: from=<[email protected]>, size=12669, nrcpt=1 (queue active)
Oct 20 20:56:20 mail postfix/pipe[12892]: 10385A08C3: to=<[email protected]>, relay=plesk_virtual, delay=0.93, delays=0.79/0.01/0/0.13, dsn=2.0.0, status=sent (delivered via plesk_virtual service)
Oct 20 20:56:20 mail postfix/qmgr[1512]: 10385A08C3: removed
Oct 20 20:56:20 mail postfix/smtp[12904]: 5A2FAA08C5: to=<[email protected]>, relay=ASPMX.L.GOOGLE.COM[74.125.133.27]:25, delay=0.58, delays=0/0.01/0.09/0.48, dsn=2.0.0, status=sent (250 2.0.0 OK 1508525785 v4si1197147wrf.175 - gsmtp)
Oct 20 20:56:20 mail postfix/qmgr[1512]: 5A2FAA08C5: removed

kind regards
 
How exactly is the "can't get sender domain" (according to the title of this thread) solved? I must have missed that. Even to this previous post the error messages persist.
 
How exactly is the "can't get sender domain" (according to the title of this thread) solved?
The thread starter solved his/her issue. So if he/she decided, that all is fine for him/her, it is quite useful that he/she marks the thread as solved... don't you think so as well? ;)
 
Hi Brujo,

Unfortunately it seems the errors still existing in the log
Having another look at your latest log - entries, I come to the conclusion, that the "error" - message might be misleading.

Your log shows, that the eMail is coming from an EXTERNAL eMail - account, is delivered to an INTERNAL ( hosted domain on your server ) eMail account, while you setup the recipient eMail address to forward to an EXTERNAL eMail - address.

Now let's look, how the whole process has been done:

Message "10385A08C3" comes in, "limit out" - handler is being skipped, quota-handler is being skipped, external SPF is being checked, passed and put to queue.
Postfix passes over to DKIM - check, dk_check verifies with a "PASS" and message goes back to queue.
Plesk-sendmail handler takes over as the next handler, but is not responsible, but still logs with
Code:
Oct 20 20:56:20 mail journal: plesk sendmail[12898]: handlers_stderr: PASS
Oct 20 20:56:20 mail journal: plesk sendmail[12898]: PASS during call 'limit-out' handler
Oct 20 20:56:20 mail check-quota[12900]: cannot get sender domain
Oct 20 20:56:20 mail check-quota[12900]: Unable to intialize check-quota mail handler
Oct 20 20:56:20 mail journal: plesk sendmail[12898]: Error during 'check-quota' handler
... which is actually not relevant, as the handler should be skipped.
"postfix/pickup" is next to pick up the ( temporary delivered eMail ( #10385A08C3 ) ... only temporary, as there is a FORWARDER for the eMail - account! ) message ( now with a new message ID #5A2FAA08C5 ! ), which will now forward the message to the EXTERNAL eMail - account and reports the action with a successful deliverey in your logs.
... while at the same time, "postfix/pipe" logs the delivery action over plesk_virtual service as being completed.

Conclusion: No error, just an irritating failure message from "plesk.sendmail", which isn't involved, but is still a valid handler in your message process. ;)
 
Hi Brujo,


Having another look at your latest log - entries, I come to the conclusion, that the "error" - message might be misleading.

Your log shows, that the eMail is coming from an EXTERNAL eMail - account, is delivered to an INTERNAL ( hosted domain on your server ) eMail account, while you setup the recipient eMail address to forward to an EXTERNAL eMail - address.

Now let's look, how the whole process has been done:

Message "10385A08C3" comes in, "limit out" - handler is being skipped, quota-handler is being skipped, external SPF is being checked, passed and put to queue.
Postfix passes over to DKIM - check, dk_check verifies with a "PASS" and message goes back to queue.
Plesk-sendmail handler takes over as the next handler, but is not responsible, but still logs with
Code:
Oct 20 20:56:20 mail journal: plesk sendmail[12898]: handlers_stderr: PASS
Oct 20 20:56:20 mail journal: plesk sendmail[12898]: PASS during call 'limit-out' handler
Oct 20 20:56:20 mail check-quota[12900]: cannot get sender domain
Oct 20 20:56:20 mail check-quota[12900]: Unable to intialize check-quota mail handler
Oct 20 20:56:20 mail journal: plesk sendmail[12898]: Error during 'check-quota' handler
... which is actually not relevant, as the handler should be skipped.
"postfix/pickup" is next to pick up the ( temporary delivered eMail ( #10385A08C3 ) ... only temporary, as there is a FORWARDER for the eMail - account! ) message ( now with a new message ID #5A2FAA08C5 ! ), which will now forward the message to the EXTERNAL eMail - account and reports the action with a successful deliverey in your logs.
... while at the same time, "postfix/pipe" logs the delivery action over plesk_virtual service as being completed.

Conclusion: No error, just an irritating failure message from "plesk.sendmail", which isn't involved, but is still a valid handler in your message process. ;)

Thank you, UFHH01... just having you explain that the error is not relevant, and why, is enough for it to be resolved for me!

It is a bit odd that it logs this as an "error" when all it is doing is receiving then forwarding the email. I wonder if this has something to do with Plesk trying to mitigate the problem it had with forwarded email counting in the "Limit outgoing email" setting... I'll have to do a few tests to see if something there was changed, and if it might be causing this error message now instead of counting against the mailbox quota when it is just a forward. This was the post I made about that years ago: Locally Forwarded email counts toward Limited Outgoing Emails Tally
 
Hi G J Piper,

I wonder if this has something to do with Plesk trying to mitigate the problem it had with forwarded email counting in the "Limit outgoing email" setting...
Yes, it has. The previous improvements have to be reviewed here again, as the "plesk.sendmail" - handler shouldn't jump into this queue.
 
Last edited by a moderator:
Hi UFHH01 and Brujo,

I appreciate a lot your generous help, but I am not sure how this was resolved, and I admit I remain rather confused about all this.
I would like to clarify that the OVH issue is not really one, the domain is registered there, but the VPS runs on another hosting provider. Therefore, there was no import issue, the subscriptions are fine.

About all the suggestions, so far i did:
  1. Changed the mynetworks parameter
  2. Run the plesk update
  3. Changed the outgoing mail mode to send from domain IP address and use domain SMTP greeting
  4. Enabled DKIM overall and activated on selected domains
  5. Tried to improve the SPF record, but I certainly fail here
  6. Assigned reverse dns to my IP, whatever that means

I may go into DMARC stuff. I have no clue for the rest of this messy topic, though.

For me the 'cannot find sender domain' remains logges for each outgoing mail (which still go through, ouff...)

Regards

P.S. Luckily I chose not to host or any email service as I would be even more hairless by now...
 
Nov 22 23:06:34 servidor postfix/smtp[1752]: connect to gmail-smtp-in.l.google.com[74.125.141.26]:25: Connection timed out
Nov 22 23:06:34 servidor postfix/smtp[1752]: connect to gmail-smtp-in.l.google.com[2607:f8b0:400c:c06::1b]:25: Network is unreachable
Nov 22 23:07:04 servidor postfix/smtp[1752]: connect to alt1.gmail-smtp-in.l.google.com[209.85.203.26]:25: Connection timed out
Nov 22 23:07:04 servidor postfix/smtp[1752]: connect to alt1.gmail-smtp-in.l.google.com[2a00:1450:400b:c03::1a]:25: Network is unreachable
Nov 22 23:07:34 servidor postfix/smtp[1752]: connect to alt2.gmail-smtp-in.l.google.com[74.125.206.26]:25: Connection timed out

Are you sure that it is not firewalled from your side? For example, I can connect to these Google mailservers from my server without any problems:

# telnet gmail-smtp-in.l.google.com 25
Trying 64.233.161.27...
Connected to gmail-smtp-in.l.google.com.
Escape character is '^]'.
220 mx.google.com ESMTP s75si67065lfi.167 - gsmtp

# telnet alt1.gmail-smtp-in.l.google.com 25
Trying 74.125.23.27...
Connected to alt1.gmail-smtp-in.l.google.com.
Escape character is '^]'.
220 mx.google.com ESMTP d25si15241376plj.693 - gsmtp
 
root@servidor:~# telnet gmail-smtp-in.l.google.com 25
Trying 74.125.141.26...
Trying 2607:f8b0:400c:c06::1a...
telnet: Unable to connect to remote host: Network is unreachable
root@servidor:~# telnet alt1.gmail-smtp-in.l.google.com 25
Trying 209.85.203.26...
Trying 2a00:1450:400b:c03::1b...
telnet: Unable to connect to remote host: Network is unreachable

Firewall turned off, and it appeared that. I am using server Vultr.
 
Thank you all for the help up to here, but giving up the use the Plesk, it really is a panel very problematic for a panel of trade.

A pity, this control panel could be a solution for those who have few sites and want more performance.

I'm going to look for a solution less cumbersome and soon I make new tests to see if it's improved anything.

Thank you to all who have tried to solve the problem, but I think that is a problem spot.

Att,

Allan Almeida
 
It's strange to blame the Plesk for problems if the problem is in the network infrastructure (Google mail server is not accessible in your network).
 
Back
Top