X-Junk-Score: 0 [] X-Cloudmark-Score: 0 [] Return-Path: Received: from mail-fx0-f215.google.com ([209.85.220.215] verified) by mail.stalker.com (CommuniGate Pro SMTP 5.2.14) with ESMTP id 54178967 for CGatePro@mail.stalker.com; Wed, 24 Jun 2009 12:33:09 -0700 Received-SPF: pass receiver=mail.stalker.com; client-ip=209.85.220.215; envelope-from=ssjakie@gmail.com Received: by fxm11 with SMTP id 11so938525fxm.45 for ; Wed, 24 Jun 2009 12:32:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=mYC1Vl7kdhgUBErRiHcyjQhAXjPw80d6GfezAYDcyM8=; b=fBqIwVCHmy5mvib0K3Cy1ROBYMnBo6ZXMveH0Zvq/166Pm1bljrmc3+mjAdgZL1HEb M/fNf7iiRPuhP3WQKs5IUeNj+RDaB+xR0QkoNEVRqiXug+7jEahuVQ1Y+xBDaw0G1P2C S6NkSWh9N6U7dzQQxexmCkNKE1R0Psooe3CHc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=cHZmioW/Kw1XcyNxOGvNmvsi0PDeufQPwnJcueTytx+2znOZyV4HzHm3/1ucrALiQz Rw9O1XE8sv8js7S+sU3sH/zENjFhUoczJ4tnBimpx1vTt0TtvDzYiNsN/pD0AeBSeH6r x7hzARYT7U76/MBep15YDgMlo+De6/5tefbs4= MIME-Version: 1.0 Received: by 10.103.214.13 with SMTP id r13mr1002101muq.37.1245871957496; Wed, 24 Jun 2009 12:32:37 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Jun 2009 21:32:37 +0200 Message-ID: Subject: Re: Bad SMTP prompt at the host, smtp closing connection during sending From: sjakie To: CommuniGate Pro Discussions Content-Type: multipart/alternative; boundary=001636a7d91276529c046d1d2b84 --001636a7d91276529c046d1d2b84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all interested, Nicholas, I'm very grateful. Your tip fixed it. Here is in detail what can be done on Cisco ASA's: This applies to Cisco ASA 5505, 5510 and 5520: If you have access to ASDM then: Configuration --> Security Policy --> Service Policy Rules --> Select General/Global Policy Inspection --> Click Edit ---> Choose Rule Actions tab --> Uncheck ESMTP Click OK --> Apply --> File --> Save If you have a standby firewall unit: Click also File --> Save running configuration to Standby Unit If you do not have ASDM, the CLI command is: no fixup protocol smtp 25 All the best, and thanks again. Sjaak On Wed, Jun 24, 2009 at 7:19 PM, Nicolas Hatier < nicolas.hatier@niversoft.com> wrote: > mx1.xs4all.nl looks ok for us. > > You probably have a PIX firewall (or other Cisco firewall) with the "SMTP > fixup" option enabled. You should disable this as it interferes with CGP, > inbound and outbound. > > NH > > --001636a7d91276529c046d1d2b84 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hi all interested,

Nicholas, I'm very grateful. Your tip fixed it.

Here is in detail what can be done on Cisco ASA's:

This applies to Cisco ASA 5505, 5510 and 5520:

If you have access to ASDM then:

Configuration --> Security Policy --> Service Policy Rules -->= =A0 Select General/Global Policy Inspection --> Click Edit ---> Choos= e Rule Actions tab --> Uncheck ESMTP

Click OK --> Apply --> File --> Save

If you have a standby firewall unit:
Click also File --> Save runn= ing configuration to Standby Unit

If you do not have ASDM, the CLI command is:
no fixup protocol smtp 2= 5

All the best, and thanks again.
Sjaak

On Wed, Jun 24, 2009 at 7:19 PM, Nicolas Hatier = <nicol= as.hatier@niversoft.com> wrote:
mx1.xs4all.nl looks ok for us.

You probably = have a PIX firewall (or other Cisco firewall) with the "SMTP fixup&quo= t; option enabled. You should disable this as it interferes with CGP, inbou= nd and outbound.

NH

--001636a7d91276529c046d1d2b84--