Re: Reading Exchange 2003 SMTP Logs / Expected emails don't always arrive

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Fri, 2 Mar 2007 15:11:29 -0000, "Sergio" <myname@xxxxxxxxxxxx>
wrote:

Hi,

We have been experiencing an issue now for a week or so and feel as though I
have exhausted every avenue in trying to find out why we are having this
issue. Essentially some emails (with attachment) aren't always received by
our users. The senders of the emails are, to the best of my knowledge,
always the same users. From what I can make out the senders IT
infrastructure has multiple Exchange servers (maila.domain.net,
mailb.domain.net, mailc.domain.net etc).

I have checked that no emails are getting blocked by the RBL we use and have
included the senders domain in a white list. I have checked that the emails
are not getting caught by our antivirus software. The email that doesn't
appear to arrive typically contains an attachment (approx 1 MB in size) and
is sent to many people (maybe 30 or 40). I can confirm that there isn't a
restriction that would block the email due to the number of intended
recipients (I have left the default setting of 5000 in Exchange) and
likewise for inbound and outbound mail size (currently set to 15 MB). There
are no individula limits set.

I have setup SMTP logging and would like some assistance in reading the
following extract (I have changed both the senders IP address and domain
name for obvious reasons).

My understanding is that, taking the extract below:
1) server 'maild.domainn.net' with IP address 1.2.3.4 has established
comunicaton with our server 'SERVER1' with IP address 192.168.30.3
sucessfully (EHLO 250).
2) It then goes on to declare the senders email address (MAIL 250)
successfully.
3) It declares the email address of the recipients successfully (RCPT 250),
and in this case there are 4 recipients.
4) There does *not* appear to be the DATA or BDAT declaration which would
tell our server to expect data (the email) to follow, it just quits
successfully (QUIT 240).

Is this normal? Why is there no DATA or BDAT?

What options have you chosen under to log under the Extended options
dialog box on the SMTP VS?




Thanks in advance for any thoughts, comments and assiastance.
Sergio

.

Relevant Pages

  • RE: Your message did not reach some or all of the intended recipie
    ... recipients' email addresses, and try again to check if the issue can be ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... >> 6) Do you have Recovery Storage group enabled on the SBS server? ...
    (microsoft.public.windows.server.sbs)
  • RE: Event 32090 when Faxing To Multiple Recipients
    ... Number of Recipients: 5. ... Step 2: Please check the Group Policy on SBS Server: ... After the report is created, select the report in the left panel and then ...
    (microsoft.public.windows.server.sbs)
  • Re: Should ISPs send bounceback on mail to non-existent address?
    ... >>very easy to detect such attacks. ... >- Sympatico has told me that it simply DISCARDS AND IGNORES any incoming ... Exchange Server 5.5 or older. ... recipients address during the SMTP phase hence can genreate those 5xx ...
    (comp.mail.misc)
  • Re: Exchange in a Child domain
    ... Service (RUS) problem. ... Do your recipients have valid e-mail addresses, ... MVP - Exchange ... in the child domain on the parent domain Exchange Server. ...
    (microsoft.public.exchange.setup)
  • Re: 554 SMTP synchronisation error - when users send large numbers of messages
    ... Again, I believe the problem is with your ISP's SMTP server, that is I believe it is that server that is issuing the 554, but I wouldn't be able to say for sure without looking at the SMTP protocol logs. ... I mean our Exchange server by 'the server' - we have a simple set up - one Exchnage server that functions as mail store & SMTP box and another exchange server that handles webmail. ... An earlier test I did was to get my user's original message and recipient list and resend it from another account with a please-ignore-this-test preamble - all recipients were BCC'd. ...
    (microsoft.public.exchange.admin)