🚀 go-pugleaf

Thanks Jon, was beginning to think that this forum was a Ghost Town.

I finally found a solution (?) which I posted over in SBS2K forum -
essentially I stopped ETRN'ing and went over to TURNing.  This had the
effect of sending (and receiving) the mail ok, with no accompanying Mystery
Data so the line closed fine after a few mins.  Gawd knows why, but it
brought my blood pressure back to normal again.

I picked up the 'Admin Exchange 2000 Server' book by Tulloch, which I'll
have to find time to pad through - guess I got a bit complacent with 4.5
being more intuitive.

I have to confess to whizzing over to your site initially, in the hope that
you'd already implemented Demon and SBS/ES2K!!!  Have you got a site counter
on that page??  I bet that it's had a fair view visitors, I know that I've
quoted the link extensively.

Jann


"Jon Grieve" <jgrieve@southdown,co,uk> wrote in message
news:tkj3a1kv6lq768@corp.supernews.com...
> Jann,
>
> You're right, Demon do not (to my knowledge) support ETRN.  However, if
you
> tell ES2K to use it, the worst that'll happen is that it'll dial, connect
> and *attempt* to issue an ETRN command which will fail.  Of course, while
> this is going on, the Demon 'punt' machines will be busily delivering the
> mail to you.
>
> What might be happening is that Exchange is not handling the return status
> from the post machine that indicated ETRN is not available, and simply
> trying again and again, etc. which may account for the constant traffic
thus
> the connection never times out.  I just checked the MSKB, and there are
> quite a few articles concerning ETRN; one may give a clue.  Also, check
out
> the documentation for ES2K SP1; this may be a bug that's fixed...
>
> So, it appears that ES2K may have changed somewhat.  With 4.5, it was very
> much a case of "Shall I work in Dial-Up Mode?" with an option 'after' that
> to specify what action to take once connected (i.e. nothing).  I haven't
> moved up from 4.5 yet, so couldn't say what's changed.  Once I upgrade
> here - hopefully in a few months- I'll update my FAQ...
>
> Regards,
>
> Jon Grieve
>
>
> (To reply, modify return address; change commas to dots)
>
>
>
>
>
>
> "jann" <jann@dial.pipex.com> wrote in message
> news:3b3d982a$0$8511$cc9e4d1f@news.dial.pipex.com...
> > ... but no ETRN (i.e. Send No Signal) means no Collection at all!
> >
> > Hi - Has anyone in the UK using Demon SMTP mail been able to get the
> SBS2000
> > ICW (Internet Connect Wiz)  to configure mail collection OK? Without
> > tinkering!!!
> >
> > I've tried 3x install of SBS with test server (see earlier thread) and
> found
> > the requested 30-min mail collection was never initiated by SBS (though
as
> > soon as a client went on to the internet to browse, mail was delivered
and
> > sent fine).  With SBS4.5 (and following Mr Grieve's advice at
> > http://www.southdown.co.uk/users/jgrieve/faq/demonexchange.htm -
thanks!)
> > it worked fine.
> >
> > Could this be the answer?: with 4.5 No Signal was sent from ExSvr to
> collect
> > mail (as I've heard that Demon don't support ETRN?). I noticed with
> SBS2000
> > ICW that choosing 'No Signal' meant that the ominous words 'You have
> chosen
> > not to download mail' become part of the wizard confirmation script.
> >
> > So... I reran the ICW, and chose 'Send ETRN'; immediately ExSvr sprang
> into
> > action and downloaded mail successfully...
> >
> > I guess that some change has occurred to SBS/Exchange behind the scenes
> > following the dropping of the 4.5 IMC from SBS2000.  Or has some one
just
> > decided that Not Sending A Signal automatically means User Never Wants
to
> > Collect Mail... (and therefore mail is only collected when a queue of
> > outgoing mail is ready to depart). Any ideas?
> >
> > The problem with the ETRN setting however is this: it does allow a
regular
> > dial up and collection, but there also seems to be permanent data
traffic
> > between here and Demon after connection. Hence the line is not
dropped...
> > Any ideas what this data traffic could be?
> >
> > I guess if all this fails, I shall have to rely on a scheduled PING to
the
> > internet to act as a collection (and delivery) trigger.
> >
> >
> > Thanks
> >
> >
> >
> >
>
>