Routine DSSendMail error

[cdp]

Our production sequence job starts failing a few days ago on the notify success activity, getting the following error:

Code: Select all

JobControl (DSSendMail): Error when executing command: C:\IBM\InformationServer\Server\Projects\sendmail_s_load_main_84225217_3112.bat
*** Output from command was: ***
SMTPMail Looking up server...
SMTPMail Opening connection to smtp.xxxx.com...
SMTPMail RCV: 220 ***************
SMTPMail RCV: 250 gatekeeper.xxxx.com
SMTPMail RCV: 250 Ok
SMTPMail RCV: 250 Ok
SMTPMail RCV: 250 Ok
SMTPMail RCV: 502 Error: command not implemented
SMTPMail RCV: 502 Error: command not implemented

Please check any paths in the following command file are correct, and if necessary adjust the 'dssendmail_template.txt' file in the project directory.

Contents of command file:
C:\IBM\InformationServer\Server\DSEngine\bin\dssmtpmail.exe -file sendmail_s_load_main_84225217_3112_file.tmp

Routine DSSendMail did not finish OK, return code = '-21'

The 'dssendmail_template.txt' file does exist under the project folder and the notification e-mails were sent without a problem for months now up to a few days ago.

I can't seem to find anything regarding this specific error and no mail exchange settings have been made which might affect the mail delivery.

Any ideas how I can resolve this?

[ray.wurlod]

This one looks like you got through (there are RECV messages), but something's changed at the receiver. Is their mailbox full? You probably need to switch on more verbose tracing in the email system to resolve this one.

[chulett]

You're certain nothing has changed? Sure seems like something must have. What about UNIX patches, changes to your SMTP software or anything of that ilk? Have you had a chat with your Admin?

According to the standards, that error is supposed to mean that the command it received was actually recognized but also recognized as not having been implemented:

4.2.4 Reply Code 502

Questions have been raised as to when reply code 502 (Command not
implemented) SHOULD be returned in preference to other codes. 502
SHOULD be used when the command is actually recognized by the SMTP
server, but not implemented. If the command is not recognized, code
500 SHOULD be returned. Extended SMTP systems MUST NOT list
capabilities in response to EHLO for which they will return 502 (or
500) replies.

Not sure how something like that would have changed on its own.