• 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.

Large number of message from sender "#@[]"

D

dourtyb

Guest
I'm looking at my mail logs using isoqlog and have a large number of messages from sender "#@[]" every day. Does anyone have any idea where they are coming from if I should worry about them. They are all sent to a local postmasteraccount.

Thanks,

Brian Dourty
 
Does your [email protected] e-mail address forward to an e-mail address not on your Plesk server? If so, that's the problem. Those are qmail double-bounces and aren't intended to leave the server (they're supposed to be delivered to a local account).

For example, [email protected] sends mail to [email protected]. Your server bounces back a message saying "[email protected] does not receive mail", to wit invaliddomain.com responds with "[email protected] does not receive mail".

An e-mail with the return address of #@[] then sends mail to [email protected] informing you of the double-bounce. If [email protected] is a local account then you receive the e-mail. If [email protected] forwards to [email protected], then somewhereelse.com responds with "#@[] has an invalid domain" and bounces the e-mail.

Yeah, it took me a few minutes to figure it out too. :lol:
 
Back
Top