Subscription expiration notices
The expiration warning system
As Wildcat! moved more into the internet, the expiration notice/warning system was working sporadically. This was because the user's last call date was being stamped via one connection
which nullified the sending of expiration warning messages via WCNAV or WEB connections.
The new logic is:
(since 5.3.447)
Expiration Warning Messages (warn*.msg) are now sent the first time the user connects for the day regardless of how he connects. In other words, the user will get his
message when he connects via POP3, WCNAV, ANSI/TELNET or WEB methods which he has an "opportunity" to receive a message. ANSI/TELNET will always display WARN*.BBS screen notices
as before. But connecting via other mean should not stop the WARN*.MSG from being sent now when he connects via POP3, WCNAV, ANSI/TELNET or WEB.
In addition, the default WARN*.BBS files should have a macro at the end of the file. Not having one may give the illusion that it was never displayed to the user.
WARNxx.BBS/.MSG
WARNxx.BBS and WARNxx.MSG files may now be created for any number of days. For example, you could have WARN14.BBS, WARN7.BBS, and WARN3.BBS files
and they would be sent at the appropriate time. In WARNxx.MSG files, you may override the default From name of "Automatic Notice" and subject of "Expiration Notice" by
including one or both of the following lines at the start of the WARNxx.MSG file:
|
From: User Name
Subject: Message Subject
|
These lines must be flush with the left margin in the WARNxx.MSG file.
Example of a WARNxx.MSG:
|
This message is automatically generated to warn you that your
subscription will expire on @ USER.EXPIREDATE @ (@ USER.EXPIREDAYS @ days from now).
|
|
