If you have SpamHalter enabled you would still have to get to each user's NewMail directory and update WI_SPH.ini to code Enable=0, but why not keep SpamHalter alive - better defence in depth?

Martin 

We've been using PMail for several years, and have recently changed our mail server to Maia Mailguard. Now that we've done so, we want to disable content-control for everyone, so they use Maia's content controls instead of Pegasus'.

In the past, when we've had site-wide changes like this, we've saved a copy of the pmail.ini for an individual, made the change, see where the change in the pmail.ini takes place, and then script that change for our 50+ mostly-non-technical users. However, when I tried that for content controls, I didn't see any changes in the PMAIL.INI.

Where is the change made that makes Content Control enabled or disabled?

> We've been using PMail for several years, and have recently changed
> our mail server to Maia Mailguard. Now that we've done so, we want to
> disable content-control for everyone, so they use Maia's content
> controls instead of Pegasus'.
>
> In the past, when we've had site-wide changes like this, we've saved a
> copy of the pmail.ini for an individual, made the change, see where
> the change in the pmail.ini takes place, and then script that change
> for our 50+ mostly-non-technical users. However, when I tried that for
> content controls, I didn't see any changes in the PMAIL.INI.
>
> Where is the change made that makes Content Control enabled or
> disabled?

Might be one of the control words that does this and I do not know where.  That said, you might want to look at the Disable extension.

The DISABLE extension allows you to override almost any main
menu function within WinPMail.  It simply pops up a message box
with the text "This option has been disabled by the Network
Supervisor" when the user either selects the option from the menu,
or presses the shortcut key, or clicks the associated button bar
button.

New versions of the DISABLE extension are now available in both
16-bit and 32-bit flavours at:

                    ftp://tui.lincoln.ac.nz

Filenames are DISABL16.ZIP and DISABL32.ZIP.

I'm having problems logging into this site so I've attached a copy.

With local installs of PMail for everyone, this would still require touching each machine, which is what I'm trying to avoid. I can go to each machine and disable content control, and this would be no problem...they won't set it back on.

I was just trying to be efficient.
 

If everyone is sharing the content control file (eg Spambust.dat), why not edit the file to either change all lines to comments or empty the file (maybe leave a comment in the file to timestamp and explain what has been done.

Martin 

[quote user="irelam"]

If everyone is sharing the content control file (eg Spambust.dat), why not edit the file to either change all lines to comments or empty the file (maybe leave a comment in the file to timestamp and explain what has been done.

[/quote]

I considered doing that, but wasn't sure if that would effectively turn off all content controls.