Write them step by step instructions, with screenshots for the client 
they use.  Tell them they have 30 days (for example), remind them at 15 
and the day before.

I've done the above at several work sites (400ish and 50ish), and once 
management was on board, it was very simple.  A tiny bit of work now, to 
solve many problems tomorrow.


On 2007 May 22 (Tue) at 15:19:33 -0600 (-0600), 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";
:>}
:


--
Kleptomaniac, n.:
        A rich thief.
                -- Ambrose Bierce, "The Devil's Dictionary"

Reply via email to