| A common complaint is that spamfilters are hard to remove. Well, no more! There is now '/spamfilter del' which will output all spamfilter along with the appropriate command to delete each spamfilter (by unique ID). This way it should be easy for anyone to delete an existing spamfilter. |
|
More...
|
over 6 years ago
|
| A common complaint is that spamfilters are hard to remove. Well, no more! There is now '/spamfilter del' which will output all spamfilter along with the appropriate command to delete each spamfilter (by unique ID). This way it should be easy for anyone to delete an existing spamfilter. |
|
More...
|
over 6 years ago
|
| Add option: set { ban-include-username yes; }; which will make bans places by spamfilters (and some other systems) to be placed not on *@ip but rather on user@ip. Note that this won't work for ZLINE/GZLINE since no ident/username lookups are done in such cases. Bit of a niche feature but okay.. |
|
More...
|
over 6 years ago
|
| Add option: set { ban-include-username yes; }; which will make bans places by spamfilters (and some other systems) to be placed not on *@ip but rather on user@ip. Note that this won't work for ZLINE/GZLINE since no ident/username lookups are done in such cases. Bit of a niche feature but okay.. |
|
More...
|
over 6 years ago
|
| Add set { cloak-method ip; }; which will make cloaking only be done on the IP and thus result in an XX.YY.ZZ.IP cloaked host. This so you can have "IP cloaking" without disabling DNS lookups. GLINES on hosts still work and IRCOps (and yourself) can still see the host in /WHOIS. Requested in 4957 by Gottem and The_Myth. |
|
More...
|
over 6 years ago
|
| Add set { cloak-method ip; }; which will make cloaking only be done on the IP and thus result in an XX.YY.ZZ.IP cloaked host. This so you can have "IP cloaking" without disabling DNS lookups. GLINES on hosts still work and IRCOps (and yourself) can still see the host in /WHOIS. Requested in 4957 by Gottem and The_Myth. |
|
More...
|
over 6 years ago
|
| In /STATS S display throttling as anti-flood::connect-flood, as that is the new name (since about 2 years). |
|
More...
|
over 6 years ago
|
| In /STATS S display throttling as anti-flood::connect-flood, as that is the new name (since about 2 years). |
|
More...
|
over 6 years ago
|
| Tweaks |
|
More...
|
over 6 years ago
|
| Tweaks |
|
More...
|
over 6 years ago
|
| Some initial work on release notes for 4.0.16. |
|
More...
|
over 6 years ago
|
| Some initial work on release notes for 4.0.16. |
|
More...
|
over 6 years ago
|
| Automatically discover SASL server if saslmechlist is sent by services and set::sasl-server is not set by the administrator. Looks like this: *** Services server 'services.test.net' provides SASL authentication, good! I'm setting set::sasl-server to 'services.test.net' internally. Hopefully this will increase SASL availability significantly. That is, once anope and atheme start sending the saslmechlist to us, of course ;) (see commit d6e26d59e5d403702152b34c94634fb873bba015) |
|
More...
|
over 6 years ago
|
| Automatically discover SASL server if saslmechlist is sent by services and set::sasl-server is not set by the administrator. Looks like this: *** Services server 'services.test.net' provides SASL authentication, good! I'm setting set::sasl-server to 'services.test.net' internally. Hopefully this will increase SASL availability significantly. That is, once anope and atheme start sending the saslmechlist to us, of course ;) (see commit d6e26d59e5d403702152b34c94634fb873bba015) |
|
More...
|
over 6 years ago
|
| Move CAP NEW "sasl" sending to after EOS (End Of Synch) This so saslmechs are properly sent in case of services (re)connect, otherwise the CAP NEW is sent too early when the saslmechs are not known yet. NOTE: This makes sending "EOS" mandatory for any SASL servers. You should be doing this since 14 years ago (it was added in 3.2beta18 in August 2003) so hopefully that is the case. Anope is good anyway :) |
|
More...
|
over 6 years ago
|
| Move CAP NEW "sasl" sending to after EOS (End Of Synch) This so saslmechs are properly sent in case of services (re)connect, otherwise the CAP NEW is sent too early when the saslmechs are not known yet. NOTE: This makes sending "EOS" mandatory for any SASL servers. You should be doing this since 14 years ago (it was added in 3.2beta18 in August 2003) so hopefully that is the case. Anope is good anyway :) |
|
More...
|
over 6 years ago
|
| Allow services to set the saslmechlist so it can be used by sasl v3.2. Note to services coders: send something like this: MD client your.services.server saslmechlist :EXTERNAL,PLAIN |
|
More...
|
over 6 years ago
|
| Allow services to set the saslmechlist so it can be used by sasl v3.2. Note to services coders: send something like this: MD client your.services.server saslmechlist :EXTERNAL,PLAIN |
|
More...
|
over 6 years ago
|
| Only send CAP parameters (token=aaaaaa) to clients with CAP proto 302 or higher, as per CAP specification. (So use "CAP LS 302" to see them) |
|
More...
|
over 6 years ago
|
| Only send CAP parameters (token=aaaaaa) to clients with CAP proto 302 or higher, as per CAP specification. (So use "CAP LS 302" to see them) |
|
More...
|
over 6 years ago
|
| Add support for "CAP extended-join". |
|
More...
|
over 6 years ago
|
| Add support for "CAP extended-join". |
|
More...
|
over 6 years ago
|
| Fix crash due to previous enhancements. |
|
More...
|
over 6 years ago
|
| Fix crash due to previous enhancements. |
|
More...
|
over 6 years ago
|
| Add "CAP chghost" support. Internal recode of userhost changes. Fix force-rejoin not working if doing SVSMODE -x/+x (Koragg, #5015). |
|
More...
|
over 6 years ago
|
| Add "CAP chghost" support. Internal recode of userhost changes. Fix force-rejoin not working if doing SVSMODE -x/+x (Koragg, #5015). |
|
More...
|
over 6 years ago
|
| Remove HOSTILENAME config.h option since running without it is and has never been supported. |
|
More...
|
over 6 years ago
|
| Remove HOSTILENAME config.h option since running without it is and has never been supported. |
|
More...
|
over 6 years ago
|
| It helps if you also update the *.h files to reflect those changes. Duh. |
|
More...
|
over 6 years ago
|
| It helps if you also update the *.h files to reflect those changes. Duh. |
|
More...
|
over 6 years ago
|
