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

Spammer authenticates somehow with email alias!

RealAbraCadaver

New Pleskian
Well I made a mistake with the first post because it didn't show up for almost 1/2 hour, and now both are deleted or locked, so apologies for the third one:

A spammer is able to authenticate and send spam using an alias nospam@domain.com which is an alias of a real mailname.

OS: CentOS 6.5 (Final)
Panel version: 11.5.30 Update #32

Installed mail server Postfix

Relaying
authorization is required:
SMTP

I cleared the queue, but the spam messages were all from nospam@domain.com and had multiple lines like:
X-No-Relay: not in my network

I see lots of these with differing clients:
Feb 11 16:09:11 u17411632 postfix/smtpd[16157]: 54842322D7: client=unknown[195.7.47.219], sasl_method=LOGIN, sasl_username=nospam@domain.com
Feb 11 16:09:11 u17411632 postfix/smtp[12874]: B830F322CE: to=<tmarantette@comcast.net>, relay=mx2.comcast.net[2001:558:fe2d:70::22]:25, delay=4.1, delays=3.2/0/0.55/0.32, dsn=2.0.0, status=sent (250 2.0.0 R99B1n0070HDTPJ0F99BDH mail accepted for delivery)

Using grep on the log created from here: http://kb.parallels.com/en/114845 I don't see anything from /var/www/vhosts.

What is going on here?!?!
 
OK, thanks. I read both of those articles but I assumed that the spammer would need my password for the real email and use it with the alias. I guess I thought this unlikely, but it seems to be the only way, they must have brute forced my password? I read another post where the user DID change his password and the spammer was still able to send using the alias.

Thanks!
 
Last edited:
We had to delete and recreate aliases yesterday. But today it seems to work ok.

You can use /usr/local/psa/admin/bin/mail_auth_view
to check password for email address and aliases.
 
Back
Top