Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request support for closing and re-opening SMTP listen port #327

Open
davidmcnabnz opened this issue Dec 16, 2022 · 3 comments
Open

Request support for closing and re-opening SMTP listen port #327

davidmcnabnz opened this issue Dec 16, 2022 · 3 comments
Milestone

Comments

@davidmcnabnz
Copy link

So far I haven't found an orderly way to close down the listening SMTP port, and re-open it at a later stage.

If this ability could be provided through methods, it would help in a lot of cases.

@pepoluan pepoluan added this to the 1.5 milestone Dec 16, 2022
@pepoluan
Copy link
Collaborator

Hmm, that's a nice feature... Currently the only way is to end the instance then recreate it again.

Might need some intensive rewrites, though. I think this will be a good feature to add to 1.5.0

@davidmcnabnz
Copy link
Author

In my use case, I've had the SMTP listener spawned by systemd. The only way to close then re-open the port, is for the process to fall on its sword, then let systemd automatically restart it. This is not among the most elegant solutions I've contrived in my time.

@pepoluan
Copy link
Collaborator

In my use case, I've had the SMTP listener spawned by systemd. The only way to close then re-open the port, is for the process to fall on its sword, then let systemd automatically restart it. This is not among the most elegant solutions I've contrived in my time.

Another way is for your enclosing program to capture SIGUSR1 or SIGUSR2 (or heck, SIGWINCH) wherein the enclosing program will perform Controller shutdown & restart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants