error poping up within commit

[sudogreg]

11/19/2010 9:33:10 AM

Error Code: 421

421 4.7.0 Temporary System Problem. Try again later (). 8sm1634541iba.10

Outgoing email queue folder:

X:\CommitCRM\Server\QSysEDOutbox\


Failed while trying to process the outgoing email file:

QItemOutbox101119093205955_DYBFPU.cmt

From: CommitCRM Alerts <commit@******.com>
To: andy@*****.com,
CC:
BCC:

========================================
< 250 2.1.0 OK 8sm1634541iba.10
> RCPT TO:<andy@*******.com>
< 250 2.1.5 OK 8sm1634541iba.10
> DATA
< 354 Go ahead 8sm1634541iba.10
> Reply-To: help@********.com
> From: CommitCRM Alerts <commit@********.com>
> To: andy@*******.com,
> Subject: [info] [customer] CommitCRM Ticket - New [0500-2690, New, G. *****on, DSFC]
> Sender: CommitCRM Alerts <commit@*******.com>
> Mime-Version: 1.0
> Content-Type: text/plain; charset=""
Content-Transfer-Encoding: quoted-printable
> Date: Fri, 19 Nov 2010 09:32:08 -0600
> Message-ID: <20101119153208205.255D462C6C2B782E@WASHPCSVR>
> X-Mailer: ICS SMTP Component V2.50
>
> [info] [customer] CommitCRM Ticket - New [0500-2690, New, G. Johnston, DSF=
> C]=0D=0A=0D=0APerformed by: dsfc1=0D=0A=0D=0A=0D=0A=0D=0ARecord Details at=
> time of sending this message:=0D=0A=0D=0AAccount: DSFC=0D=0AContact: Kris=
> Evans=0D=0AManager: G. Johnston=0D=0ATicket Type: General=0D=0ATicket: 05=
> 00-2690=0D=0A=0D=0ADescription: =0D=0AI need a black cartridge for a Samsu=
> ng CLP 315w machine.=0D=0AThe replacement cartridge number is: CLT =96=
========================================


Solution:
------------
Verify that the mail server allows the CommitServer Windows Service to send emails.

Verify that all email addresses are valid.

Make sure that your mail server is configured to allow message relaying. Relaying support is required only when the option to select the original message 'As-Is' option is selected (i.e. it is not required when the system is configured to forward emails as attachments).

Once you handled the above issue, restart CommitServer service so another Send attempt will occur.
If, after restarting the service, the email is still not being sent and you see the same error again, it is possible that the email message file in queue cannot be sent due to incorrect previous settings.
Try skipping this email message by moving the email message file listed above to a backup folder and restarting CommitServer service.
This will let the CommitCRM Server try to process and send the next email message waiting in queue.


For more information visit CommitCRM online support resources at Support

Date Ref # 101119

[Support Team]

Re: error poping up within RangerMSP

sudogreg,

This error code (421) is the one received from your mail server.

I Googled this mail server error code and here's some explanations I found about it, you may search and find some additional information.

I hope this will help you find the problem.

Thanks,
Doron


Here's what I found (other reasons may still exist):

---
SMTP Error 421 : The Mail transfer service is
unavailable because of a transient event. SMTP reply
421 can be caused by many things but generally indicates
that the mail server which returns this status code is
currently unavailable but may be available later.

For example, the server administrator may have stopped
the mail service to troubleshoot a problem, or the mail
server is right in the middle of rebooting, or the mail server
is currently processing too many incoming messages or
incoming requests, etc.... Note : “Mail Server” in this
case can be any of the mail servers on the message’s
route – the sending server (your server), the ISP SMTP
server, or the recipient’s mail server.

Clearly, if you repeatedly receive an SMTP status 421 then
the problem is no longer of a transient nature and you
need to investigate or inform the relevant network
administrator, ISP tech support, or the recipient.
---
SMTP Response 421 can also be received as a result of
your message server sending an email where the total
number of TO, CC, and BCC users results in a
number of simultaneous SMTP connections that is in
excess of the number of connections your ISP or
SMTP service allows. A typical error message for this
situation would be : “421 Too many concurrent SMTP
connections from this IP address; please try again later”.
Typically, when this happens your server will have sent
some of the messages (note that for all servers, each
email sent by a user always gets broken down into
individual separate emails to each of the recipients in the
TO, CC, and BC fields), and will automatically retry a little
later to send the remaining messages.