View Issue Details

IDProjectCategoryView StatusLast Update
0001755Anope Stable (2.0.x series)Generalpublic2023-03-09 15:06
Reporterdbx12 Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
OSDebian 
Summary0001755: ns_no_expire is not set by default to newly registrated accounts
DescriptionWhile having ns_no_expire in nickserv.default module, new accounts do not get that option, nor is it added upon confirmation of that user (only tested with CONFIRM <othernick>).
The option can be set without problems using SASET NOEXPIRE after which it is shown on INFO requests about that account.
A work around proposed by Adam is setting nickserv.expire to 0d
Steps To Reproduce- Register new nick "john.doe"
- show INFO john.doe and see it is unconfirmed with an expire matching ns_register.unconfirmedexpire
- Confirm the account with CONFIRM john.doe (as a services oper)
- show INFO john.doe and see it is now confirmed but lacking the "No expire" option and having an expire time matching nickserv.expire
Additional InformationThe configuration of my nickserv and ns_register modules. (Yes, the expire is extremely high, that is intentional since it is an internal network)
https://pastebin.anope.org/index.php?page=viewpaste&id=c98a1b8297
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2023-03-09 15:06 dbx12 New Issue