If you are a current client of MxToolBox and are utilizing our Spam and Virus Protection with Emergency Mail with Tag and Deliver (TAD) class of service, this means that we will not Quarantine SPAM messages for you, but will allow that mail to come through. With this option we are modifying the email header with a Spam Flag, that way you can move all of these messages to a specified folder using the rule below.
To move SPAM tagged mail (TAD) to a specified folder:
- Click on Tools -> Rules and Alerts
- Click on New Rule..
- Start from a blank rule, Check messages when they arrive, Next
- Check “with specific words in the senders address”, then click on “specific words” in the bottom window
- Put this entry: Header Named: X-Spam-Flag value = “suspect” and Click Add6) Click OK7) Click Next8) Check “move it to the specified folder”, click on “specified” in the bottom window
- Next and Next again
- Type a name for your rule, we recommend “Tagged SPAM”
Typically our Spam and Virus Protection with Emergency Mail is a Tag and Quarantine service which means that we Quarantine any suspect spam and place it in your Emergency Mailbox. Customers have the ability to select Tag and Deliver so that the Junk Mail goes directly to their local Email Client and then this rule moves the mail to a designated folder.
Bounce backs and error codes for email can be very mysterious and misleading. To help with that we have started a new series on the blog dedicated to demystifying these mysteries. To read all of the blogs in this series, go here.
We see this type of error pretty often here at MxToolbox and so we wanted to post about it here. Customers Exchange servers can mistakenly react to normal mail flow and cause a disruption in service. The error that is posed is ‘4.3.1 Insufficient system resources’.
A feature called Back Pressure in Exchange 2007 can sometimes cause this error to be received when we try to deliver messages to the customer server. When Back Pressure detects overused resources the Exchange Server controls system resources to prevent them from being overwhelmed and it allows the delivery process for current messages to be worked out. All these processes are part of the Back Pressure feature which is responsible for monitoring certain Exchange Server 2007 resources.
The drive on which the Queue DB and logs are stored must have 4GB or more free space otherwise the server will apply back pressure and start slowing the flow of messages! The main database file is called mail.que and by default can be found here:
C:Program FilesMicrosoftExchange ServerTransportRolesdataQueue
Other helpful articles:
Bounce backs and error codes for email can be very mysterious and misleading. To help with that we have started a new series on the blog dedicated to demystifying these occurrences. To read all of the blogs in this series, go here.
To kick off our series on demystifying and understanding email bounce backs and errors, we thought it would benefit everyone to go over how to read a bounce back. Some bounce backs are very cryptic and full of codes and numbers. How are you supposed to figure it out? Let’s break down a typical bounce back:
- The top part of this message is the actual bounce back. This is the “meat” of what you need to identify. Sometimes bounces include lots of numbers and codes; ignore all that and find the string that references the 400 or 500 number. (What’s the difference between a 400 and a 500 error?). In this case the error is ‘550 No such user’. Since this account doesn’t exist at mxtoolbox.com the message was bounced by the recipient server.
- The second half of the bounce is the email headers. Keep in mind that not all bounce backs include this information, however, most do. This information is really helpful as it contains the Sender, Recipient, Date, Time and Subject, as well as server hops. If you are unable to figure out the issue, make sure you send the complete bounce back including the email headers to your IT administrator. All of this information is critical in understanding a bounce back. If you need help reading headers, try our free tool, the Header Analyzer. It makes the email header a bit easier to read.
As with all things Exchange, they have their own way of doing things. Exchange bounces include a top header section; however, we tend to ignore that section as it has very little helpful information. Remember to focus on the “Technical details” or the “Diagnostic Information for administrators;” as this is the “meat” of the data you need to analyze. You may also notice that Exchange bounces include two conflicting “who rejected your message” statements. The second one labeled “Generating Server” is generally the server that issued the bounce.
Remember that knowledge is power! We at MxToolBox are constantly educating ourselves about all the different bounce backs that exist. Also keep in mind that with some Vendors and ISPs you have the ability to create custom bounce back errors…so you always have to be on your toes!
If this is a bit overwhelming or you don’t want to mess with understanding bounce backs or error codes, don’t worry. It can take years of experience to feel comfortable reading and deciphering this information. We understand that you just want your email to work! Implementing one of our Managed Business Email Products such as Spam and Virus Filtering or Hosted Email can help alleviate these issues and put someone in your back pocket to help understand when these problems occur.