Discussion Locked

You only do it if you love it

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
blog root

4 replies

by lyallaust

Exchange server, in it's infinite wisdom, should be setup with each email domain controlled by a separate recipient policy.  If not, the mail destined for local users, but not at the default mail address will probably end up getting routed externally. For example:

%g@thisdomain.com.au

%g%1s@thisdomain.com.au

@thisdomain.com.au

where the %g means use the surname to generate the email address;  %g%1s means use the given name and the first letter of the surname.  The domain listed in bold is the default, and should not contain and prefix delimiters.

by lyallaust

Although I find Microsoft Exchange as the best excuse to stick with Microsoft servers, it does have its bad side.  One of the biggest problems is the amount of space the replay logs take up.  If you dont run a backup that flushes the log, or turn on circular logging you will lose a lot of space.  Of course once you know about them you can do something about it.

Unfortunatelly, the latest glitch was not the logs, I had all of them from e00 onwards but it did not help.  What I was getting was a failure of the server to download from a domainpop mailbox.  If you open the POP3 Mail connector in the system manager and clock "retrieve now" you get a nice friendly reply, "Cannot Initialize".  After finding absolutelly nothing about this error in any tech manual I began just randomly trying things.

The End users were still able to get at their mail via POP3, and telnet on port 110 looked OK, so it wasnt firewall. The service Microsoft Exchange POP3 Connector wasnt started, and would generate an error 1067 when trying to start. Unable to find any way to recreate this connector in Exchange 2000 (as part of SBS 2000) I tried the next best thing, reapply all the latest service packs... no luck. Running back through the usual processes (IISLockD, network setup wizard, antivirus scan, stopping anything not being used, start the service under different usernames, and multiple reboots) also did not yeild any results.

Fearing a long involved process, the server was taken back to the main office to backup the mailboxes before I set about removing exchange. Just for fun I thought it would be a good idea to make sure the antivirus was up to date before putting it on the main network. After adjusting the IP address on the network card and running the Network Configuration Wizard (in the SBS console) the server was rebooted. I noticed a large amount of network traffic on the restart, and upon checking the mail system it was now working.  The only thing different was the IP address was changed on the network card and the ISA LAT was changed to match.  Would be nice if anyone else has seen this and can tell me why only DomainPOP was affected.

by lyallaust

The main reason I had mentioned the replay logs was because of a problem with another server where there were poor backups and it had suddenly taken to running slow.  Rebooting didnt help, and the hard drive access was off the scale. The reason turned out to be a few (over 10Gb) of these replay logs on the boot partition so there was no space left.  Just a friendly warning.

by lyallaust

A lovely useful utility I have used occassionally over the past few years is SC.EXE.  Trying to explain it to one of the other technicians, i thought to check to see if Windows XP has it.  Yes, it does.

So now I am writing this mostly to keep records of when I thought to question when a spammer or virus creator will think to use this utility for their own nefarious ends.  My bet is on six months.

This discussion is closed to new replies.