AUTH LOGIN provides the ability for clients to authenticate to an SMTP server.
AUTH LOGIN was supported in GWAVA 6.5 but support was not provided in SMG.
Some SMTP servers require clients to authenticate before they will accept email. If you want to use your SMTP server to send email to external email addresses, this is known as relaying. To prevent abuse from spammers, SMTP servers are configured to permit relaying only after the client authenticates (via AUTH LOGIN).
If your email app allows you to specify a username and a password and indicate that your SMTP server requires authentication, it will use that information to authenticate to the SMTP server using AUTH LOGIN.
If your mobile devices have been sending SMTP email to GWAVA or to your SMTP server (like GroupWise/GWIA), things probably have been working pretty much as expected.
If you upgrade from GWAVA to SMG or deploy a new SMG appliance to front end your SMTP server, this is what will happen:
This is an important feature that can severely impact certain customers and was provided in previous versions.
Independent of this thread we should ask for a clearer appliance numbering!
Use "Verified Answers" if your problem/issue has been solved!
The Update went well. We will test and implement monday morning.
This only updates the SMG code to 178.
Appliance version stays untouched on the original version which was deployed. Mine was and is 220.127.116.11.
You can and should configure online update for the appliance itself to get the SLES updates. But this does not change the appliances version number, as far as i see...
5 days left ....
oh, wait, weekend...
3 days left ..
oh, implement and test ..
1 day left...
we need SMTP AUTH login tomorrow 2021-02-24