It seems IPB's email settings are too limited and don't allow for the outbound mail to use an encrypted port and/or authenticated B. smtp which is insecure. Because of this we are having limitations on email. If we encrypt smtp, then IPB won't work. A hacker can "sniff" our traffic unencrypted and determine passwords, usernames, etc.


The solution to this is as follows:

1. IPB to have configuration options for encrypted snmp and appropriate ports.

2. IPB to have configuration options to allow for authenticated snmp. Therefore making the process of sending notifications secure by having to provide a username and password.

3. IPB to have configuration options to allow the use of multiple outbound servers in case on goes down. (this one is more a nice to have)

Any chance this can be accomplished?

I'll move this to the Feedback forum, since you're asking for changes to the software.

Thanks.