5 In versions of ProFTPD prior to 1.2.10rc1, a proftpd.conf that used Classes
11 Class foo ip 127.0.0.1
12 Class foo regex *.evil.com
17 The new Class code uses <Class> sections. The above configuration would
25 The Class and Classes configuration directives are deprecated. The new
26 <Class> sections do not support the old "limit" keyword. Instead,
27 a new MaxClientsPerClass configuration directive can be used:
29 MaxClientsPerClass foo 10
31 There is no equivalent for the old "Class" directive. The proftpd engine
32 will always try to determine if the connecting client belongs to a defined
33 class. No class definitions means that classes will not be used.
35 Classes can only be defined in the "server config" context, not on a <Global>
36 or per-<VirtualHost> basis. This is because the class for a client is
37 determined as soon as the client connects to the server, before the server
38 determines which <VirtualHost> the client is trying to reach. Therefore,
39 class definitions always apply to the entire server.