Bouncer for Entourage - 2.0

The developer wrote in the read me file the following:
"You can use the same account that received the message, but don't you think that it might seem kind of strange to receive a bounce message for a non-existant account (which is what a bounce is designed for) from that account?" What does this really mean? Do I have to create another POP account just to bounce or I can use the account that get the spam mail to bounce those e-mails. Help please!

good. I just hope to reduces my junk mail!! Here is to no more junk mail! I get about 100 junk messages a day.

disrespectful to BTP, but have they actually looked at a bounce message from an SMTP server and from Bouncer? Very rarely today does a sender actually connect to the server that knows whether the account is valid or not. Bouncer is just as effective as an SMTP server two or three "hops" from the originating server.

use for bounce features for bozos instead of spam, and it works great. Such as: user sends mail to entire IT department with problem instead of calling the help desk, usually, 'my password is not working because i am too stupid to realize my caps lock is on' Voila, bounce to sender. One more reason for the user to call the help desk.

AustinSoft, but this app not only does't work it CAN'T. I couldn't say this better than Scott Boone: "During most SMTP transactions, a bounce would occur right after the RCPT command, indicating that the user is not available on that server. The remote server (the sender) is then left to dealing with the message. However, in the case of a user-initiated bounce, the remote server has already accomplished its task--and is long gone. Therefore the local server has to pick up the tab for returning the message to the sender. Unfortunately, because most of the MAIL commands and header information used by spammers is illegitimate (spoofed, hijacked, or simply non-functioning), your local server ends up bearing a disproportionate amount of the burden. In the default case for most SMTP mail transfer agents, after mail is dropped into a POP box, all MAIL and RCPT headers are lost...so all your local POP client has to go on is the probably-faked message headers. What does this mean? This means that if you look at the source for most of your SPAM, you will find that the From: header doesn't match the Return-Path: header, and none of it matches the Received: information; and all that means is that you probably don't have enough information to appropriately bounce the message and will simply be creating a tit-for-tat response--both being junk. In the end you are better off simply throwing the thing to /dev/null, the bit-bucket, or file 13 (whateverÐ