X-Junk-Score: 0 [] X-Cloudmark-Score: 0 [] Return-Path: Received: from ems.ch ([212.74.146.1] verified) by mail.stalker.com (CommuniGate Pro SMTP 5.3.9) with ESMTP id 61626057 for CGatePro@mail.stalker.com; Tue, 31 Aug 2010 22:51:38 -0700 Received-SPF: none receiver=mail.stalker.com; client-ip=212.74.146.1; envelope-from=ugruetzner@ems.ch X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.9.4 (ClamAV engine v0.95.1) X-ExtScanner: Niversoft's Find_Attachments Received: from ems012.worldcom.ch (account ugruetzner [212.74.146.12] verified) by ems.ch (CommuniGate Pro SMTP 5.1.16) with ESMTPA id 3438902 for CGatePro@mail.stalker.com; Wed, 01 Sep 2010 07:51:03 +0200 Message-Id: <55BC3C05-B8CF-4D81-9A48-261D693408E6@ems.ch> From: Urs Gruetzner To: CommuniGate Pro Discussions In-Reply-To: Content-Type: multipart/alternative; boundary=Apple-Mail-30-70385393 Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: HELO failure Date: Wed, 1 Sep 2010 07:51:03 +0200 References: X-Mailer: Apple Mail (2.936) --Apple-Mail-30-70385393 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Buon giorno Thanks for your confirmation and your suggestion concerning the working domains. I let have changed the DNS entry as I described and now also the sbb.ch "mailing partner" is satisfied with the HELO. Ciao Urs Am 27.08.2010 um 13:01 schrieb CommuniGate Pro Discussions: > Von: Massimo Bolzoni > Datum: 26. August 2010 16:57:02 GMT+02:00 > Betreff: Re: HELO failure > > > Ciao, > > yes this is the right solution, it is easyer and make definitelly > sense.... at least for me :) > > Also, the suggestion I use to give is to use a main domain name that > is not going to host any account but postmaster, and use "working > domains" as additional ones. This allow much more flexibility in > operation. > > Actually there is no problem at all to use directly the MDN as > working domain, so no reason to change the setup, but generally > speaking for new set up this is the long term solution with less > problem... think about you company or institution define to change > the domain name .... > > Ciao > > Massimo > > Il giorno 26/ago/10, alle ore 07:40, Urs Gruetzner ha scritto: > >> (sorry wrong subject in previous mail) >> Thanks for explanations >> >> Instead to change the FQDN for the mail server to mail.ems.ch, >> could it be the easiest solution to change the DNS entry for >> 212.74.146.1 to ems.ch than mail.ems.ch instead? >> >> Also the MX entry should be ems.ch instead of mail.ems.ch ? >> >> >> >> Reason: the forward lookup for ems.ch points already to the correct >> IP, so there is no need that the reverese lookup is mail.ems.ch. >> Also when sending a mail from outside to xy@ems.ch the lookup of MX >> of ems.ch has the correct IP as result. There is no need to use >> mail.ems.ch. >> >> Thanks for further help --Apple-Mail-30-70385393 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
Buon = giorno

Thanks for your confirmation and your = suggestion concerning the working = domains.


I let have changed the = DNS entry as I described and now also the sbb.ch "mailing partner" is = satisfied with the HELO. =  

Ciao

Urs


Am 27.08.2010 um 13:01 schrieb CommuniGate Pro = Discussions:



Ciao,

yes this is the = right solution, it is easyer and make definitelly sense.... at least for = me :)

Also, the suggestion I use to give is to = use a main domain name that is not going to host any account but = postmaster, and use "working domains" as additional ones. This allow = much more flexibility in = operation.

Actually there is no = problem at all to use directly the MDN as working domain, so no reason = to change the setup, but generally speaking for new set up this is the = long term solution with less problem... think about you company or = institution define to change the domain name = .... 

Ciao


= --Apple-Mail-30-70385393--