Jump to content


Photo

Clients being rejected

Rejected emails

Best Answer mheller, 10 February 2016 - 12:07 PM

Hi Julian,

 

We are blocking this correctly for SPF violations from the fishersauls.com domain.

 

Received-SPF: fail (mx1416.ess.rzc.cudaops.com: domain of btv1==8488fd41e8b==DCarroll@fishersauls.com does not designate 72.77.183.2 as permitted sender)
X-ASG-Debug-ID: 1455114365-03a00f23567f3b0001-RMEPcn

 

Performing a SPF lookup on the domain fishersauls.com confirms the 72.77.183.2 entry isn't in there

 

matty@dethrone:~$ dig txt fishersauls.com +short
"v=spf1 mx mx:mail.fishersauls.com mx:mail1.fishersauls.com -all"
 
mail.fishersauls.com. 7200 IN A 24.227.47.2
mail1.fishersauls.com. 7184 IN A 24.227.47.3
 
Go to the full post


  • Please log in to reply
13 replies to this topic

#1 Julian Keller

Julian Keller
  • Members
  • 6 posts

Posted 10 February 2016 - 10:32 AM

So I have 3 clients all using Barracuda Spam Firewalls.  This started 2 days ago with one client and now as of yesterday the other 2 started.

 

At first I thought it was an AOL issue and put in a ticket for them as it was only happening with AOL email addresses. Now it is more than that.

 

I was able to send emails from my gmail account to the email addresses just fine and the recipients responded so i know the emails are good.  It happens with EVERY AOL address adn starting to happen with recipient with a barracuda now.

 

They are able to email me fine and other people just fine.

 

Below you will see a snip of the errors.  

 

 

The following organization rejected your message: d73012a.ess.barracudanetworks.com

 

And

 

There's a problem with the recipient's mailbox. Please try resending this message. If the problem continues, please contact your helpdesk.

The following organization rejected your message: mailin-01.mx.aol.com.

mailin-01.mx.aol.com #<mailin-01.mx.aol.com #5.2.1 smtp; 521 5.2.1 : AOL will not accept delivery of this message.> #SMTP#



#2 John

John
  • Members
  • 131 posts
  • LocationChicago

Posted 10 February 2016 - 10:38 AM

Check to see if you are on a rbl.

http://mxtoolbox.com/blacklists.aspx

I recently was added to Barracuda Networks rbl list for sending email to a domain we always send too...



#3 Barry van Hattum

Barry van Hattum
  • Members
  • 22 posts

Posted 10 February 2016 - 10:40 AM

Hi Julian,

 

The message is clear. The other side (AOL) is rejecting the message. This does not mean that the problem is based on their side, however it could be a combination of the settings on the AOL domain and the settings on the Barracuda. You would have to ask them for more details about the reason for the rejection.

 

- Is email encryption being used? Maybe it has something to do with ciphers in the certificate?

- Maybe you are on a blacklist.

 

Hope this helps.



#4 mheller

mheller

    Nobody

  • Moderators
  • 1,299 posts
  • LocationSan Jose, CA

Posted 10 February 2016 - 11:29 AM

Hi Julian,

 

To add on to everyone elses point, we'd need to see a sample message, including the message_id and sending domain for us to review if desired



Matthew Willson-Heller
Support Escalation Manager, US

Barracuda Networks Inc.
Phone: +1 408.342.5300 x5346
Fax: +1 408.342.1061
Web: www.barracudanetworks.com



#5 Julian Keller

Julian Keller
  • Members
  • 6 posts

Posted 10 February 2016 - 11:35 AM

I checked the blacklists for all 3 clients and they are all clear. The cert are good.  I just received a response from AOL saying they added one of them to the Protected list and when i did the test it worked. I had the others try and they are still being bounced as of right now but have not been added yet.

 

Still on one client they are getting bounces from other receivers that they were sending to just yesterday morning and now they cannot. The mail is going out but being bounce by a Barracuda and by AOL. The AOL I am sure can be fixed by adding to the protected IP's even though they are not on a blacklist of any sort.

 

Still has me puzzled.



#6 Julian Keller

Julian Keller
  • Members
  • 6 posts

Posted 10 February 2016 - 11:35 AM

Hi Julian,

 

To add on to everyone elses point, we'd need to see a sample message, including the message_id and sending domain for us to review if desired

Let me get that real quick to a non-AOL address



#7 John

John
  • Members
  • 131 posts
  • LocationChicago

Posted 10 February 2016 - 11:37 AM

I remember this happening to me. I think I had to request to be white listed by AOL.

https://postmaster.aol.com/sa-ticket


#8 Julian Keller

Julian Keller
  • Members
  • 6 posts

Posted 10 February 2016 - 11:49 AM


Subject: Undeliverable: Steel Gate - closing, title fees

Delivery has failed to these recipients or groups:

tonya@achievetitle.com<mailto:tonya@achievetitle.com>
A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.

The following organization rejected your message: d73012a.ess.barracudanetworks.com.

Diagnostic information for administrators:

Generating server: mail1.fishersauls.com

tonya@achievetitle.com<mailto:tonya@achievetitle.com>
d73012a.ess.barracudanetworks.com #<d73012a.ess.barracudanetworks.com #5.0.0 smtp; 550 permanent failure for one or more recipients (tonya@achievetitle.com:quarantined<mailto:tonya@achievetitle.com:quarantined>)> #SMTP#

Original message headers:

Return-Path: <XXXXUSERXXXXX>>

X-ASG-Debug-ID: 1455114678-03a00f23567f500001-RMEPcn

Received: from FSEX.FSDOM.PVT (fsex.fsdom.pvt [10.10.200.222]) by mail1.fishersauls.com with ESMTP id kFqa5KsLtfyUWGF6 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO) for <tonya@achievetitle.com<mailto:tonya@achievetitle.com>>; Wed, 10 Feb 2016 09:31:18 -0500 (EST)

X-Barracuda-Envelope-From: XXXXUSERXXXXX

Received: from FSEX.FSDOM.PVT ([fe80::7047:9381:165b:7b3d]) by FSEX.FSDOM.PVT

([fe80::7047:9381:165b:7b3d%11]) with mapi id 14.01.0218.012; Wed, 10 Feb

2016 09:27:47 -0500

From: "XXXXUSERXXXXX>>

To: 'Tonya Sewell' <tonya@achievetitle.com<mailto:tonya@achievetitle.com>>

Subject: FW: Steel Gate - closing, title fees

Thread-Topic: Steel Gate - closing, title fees

X-ASG-Orig-Subj: FW: Steel Gate - closing, title fees

Thread-Index: AdFkDnsTSNyCqtFeSsyl9IgYvRTnSwAAI7Mg

Date: Wed, 10 Feb 2016 14:27:46 +0000

Message-ID: <FD531A1E6C438A4585771CEB4BFE83633541D742@FSEX.FSDOM.PVT<mailto:FD531A1E6C438A4585771CEB4BFE83633541D742@FSEX.FSDOM.PVT>>

References: <FD531A1E6C438A4585771CEB4BFE83633541D71A@FSEX.FSDOM.PVT<mailto:FD531A1E6C438A4585771CEB4BFE83633541D71A@FSEX.FSDOM.PVT>>

In-Reply-To: <FD531A1E6C438A4585771CEB4BFE83633541D71A@FSEX.FSDOM.PVT<mailto:FD531A1E6C438A4585771CEB4BFE83633541D71A@FSEX.FSDOM.PVT>>

Accept-Language: en-US

Content-Language: en-US

X-MS-Has-Attach: yes

X-MS-TNEF-Correlator:

x-originating-ip: [10.10.200.113]

Content-Type: text/plain

MIME-Version: 1.0

X-Barracuda-Connect: fsex.fsdom.pvt[10.10.200.222]

X-Barracuda-Start-Time: 1455114678

X-Barracuda-Encrypted: AES128-SHA

X-Barracuda-URL: https://10.10.200.214:443/cgi-mod/mark.cgi

X-Barracuda-Scan-Msg-Size: 42708

X-Virus-Scanned: by bsmtpd at fishersauls.com

X-Barracuda-BRTS-Status: 1

X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210

X-Barracuda-Spam-Score: -2.02

X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests=EXTRA_MPART_TYPE, HTML_MESSAGE

X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.26917

Rule breakdown below

pts rule name description

---- ---------------------- --------------------------------------------------

0.00 EXTRA_MPART_TYPE Header has extraneous Content-type:...type= entry

0.00 HTML_MESSAGE BODY: HTML included in message

There ya go.  I rechecked the BRBL and the MX toolbox BL and they are all clean still. I bolded and italicized something that was interesting but not sure if it has any meat on the matter.

 

***EDIT** I thought it would but here is what I saw and was trying to point out:  tonya@achievetitle.com:quarantined<mailto:tonya@achievetitle.com:quarantined



#9 Julian Keller

Julian Keller
  • Members
  • 6 posts

Posted 10 February 2016 - 11:50 AM

 

I remember this happening to me. I think I had to request to be white listed by AOL.

https://postmaster.aol.com/sa-ticket

Yes i did that with one and it worked so it looks like yesterday and is working today but they were only having issues with AOL. The Other is having issues with different domains.

 

I just want to say thank you to everyone that is trying to help.



#10 mheller

mheller

    Nobody

  • Moderators
  • 1,299 posts
  • LocationSan Jose, CA

Posted 10 February 2016 - 12:07 PM   Best Answer

Hi Julian,

 

We are blocking this correctly for SPF violations from the fishersauls.com domain.

 

Received-SPF: fail (mx1416.ess.rzc.cudaops.com: domain of btv1==8488fd41e8b==DCarroll@fishersauls.com does not designate 72.77.183.2 as permitted sender)
X-ASG-Debug-ID: 1455114365-03a00f23567f3b0001-RMEPcn

 

Performing a SPF lookup on the domain fishersauls.com confirms the 72.77.183.2 entry isn't in there

 

matty@dethrone:~$ dig txt fishersauls.com +short
"v=spf1 mx mx:mail.fishersauls.com mx:mail1.fishersauls.com -all"
 
mail.fishersauls.com. 7200 IN A 24.227.47.2
mail1.fishersauls.com. 7184 IN A 24.227.47.3
 


Matthew Willson-Heller
Support Escalation Manager, US

Barracuda Networks Inc.
Phone: +1 408.342.5300 x5346
Fax: +1 408.342.1061
Web: www.barracudanetworks.com



#11 Julian Keller

Julian Keller
  • Members
  • 6 posts

Posted 10 February 2016 - 12:15 PM

 

Hi Julian,

 

We are blocking this correctly for SPF violations from the fishersauls.com domain.

 

Received-SPF: fail (mx1416.ess.rzc.cudaops.com: domain of btv1==8488fd41e8b==DCarroll@fishersauls.com does not designate 72.77.183.2 as permitted sender)
X-ASG-Debug-ID: 1455114365-03a00f23567f3b0001-RMEPcn

 

Performing a SPF lookup on the domain fishersauls.com confirms the 72.77.183.2 entry isn't in there

 

matty@dethrone:~$ dig txt fishersauls.com +short
"v=spf1 mx mx:mail.fishersauls.com mx:mail1.fishersauls.com -all"
 
mail.fishersauls.com. 7200 IN A 24.227.47.2
mail1.fishersauls.com. 7184 IN A 24.227.47.3
 

 

Strange as they were able to send up until yesterday.  I will take a look at that. As of right now the AOL Issue seems to be resolved with all 3. Just the other issue with this client sending out. to certain people.  

 

Thank you.



#12 mheller

mheller

    Nobody

  • Moderators
  • 1,299 posts
  • LocationSan Jose, CA

Posted 10 February 2016 - 12:18 PM

Our pleasure,

 

If you get any further blocks, kindly send us the message headers and we will help review!



Matthew Willson-Heller
Support Escalation Manager, US

Barracuda Networks Inc.
Phone: +1 408.342.5300 x5346
Fax: +1 408.342.1061
Web: www.barracudanetworks.com



#13 Chris Roberts

Chris Roberts
  • Members
  • 4 posts

Posted 02 February 2017 - 11:11 PM

We have experienced the rejection of Out Of Office bounces due to the BTV1 prefix being added to the outgoing emails.  Only have minimal evidence from the log, however it appears that if the original recipient is on a white-list, the BTV1 prefix is not stripped off the bounce email before it is forwarded to our Exchange server which rejects it.  



#14 Shawn Wyatt

Shawn Wyatt
  • Members
  • 4 posts

Posted 09 July 2019 - 07:20 AM

I am having the same error with the below. Can you tell me why we are being blocked?

 

Reporting-MTA: dns; mail.akt3.com
X-Postfix-Queue-ID: 068032149D3
X-Postfix-Sender: rfc822; cbates@akt3.com
Arrival-Date: Sun,  7 Jul 2019 10:35:43 -0400 (EDT)

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