• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

SMTP: Mail aliases and SPAM managing

M

Magumo

Guest
I make extensive use of email aliases to manage SPAM. Each alias is specific to an organisation and only provided to this one organisation. E.g. if I considered Admin a SPAM risk, I would set up [email protected].

In the past the mail headers always included the alias to which a mail message was delivered. Thus I could see which address was receiving large volumes of SPAM and remove it.

Lately the mail header often does not show to which address the mail was delivered. Any reason for this?
The mail was delivered, so the address to which it was directed must be available.

Any way to determine to which of my aliases this was delivered?
 
Back
Top