Raintree's questions

I have a number of clients on Small Business Server 2003, which includes Exchange Server 2003. A few of them have AT&T as their ISP.

In an effort to avoid losing email send abilities due to temporarily getting block-listed for a spambot, I would like to hand off email delivery to AT&T instead of delivering it directly (yes, we will still clean up the spambots). AT&T requires SSL, Microsoft does not seem to support it until Exchange 2007.

I have found references to STunnel as a possible work-around, but it looks like the tunnel has to stay up permanently?

1. Has someone used STunnell successfully in an Exchange 2003/AT&T environment and be willing to share the recipe?

2. Does someone know of a better solution using Exchange 2003 and AT&T?

I recently had to rebuild a Small Business Server 2003 Standard after a crash. I then rejoined the workstations to the domain. Subsequently, many of the Windows XP Pro workstation domain members are experiencing intermittent locked profiles when a user attempts to login, usually after several hours of having no account logged in. A reboot resolves the issue.

We are not using roaming profiles or Terminal Services, and UPHClean in its native configuration is not shedding any light. I have removed and reinstalled the Trend Micro AV client, and disabled many (but not all - some are mission-critical) of the third-party startup services/applications. On three of the workstations, I have renamed the profile and started with a clean profile and copied user files over (but not the Application Data or Local Settings folder, let alone the NTUSER.DAT file).

Any ideas? I'm stumped...