Jump to content


Photo

SPF Fail - Bug BNESS-6849

ESS BUG

  • Please log in to reply
2 replies to this topic

#1 Jason Waldhelm

Jason Waldhelm
  • Members
  • 2 posts

Posted 27 March 2017 - 11:18 AM

Hi,

 

I opened a case #2457759 that resulted in bug BNESS-6849 - this was found to be a problem in the SPF header parsing between our on premise Email Security Gateway 600, and our Essentials package for 365 (ESS).  I was directed to this forum by the tech support group as they were unable to give me any insight into what the development group's progress on the above bug is.

 

Here is a sampling of the headers:

Final-Recipient: rfc822; jason@yeah.com
Original-Recipient: rfc822;jason@yeah.com
Action: failed
Status: 5.0.0
Remote-MTA: dns; d119377a.ess.barracudanetworks.com
Diagnostic-Code: smtp; 550 permanent failure for one or more recipients
(jason@yeah.com:blocked)

 
It seems it failed the SPF check because the ESS system parses the headers incorrectly (reading the address as localhost) as follows:
 
Received: from [127.0.0.1] (helo=mail.yeah.com)
    by mail.yeah.com with esmtpsa (TLS1.0:ECDHE_RSA_AES_256_CBC_SHA1:256)
    (Exim 4.87)
    (envelope-from <m03@key.com>)
    id 1crksb-0007SD-Iv
    for jason@yeah.com; Sat, 25 Mar 2017 07:33:13 -0500
 
All of this should be notated in the bug BNESS-6849.  I'm curious if anyone can give me some followup.
 
I appreciate any feedback you can give me.
 
Jason


#2 Michelle Exner

Michelle Exner

    BSF / BESS Moderator

  • Moderators
  • 409 posts

Posted 27 March 2017 - 12:53 PM

Jason,

This really isn't the place to get updates on a bug. The support person you were talking with should have given you a correct update.

We have no way to resolve this bug in real time due to the fact that we don't make major changes to the Email Security Service without fully testing the revisions.

We release new builds of the ESS firmware approximately every three months and are about 2 1/2 months away from the next release.

Engineering is aware of the bug and will be working on it for the next release.

Thank you,


Michelle Exner
Product Lead Support Engineer
Barracuda Email Security
(408) 342-5300


#3 Jason Waldhelm

Jason Waldhelm
  • Members
  • 2 posts

Posted 04 April 2017 - 01:40 PM

Sorry to have bothered - the tech told me this would be the best place for followup as he had no visibility into the development queue.