Hi!I must stop receiving emails when the server is stopped.
So, at the time the user types quit in the server, the connection is alive for some seconds (or minutes) and in this meantime some emails are created in the mail.box and I want to prevent it. I was thinking that the tasks that creates email in the mail.box is http (for iNotes), smtp, and the nserver task itself (for internal emails)
So I wrote a server task that when it is executed, it stops the smtp and http tasks and disables all ports and then it sends a quit command. The problem is that next time the server is started all ports are disabled and users cannot stablish any connection.
Is there any other way to either suspend the ports, or avoid receiving emails?
In the server I wrote a server task that processes email. Now, when the admin types quit to stop the server, this server task may be the first task to be stopped. So it is stopped but then in the following seconds users will keep creating emails in the mail.box until the server is really down and these emails are not processed.That’s why I want to implement my own little shutdown procedure that when it is executed it quit the connection first, then stop my server task and then it stops the server, so my little server task will not skip any email.