ShocKNetworK Blog

2 – imsimta refresh
3 – should work – imsimta test -rewrite -filter [email protected] If you look at RFC 3028, you could get a better understanding of the
language. Example of imta.filter file:
require “envelope”;
require [“reject”]; if header :contains “From” “[email protected]”
{
reject “[email protected]”;
} if envelope :contains “From” “[email protected]”
{
discard;
} if header :contains “Subject” “$$$” {
reject “I don’t want your mail!”;
} if header :contains “To” “Undisclosed Recipients” {
reject “I don’t want your mail!”;
} require “fileinto;
if header :contains “To” “Undisclosed Recipients” {
fileinto “SPAM”;
}]]>

How to change user for Admin Server

Problem Statement:

S1DS 5.2(compressed archive) does not offer the option of specifying the

owner of the admin server during installation. When you specify

non-privilege user, such as nobody, for directory server, admin server is

also running as same non-privilage user as well as directory server.

Therefore, if you specify privilege port in unix (<1024) for the directory server, this will result in not being able to start / restart the directory server instance via the console. Troubleshooting Steps: If admin server is running as user except for root, you can't change the user for admin server via cosole. Here is a steps to change user for Admin server by hand. ** admin server should be stopped before conducting this procedure, but ns-slapd for configuration instance should be on-line. 1. change directive named 'User' in ServerRoot/admin-serv/config/magnus.conf to 'root' by text editor. 2. change file owner under ServerRoot/admin-serv to user you want as follows a. # cd /admin-serv

b. # chown -R root *

3. change attribute ‘nsSuiteSpotUser’ of admin server configuration entry

in your Directorty Server like

dn: cn=configuration, cn=admin-serv-, cn=Administration

Server, cn=Server Group, cn=, ou=, o=NetscapeRoot

to the user you want to change to.

For example) in case of using ldapsearch

a. do the following ldapsearch to determine target entry

#./ldapsearch -p -h -D “cn=Directory Manager” -w -b o=NetscapeRoot -s sub “nsSuiteSpotUser=*” dn nsSuiteSpotUser

dn:cn=configuration, cn=admin-serv-test, cn=Administration Server,

cn=Server Group,cn=test.example.com, ou=example.com, o=NetscapeRoot

nsSuiteSpotUser=nobody

#

b. modify usr in attribute nsSuiteSpotUser of this entry to ‘root’

# ldapmodify -p -D “cn=Directory Manager” -w dn: cn=configuration, cn=admin-serv-test, cn=Administration Server,

cn=Server Group, cn=test.example.com, ou=example.com, o=NetscapeRoot

changetype: modify

replace: nsSuiteSpotUser

nsSuiteSpotUser: root

modifying entry cn=configuration, cn=admin-serv-test,

cn=Administration Server, cn=Server Group, cn=test.example.com,

ou=example.com, o=NetscapeRoot

^D

#

you can also do same modification via directory TAB in directory

server console.

Description: Directory server 5.2 may have trouble in configuring itself on installation
if you set the server to run as another user. Here’s the workaround. Document Body: Directory server 5.2 may have trouble in configuring itself on installation
if you set the server to run as another user. Here are sample error messages you will get on installation: Created new Directory Server
Start Slapd Starting Slapd server configuration.
Fatal Slapd Missing configuration file
/opt/app/sunone/dir5_2/setup/slapd/slapd.inf
Configuration of the Directory Server failed.
Error Directory Server configuration failure Here’s the workaround. cd
slapd-/stop-slapd
find slapd- | xargs chown the_right_user
edit slapd-/config/dse.ldif
replace nsslapd-localuser line with:
nsslapd-localuser: the_right_user
slapd-/start-slapd Now you have a directory server that should be started by root or through
the admin server and run as “the_right_user”]]>

2.On all hosts, remove replication state.
– Use Console disable the replica role for userRoot.
– If a master, delete the changelog associated with the userRoot database
– restart the slapd process. 3.Reinitialize primary master with it’s own data, stripped of replication state
– invoke an in-line db2ldif dump, without the ( -r ) switch
– stop slapd
– classic ldif2db using the dump just created to rebuild database
– start slapd, validate basic serviceability 4.Configure Replication on master 1
– Use console to enable/ configure a changelog for userRoot
– Enable replication in a multi master role 5.Prepare seed LDIF
– invoke and in-line db2ldif dump, USING the ( -r ) switch. Confirm that ldif carries replication state data.
– Copy the seed LDIF to consumer (master 2) 6.Enable replication on master 2
– Enable / configure a changelog for userRoot
– Enable replication in a multi-master role
– stop slapd
– classic ldif2db import using the seed ldif from master1
– start slapd (master 2), validate basic serviceability 7.Test functional replication , both ways, master1 <-> master 2]]>