🚀 go-pugleaf

I know a guy how deploys SBS all the time and with Demon accounts, the other
day he was telling me that he found a site with out packet filtering turn on
so enabled it, incoming mail stopped....This is what he did, selected these
ports to open from the built in list ( do not spec your own) SMTP, POP3,
HTTP & HTTPS and set open both ways. This will allow exchange to listen on
port 25 which Demon will deliver to.


"Miles Gaynor" <mg@castlehoward.co.uk> wrote in message
news:E604B4DA88E0D311B6A2009027E0197E0BD2E3@SBSSERVER...
> I use sbs 4.5 as well, in fact it may have been my post that you were
> referring to.
> Still, I can't get this to work. I am rapidly starting to think that
> Demon do something
> weird with regards to working out who is connected. Once I have IP
> filtering in place,
> and have set up what /should/ be the correct filters, only a mailkick
> from a demon tech
> will start the mails flowing. I have tried setting a filter for identd
> with remote host
> set to any, I have set open stmp ports for all the demon mail servers I
> could find IP
> addresses for (at least 15!). I even set a filter opening SMTP for both
> directions and
> any remote host IP but still no joy - unless Demon did a mailkick and
> then the email
> would come in. The weird thing was that I didn't have to drop and
> reconnect. The
> filters worked fine and let in what they were supposed to. It seems that
> Demon  just don't
> send the mail. The Echange server is all ready to take the traffic, but
> Demon just don't
> send! Now, since Demon don't support ETRN or TURN, how can we let them
> know that we want
> our mail? I assumed that the act of logging in would do it (as I guess
> Demon did too) but
> what have we missed?
>
> Maybe we could collaborate via email once the group gets bored of us
> SBSsers dissing Demon!
> Sory to wibble, it's too late to be at work!!
> Miles
>
>
>