You are not logged in.
Pages: 1
250 email-smtp.amazonaws.com
250-email-smtp.amazonaws.com
250-8BITMIME
250-SIZE 10485760
250-STARTTLS
250-AUTH PLAIN LOGIN
250 Ok
334 VXNlcm5hbWU6
334 UGFzc3dvcmQ6
535 Authentication Credentials Invalid
530 Authentication required
503 Error: need MAIL command
503 Error: need MAIL command
500 Error: command not implemented
500 Error: command not implemented
500 Error: command not implemented
500 Error: command not implemented
500 Error: command not implemented
500 Error: command not implemented
500 Error: bad syntax
501 Input line length is too long!
I'm testing w/ SES for sending mail alerts. I get the feeling the key generated by AWS is too long for the field.
I have tried multiple SES users and keys - all will fail when I know i have all the proper flags:
[root@mblesx01:/vmfs/volumes/e411d104-0adf4aab/xsi-dir] "/vmfs/volumes/e411d104-0adf4aab/xsi-dir/xsibackup" --backup-prog=onediff --options=no-500M-check --backup-point="/vmfs/volumes/backup/VMs/xsi" --b
ackup-type=custom --backup-vms="unifi" --mail-from=noc@xxx.com --mail-to=noc@xxx.com --smtp-srv=email-smtp.us-east-1.amazonaws.com --smtp-port=587 --smtp-usr=A-----------------B
4KA --smtp-pwd=z----------------------------------------------u --smtp-sec=TLS --test-mode=true
Please assist
Thank You
Offline
BTW - this is for 'Pro' registered user info@mbl-arch.com
Offline
When you say key, I guess you mean the password, right?
There is no limit in the length of the fields, they aren't cut down. Nevertheless you could run into this issue if:
- Your password is not double quoted
- Your password contains special characters that need to be escaped, even although it's double quoted
Offline
Hmm, thought I tried all that ...but will try again and report back.
So there's nothing to this message: "501 Input line length is too long!" from the error output?
Offline
That's way below the error:
[b]535 Authentication Credentials Invalid[/b]
It makes no sense to try to interpret a derived error message before actually fixing the primary one.
Last edited by roberto (2017-11-21 14:59:55)
Offline
@roberto - I hear what you are saying, but when I test thru an online relay tester ([url]https://smtper.net[/url]) with the same credentials and settings it works fine.
I ran the test 2 times just now from CLI - double quoting the password and verifying the one special character in the password is escaped \
still fails
Offline
[b]smtp.amazonaws.com[/b] needs to have the PIPELINING extension enabled, by what I see in the SMTP conversation, it probably doesn't. Fortunately you can use any other SMTP server that does, including: gmail.com, hotmail.com, yahoo.com, etc...
Offline
Implemented a free GMAIL account for a noreply relay - works fine.
Thanks for the assistance
Offline
Please, note this thread corresponds to an old software edition - (c)XSIBackup Classic - which has been deprecated. Use our latest software edition: [b](c)XSIBackup-DC[/b] and refer to [url=https://33hops.com/xsibackup-dc-full-manual-home.html]its manual[/url] to [url=https://33hops.com/xsibackup-vmware-esxi-backup.html#prodchart]backup your (c)ESXi VMs[/url] as of 2021
Offline
Pages: 1