I wonder if that's Tina's problem.

No, I don't have a problem of duplicate forms arriving. The print screen I posted was of Scott's computer. Nothing to do with duplicate forms but of an issue that may have been causing the duplicate email problem - as well as being an issue by itself.

Did you ever test another email client besides AOL? Will you still be doing that?

I tried it with my gmail accounts, one personnel and the other my coffeecup account, and I tried it with outlook 2010 for my work email and they all look the same as my aol. I hit reply for all of them and the only info I could see was the email I set the form up with.

Is the form named the same as your email address and can you provide print screens? (just because this is hard to believe) There may be a difference of using S-drive verses manual export. I do use manual export, but I'm really sure Scott used S-drive and has the same issue as me.

My forms aren't named the same as my email address. I wasn't forced to name it like that anywhere in the design process.
So is the form your having the problem with named the same as your email address?

I'm not having a problem with the forms. They work fine. It's how FB is attaching the form name and creating a completely new email address that doesn't exist to the form notifications.

The program doesn't force you. You are forced to do so IF you care about hitting reply to the notification email to write to your customer and see the original text in the email below your reply that has an email address that starts with your form name at your domain.com (see image I posted earlier of Scott's own test).

Yes, now I must name my form the same name as my email address.

Quote from Scott, "Whatever the form name saved as, that is what is comes from."

In FB, I used email address of special@domain.com and named my form coupons.
When my client hits reply when they get their notification from specials@domain.com in the reply email will be this (there is no such email address as coupons@mydomain.com):

Original Email
To: customeremailaddress
From: coupons@domain.com
Subject: Coupon Specials from Client Name

Hey You!
form's content here

We're now off topic here. If we can continue without Mods jumping on us, I'd like to so I can find out why yours doesn't do it and mine and Scott's do. I really need print screens though.

"When my client hits reply when they get their notification from specials@domain.com in the reply email will be this (there is no such email address as coupons@mydomain.com:"

Yes, that is correct. That is because the email comes from your web server as coupons@mydomain.com but when you hit reply, it goes to specials@domain.com (that is the ReplyTo address)

We cannot change the address in the body of the message because that email address is what was used when the email was received.

What's AFTER the @ sign in the email address comes from our web server. What's before the @ sign comes directly from Coffee Cup Form Builder adding it based on the form's name.
(see attached image)

So when you say it's because the email comes from your webserver, this is misleading because only the domain name is coming from our webserver - for non-spoofing purposes- but what's in front of the @sign comes from Coffee Cup's programming.

Coupons@domain.com does not exist on our web server, nor entered into the form, but is only the name of the form.

So since we already know this and there is no debate between me and Scott on this happening (except he likes to skirt the issue that Coffee Cup uses the form name) why is it that Eric cannot see this happening with his forms?

Just as one more confirmation of what Tina is describing, I'm attaching a screenshot of the header from a response to one of our forms. Not that it is really needed, since Scott has already confirmed and explained, but I'm also curious about Eric's forms, in case he is seeing something different...
In my case there is the added twist that the form name has been modified by removal of dashes in the name. This is presumably due to dashes being illegal characters in e-mail addresses (??), but has the effect of making it even less intelligible...