自动封禁

自動封鎖造成附帶損害的範例 这显示使它看起来像管理员Curps封锁多个其他用户（由匿名的六位数确定）。 在现实中，curps只封锁了用户，和所有其他的“附带损害”被封锁因为他们使用相关的IP地址的封锁用户。

自动封锁是一个自动的封锁的IP地址，由MediaWiki软件做的。 自动封锁是企图从一个被封锁的用户最近使用的IP地址编辑Wiki的结果，所以他們無法匿名或使用不同用戶名做出編輯。

用户每次编辑Wiki，使用的IP地址连接到网站是由MediaWiki软件的权力Wiki记录。 日志的IP地址使用由每个用户是私人饲养的，只有通过用户查核员访问MediaWiki软件的用户可以访问。

The autoblock will duplicate most of the block settings, including if the block is sitewide or partial, but does not include the original duration, blocking email, and hardblock.

解封一位自动封禁的用户

如果一个用户自动封锁，例如如果一个命名用户解除封锁，但他们的IP地址仍然是自动封锁，管理员可以明确自动封锁的：

• 回顾为列表Special:BlockList，搜索用户的帐户名称。 这是一个区分大小写的搜索。
• 确定关联的编号 #xxxxx。 如果搜索这个编号，请确保包含 "#" 号
• 点击 "解封" 链接解除对 #xxxxx 的封禁

注意，一旦自动封禁被解除，这个用户的账户名将不再出现在列表里。

訊息

日志消息

有时“停用自动封禁”一词将出现在封锁消息中。 这意味着当一个用户被封禁时，只有他们的用户名被封禁，但其他使用相同 IP 地址的用户依然可以自由地编辑。

封禁的默认设置是开启自动封禁，但不会明确地在封禁消息中提到这一点。 要禁用对一个账号的自动封锁，管理员必须要手动取消勾选 "自动将此用户最后所使用的，以及后续编辑所在的所有IP地址封禁$1" 复选框。

主功能

在使用Bad article creation bot用户破坏英文維基百科之后不久的Gmaxwell。
他的破坏导致了harej不小心「自动封禁」了整个维基会议NYC 2009。 一位维基百科管理员Kirill Lokshin不太赞成地查看此事件。

当自动封禁发生时，用户可能因为使用相同互联网服务提供商的另一个用户的行为而被封禁。 因此，不同的用户可能最终会被封锁，即使他们个人没有做错任何事情。 这被称为「附带损害」。 例子：

1. 用户:Susan，管理员，封禁用户:Bort为24小时 Susan并不知道，Bort使用AOL编辑维基，并且实施封禁的时候自动封禁是开启的。
2. 用户:Steven，同样在家里使用AOL，被分配到了Bort上次使用过的IP地址，然后登录了维基。

1. Steven receives a "You have been blocked" message when he clicks "Edit", doesn't understand what an autoblock is, and angrily demands to know why admin Susan has blocked him.

1. Steven tries to edit from his work computer (which does not use AOL). He learns that autoblocks only propagate from usernames to IP addresses, and decides to resume normal editing there.

用户需要理解，管理员并不设置自动封禁，这很重要；一旦他们在自动封禁选项开启的情况下封禁了一位用户，自动封禁都是由 MediaWiki 软件设置的。 自动封禁不会出现在管理员的封禁日志里，并且管理员也不会收到它们的通知。 这是保护已登录用户的 IP 地址私有的必要措施。 所以，虽然每次编辑的 IP 地址都会被 MediaWiki 软件记录下来，但即使是管理员、即使在用户已经被封禁的情况下，也无法访问到这一信息。

追踪

MediaWiki版本：

≥ 1.29

If $wgCookieSetOnAutoblock is enabled a cookie ({$wgCookiePrefix }BlockID) will be set on an autoblocked user's browser. 这意味着即使在登出并移动到一个新IP地址之后，用户仍然会被封禁。

当cookie设置，和用户尝试编辑一个页面，页面将加载在cookie指定原封禁和防止用户制作编辑。 This does not, however, create a new autoblock for the new IP address. That only happens if the user logs into the original blocked account.

This form of tracking is dependent on the user's browser retaining the cookie, and so will not work for all blocked users in all situations. The feature is intended to provide a small extra level of protection against blocks being circumvented.

禁用自动封锁

When a block is issued, autoblocking is usually turned on by default, except for common dynamic IP ranges, such as those used by AOL.

MediaWiki版本：

≥ 1.9

A list of such automatically exempt IP ranges can be set in MediaWiki:Block-autoblock-exemptionlist.

Lines starting with * indicate exempt addresses, with the text after being an IP range (leading and trailing whitespace is ignored). All other lines are ignored and may be used as comments. An example of such a page is Wikipedia's exemption list.

Administrators can disable autoblocking at the time of blocking a user, by unchecking the checkbox. Once an "enabled" block is placed, it can also be fixed by modifying the user's block, but this should not be done unless absolutely necessary.

自动重置

There is an internal autoblock expiry time variable, $wgAutoblockExpiry , which is set to 24 hours, meaning that autoblocks only last for 24 hours. However, in the case of dynamic IP address pools (such as those used by AOL), this may affect hundreds of users before the block expires. So in the case of an indefinite block, autoblocks may continue to be set by the software, weeks or months after the initial block has been set. Older indefinite blocks, dating from before the autoblock exemption whitelist and the option to disable when blocking, may also trigger autoblocks.

MediaWiki版本：

≥ 1.20

Manually lifting the original account block automatically lifts every auto block that was created as a consequence of that block. (If the original block merely expires automatically, any dependent autoblocks are not immediately lifted.)

IP封锁列表

When IP addresses are autoblocked, they appear in Special:Ipblocklist (but not in the admin's block log) with a special mask that prevents the IP address from being seen. Instead, the block is identified by the block ID and is labeled "Autoblock #xxxxxx" in the BlockList. Autoblocks register on Special:Ipblocklist, Special:AutoblockList and in the banner available to the blocked user, with the name of the admin that set the original block. However, the admin is not notified that an autoblock has been placed. Diligent administrators who lift a block early may wish to check the blocklist in order to check for any autoblocks that need to be cleared.

提示

• It is helpful for all involved, especially AOL users, who are often chronically autoblocked by collateral damage, to remain patient and remember that it is the software that is responsible for the autoblock, not the administrator who is unfortunate enough to have their name appear on the block log.

• Equally important is for admins to check Special:Ipblocklist and Special:AutoblockList regularly, and unblock all autoblocks from a particular user if more than two autoblocks are set in rapid succession.

• If more than two IP addresses are autoblocked within seconds/minutes of each other, it is a good indication that it is a dynamic IP address pool and the blocks are collateral damage.