I upgraded (via the functions built in to ArgoMail and ArgoMail .NET). Occurs on version 1.0.4.1

Pre .NET Version.
Many customers carried the postmaster account as a catch all. When some address got abused, it was added as an alias to a "bounce" mailbox that was disabled.

New Version - .NET:
Accounts with "disabled" checked in user settings are confirmed to be accepting email and placing email into mailboxes. Unchecking and checking will not fix the problem. Therefore, accounts cannot be disabled to reject email (needed with a catch all postmaster account). The accounts were also confirmed disabled via a Database query (value of "1" for column disabled, when doing select * from dbo.Users). This results in email being delivered to accounts that should not be getting email

One example below.

282    postmaster                                                          Group of removed.com                                                                                                                    1    0        0    0                                                                                                                                        Sent Items                                                                                                                          0    0    0    0    0    2007-11-21 03:24:20.677    ???                                 NULL                                                                        0                                                                                                                                              0    us-ascii                                a46c6028-b7f2-4791-adeb-ea6b079731a5    2007-11-21 03:24:20.677    2007-11-21 03:24:20.677    2007-11-21 03:24:20.677    removed.com Postmaster                                                                                                                                                                                                                                                                                                                                                                              25    us-ascii                                                            0    0    0    0    1        0    0    1        0                                                                                                                                                                                                                                                                       24    0    0    0    0

Confirmed & Reported to ArgoSoft.

Thanks. This represents about 100 accounts getting/processing email that otherwise would/should not. May be a contributing factor to other problems I have (at least amplifying other issues).

Hopefully it will resolve some of the issue. I did notice if you select DUMMY mail will not actually be accepted for that account.

Thanks, I had already tried that. But you'll note the DUMMY account does not serve the same purpose as a disabled account. In the 1.0.4.0 help file it reads:

Dummy - if checked, an account is a "dummy" account. Server will behave as if an account exists, it will not generate any errors when there are attempts to deliver mail there, but will discard all mail arriving to this account.

I NEEDED to return a 550 for "disabled" accounts and reject that email (just as the ArgoMail did in the non .NET version). DUMMY account will not do that. Here is a log sample from the old versions for disabled accounts:
11/18/2007 6:56:17 PM - ( 33863) 550 Account is inactive

In the most recent 1.0.4.1 test version Archie sent me, it now handles disabled accounts properly, so it looks like he fixed it. As an example:
[SMTP 000641 16-12-07 00:01:39] 550 User account is disabled

I agree. I have the same issue with bogus email address for my domains. You're one step ahead of me.. He has not released publically that release.