Article ID: 121531, created on May 10, 2014, last review on May 10, 2014

  • Applies to:
  • Business Automation 5.5

Symptoms

Bad command sequence error appears in AMAIL.log:

[14-03-07 11:17:21.094 Worker1.3   RQ00229 TRC] +++[0] Str<unnamed>::sendPlainMail(MailMessage&, Str&, STLRT::Log::Entry&)()
[14-03-07 11:17:21.094 Worker1.3   RQ00229 TRC] sendPlainMail for
[14-03-07 11:17:21.094 AMAIL2      RQ00229 TRC] AMAIL2: start mail sending
[14-03-07 11:17:21.109 AMAIL2      RQ00229 WRN] AMAIL2 FAILED (2):mailsmtp_data failed with code error 12:'Bad command sequence'

Cause

Some notification templates have empty "To address" specified

Resolution

Check pending messages in PBA-E > Home > System > Logs > Outgoing E-Mail Log, choose "Scheduled" from "Status" drop down

If some of these messages have empty "To address" check notification template based on which these messages were generated and correct "To address" in the template. Mark existing scheduled messages with empty "To address" and delete them as PBA-E will not be able to send them anyway.

Search Words

AMAIL log

notification

bad command sequence

To address

Scheduled

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF