Monitored Item - File System

POP Account Field Descriptions

Folder Path: This is the path to an existing folder you want BounceStudio Enterprise to monitor. To select a folder, click the "..." button next to the text box. BE VERY CAREFUL when selecting a folder, because BounceStudio Enterprise will delete files from the folder you select once it is done processing each file.

File Type: Currently, BounceStudio Enterprise parses text based message files that are RFC 822 compliant. For an example of what an RFC 822 compliant text based message file looks like, click HERE, or see below. Watch for new file formats in the future (i.e. PowerMTA log files).

Return-Path: <>
Received: from ([])
          by (Post.Office MTA v3.5.3 release 223
          ID# 0-65382U1000L100S0V35) with SMTP id net
          for ; Mon, 21 Aug 2000 14:07:48 -0700
Received: (qmail 849 invoked for bounce); 21 Aug 2000 21:08:21 -0000
Date: 21 Aug 2000 21:08:21 -0000
Subject: failure notice

Hi. This is the mail transport agent at
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. If you have questions about this
notice, please forward it to along with your comments.

Sorry, this account has been deactivated. (#5.2.1)

--- Below this line is a copy of the message.

Received: (qmail 841 invoked from network); 21 Aug 2000 21:08:21 -0000
Received: from (HELO (
  by with SMTP; 21 Aug 2000 21:08:21 -0000
Received: from detcmail02 ([]) by with Microsoft SMTPSVC(5.0.2172.1);
	 Mon, 21 Aug 2000 14:08:20 -0700
From: "JOE.NET" 
Reply-To: "JOE.NET" 
Date: Mon, 21 Aug 00 14:08:20 -0700
Subject: JOE.NET NEWS!
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_Send_NextPart_180_03281976"
X-OriginalArrivalTime: 21 Aug 2000 21:08:20.0944 (UTC) FILETIME=[EF5F8500:01C00BB3]

This is a multi-part message in MIME format.

Content-Type: text/plain; charset=us-ascii

Here's my test message.  This is the body of the message....  Cool....  Okay, bye!

Ignore Extensions: Sometimes email servers will create multiple files for a single bounced message. For instance, in the case of Microsoft's IIS SMTP Server you'll see 3 files that pertain to a single bounced email message. Each file has a different extension (i.e. .bdp, .bdr, and .bad). The only files that BounceStudio Enterprise needs to be concerned with in this case are the ".bad" files. You can tell BounceStudio to ignore the ".bdp" and ".bdr" files using this setting. You can enter multiple extensions here, just make sure they are each delimited by a space character. See screenshot above. If BounceStudio encounters these files, it will delete them without parsing them.

Mandatory Ignored Extensions: By default, and as a safety precaution, BounceStudio Enterprise will ALWAYS ignore the file extensions listed below. BounceStudio will not parse and will not delete files with these extensions. If you're careful with your folder selection above then BounceStudio should never encounter these files, but it's better to error on the side of caution.

.exe .dll .com .bat .cmd .bin .inf .ins .inx .isu .job .jse .lnk
.msc .msi .msp .mst .paf .pif .ps1 .reg .rgs .scr .sct .shb .shs
.u3p .vb .vbs .vbe .ws .wsf .wsh .gadget .vbscript

NOTE: If you know of some extensions that should be added to this list, please let us know.

From Address: This is the email address of the "bounce" email box associated with this folder. All of your email bounces are sent to this email address.

Reply-To Address: The "Reply-To" email address is the email address that is used when your email recipients hit "reply" to your messages. When they hit "reply", their email message is sent to the "Reply-To" email box. It's highly recommended that you have two email boxes for all of your opt-in email communications. One email box for all of your "bounces" to go too, and one email box for all of your "replies" to go too. Having two email boxes for all of your opt-in email communications will allow all of the "email bounces" to end up in one email box, and all of the "replies" to end up in a separate email box. Doing this will improve BounceStudio Enterprise performance tremendously because BounceStudio Enterprise won't have to parse all of your "non-bounce" replies.

Ignore Addresses: The "Ignore Addresses" field isn't used by BounceStudio Enterprise in all cases. Sometimes BounceStudio Enterprise knows that a message is a bounce, but for some reason the email address of the recipient isn't in the position that BounceStudio Enterprise is expecting it to be in. When this occurs, BounceStudio Enterprise does a deeper scan of the bounced message to find the proper recipient email address. BounceStudio Enterprise doesn't want to pass back the From, Reply-To, or the Ignore Addresses of the original sender by mistake, so it checks for these while calculating who the original recipient was. You do not need to re-enter your "From" and "Reply-To" email addresses here, but you may use this field for any other email addresses that may appear in your outbound messages.

You can enter several email addresses in this field if you need too. Just make sure you separate each email address with a PIPE character. For example:|

The example above is made up of 2 email addresses. and

You can also using a wild-card here. For instance, if you want to ignore all email addresses from a specific domain (i.e., then you can enter the following in the Ignore Addresses field:

You can also combine complete email addresses with wild-cards in your list of Ignore Addresses. For example:|

This example will ignore any email addresses that match and also ignore all email addresses that have a domain of

VERP Prefix: This setting is typically left blank. If you're sending your email newsletter/campaigns using VERP, then you'll need to enter the VERP Prefix of your VERP addressing scheme here. Entering your VERP Prefix here will enable the #VERPEMAIL# BounceStudio Variable which can be used in your Database Action SQL Statement and/or your Http Push Action Web Url. For more information on VERP, click HERE.

Account Disabled: Selecting this option will disable the BounceStudio "File System" monitored item. The BounceStudio Enterprise Bounce Service will not monitor a disabled monitored item. After setting a monitored item to disabled, a red X will be placed on the item in the TreeView Window (see below).

NOTE: When sending your outbound email messages, some email systems allow you to set a Return-Path email address that is different than the FROM: email address. The Return-Path is the actual email address that gets used in the "MAIL FROM" SMTP command during the SMTP session. In this case, all of your email bounces will be sent to the Return-Path email address. If you designed your outbound email system to work like this, then you'll want to put your Return-Path email address in the BounceStudio Enterprise monitored item "FROM" setting, and your FROM: email header value in the BounceStudio Enterprise monitored item "Reply-To" setting. When you use a Return-Path value that's different than the FROM: email header value, you're probably not going to need a Reply-To Email header value in your outbound message. But, if you do have a Reply-To email header value and a Return-Path that is different from the FROM: email header value, then you should put the Reply-To email header value in the BounceStudio Enterprise monitored item Ignore Addresses field.

Below is a sample SMTP session that shows a Return-Path setting that's different than the FROM: email header value. In this case, all of the email bounce messages will be sent to the email address, instead of the email address.
helo boogie01
250 <>... Sender ok
250 Recipient <> ok
Subject: Hey dude!

This is the message Body!!!!  Testing.
250 SMTP Session Complete
If your SMTP sessions look similar to the one above, then your BounceStudio Enterprise monitored item settings could look like the following:
From Address:
Reply-To Address:
Ignore Addresses: