November 2007 Archives

Note, before you read this, you should have an SMTP edge server in front of your Exchange Server. These details are for those of you that don't have an SMTP filter, can't afford one or just can't fix your SMTP blobbing issues any other way. I've had to do this twice recently, so thought I'd blog it.

Basically, if you start seeing a bunch of XEXCH50 errors in your logs and can't receive emails from a foreign domain (usually running Exchange by the way), or can't receive messages with attachments (in our case, over 256kb in size), you may need to 'dumb down' your SMTP verbs in Exchange.

Reference: http://support.microsoft.com/kb/257569

Reference: http://support.microsoft.com/kb/843106/en-us

In my case, a client had a Sonicwall with old firmware that was gobbling up emails and not letting the SMTP complete its little chat.

So, to resolve this (until we can deal with the Sonicwall), do the following (again, try and use a real SMTP gateway instead):

1. cd "c:\Program Files\Exchsrvr\bin" (or wherever your path is)
2. regsvr32 /u peexch50.dll
3. iisreset

By the way, to determine before and after....

Before doing the above, do the following...
telnet localhost 25.
Then issue the command "ehlo somewhere.com"
If 250-EXEXCH50 is there, then the EXCH50 sink is enabled

After the change, do the same - you should see that it is gone...

Powered by www.itgroove.net

Sponsored by Major Change (.com), the Online Change Register

I don't like when Microsoft makes decisions for me... Until I give a crap about IPV6 or if you need to reset your IP on Vista, do the following...

Make sure IPV6 is not installed on your NIC, then...

From the commandline:

ipconfig /flushdns
nbtstat -R
nbtstat -RR
netsh int reset all
netsh int ip reset
netsh winsock reset

Then reboot