hi,
I wonder if anyone has come across this problem before.
Some users had reported over time that they did not receive email
that outside people (their customers) had sent to them. The users
had no idea of such email until they had to countercheck some matters.
Obviously not a good thing.
Going thru Admin mailbox, I found that among all the spoofs and spam,
were many NDRs to external email addrs. Checking some of these
(open the NDR, click Resend), I find that these appear to be NDRs
being sent from the SBS to the external users but had failed, i.e. the
NDRs themselves became NDRs. The Admin mailbox doesn't have
the 'original' NDR (Exchange is set to send a copy of NDR to Admin)
but the NDRs of NDRs.
These NDRs have 2 text attachments. One is the transaction with
Exchange (SMTP 550 etc), the other appears to be the email header
of the NDR that failed to make it out of SBS. Many of these header
texts appear to contain legit emails, by looking at the sender (external)
addr, recepient (valid internal addr), subject (appears to be genuine
business topic in a common format/structure for subject). Some other
NDRs I'm not so sure about, but could also be genuine mail that failed
to get thru and also failed to bounce out, these include from mailing lists,
PocketPC.com etc.
This header text shows email being d/l from POP, there's some trace
of where it was before POP. It doesn't show email failing to get to
the internal email acct, that's the unusual thing - it looks exactly like
an email that successfully made it through (the header that is).
However, not all emails are being affected, eg. many emails appear to
be affected during the first POP download on Monday morn as the
SBS is off over weekend, yet some email make it thru later and then
some other email failed the same way in the afternoon.
How do I diagnose, log and fix this? I would be grateful for any ideas
or clues.
This is a SBS2000, 2 Nics, ISA, 1GB ram, 2xOpteron, using POP
Connector to download and SMTP out to ISP's SMTP configured
in SBS SMTP connector. The only change made recently was to
install Symantec AVEE ver10 which includes File system scanner and
the mailscanner (SAVCE and SMSMSE). I don't think SAVEE is
the cause though.
TIA,
Eugene Tan