Software·43,883 discussions

Former Q&A email issue resolved

Locked

I closed this question prematurely, and would like to post the resolution to the issue. I forgot to check one vital option in OE.

http://techrepublic.com.com/5208-6239-0.html?forumID=50&threadID=165971&start0

Fot those who care… shortly after closing the question, I finally realized (through brain bashing) that this client had a fax machine wired to his network that was causing issues. He had not had a metric specified for priority communication, nor did he have a default path set up for his OE. For these reasons the mail was trying to go through the network to his fax machine.

Very strange indeed, but it is now fixed. I blame Microsoft for their misleading error codes. 😉

Topic

is the blame..

In reply to Former Q&A email issue resolved

anything like big blue’s cryptic error codes from thier bios?
( boot error 1962 Q&A question on here )

useless diagnosis data from any company is nothing but a time waster for all that companies customers.

( borland’s error code 10 … a generic meaningless error code according to them )

Exception Error ….

In reply to is the blame..

Yep. I love the old …

A fatal exception 0E has occurred at 0028:xxxxxxxx in VxD VMM(06) + xxxxxxxx

Kinda like decoding that message in Contact.

I was doing work for a company at one time, who actually paid Microsoft for Tech Support … and even those guys couldn’t figure out what this error was (well, one similar to above).
What ever happened to meaningful messages like ‘Disk is write protected’, and such. Things were easier to cope with in those days.

DUN 718

In reply to is the blame..

ever seen this one in Windows Me??? It means bad password, bad lines, invalid settings, reset the modem, do a winsock repair, connection time out, sour milk, and a wicked itch.

For my original post though, I should have know that it could have been trying to go elsewhere, but the client wasn’t honest about the configuration initially (as always) – Oh well. 😉

[Author]

Replies