We just tossed IIS on a box of our dev/pre environment and lock it down by IP address. You can use user authentication if you want though. You should have some sort of restrictions on the system.
Any automation senders we have a documented company formart for this type of thing noreply-<applicationName>@example.com We require an applicationName or some identifier intheir so that should their script go beserk we can more easily hunt down the offender by glancing at logs instead of really digging into them Steven Peck http://www.blkmtn.org On Wed, May 18, 2011 at 11:42 AM, Lewin, Greg <[email protected]> wrote: > > > We have a sister company that recently moved to Hosted Exchange 2010 and no > longer have an SMTP server in house. They have a old copier that used to > send emails via > > The old internal Exchange server(5.5). It does not have authentication > capabilities, only the ability to send to an IP address. They would like to > be able to send mail to their internal users from this device. > > I have a call into the Hosting company looking for suggestions. I was > wondering if you folks might have any ideas. > > > > Thanks > > > > Greg > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
