Configuring transport tables to relay emails to a different mail server. In this example I am forwarding all emails for otherdomain.com to smtp.otherdomain.com . You can add as many transport maps as you need. All commands should be run as a user ‘zimbra’. After 5.0.9, postfix_transport_maps has been modified a bit, so we’ll show both ways.
$ zmlocalconfig |grep -i postfix_transport_maps
This will show you the current transport maps file configuration:
postfix_transport_maps = proxy:ldap:/opt/zimbra/conf/ldap-transport.cf
Create your transport file (owner/group-owner should be zimbra):
vi /opt/zimbra/postfix/conf/transportfile otherdomain.com :[smtp.otherdomain.com]
You can also add multiple transport maps, for example:
mydomain.com :[mail.otherdomain.com] mydomain.org :[mail.otherdomain.com] hisdomain.net :[mail.otherdomain.com]
In this example all emails for 3 different domains will go to mail.otherdomain.com, so destination will be changed, while user name will remain as in original email address.
Convert the transport file into maptype database file:
$ postmap /opt/zimbra/postfix/conf/transportfile
The file transportfile.db will be created in this directory. Define the new transport file (original, not *.db one) BEFORE the default one. Run:
$ zmlocalconfig -e postfix_transport_maps=hash:/opt/zimbra/postfix/conf/transportfile,proxy:ldap:/opt/zimbra/conf/ldap-transport.cf
Finally, make sure that the relay_domains parameter in main.cf contains all domains handled by the server, whether locally or relayed elsewhere:
$ vi /opt/zimbra/postfix/conf/main.cf relay_domains = otherdomain.com, mydomain.com, mydomain.org, hisdomain.net, locallyhandleddomain.com, localaliaseddomain.com
Restart Zimbra:
zmcontrol stop zmcontrol start
This will forward all emails for the example domains and subdomains to host smtp.otherdomain.com while allowing local domains to continue to be delivered locally. However you’ll need to be careful at zimbra upgrades. The modification will be overwritten by the upgrade. If you still not able to set the correct transport tables, contact Zimbra Support.
http://wiki.zimbra.com/index.php?title=Transport_Table_for_external_servers
Just do a tag-pattern (bound to T here), put in ~= as the pattern, then all duplicates will be tagged. After that, you can delete tagged messages (bound to ;d, or just d if you have $auto_tag=yes).
/root/bulk-user-add.txt:
sanjay:mypass99:555:555:Sanjay Singh:/home/Sanjay:/bin/bash
frampton:mypass99n:556:556:Frampton Martin:/home/Frampton:/bin/bash
—-
–
—
barun:mypass99:560:560:Barun Ghosh:/home/Barun:/bin/bash
# newusers /root/bulk-user-add.txt
Install "wipe", its in the repos.
To delete dirs use it like this: wipe -rfs
Add a nautilus action (menu system > prefs > nautilus actions) like this to make it available in nautilus (you can then select all the dirs and files you want and shred them with 1 right click):
path : wipe
params: -rfs %M
Edit: you need to install nautilus-actions from the repos for this…
/etc/sudoers:
zabbix ALL=NOPASSWD: /usr/sbin/hddtemp
zabbix_agentd.conf:
UserParameter=disk.temp[*],sudo hddtemp -n $1
item in zabbix:
disk.temp[/dev/hda]
hostname hpuxdev11 #(node name)
uname –S hpuxdev11
vi /etc/rc.config.d/netconf
HOSTNAME=”hpuxdev”
OPERATING_SYSTEM=HP-UX
LOOPBACK_ADDRESS=127.0.0.1
/sbin/init.d/net start
also it is a good ideea to change the name in /etc/hosts.
# diskinfo /dev/rdsk/c1t3d0