"Egbert Nierop" <egbert_nierop@nospam.invalid> wrote in message
news:16951BA1-E622-44CA-A506-889E775D2618@microsoft.com...
>
> "Ben" <benb@nospam.postalias> wrote in message
> news:%23vL2PbiQIHA.4476@TK2MSFTNGP06.phx.gbl...
>> Hi,
>>
>> We're running Windows 2003 Server (standard) SP2, with ISA Server 2006
>> (standard). IIS6 is setup as our edge SMTP relay, with an Exchange 2003
>> server (standard) SP2, on our internal network.
>>
>> For a while now we've been told that some emails aren't getting through
>> to us. This only seems to be from 1 or 2 domains, but its always the same
>> domains.
>
> just a sanity check. If its just a domain or two that won't be passed,it
> might be that there have been defined local domains or aliasses in the
> SMTP snap-in. If that is the case, it's delivered locally, but won't
> arrive.
>
>> I've checked the SMTP logs, and it shows the below information, which
>> seems to suggest a timeout (TIMEOUT 121). I have tried solving this by
>> increasing the timeout to 15, and then 20 minutes, but this didn't solve
>> the problem. Having googled the issue some people suggest changing the
>> MTU size of any routers, so on our DSL router I have dropped this from
>> 1458, down to 1412, and then 1400 (2 suggested values), but still the
>> problem persists.
>>
>> I'm not too sure what else could be causing the problem. ISA 2006 seems
>> to be configured correctly! Could it be something on the sending SMTP
>> server? Something misconfigured on a router between us and the sender? If
>> so, how do you go about solving this?
>>
>> What does the large number after the result code in the log below
>> represent (953594) - if its the message size, is it bytes or kilobytes -
>> if its bytes then the message is less than 1mb, but if its kb, then the
>> message is over 116mb, which would explain the timeout. Although the
>> messages that we've been told we're not getting, have since been
>> forwarded to a yahoo account, and they are just small plain text emails,
>> no massive attachments or anything!
>>
>> 2007-12-19 01:14:33 194.xx.xx.139 remotedomain.com SMTPSVC1 ISA
>> 192.168.0.1 EHLO 250 0 - -
>> 2007-12-19 01:14:33 194.xx.xx.139 remotedomain.com SMTPSVC1 ISA
>> 192.168.0.1 MAIL 250 0 - -
>> 2007-12-19 01:14:33 194.xx.xx.139 remotedomain.com SMTPSVC1 ISA
>> 192.168.0.1 RCPT 250 0 - -
>> 2007-12-19 01:30:25 194.xx.xx.139 remotedomain.com SMTPSVC1 ISA
>> 192.168.0.1 TIMEOUT 121 953594 - -
>> 2007-12-19 01:30:25 194.xx.xx.139 remotedomain.com SMTPSVC1 ISA
>> 192.168.0.1 QUIT 240 953594 - -
>>
>> Any help, or suggestions greatly appreciated!
>>
>> Ben
>>
>

> We have 2 domains defined in the SMTP mmc, one is local (default),
> and has the hostname of the server (ISA), the other is a remote
> domain, which is our domain name (ourdomain.com).

> The local (default) domain only has one setting, which is the drop
> directory, set to C:\Inetpub\mailroot\Drop, however, there is
> nothing in this directory to indicate failed/dropped messages.

> Should I have the local domain defined? It was setup by default when
> SMTP was installed. And most of the SMTP config articles I've read
> reference the local (default) domain.

"Sanford Whiteman" <swhitemanlistens-software@cypressintegrated.com> wrote
in message news:op.t4yao2w06c17zw@gw02.broadleaf.local...
>> We have 2 domains defined in the SMTP mmc, one is local (default),
>> and has the hostname of the server (ISA), the other is a remote
>> domain, which is our domain name (ourdomain.com).
>
> Traditional setup, yes.
>
>> The local (default) domain only has one setting, which is the drop
>> directory, set to C:\Inetpub\mailroot\Drop, however, there is
>> nothing in this directory to indicate failed/dropped messages.
>
> \Drop isn't for "dropped" as in "disconnected" nor "undeliverable" --
> it's for messages that are addressed to users @ the corresponding
> domain and "dropped" into this primitive catch-all mailbox. Barring an
> event sink or other special routing, msgs to jill@<default_domain>,
> joe@<default_domain> -- anyone@<default_domain> -- will go in \Drop.
>
>> Should I have the local domain defined? It was setup by default when
>> SMTP was installed. And most of the SMTP config articles I've read
>> reference the local (default) domain.
>
> You absolutely need the default domain. Do not remove it.
>
> --Sandy
>