sbeitzel / stumpy Goto Github PK

The app is expecting data one line at a time. If a message comes in all at once, or in just a couple of chunks, it doesn't get processed correctly.

Let's go ahead and update for Swift's concurrency features and use NIO at the same time. It'll be a good experience to learn how to deal with NIO, at the very least.

See, RFC 5321 and examples such as those at Cisco's marketing site or at SamLogic's website

HELO just responds with an ok, but EHLO should be more verbose.

App store review rejected the app because the UX is not up to snuff. It's a good point. You shouldn't have to resize the main window just to get to all the information. The reviewer used the term, "tab," and that's something to consider for the future, but at the very least we could stick the MailstoreControlViews in a ScrollView so a user can get to them all.

We store the capacity in our ServerSpec data structure. Let's go ahead and allow it to be set while the server is not running.

Since the whole point of this project is to provide a dummy email server for applications (services) that generate/consume email, maybe let's have a headless version that could be deployed to a Docker container.

Currently load saved just instantiates a server per record. We should only add missing servers.

Once you have multiple server definitions, it can be nice to name them. Let's add that capability, both to the ServerSpec and to the UI.