Thomas

yeah I know the workarounds. nevertheless hashcheck should have a way to save the file properly.

I also would appreciate the ability to show the arguments throug `choco`. the security concerns raised in this issues are kind of moot when [NugetEncryptionUtility](https://github.com/chocolatey/choco/blob/6ba4f47360cb0324e0d5af4023b46c72165a3a5b/src/chocolatey/infrastructure.app/nuget/NugetEncryptionUtility.cs) uses the [machine key](https://docs.microsoft.com/en-us/dotnet/api/system.security.cryptography.dataprotectionscope?view=netframework-4.7.2) for...

so in other words, Chocolatey in the open source version could easily add a parameter to show the arguments, without any of the aforementioned concerns raised. personally, I doubt that...

this systemd unit works fine for me: ``` [Unit] Description=MailDev After=network.target StartLimitIntervalSec=0 [Service] Type=simple EnvironmentFile=-/etc/default/maildev ExecStartPre=/usr/bin/test -x /usr/bin/maildev ExecStart=/bin/sh -c '/usr/bin/maildev ${DAEMON_ARGS} >> /var/log/maildev.log 2>&1' PIDFile=/run/maildev.pid Restart=always RestartSec=10s User=maildev Group=maildev...

I think this is fixed in 2.0.0, see https://github.com/maildev/maildev/issues/287

no, it prevents maildev from exiting after any smtp protocol errors encountered in the upstream smtp npm packages: ```client.on('error', function(e) { logger.error('Caught SMTP protocol error: ', e) })``` haven't had...

awesome!

thanks all, this looks great! having these changes on npm would certainly be welcomed for users (like me) as well :)

awesome, looking forward to a new release! thanks for your work, very much appreciated!

would be nice if one of the forks could also push their updated code to the npm repository (https://www.npmjs.com/search?q=maildev) for the end users :)