X-Junk-Score: 0 [] X-Cloudmark-Score: 0 [] Return-Path: Received: from mail.virtuelle.no ([83.137.200.195] verified) by mail.stalker.com (CommuniGate Pro SMTP 5.2.14) with ESMTP id 54230120 for CGatePro@mail.stalker.com; Fri, 26 Jun 2009 09:23:51 -0700 Received-SPF: pass receiver=mail.stalker.com; client-ip=83.137.200.195; envelope-from=nicolas.hatier@niversoft.com X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.72 (ClamAV engine v0.91.2) Received: from [66.110.158.160] (account nicolas.hatier HELO niversoft.com) by mail.virtuelle.no (CommuniGate Pro SMTP 5.0.13) with ESMTPSA id 7120382 for CGatePro@mail.stalker.com; Fri, 26 Jun 2009 18:23:17 +0200 X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.9.3 (ClamAV engine v0.95.1) X-ExtFilter: Niversoft's DomainKeys Helper DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; d=niversoft.com; s=default; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type; b=K87oNf30amhTI2YmorhGIMqLTCqJHBx2bZIzCnzK7Uf3oNjJw+TOTn1k9Syc9Rqca+ hxRT9WtPVJCqk/RzQ6pgP2ox9KeUhP9oSy3TEwfPFeMGRI0mEFxhOT/S7FI0eqKyrWyf J+NT0HvBFG9wAymY+jOBAMgd8Sqy+uYk40u/o= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niversoft.com; s=default; l=3560; t=1246033395; x=1246638195; q=dns/txt; h=Message-ID:Date:From:User-Agent:MIME-Version:To: Subject:References:In-Reply-To:Content-Type; bh=NVfKQ+gDiE2G1sJn n8g9kYQ40Pnl/1Z2+fv6ByATJFc=; b=woH+0Xtdnv5jrDmgqY/XiJos8aC2eJ7G nwy+JCscNbTKnAdvUrLOUfdeTu24g5ZEtJ5LJj6llpKCPqfCY2+BnWXYyIrGCLAR 481jGo7aKLYupYsCW9TVOO253LYxv8fX4zlaTzreEuEiq9sfaXDAaL48A0lHjtU6 jGf7NnHv9ss= Received: from dummy.name; Fri, 26 Jun 2009 12:23:14 -0400 Message-ID: <4A44F5F2.3060706@niversoft.com> Date: Fri, 26 Jun 2009 12:23:14 -0400 From: Nicolas Hatier User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090302 Lightning/0.9 Thunderbird/2.0.0.21 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: CommuniGate Pro Discussions Subject: Re: Sending FROM accounts in domain even with authentication enabled References:

In-Reply-To: Content-Type: multipart/alternative; boundary="------------010008020807000501000907" This is a multi-part message in MIME format. --------------010008020807000501000907 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Lyle Giese wrote: > That is the difference between the envelope from and the from on the=20 > email. > > I usually explain it by comparing it to a letter you send in the US=20 > Mail. What is logged in the mail server logs and in a mail filter is=20 > the envelope From & To. This would be comparable to what is printed=20 > on the outside of the envelope. > > But the letter inside can have an entirely different From & To and=20 > that is what the mail server would use to route and deliver the email. Wrong, sorry. The mail server does not use the From & To written in the=20 message to route and deliver the message, unless you use specific rules=20 to do so. The mail server uses the envelope information (MAIL FROM, RCPT = TO). > > The US Mail can only go by the envelope From & To. And what you are=20 > doing can only apply to the envelope From & To as the action is=20 > triggered before the body of the email with it's From & To are sent to = > the mail server. > > Lyle Giese > LCR Computer Services, Inc. > > David Modoski wrote: --=20 *Nicolas Hatier* > Niversoft id=E9es logicielles - http://www.niversoft.com --------------010008020807000501000907 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

Lyle Giese wrote:

That is the difference between the envelope from and the from on the email.

I usually explain it by comparing it to a letter you send in the US Mail. What is logged in the mail server logs and in a mail filter is the envelope From & To. This would be comparable to what is printed on the outside of the envelope.

But the letter inside can have an entirely different From & To and that is what the mail server would use to route and deliver the email.

Wrong, sorry. The mail server does not use the From & To written in the message to route and deliver the message, unless you use specific rules to do so. The mail server uses the envelope information (MAIL FROM, RCPT TO).

The US Mail can only go by the envelope From & To. And what you are doing can only apply to the envelope From & To as the action is triggered before the body of the email with it's From & To are sent to the mail server.

Lyle Giese
LCR Computer Services, Inc.

David Modoski wrote:

Nicolas Hatier <nicolas.hatier@niversoft.com>
Niversoft idées logicielles - http://www.niversoft.com

--------------010008020807000501000907--