• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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.

Issue maillog - cannot get sender domain

RuiCadete

New Pleskian
Hello,

I am getting in some messages the cannot get sender domain in the mail log. This leads to spamassassin to fail and the email is delivered skipping the spamassassin checks. witch is very annoying. Does anyone has this same problem?

  • plesk Onyx 17.8.11
  • dovecot 2.3.0.1-centos7.18031217
  • dovecot-pigeonhole 0.5.0.1-centos7.18031217
  • postfix 2.10.1-7.el7
  • spamassassin 3.4.0-4.el7_5

Maillog:

Jan 29 11:51:55 LCSrv02 postfix/smtpd[29199]: A92534369AA: client=unknown[122.128.107.244]
Jan 29 11:51:55 LCSrv02 postfix/cleanup[29143]: A92534369AA: message-id=<[email protected]>
Jan 29 11:51:55 LCSrv02 /usr/lib64/plesk-9.0/psa-pc-remote[28624]: handlers_stderr: SKIP
Jan 29 11:51:55 LCSrv02 /usr/lib64/plesk-9.0/psa-pc-remote[28624]: SKIP during call 'limit-out' handler
Jan 29 11:51:55 LCSrv02 check-quota[31172]: cannot get sender domain
Jan 29 11:51:55 LCSrv02 check-quota[31172]: Unable to intialize check-quota mail handler
Jan 29 11:51:55 LCSrv02 /usr/lib64/plesk-9.0/psa-pc-remote[28624]: Error during 'check-quota' handler
Jan 29 11:51:56 LCSrv02 postfix/qmgr[28991]: A92534369AA: from=<>, size=4152, nrcpt=1 (queue active)
Jan 29 11:51:56 LCSrv02 postfix-local[31173]: postfix-local: from=MAILER-DAEMON, to=[email protected], dirname=/var/qmail/mailnames
Jan 29 11:51:56 LCSrv02 spamassassin[31174]: cannot get sender domain
Jan 29 11:51:56 LCSrv02 spamassassin[31174]: Unable to intialize spamassassin mail handler
Jan 29 11:51:56 LCSrv02 postfix-local[31173]: Error during 'spam' handler
Jan 29 11:51:56 LCSrv02 postfix/smtpd[29199]: disconnect from unknown[122.128.107.244]
Jan 29 11:51:56 LCSrv02 dovecot: service=lda, user=[email protected], ip=[]. msgid=<[email protected]>: saved mail to INBOX
Jan 29 11:51:56 LCSrv02 postfix/pipe[29195]: A92534369AA: to=<[email protected]>, relay=plesk_virtual, delay=0.66, delays=0.42/0/0/0.24, dsn=2.0.0, status=sent (delivered via plesk_virtual service)
Jan 29 11:51:56 LCSrv02 postfix/qmgr[28991]: A92534369AA: removed


Thank you in advance,
Rui Cadete

 
Check this topic maybe it can help:
Resolved - cannot get sender domain

Additionally:
This error means that the email was not properly formed and the SMTP MAIL FROM: does not contain domain part after @. Such a situation is usually observed when emails are sent by a script: automatic notifications by OS services, "contact us" forms on websites and so on.
 
Thanks Arashi,

I believe that the link you gave me was for sending email... My problem is receiving. I think someone is sending SPAM from another server using my email in the FROM, then I receive the fail notifications.

This is an example of the header of an email with the problem that I have received. I don´t see any error after @... Where from is the sender domain picked from? I anso see mailnull... is this ok?

Return-Path: <MAILER-DAEMON>
X-Original-To: [email protected]
Delivered-To: [email protected]
Received: from host.reholi.com (unknown [122.128.107.244])
by LCSrv02.myemailserver.com (Postfix) with ESMTPS id A92534369AA
for <[email protected]>; Tue, 29 Jan 2019 11:51:55 +0000 (GMT)
Received: from mailnull by host.reholi.com with local (Exim 4.87)
id 1goRvk-0000YW-Tv
for [email protected]; Tue, 29 Jan 2019 17:51:52 +0600
X-Failed-Recipients: [email protected]
Auto-Submitted: auto-replied
From: Mail Delivery System <[email protected]>
To: e[email protected]
Content-Type: multipart/report; report-type=delivery-status; boundary=1548762712-eximdsn-915171973
MIME-Version: 1.0
Subject: Mail delivery failed: returning message to sender
Message-Id: <[email protected]>
Date: Tue, 29 Jan 2019 17:51:52 +0600
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.reholi.com
X-AntiAbuse: Original Domain - xxxxxx.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain -
X-Get-Message-Sender-Via: host.reholi.com: sender_ident via received_protocol == local: mailnull/primary_hostname/system user
X-Authenticated-Sender: host.reholi.com: mailnull
X-Source:
X-Source-Args:
X-Source-Dir:

--1548762712-eximdsn-915171973
Content-type: text/plain; charset=us-ascii

This message was created automatically by mail delivery software.


Thanks!
 
I think that the problem could be fixed by applying

spf01.jpg

in the mail server settings. The reason for it is that when the domain cannot be resolved, SPF will fail, and when SPF fails, the mail won't be delivered in this setting.
 
Back
Top