• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Mail from non-existant user of a local domain

tkalfaoglu

Silver Pleskian
Server operating system version
AlmaLinux
Plesk version and microupdate number
Obsidian
Interesting thing.. I'm seeing this in the logs:

Code:
Oct 01 16:31:53 storm postfix/smtpd[30855]: disconnect from r31.mail.safisalons.fr[192.243.255.31] ehlo=1 starttls=0/1 commands=1/2
Oct 01 16:32:02 storm postfix/pickup[63938]: 2A76841426BB: uid=10181 from=<[email protected]>
Oct 01 16:32:02 storm postfix/cleanup[30875]: 2A76841426BB: message-id=<[email protected]>
Oct 01 16:32:02 storm postfix/qmgr[6297]: 2A76841426BB: from=<[email protected]>, size=12360, nrcpt=1 (queue active)
Oct 01 16:32:03 storm postfix/smtp[31440]: 2A76841426BB: to=<[email protected]>, relay=mxin5.ziggo.nl[212.54.42.8]:25, delay=1.1, delays=0.14/0.01/0.27/0.66, dsn=2.
0.0, status=sent (250 2.0.0 MXIN650 mail accepted for delivery ;id=ecb4oYyqRIVwNecb4offlg;sid=ecb4oYyqRIVwN;mta=mx5.tb;dt=2022-10-01T15:32:03+02:00;ipsrc=176.9.1.
236;)
Oct 01 16:32:03 storm postfix/qmgr[6297]: 2A76841426BB: removed

The domain "ucyildizltd.com.tr" exists and has email service enabled.. But it has NO email addresses defined.. So, the [email protected] is NOT a user that exists. So, why is the mail "from" that user is accepted, and how can I prevent it?

Many thanks, -t
 
Do you have this email in the output of the command:

# postmap -s /var/spool/postfix/plesk/virtual | grep @ucyildizltd.com.tr

?
 
The first line of your code sample is misleading. It is not part of the transaction. The transaction starts with the second line, the "pickup". This indicates that the mail is transmitted to your local mail server from an authorized system that does not need to login using a user name or password. This is the web server. So what you are seeing there is a website using the PHP mail() function to submit mail to the mail server.

In most cases this is caused by either insecure forms (forms without captchas) that are abused by spambots to send spam. Second comes insecure website scripts that give way to malware or are malware themselves. The best practice is to first secure all website forms with captchas, then check if the problem persists.
 
The first line of your code sample is misleading. It is not part of the transaction. The transaction starts with the second line, the "pickup". This indicates that the mail is transmitted to your local mail server from an authorized system that does not need to login using a user name or password. This is the web server. So what you are seeing there is a website using the PHP mail() function to submit mail to the mail server.

In most cases this is caused by either insecure forms (forms without captchas) that are abused by spambots to send spam. Second comes insecure website scripts that give way to malware or are malware themselves. The best practice is to first secure all website forms with captchas, then check if the problem persists.
Wonderful -- many thanks.. I will disable their access to "sendmail" in mail settings. Hopefully this will help. I'll also inspect their web site now..
 
Back
Top