Mailing List Message #94901
From: Uwe Baemayr <>
Subject: SPF and "mirror" question
Date: Fri, 25 Apr 2008 11:15:04 -0500
To: communiGate Pro Discussions <>
X-Mailer: Pegasus Mail for Windows (4.41)

A Communigate SPF question: I "mirror" my email from my account at work to my account at home, using an account-level forwarding rule with the "keep a copy" option.  Both are Communigate servers. 

This morning, I received two messages with "Received-SPF: fail".  One such message, from is below.  It looks to me like the Communigate server at home (v5.1.14) was performing SPF checking and used the address of the Communigate server at work (v5.0.8) that "mirrored" the message as the sending host, so SPF failed.

Names below obfuscated (don't want to see questions about my domains in Google), but the routing is: -> (mirror) ->

Is this expected behavior?  I would think that Communigate would check the original sender, not the relay.  Or could this problem be solved by having '' also check SPF -- would '' not check SPF if there was already an SPF record in the headers?  That would seem a little dangerous.

 Return-Path: <>
 Received: from [] (HELO
   by (CommuniGate Pro SMTP 5.1.14)
   with ESMTP id 6175572 for; Fri, 25 Apr 2008 03:58:36 -0700
 Received-SPF: fail; client-ip=;
 Received: from <>
   by (CommuniGate Pro RULES 5.0.8)
   with RULES id 2650887; Fri, 25 Apr 2008 05:10:26 -0500
 X-Autogenerated: Mirror
 Resent-From: <>
 Resent-Date: Fri, 25 Apr 2008 05:10:26 -0500
 Received: from [] (HELO
   by (CommuniGate Pro SMTP 5.0.8)
   with SMTP id 2650886 for; Fri, 25 Apr 2008 05:10:26 -0500
 Received: from ([]) by with
   Microsoft SMTPSVC(6.0.3790.1830);
   Fri, 25 Apr 2008 05:11:52 -0500


--- Uwe
Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster