Greetings! I'm trying to help a client troubleshoot a spammer in his network, coming from behind a NAT IP address. If I could tell him which TCP Port the spam was coming from, he could look up the private IP address in his router's NAT table. However, the field in the SMTP log which I THOUGHT reflec...

Jesper, Assuming your goal is to prevent the public from sending mail to the postoffice in question, here's one way to do it, IF you have an additional public IP address available for your server: Bind the postoffice in question to a different IP address, and filter access to that IP in your firewal...

Four days after removing those over-filled mailboxes, the server is still running great, and the disk queue has remained very low (usually 0 or 1 under normal operation, with occasional spikes to 3 or 4 during backups and other maintenance). It occurred to me today that I never mentioned that our "s...

Awesome, glad to hear it!
-Tom R.

Just an update to the performance discussion that some people might find interesting... Short version: E-mail accounts that were full and had been abandoned were causing the Post Office connector to take a very long time to check quotas. The problem was compounded by the "Message rejected because yo...

Yes, we played with that. We thought just dropping the message would be best, because we don't use Junk folders yet, and the "replace link' feature had two issues: First, the link gets replaced with "REMOVED: URISBL->Spamhaus " which was confusing and generated tech support calls, and second, in man...

It's hard to say, the debug log entries aren't labeled very well. We sometimes receive 5 or 10 messages within the same second, so with no message ID or identifying IP address on most entries in the debug log, I don't know how to relate them to the proper message.
-Tom R.

When a message is blocked by the "URL Blacklisting" feature of DNS Blacklisting, the only indication is an entry in the SMTP-Debug log that mentions the URL and corresponding IP address that caused the message to be blocked. However, there is nothing in this entry to indicate WHICH message this happ...

Hello, We moved several thousand customers (in about 150 mail domains) from an old Unix mail server running sendmail to a new Windows 2003 server running MailEnable about four months ago. Almost everything seems to be fine, except for one rare and fairly minor issue, which started to occur when we s...

I have noticed in our SMTP logs that the Message ID for an incoming message remains the same through most of the SMTP exchange, but for the log entry containing the QUIT command and the Subject, the message ID changes. I'm not talking about the new Message ID that gets assigned during MTA processing...

For #3 (setting quota for the postoffice), click on the Postoffice in the left pane of the MMC. This will display a set of icons in the right pane, one of which is "Set Quota". This will set the quota for all mailboxes in the domain.
-Tom R.

The registry setting works for us (set it to 2, and a "-" is displayed for Disk Usage and Inbox Messages), however it doesn't help with the similar (but not identical) problem we are experiencing.... For most of our postoffices, MMC performance is fine (up to 300 mailboxes, many with thousands of me...

MailEnable provided a patch for the SPF issue on Monday, and we have been running stable ever since. The patch is available as a Hotfix in the Downloads section.
-Tom R.

There was also a recent issue with URL Blacklisting, so you might want to try disabling that. For issues like this, it is always best to open a ticket with them.

Configuring the service to auto-restart upon failure helped us when SMTP kept crashing, so consider that too.

-Tom R.

We have been stable ever since we disabled SPF earlier this week too. I'm glad they found a workaround, but I hope they release a patch soon!
-Tom R.