If recipients report spam from your address, or you see messages in Sent that you did not send, your mailbox (or one of your devices) may be compromised.
Step 1: Change the mailbox password now
- Business Email: log in to GARMTECH.Email and change your password in the account/security settings.
- Hosting email (Plesk): log in to Plesk from My.GARMTECH, open Mail → select the mailbox → change the password.
Password rules: use a long, unique password (do not reuse it on other websites).
Step 2: Enable 2FA (strongly recommended)
- Enable 2FA in GARMTECH.Email.
- Enable 2FA in My.GARMTECH as well (this protects your client area).
Step 3: Check for malicious mailbox settings
Attackers often hide their activity by creating rules or forwarding.
- Review Forwarding (any unknown external address is suspicious).
- Review Filters / Rules (for example, auto-delete, auto-archive, “mark as read”).
- Check Signatures (remove anything you did not add).
- Check Auto-replies (disable unknown ones).
Step 4: Secure your devices
- Run an antivirus/malware scan on all devices that access this mailbox (PC, phone, tablet).
- Remove suspicious browser extensions and unknown email apps.
- Update the operating system and the email app.
Step 5: If the spam comes from a website contact form
Sometimes mailboxes are not hacked — instead, a contact form is abused to send spam through your website.
- Enable CAPTCHA or other bot protection on forms.
- Use SMTP authentication (recommended) and make sure the form plugin is up to date.
- Limit sending rate / add firewall rules (for example, via a CDN such as Cloudflare).
What to expect after you fix it
- You may continue receiving bounces for a short time (spam was already sent).
- If your IP or mailbox was rate-limited due to spam, sending may recover after the issue is resolved and traffic normalizes.
If you are unsure what was compromised, open a ticket in My.GARMTECH and include: the affected email address, the approximate time you noticed the issue, and any suspicious “Sent” examples (subject lines + timestamps). (/tickets/create/step1)
