What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
Stop the delivery first, preserve evidence, then identify the process that submitted the messages. The www-data account is commonly used by Apache, PHP-FPM, and other web services, so spam sent as that user usually points to a vulnerable application, stolen credential, malicious upload, scheduled task, or abused local mail interface. Disabling mail blindly may stop the symptom while leaving the compromise active—or break legitimate password resets and alerts.
A reliable fix has two parts: investigate the incident and enforce a mail policy. Save the mail and web logs, map queue activity to a site and script, remove the cause, and then either disable local PHP mail for web requests or require narrowly controlled authenticated SMTP submission. The exact configuration depends on your distribution, PHP SAPI, mail transfer agent (MTA), and hosting panel.
1. Contain the spam without destroying evidence
Work from a console or an out-of-band management session if possible. Do not start by deleting the mail queue or wiping the suspected website; those actions can remove the queue IDs, timestamps, and files needed to identify the sender.
Preserve the relevant records
- Copy the MTA log files, including the period before and after the first alert.
- Save web-server access and error logs, PHP-FPM logs, application logs, and authentication logs.
- Record the current queue, the server time zone, and the time of the first known spam message.
- Capture running Apache, Nginx, PHP-FPM, cron, and MTA processes, including their user IDs and command lines.
- Save several spam samples with their complete headers and any queue ID shown by the MTA.
Linux audit facilities can add process-level evidence. When auditd is enabled, its records can be searched with ausearch or summarized with aureport. If auditing was not enabled before the incident, it cannot reconstruct earlier executions, but enabling it after containment can help catch a recurrence.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Stop further delivery temporarily
Use the administrative controls for your MTA rather than killing arbitrary processes. A temporary stop, outbound firewall rule, or queue hold limits damage while you investigate. A full MTA stop affects every local service, so schedule it only when that blast radius is acceptable.
- Check which MTA is active: common choices are Postfix and Exim, but package names differ by distribution.
- Place new mail on hold or stop the MTA during the investigation. Use the MTA’s documented queue-management command for your release.
- If the host is still sending directly, restrict outbound TCP port 25 at the firewall. Keep an exception for the approved submission service if one is required.
- Notify the owner of any hosted sites and your upstream provider if large volumes were delivered; reputation damage can continue after the process is stopped.
Do not purge the queue until you have exported its IDs, envelope senders, recipients, and timestamps. Holding messages gives you time to distinguish legitimate notifications from abuse.
Free tools Windows power users keep installed
One-click scans. No signup required.
2. Prove which account and process submitted the mail
Start with the MTA log and queue ID
Search the mail log for the envelope sender, recipient domain, queue ID, and delivery status. The queue ID is the bridge between an MTA event and the message content. On a Postfix host, a queue listing can be viewed with postqueue -p; inspect individual messages with the queue tools supplied by your installed version. Log locations vary, commonly under /var/log/maillog or /var/log/mail.log.
Record whether the message entered through local sendmail compatibility, an SMTP listener, or an authenticated submission service. Look for the executable, client address, SASL username, envelope sender, and operating-system UID. A message accepted from localhost by the sendmail interface has a different investigation path from one accepted over the network with a stolen SMTP password.
Correlate the UID with PHP-FPM or the web server
On a single-site server, www-data may identify the web worker directly. On a multi-tenant host, it may be shared, making attribution ambiguous. Check PHP-FPM pool definitions, Apache or Nginx worker settings, and the process list to determine which virtual host or pool ran as that UID. Hosting panels that execute PHP as the account owner can provide a more precise account-level attribution; some record an actual_sender value for this purpose.
Match the MTA timestamp to web access and error logs. Repeated POST requests to an upload, contact form, plugin endpoint, or unfamiliar PHP file immediately before the queue events are strong leads, not proof by themselves. Preserve the original file and its metadata before editing it.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Use audit records when available
Audit rules that capture execution of the sendmail-compatible binary, changes under web roots, and writes to upload directories can identify the parent process and UID. Search the event time window with ausearch, then use aureport to summarize executable and user activity. The absence of an audit event does not prove that no mail was sent; many systems were not configured to audit those paths.
3. Find the actual origin inside the site
Mail submission is only the last step. The code or credential that triggered it may still be present after you stop the queue.
Inspect recently changed and writable files
- List PHP files changed around the first spam timestamp, including files outside the normal application directories.
- Examine writable upload, cache, temporary, and media directories for executable files or double extensions.
- Compare core CMS and extension files with clean copies from the same release.
- Search application code for calls to
mail(),proc_open(),shell_exec(), backticks, and sendmail-wrapper paths. - Check web roots, document stores, and temporary directories for web shells or obfuscated code.
A recently modified file is a lead, not automatic evidence of authorship: deployment tools, updates, and cache jobs also change files. Keep a forensic copy and record hashes before removing anything.
Check scheduled and persistent execution
Review the web account’s crontab, system cron directories, systemd timers, queue workers, and application schedulers. Inspect startup files and service definitions for commands running as www-data. Remove unauthorized persistence only after saving its content and timestamps.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Assume credentials may be exposed
Rotate SMTP passwords, API keys, database passwords, CMS administrator credentials, deployment keys, and hosting-panel credentials that the site could read. Revoke old tokens rather than merely changing a local configuration file. Review privileged accounts and active sessions for additions made during the same period.
4. Understand how PHP sends mail
On Unix-like systems, PHP’s mail() function normally hands a message to the configured sendmail-compatible transport; PHP itself is not the final delivery system. The PHP manual documents /usr/sbin/sendmail -t -i as the usual sendmail_path default, but distributions can change it.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Every active PHP SAPI has its own configuration. Check the CLI binary, Apache module, and PHP-FPM pools separately; changing the CLI php.ini does not necessarily change the FPM configuration used by web requests. Confirm the effective value from the runtime that serves the affected site, then restart or reload the relevant service after a change.
Decide whether web applications need local mail
- No legitimate web mail: disable the sendmail path for the web SAPI or point it to a wrapper that logs and rejects attempts.
- Legitimate notifications exist: keep local invocation unavailable to untrusted code where possible, and route approved applications through authenticated SMTP submission.
- Several sites share the host: use per-site pools, users, or wrappers so one compromise cannot submit as every tenant.
A rejection wrapper is safer than silently discarding messages because it leaves an auditable event and exposes applications that still depend on local mail. Test password resets, contact forms, billing notices, and monitoring alerts before deploying the policy broadly.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute5. Lock down Postfix relay policy
Postfix’s normal model is moderately restrictive: relay is allowed for trusted networks or authenticated clients, while unauthenticated destinations are deferred. The commonly documented restriction pattern is:
smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, defer_unauth_destinationApply the setting in the configuration used by the running Postfix instance, validate the resulting configuration, and reload Postfix. The exact command and service name depend on the package. Review both IPv4 and IPv6 listeners, trusted network definitions, and any included configuration fragments.
Audit legacy recipient rules
Older configurations sometimes put broad permit rules in recipient restrictions. That can unintentionally create an open relay even when a newer relay-restriction setting looks correct. Test from an unauthenticated external host and from localhost; a successful delivery to an unrelated external domain is a serious policy failure.
Use SASL for approved applications
Authenticated SMTP submission preserves required mail while making credentials independently revocable. Create a narrowly scoped account for each application or site, restrict its sender identities where your system supports that, and apply rate limits. Submit through the designated submission service rather than allowing arbitrary local scripts to invoke a powerful sendmail binary.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Protect credentials in a secret store or root-readable configuration, use TLS as required by the submission service, and rotate keys after any suspected web compromise. Authentication proves which credential submitted a message; it does not make a vulnerable application trustworthy, so keep the per-account and rate controls.
6. Configure Exim and hosting panels for attribution
Exim’s trusted-user behavior and sender checks determine which envelope data a local process may assert. Review trusted users, local interfaces, and sender verification in the active Exim configuration instead of assuming that a local www-data process is harmless.
On hosting panels, prefer per-account execution. When PHP runs as the owning account and the panel logs an actual_sender, a compromised site can be separated from other tenants quickly. If all sites execute as one shared UID, improve isolation with separate pools or account users before relying on log-based attribution.
7. Protect the queue and recipient policy
Rejecting unknown recipients can prevent queues from filling with undeliverable MAILER-DAEMON messages. It is useful when your server is authoritative for a known set of domains or users, but recipient probing during dictionary attacks can itself create load. Set recipient validation with awareness of your directory, aliases, catch-all addresses, and abuse volume.
Set queue limits, concurrency limits, and per-account rate limits appropriate to the host. Alert on sudden increases in message count, distinct recipients, failed deliveries, or messages submitted by a web UID. Keep enough queue history to investigate without allowing a runaway queue to exhaust disk space.
8. Repair the application and credentials before reopening mail
- Patch the CMS, framework, plugins, themes, libraries, and operating system packages that are exposed to the Internet.
- Remove malicious files and unauthorized scheduled tasks, then restore altered code from a verified clean source.
- Rotate and revoke credentials, including SMTP and API credentials that were readable by the web process.
- Review administrator accounts, SSH keys, database users, and panel users for persistence.
- Fix file ownership and permissions so uploads are not executable and the web process cannot modify application code unnecessarily.
- Rebuild or redeploy from a known-clean image when you cannot establish that the host is trustworthy.
- Re-enable mail for one application at a time and verify the process identity, envelope sender, queue behavior, and rate limits after each change.
9. Choose the control that fits your server
| Control | Legitimate mail | Site or user attribution | Credential revocation | Visibility and limits | Operational impact |
|---|---|---|---|---|---|
| Disable local PHP mail | Stops applications that depend on mail() until they are reconfigured |
Strong for containment, but attribution ends at the rejected attempt unless the wrapper logs it | Not applicable to local mail; existing external credentials still require rotation | Good if the wrapper records caller and path; no outbound queue from PHP | Highest chance of breaking notifications, but smallest delivery blast radius |
| Authenticated SMTP submission | Preserves approved notifications | Depends on separate pools, users, or application credentials | Strong: revoke one application’s credential without disabling others | Supports per-account rate limits and submission logs | Requires secret management, TLS, account policy, and monitoring |
| Per-account execution | Preserves mail while separating tenants | Strong when the MTA records the owning account or actual sender | Can be combined with per-account credentials | Improves queue and abuse attribution | Requires hosting/runtime support and migration work |
| Open local relay with broad permissions | Usually works until abuse occurs | Poor | Poor | High queue and reputation risk | Unacceptable for an Internet-facing server |
10. Verify that the fix works
Test from the same execution context that generated the spam. A shell test as your administrator does not prove that PHP-FPM running as www-data is blocked or correctly authenticated.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
- Confirm the web SAPI’s effective
sendmail_pathand restart the correct PHP-FPM or web service. - Submit a legitimate notification through the approved application path and record its queue ID.
- Attempt an unauthenticated relay to an unrelated external domain; it should be rejected or deferred according to policy.
- Attempt a message with an invalid recipient and verify that recipient controls behave as intended.
- Watch MTA, web, PHP, and audit logs while testing, then confirm that the expected UID, account, sender, and authentication identity appear.
- Check the queue and disk usage after the test window; no uncontrolled growth should occur.
11. Troubleshooting common outcomes
Spam continues after PHP mail is disabled
The source may be an already queued message, a different PHP SAPI, an SMTP credential used directly, a cron job, or another service account. Hold and inspect the queue, search for authenticated submissions, and compare process UIDs. Verify that every active FPM pool and Apache module uses the intended configuration.
Legitimate notifications stopped
Identify the application and its required transport from logs. Restore only the approved submission path, preferably with a dedicated authenticated account and rate limit. Do not re-enable unrestricted local sendmail access merely to make one form work.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →The queue is empty but the server is listed by anti-spam services
Reputation systems can continue listing an address after delivery stops. Preserve evidence, notify the relevant upstream provider, fix the vulnerability, and monitor for renewed attempts. Removing the queue does not undo messages already delivered.
Several sites appear to send as www-data
Shared execution prevents reliable attribution. Separate PHP-FPM pools or operating-system users, record the owning account in MTA logs, and apply per-account credentials and limits. Until isolation is implemented, treat every site writable by that UID as potentially affected.
A relay test appears to succeed
Distinguish acceptance for local processing from final delivery. PHP documentation notes that acceptance by mail() does not guarantee arrival at the destination. Follow the queue ID through the MTA log and test from an unauthenticated external network; a localhost acceptance alone is not an open-relay test.
Quick Recap
12. A maintenance checklist
- Keep the CMS, extensions, PHP, MTA, and operating system patched.
- Review web-root and upload permissions; prevent execution in directories intended only for data.
- Use separate service users or pools for separate sites.
- Require authenticated submission for applications that must send mail.
- Rotate SMTP and API credentials on a schedule and after every suspected compromise.
- Set queue, concurrency, recipient, and per-account rate limits.
- Retain MTA, web, PHP-FPM, and audit logs long enough to correlate incidents.
- Alert on unusual volume, recipient diversity, sender identities, and submissions by web accounts.
- Exercise the containment and restoration procedure before the next incident.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
