• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

a piece of maillog

RamlazanC

New Pleskian
could anyone tell me what happens here ?
actually i want to know is this sending this email by my smtp server?

thanks by advance

Feb 23 14:49:36 nsxxxxxx /var/qmail/bin/relaylock[9836]: /var/qmail/bin/relaylock: mail from 187.5.81.179:51251 (187-5-81-179.bsaco701.dsl.brasiltelecom.net.br)
Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers[9838]: Handlers Filter before-queue for qmail started ...
Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers[9838]: from=[email protected]
Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers[9838]: to=[email protected]
Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers[9838]: handlers_stderr: SKIP
Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers[9838]: SKIP during call 'limit-out' handler
Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers[9838]: handlers_stderr: SKIP
Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers[9838]: SKIP during call 'check-quota' handler
Feb 23 14:49:37 nsxxxxxx qmail-queue-handlers[9838]: starter: submitter[9841] exited normally
Feb 23 14:49:37 nsxxxxxx qmail: 1424699377.876704 new msg 77463900
Feb 23 14:49:37 nsxxxxxx qmail: 1424699377.876725 info msg 77463900: bytes 3218 from <[email protected]> qp 9841 uid 2020
Feb 23 14:49:37 nsxxxxxx qmail: 1424699377.946722 starting delivery 287: msg 77463900 to local [email protected]
Feb 23 14:49:37 nsxxxxxx qmail: 1424699377.946742 status: local 1/10 remote 0/20
Feb 23 14:49:37 nsxxxxxx qmail-local-handlers[9842]: Handlers Filter before-local for qmail started ...
Feb 23 14:49:37 nsxxxxxx qmail-local-handlers[9842]: from=[email protected]
Feb 23 14:49:37 nsxxxxxx qmail-local-handlers[9842]: to=[email protected]
Feb 23 14:49:37 nsxxxxxx qmail-local-handlers[9842]: mailbox: /var/qmail/mailnames/xxxxxxxxxx.be/info
Feb 23 14:49:37 nsxxxxxx qmail: 1424699377.993431 delivery 287: success: did_0+0+2/
Feb 23 14:49:37 nsxxxxxx qmail: 1424699377.993453 status: local 0/10 remote 0/20
Feb 23 14:49:37 nsxxxxxx qmail: 1424699377.993463 end msg 77463900
 
If they are SPAM and are coming from a compromised Form then chances are they don't have valid headers that define senders which could be the reason why you can't see the senders in the logs.
 
Hi abdi
Ok i tried to understand, all receiving emails to [email protected] should comes in the maillog if headers are valid?
and where should come the logs on sending emails by submission or smtp port?
 
Back
Top