First of all, thank you for your input. I think that I am getting what I
need taken care of for now. I will agree that sub-optimal is not the way
to go but for the time being it is a satisfactory workaround. More than
half of the legacy systems will not support any kind of authentication to
my mail
Ok[1], well no offense, but I'm not going to extend any effort in my lab
trying to make what you want to happen work because sub-optimal was
polite-speak for stupid. I'll point you to "Recipient Policies" and let you
try and create it again if that's really the route you want to take.
Did I mentio
Recreating the thread I felt I needed to do to make some things more clear
than what I did earlier. To expand of my scenario, the remote PC is
actually 312 remote PC's. So entering their IP addresses is not really an
option. Suboptimal will do for now as we are in the process of writing
software so
Starting a new thread on the same topic is probably not as useful as
replying to the response(s) to your existing thread. Did you add the IP
address of the machine in question as one allowed to relay through your
server?
The way you'd done it previously was sub-optimal. Rather trying to recreate
a
In 5.5 I can set up in the routing tab of the IMS to reroute incoming SMTP
mail, sent to whatever domain to relay, overriding relay restrictions even
tho the mail is coming from another site. Where is this in 2k? I was able
to see some things that were close but not quite what I needed and
tinkerin
5 matches
Mail list logo
