Strict Standards: Static function JDatabase::test() should not be abstract in /home/lyonsdig/public_html/libraries/joomla/database/database.php on line 350

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/lyonsdig/public_html/libraries/joomla/database/database.php:350) in /home/lyonsdig/public_html/libraries/joomla/session/session.php on line 462

Strict Standards: Accessing static property JCache::$_handler as non static in /home/lyonsdig/public_html/libraries/joomla/cache/cache.php on line 394

Strict Standards: Accessing static property JCache::$_handler as non static in /home/lyonsdig/public_html/libraries/joomla/cache/cache.php on line 396

Strict Standards: Only variables should be assigned by reference in /home/lyonsdig/public_html/plugins/system/mobilebot/mobilebot.php on line 32

Strict Standards: Only variables should be assigned by reference in /home/lyonsdig/public_html/plugins/mobile/terawurfl/terawurfl.php on line 47

Strict Standards: Only variables should be assigned by reference in /home/lyonsdig/public_html/plugins/system/mobilebot/mobilebot.php on line 519

Strict Standards: Only variables should be assigned by reference in /home/lyonsdig/public_html/plugins/system/mobilebot/mobilebot.php on line 544

Strict Standards: Only variables should be assigned by reference in /home/lyonsdig/public_html/plugins/system/mobilebot/mobilebot.php on line 300

Strict Standards: Only variables should be assigned by reference in /home/lyonsdig/public_html/plugins/system/mobilebot/mobilebot.php on line 308

Strict Standards: Only variables should be assigned by reference in /home/lyonsdig/public_html/plugins/system/mobilebot/mobilebot.php on line 327
Lyons Digital Media

Lyons Digital Media, Home

Spoofing, Spamming, and Your Account Security

securityThis past week, we received an email abuse report from our data center. We always take these issues quite seriously and investigated the report. The spam emails were coming from our server. We were able to verify this by looking at the header information of the email messages, which clearly showed them passing through our customer's server even though the email account listed as the sender appeared to be bogus.

The messages were sentĀ from an email address that had been compromised. An email account had been hacked by brute force and the spammers used the account to send mail under various aliases through the customer's server.

Following security procedures, we changed the password on the account to a new secure password, notified the customer of the issue, and monitored the mail flow to insure that no more messages were being sent by the account.

Read more: Spoofing, Spamming, and Your Account Security