<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>spam - Matteo Cisilino</title>
	<atom:link href="https://www.cisilino.com/en/tag/spam-en/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.cisilino.com/en/</link>
	<description>Guide su WordPress, server e sicurezza</description>
	<lastBuildDate>Wed, 11 Nov 2026 17:53:04 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>
	<item>
		<title>Comment spam and Contact Form 7: limiting visitors</title>
		<link>https://www.cisilino.com/en/2026/11/11/comment-spam-contact-form-7/</link>
					<comments>https://www.cisilino.com/en/2026/11/11/comment-spam-contact-form-7/#respond</comments>
		
		<dc:creator><![CDATA[matteocisilino]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 17:47:00 +0000</pubDate>
				<category><![CDATA[csdn]]></category>
		<category><![CDATA[Contact Form 7]]></category>
		<category><![CDATA[rate limiting]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[WordPress comments]]></category>
		<guid isPermaLink="false">https://www.cisilino.com/?p=168</guid>

					<description><![CDATA[<p>How to stop spam in comments and Contact Form 7: a limit on logged-out visitors blocks bots without stopping people who really write.</p>
<p>The post <a href="https://www.cisilino.com/en/2026/11/11/comment-spam-contact-form-7/">Comment spam and Contact Form 7: limiting visitors</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>Two messages in ten seconds come from a person in a hurry. Twenty are a bot. For <strong>Contact Form 7 spam</strong> and spam in comments the plugin relies on exactly this difference.</p>
<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" src="https://www.cisilino.com/wp-content/uploads/2026/10/comment-spam-contact-form-7-wordpress.webp" alt="Contact Form 7 spam: two comment bubbles crossed by a pink diagonal line" width="1200" height="630"/></figure>
<h2>How the Contact Form 7 spam limit works</h2>
<p>A logged-out visitor who submits more than N comments or forms (2 by default) within a short window (60 seconds by default) is blocked <strong>only for that type of submission</strong>, for a configurable length of time (1 hour by default). The pages stay reachable: what is refused is the submission that looks like Contact Form 7 spam, not the visit. Someone who overdid it in good faith doesn&#8217;t lose the site.</p>
<h2>It works with comments disabled too</h2>
<p>The count lives in a dedicated table. If comments are off and the only way in is the contact form, the limit still protects you from Contact Form 7 spam.</p>
<h2>What you can adjust in the Contact Form 7 spam limit</h2>
<p>These settings shape how the Contact Form 7 spam limit behaves:</p>
<ul>
<li>A separate switch for the limit and for the email alert.</li>
<li>Alert on authors is on by default, the one on visitors is off.</li>
<li>N, window and block length, all adjustable.</li>
<li><a href="https://www.cisilino.com/en/2026/10/29/cisilino-site-defense-network-security-plugin/">Cisilino Site Defense Network: the WordPress security plugin</a></li>
</ul>
<h2>A classic scenario</h2>
<p>A brochure site with a single contact form can suffer classic Contact Form 7 spam: every night a bot sends hundreds of requests full of links. The company mailbox becomes unusable. With the limit on, the bot crosses the threshold after a few requests, its IP stays out of the forms for an hour and the flow stops. Anyone who really writes from another address doesn&#8217;t notice. The form plugin&#8217;s own page is <a href="https://wordpress.org/plugins/contact-form-7/" target="_blank" rel="noopener">Contact Form 7 on WordPress.org</a>, useful to check which version you run.</p>
<p>A warning for sites behind a proxy or CDN: if every visitor appears to come from the same address, the block would hit everybody. Before switching it on, check that WordPress sees the real IP.</p>
<h2>Frequently asked questions</h2>
<h3>Does the limit block the whole site for the visitor?</h3>
<p>No. It only refuses the submission of comments or forms, the pages stay reachable.</p>
<h3>Does it work against Contact Form 7 spam?</h3>
<p>Yes, it counts both comments and Contact Form 7 form submissions, even with comments disabled.</p>
<h3>What values does it use by default?</h3>
<p>More than 2 submissions in 60 seconds, a 1-hour block. All values are configurable.</p>
<h2>Read more</h2>
<ul>
<li><a href="https://www.cisilino.com/en/?p=97">Compromised WordPress account: suspend users who publish too much</a></li>
<li><a href="https://www.cisilino.com/en/?p=85">WordPress IP whitelist: manual unblocking and timed bans</a></li>
</ul><p>The post <a href="https://www.cisilino.com/en/2026/11/11/comment-spam-contact-form-7/">Comment spam and Contact Form 7: limiting visitors</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://www.cisilino.com/en/2026/11/11/comment-spam-contact-form-7/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Compromised WordPress account: suspend users who publish too much</title>
		<link>https://www.cisilino.com/en/2026/11/11/compromised-wordpress-account/</link>
					<comments>https://www.cisilino.com/en/2026/11/11/compromised-wordpress-account/#respond</comments>
		
		<dc:creator><![CDATA[matteocisilino]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 17:46:00 +0000</pubDate>
				<category><![CDATA[csdn]]></category>
		<category><![CDATA[compromised account]]></category>
		<category><![CDATA[rate limiting]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[WordPress users]]></category>
		<guid isPermaLink="false">https://www.cisilino.com/?p=167</guid>

					<description><![CDATA[<p>A compromised WordPress account can publish hundreds of spam pages in minutes. The author limit suspends the user before the damage is done.</p>
<p>The post <a href="https://www.cisilino.com/en/2026/11/11/compromised-wordpress-account/">Compromised WordPress account: suspend users who publish too much</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>It happens more than you would think. A <strong>compromised WordPress account</strong>, perhaps with author permissions, publishes dozens or hundreds of spam pages within minutes. By the time you notice, search engines have already seen something.</p>
<figure class="wp-block-image size-large"><img decoding="async" src="https://www.cisilino.com/wp-content/uploads/2026/10/compromised-wordpress-account-suspension.webp" alt="Compromised WordPress account: a user icon inside a circle, with a yellow pause symbol at the bottom right" width="1200" height="630"/></figure>
<h2>What the author limit does to a compromised WordPress account</h2>
<p>It counts how many posts or pages a user creates or publishes within a time window. If they go over the threshold, as happens with a compromised WordPress account, they are <strong>suspended</strong> for a length of time you choose. They can no longer create or publish, but their role stays the same. The main administrator can receive an email with the recent content to check. The suspension does not change or delete anything.</p>
<h2>The default, and why it changed</h2>
<p>As of version 1.0.13 the default limit is 150 items in 5 minutes. Before it was 3, and it also suspended an administrator who was simply importing or duplicating pages. The new value copes with real heavy use and still stops a compromised WordPress account publishing hundreds in one go. Anyone who had already customised the value is left untouched.</p>
<h2>What counts and what doesn&#8217;t</h2>
<p>Only posts and pages count towards flagging a compromised WordPress account. Plugin installs and updates, logins, autosaves, revisions, trash, media and other content types do not. Neither does anything that happens in a temporary installation with a different table prefix. Plugin Check creates one with a sample post and page, and in the past it suspended whoever was using it.</p>
<h2>What a suspended user sees</h2>
<p>A notice in the dashboard with the reason and the end date. Administrators see the list of suspended users with a link to revoke. Revoking can also be done from the <em>Rate limiting</em> tab, before the suspension expires.</p>
<p>The limit is a brake and a doorbell, not proof: the email is there to help you decide quickly whether it is a compromised WordPress account or very heavy legitimate use. If it is a real compromise, the official guide <a href="https://wordpress.org/documentation/article/faq-my-site-was-hacked/" target="_blank" rel="noopener">My site was hacked</a> is a good starting point for the clean-up.</p>
<h2>Frequently asked questions</h2>
<h3>How do you stop a compromised WordPress account that is publishing spam?</h3>
<p>By limiting how much content it can create within a time window. The plugin suspends the user who goes over the threshold, without changing their role or deleting their content.</p>
<h3>What is the default threshold?</h3>
<p>From version 1.0.13 it is 150 items in 5 minutes. Threshold, window and suspension length are all configurable.</p>
<h3>Can an administrator be suspended by mistake?</h3>
<p>With the default value it is unlikely, even when importing many pages. A suspension can be revoked at any time from the Rate limiting tab.</p>
<h2>Read more</h2>
<ul>
<li><a href="https://www.cisilino.com/en/?p=99">Comment spam and Contact Form 7: limiting visitors</a></li>
<li><a href="https://www.cisilino.com/en/?p=101">Secure WordPress user registration: roles and email</a></li>
<li><a href="https://www.cisilino.com/en/2026/10/29/cisilino-site-defense-network-security-plugin/">Cisilino Site Defense Network: the WordPress security plugin</a></li>
</ul><p>The post <a href="https://www.cisilino.com/en/2026/11/11/compromised-wordpress-account/">Compromised WordPress account: suspend users who publish too much</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://www.cisilino.com/en/2026/11/11/compromised-wordpress-account/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
