You should not have to touch every end user workstation to make such a simple config change.

Windows, Outlook, and Active Directory can be controlled via scripting. (Yes, I'm going out on a limb and guessing you're in the 90% of businesses that run all three for end users and their workstations.)

OS X, Mail, and Entourage can also be remotely controlled and scripted.

I'm not familiar with other mail clients to speak about their capabilities. Though, obviously, nix-based setups are typically scriptable.

It has been a long time since I've had to directly support end users and their workstations, so you'll have to do your own homework on how to do this. I only know you can do it.


Aside: Anytime you, as a sysadmin, consider touching every end user workstation something has gone very, very wrong.

Either you need to bone-up on administration best practice or get/learn better tools or both.

I hope this helps.
--
Freedom, Truth, Love, Beauty.
John Rodenbiker
[EMAIL PROTECTED]



On May 22, 2007, at 4:19 PM, Stephen Schaff wrote:

That's a really good point. However we have about 200 users we'd have to get to switch their mail settings - 99% of don't know what mail settings are of course. Changing ports could prove very painful. I will definitely consider it though, given how painful email is without greylisting.


Best Regards,
Stephen

On 22-May-07, at 3:10 PM, Bob Beck wrote:


        Trust me - bit the bullet and change to 587/465 anyway.
we had to for road warriors because 25 is blocked in so many
places anyway from walkups. You're better just getting your
users to switch.
        

* Chad M Stewart <[EMAIL PROTECTED]> [2007-05-22 12:46]:
Since having users change their settings can be problematic in many
environments, instead change the MX record.  This way you can
implement spamd right away and your users will not have to change
anything.  Though I would suggest moving the users to 587/465 in the
future so that they don't get burned at places like hotels that
redirect outbound port 25 traffic to a local SMTP proxy, that won't
have a clue how to authenticate the user anyways.

-Chad


--
#!/usr/bin/perl
if ((not 0 && not 1) !=  (! 0 && ! 1)) {
   print "Larry and Tom must smoke some really primo stuff...\n";
}

Reply via email to