You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would require the contents of smtpServer to look something like:
{
"TestServer": {
"Name": "TestServer",
"Save": true,
"Email": "[email protected]",
"Host": "webmail.emailAddr.com",
"Port": "25",
"Username": "",
"Password": "",
"Mechanism": "PLAIN"
}
}
The auto-forward would require a server from the provided config. You could require that there be an email address provided in the server given to the auto-forward option, and default save to true. If you want to go crazy, you could use the recipient of the email sent to mailhog and if there's a server in the config that matches that address, it would automatically forward there. In this case you could eliminate the server name from the auto-forward argument and just default to the first server in the list if the email address doesn't match any of them.
My use case is that I have several environments I want to run automation against, so I want mailhog to run on each box and keep emails in memory. This eliminates the need for a central mail server or running heavy mail servers on each box. However, I want to keep a longer-lasting record so we can look back at emails from a central place that users can access via Thunderbird or SquirrelMail, as we have many different levels of user. If that server is down, our automation can at least run and pass. Right now we're tied to the central server, which gives us a single point of failure, so using mailhog as a pass-through with a local copy would solve our problems.
The text was updated successfully, but these errors were encountered:
I would love to have an option to have all emails forwarded to an SMTP server. I was thinking of something like using command-line options as such:
Mailhog -outgoing-smtp smtpServer -auto-forward TestServer
This would require the contents of smtpServer to look something like:
{
"TestServer": {
"Name": "TestServer",
"Save": true,
"Email": "[email protected]",
"Host": "webmail.emailAddr.com",
"Port": "25",
"Username": "",
"Password": "",
"Mechanism": "PLAIN"
}
}
The auto-forward would require a server from the provided config. You could require that there be an email address provided in the server given to the auto-forward option, and default save to true. If you want to go crazy, you could use the recipient of the email sent to mailhog and if there's a server in the config that matches that address, it would automatically forward there. In this case you could eliminate the server name from the auto-forward argument and just default to the first server in the list if the email address doesn't match any of them.
My use case is that I have several environments I want to run automation against, so I want mailhog to run on each box and keep emails in memory. This eliminates the need for a central mail server or running heavy mail servers on each box. However, I want to keep a longer-lasting record so we can look back at emails from a central place that users can access via Thunderbird or SquirrelMail, as we have many different levels of user. If that server is down, our automation can at least run and pass. Right now we're tied to the central server, which gives us a single point of failure, so using mailhog as a pass-through with a local copy would solve our problems.
The text was updated successfully, but these errors were encountered: