iis smtp nntp:
It seems to me that in order to send email using ASP that you have to have a COM to do it. This requires that you enable relaying, but that opens up a hole. How can I get this accomplished without getting hacked? I have ASPEmail installed (CDO was giving me problems), and I have to enable relaying to send mail. Is this just a huge paradox? If not, can you please let me know how to allow relaying, but not be vulnerable. Thanks, Drew Laing
And I lock this down on IIS or Exchange? Just checking, I am a programmer, not so much administrator! Thanks, Drew [quoted text, click to view] "Jason Brown [MSFT]" <i-brjaso@online.microsoft.com> wrote in message news:OFT%23lcuKFHA.2936@TK2MSFTNGP15.phx.gbl... > Personally, I lock down the 'connection control' section so that only > 127.0.0.1 can connect at all. You can lock this down a few ways, but this > is the simplest, IMO. However it doesn't protect against malware running > on the local machine, which is a slight possibility in some > configurations. > > > -- > Jason Brown > Microsoft GTSC, IIS > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > "Drew" <drew.laing@NOswvtc.dmhmrsas.virginia.SPMgov> wrote in message > news:unrFm8mKFHA.2764@tk2msftngp13.phx.gbl... >> It seems to me that in order to send email using ASP that you have to >> have a COM to do it. This requires that you enable relaying, but that >> opens up a hole. How can I get this accomplished without getting hacked? >> I have ASPEmail installed (CDO was giving me problems), and I have to >> enable relaying to send mail. Is this just a huge paradox? If not, can >> you please let me know how to allow relaying, but not be vulnerable. >> >> Thanks, >> Drew Laing >> > >
Personally, I lock down the 'connection control' section so that only 127.0.0.1 can connect at all. You can lock this down a few ways, but this is the simplest, IMO. However it doesn't protect against malware running on the local machine, which is a slight possibility in some configurations. -- Jason Brown Microsoft GTSC, IIS This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Drew" <drew.laing@NOswvtc.dmhmrsas.virginia.SPMgov> wrote in message news:unrFm8mKFHA.2764@tk2msftngp13.phx.gbl... > It seems to me that in order to send email using ASP that you have to have > a COM to do it. This requires that you enable relaying, but that opens up > a hole. How can I get this accomplished without getting hacked? I have > ASPEmail installed (CDO was giving me problems), and I have to enable > relaying to send mail. Is this just a huge paradox? If not, can you > please let me know how to allow relaying, but not be vulnerable. > > Thanks, > Drew Laing >
On Wed, 16 Mar 2005 16:28:49 -0500, "Drew" [quoted text, click to view] <drew.laing@NOswvtc.dmhmrsas.virginia.SPMgov> wrote: >It seems to me that in order to send email using ASP that you have to have a >COM to do it. This requires that you enable relaying, but that opens up a >hole. How can I get this accomplished without getting hacked? I have >ASPEmail installed (CDO was giving me problems), and I have to enable >relaying to send mail. Is this just a huge paradox? If not, can you please >let me know how to allow relaying, but not be vulnerable.
If you need to relay, it's not due to any ASP requirement. The components, and CDO, send to a SMTP server. How that SMTP server reaches the destination is irrelevant. If the SMTP needs to relay, you lock it down by specifying systems to relay for. An IP range, a specific system, whatever. You can also force a login to a valid account.
I have IIS running on a Windows 2000 Server and Exchange 5.5 running on a newly upgraded (note: upgraded, not fresh install which would have probably been better) Windows 2000 Server. Thanks, Drew [quoted text, click to view] "Jason Brown [MSFT]" <i-brjaso@online.microsoft.com> wrote in message news:elb9Mg0KFHA.3296@TK2MSFTNGP15.phx.gbl... > Do you have exchange running on the same machine, and what version? > > I think in Exchange 2k3 boxes you'd administer it from the 'protocols' > section of the exchange management tool. To be on the safe side, check in > both locations, IIS SM and Exchange SM. > > > -- > Jason Brown > Microsoft GTSC, IIS > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > "Drew" <drew.laing@NOswvtc.dmhmrsas.virginia.SPMgov> wrote in message > news:OrKM9mxKFHA.3076@tk2msftngp13.phx.gbl... >> And I lock this down on IIS or Exchange? Just checking, I am a >> programmer, not so much administrator! >> >> Thanks, >> Drew >> >> "Jason Brown [MSFT]" <i-brjaso@online.microsoft.com> wrote in message >> news:OFT%23lcuKFHA.2936@TK2MSFTNGP15.phx.gbl... >>> Personally, I lock down the 'connection control' section so that only >>> 127.0.0.1 can connect at all. You can lock this down a few ways, but >>> this is the simplest, IMO. However it doesn't protect against malware >>> running on the local machine, which is a slight possibility in some >>> configurations. >>> >>> >>> -- >>> Jason Brown >>> Microsoft GTSC, IIS >>> >>> This posting is provided "AS IS" with no warranties, and confers no >>> rights. >>> >>> "Drew" <drew.laing@NOswvtc.dmhmrsas.virginia.SPMgov> wrote in message >>> news:unrFm8mKFHA.2764@tk2msftngp13.phx.gbl... >>>> It seems to me that in order to send email using ASP that you have to >>>> have a COM to do it. This requires that you enable relaying, but that >>>> opens up a hole. How can I get this accomplished without getting >>>> hacked? I have ASPEmail installed (CDO was giving me problems), and I >>>> have to enable relaying to send mail. Is this just a huge paradox? If >>>> not, can you please let me know how to allow relaying, but not be >>>> vulnerable. >>>> >>>> Thanks, >>>> Drew Laing >>>> >>> >>> >> >> > >
Do you have exchange running on the same machine, and what version? I think in Exchange 2k3 boxes you'd administer it from the 'protocols' section of the exchange management tool. To be on the safe side, check in both locations, IIS SM and Exchange SM. -- Jason Brown Microsoft GTSC, IIS This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Drew" <drew.laing@NOswvtc.dmhmrsas.virginia.SPMgov> wrote in message news:OrKM9mxKFHA.3076@tk2msftngp13.phx.gbl... > And I lock this down on IIS or Exchange? Just checking, I am a > programmer, not so much administrator! > > Thanks, > Drew > > "Jason Brown [MSFT]" <i-brjaso@online.microsoft.com> wrote in message > news:OFT%23lcuKFHA.2936@TK2MSFTNGP15.phx.gbl... >> Personally, I lock down the 'connection control' section so that only >> 127.0.0.1 can connect at all. You can lock this down a few ways, but this >> is the simplest, IMO. However it doesn't protect against malware running >> on the local machine, which is a slight possibility in some >> configurations. >> >> >> -- >> Jason Brown >> Microsoft GTSC, IIS >> >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> "Drew" <drew.laing@NOswvtc.dmhmrsas.virginia.SPMgov> wrote in message >> news:unrFm8mKFHA.2764@tk2msftngp13.phx.gbl... >>> It seems to me that in order to send email using ASP that you have to >>> have a COM to do it. This requires that you enable relaying, but that >>> opens up a hole. How can I get this accomplished without getting >>> hacked? I have ASPEmail installed (CDO was giving me problems), and I >>> have to enable relaying to send mail. Is this just a huge paradox? If >>> not, can you please let me know how to allow relaying, but not be >>> vulnerable. >>> >>> Thanks, >>> Drew Laing >>> >> >> > >
Don't see what you're looking for? Try a search.
|