Change of Mail Domain in SJS Messaging Server 2004Q2

Hi,
I've installed the SJS Messaging Server 2004Q2 with LDAP Schema 2 and a domain name abc.com. How can I change the domain name to xyz.net without any user migration and mail migration. Should I use thing like domain alias to other to achieve this task.
Clive

What I really want to do is that users are previously using abc.com as mail address and webmail and then switch to xyz.net in both mail address and webmail but still can receive mail using abc.com. Moreover I don't want to change the DIT and add a new organization in my ldap server
Adding domain alias, I think I should use associatedDomain attribute. But, what is the meaning of change every reference to abc.com in ldap to xyz.net. Is it means changing the value of attributes in every mail user entry?

Similar Messages

How to configure Symantec Mail Security for SMTP & Messaging Server 6.3

Hi!
I want to install a Symantec Mail Security for SMTP 5.0.1(host1) with Messaging Server 6.3 (in production - host2), but when I try to access to POP protocol to send a message from Internet, the system display a message with a relay problem.
- Could you help me with this issue?,
- Do you know some documentation that speaks of this?. I can't find any documentation that explain how to configure and integrate SMS and Messaging Server. Thanks in advance.
Regards, CR

ctemp1 wrote:
I want to install a Symantec Mail Security for SMTP 5.0.1(host1) with Messaging Server 6.3 (in production - host2), but when I try to access to POP protocol to send a message from Internet, the system display a message with a relay problem.I take it that you have configured the symantec software like this?
internet -> symantec mail security system -> sun messaging server -> recipientA better approach is the following
internet -> sun messaging server -> recipient
                          |
                         V
              symantec mail security system(refer here: http://blogs.sun.com/factotum/entry/messaging_server_correctly_deploying_the)
- Do you know some documentation that speaks of this?. I can't find any documentation that explain how to configure and integrate SMS and Messaging Server. Thanks in advance.There is no documentation specifically for symantec software but we do document how to send emails via the symantec mail security server using the aliasdetourhost channel keyword:
http://docs.sun.com/app/docs/doc/819-4428/6n6j42615?a=view#bgaqy
Regards,
Shane.

Changing the default domain name of the server.

I know this is not the correct title for the topic. but its the best word i could found on my voculabary.
here's my problem.
Im using Sun App Server 9. the server is installed in the local machine. for testing purposes client access from the local server is sufficient. I deployed a web service using net beans 5.5. My problem is that the WSDL file is generated (by server) uses a fully qualified domain name rather than localhost. for example it uses http://mlb.stdmlb.sliit.lk:8080. When i try to create a client using netbeans it tries to access the server using this address (the one in the WSDL) but the firewall denies access to port 8080. Therefore i want to use the server to use localhost rather than the long domai name. (at least http://mlb) Can anyone tell me how to configure this?
Lahiru

These are the steps for changing domain name & IP address without reinstall
a) Stop the Gateway and Server .
b) Export the profile server database to a flat ldif file:
# /opt/netscape/directory4/slapd-host_name/db2ldif /temp/profile.ldif
c) Use awk, perl, or vi, to change every instance of the system domainname in the ldif file to that of the new system.
d) Import the edited ldif file into the profile server on the new machine:
# /opt/netscape/directory4/slapd-/ldif2db -i /temp/profile.ldif
e) edit etc/opt/SUNWips/platform.conf and change all the domain name & Ip address
f) edit /etc/opt/SUNWips/properties.file change the domain name
g) Start the platform server and gateway on the new machine.

How can we change the default domain in iPlanet messenger server 5.1 through delegated administrator?

The default domain for a iMS server is an option in configutil. Delegated administrator manages the data in LDAP. Delegated admin can edit the domain properties, but can't change what the default domain is for a given server.

Mail.app and Netscape Messaging Server v3.6

We are trying to track down performance issues with Mail.app in both Tiger and Panther. Issues include how long it takes to download large attachments (PDFs upwards of 10MB), how long it takes to synchronize and cache, and other things that appear in Mail's activity window and never go away. Downloading large attachments puts a large CPU load on our mail server. We are looking at all variables -- switches, network configs, local client settings, etc. We are on a switched network with a mix of Gig and 100BT to the desktops. But my question here is: What might be the advantage of upgrading to a newer mail server? Our Netscape 3.6 software is very old, but the Sun hardware it lives on had a CPU upgrade last year. Even though the IMAP protocol itself has been pretty stable for years, would we find newer platforms more efficient with modern needs such as large attachments and inboxes that receive dozens of messages a day?

Wow, this is dusting off the cobwebs. NS 3.X has a different format for mail message, the IMAP data is contained in the first 400 bytes (or so) of the message file. So sending them through the deliver program is not an option, unless you strip the bytes off.
When you ran upgrade on an individual user, did you first remove the 4.15 mailbox with mboxutil -d?

Change where Mail stores my email messages

Mail (Mavericks version) seems to be taking a lot of space on my small SSHD boot drive to store my email messages. I can't find how to change the location to my 2TB HD (which is also internal to my iMac, but not the boot drive).
Can anyone assist?

That article gets around to talking about it half way through, but you can simply move a single folder in your home directory someplace else and make a link (alias) of it in your home directory.
I already do this with my Mail -- i put my actual Mail folder in an encrypted sparse image, then in my ~/Library i link the moved folder "Mail" to where it sits in the encrypted volume.

How do I host multiple domains on a single Messaging Server?

How do I host multiple domains on a single Messaging Server?

To host multiple domains on one Messaging Server, use the
mailAlternateAddress attribute. If you want to host two domains
(customer1.com and customer2.com) on your server mail1.domain.com,
make sure that:
The various domains (in DNS) point to the installed mail server
(you must have the MX records that
points mail for customer1.com to mail1.domain.com and
customer2.com to mail1.domain.com)
That each person receiving mail at customer1.com and
customer2.com has an appropriate mailAlternateAddress
attribute describing the appropriate email address. For
instance, John Doe can have an email address (i.e. the value
of the 'mail' attribute for the John Doe LDAP entry) of
[email protected] and receive his mail on
[email protected] (the value of the mailAlternateAddress
attribute)
With Messaging Server 3.5, mailAlternateAddress can take the
form of @mail1.domain.com. If jdoe's mailAlternateAddress is
set to @mail1.domain.com, mail sent to [email protected]
will be delivered to [email protected]

jaygatsby1123 wrote:
So what exactly am I doing with virtual hosts? There is a place for Aliases... What would I put in the "Aliases" box?
Any other host name that you want to resolve to the specified virtual host. It's quite literally an alias.
if you want www.example.com and www.example.org to end up at the same web site and you already have a virtual host — Apple refers to virtual hosts as sites — configured for www.example.com in Server.app, then you'd add www.example.org as an alias for the www.example.com virtual host (site).
Virtual hosts are implemented in a web server using some details of the HTTP or HTTPS protocol, and what the web browser (client) specified. The client gets handed an IP address or a domain name by the user, and the client then fetches the associated IP address for the target web server from the client's DNS services or local host database, and the client then connects to the IP address and passes over the text string that the user had requested — the IP address or domain name or even some local shortcut set up in the client system — via the HTTP or HTTPS protocol. The web server receives and processes this arriving text string from the client, and uses it to select which web site to render back to the web client. One subtle detail lurks here, too: the server's own DNS configuration really isn't involved in the selection of the virtual host.

Messaging Server: local DNS domain should include "localhost"

I'm having problems with Netscape
Messaging Server (3 and 4) in environments with certain DNS configurations.

Most customers configure their systems to use the local hosts database (/etc/hosts file)
before using DNS to resolve hostnames to IP addresses.

Netscape Messaging Server uses its own custom hostname resolution software, and
generally ignores system configurations that use /etc/hosts. This can cause
problems if the Messaging Server were to look for information that is not in
DNS, but in /etc/hosts.

Netscape Messaging software will occassionally attempt a DNS lookup on
"localhost". If you do not have localhost entries in the search path, you
may see one of two problems:
<OL>
<LI>Sendmail Emulator will return spurious Couldn't connect to
<mailserver hostname> to deliver mail. error.

This problem will happen in Messaging Server 4.0, 4.0.1, 4.0.3. This problem is fixed in 4.05 and 4.1.

For example, if you typed the following:

#/usr/lib/sendmail -v [email protected]
Subject: this is a test message
test text
You might have received the following response:

sendmail: Couldn't connect to to deliver mail.
sendmail: Message saved in /dead.letter

<LI>smtp is very slow (15 seconds - 2 minutes) in returning banner.

This problem may happen with Messaging Server 4.1.

System/Mail Administrators:

Netscape Messaging Server will ignore /etc/hosts
and NIS in this case.
Adding localhost to your /etc/hosts
file or NIS hosts database will not
resolve this problem.

You can verify the source of this problem with nslookup:

(succesful test)

machinename.domain.com% nslookup localhost
Server: nameserver.domain.com
Address: 200.00.XX.XXX
Name: localhost
Address: 127.0.0.1
(failed test)

kwikimart.mcom.com% nslookup localhost.machinename.domain.com.
Server: machinename.domain.com
Address: 200.00.XX.XXX
*** machinename.domain.com can't find localhost.domain.com.: Non-existent
host/domain

Network/DNS Administrators:

A DNS entry for localhost should be created for any domain in the search
path of the messaging server. "localhost." exists in the root nameservers
on the Internet, so this problem should onnly occur in networks where the
following is true:
<OL>
<LI>Direct access to the internet root (.) is not available.
<LI>Internal DNS does not have an entry for "localhost."
</OL>

The simplest solution is to create a domain and entry for "localhost." or
add "localhost" to a domain in mail server's domain search path.

NOTE: Netscape Technical Support can explain what DNS entries are required
for Netscape products. Netscape Technical Support does not support or
configure DNS for customers. This includes BIND (named) and Microsoft DNS.
</OL>

I think I found the answer to your problem here.
To save you some trouble, here is the quote:
{quote}
Q: Names on the internet are working fine, but looking up local names
from /etc/hosts or DHCP doesn't seem to work.
A: Resolver code sometime does strange things when given names without
any dots in. Win2k and WinXP may not use the DNS at all and just
try and look up the name using WINS. On unix look at "options ndots:"
in "man resolv.conf" for details on this topic. Testing lookups
using "nslookup" or "dig" will work, but then attempting to run
"ping" will get a lookup failure, appending a dot to the end of the
hostname will fix things. (ie "ping myhost" fails, but "ping
myhost." works. The solution is to make sure that all your hosts
have a domain set ("domain" in resolv.conf, or set a domain in
your DHCP server, see below fr Windows XP and Mac OS X).
Any domain will do, but "localnet" is traditional. Now when you
resolve "myhost" the resolver will attempt to look up
"myhost.localnet" so you need to have dnsmasq reply to that name.
The way to do that is to include the domain in each name on
/etc/hosts and/or to use the --expand-hosts and --domain options.
{quote}

When i send a mail to the user of messaging server, it returns saying unknown user.

I am trying to add a mail user to iplanet messaging server 5.1, I am able to configure that user from my mail client (outlook) but when i send mail to that user, it returns saying unknown user. I can see that user in LDAP data base/

This could be symptomatic of the iMS 5.1 server not yet having done a full synch to its alias database of the LDAP server. This is done every 24 hours (default) at 2 or 3 am. You can synch manually by running the "imsimta dirsync -F" command.

Changing the default mail sender name in Application server

Hi,
how do I change default mail sender name in application server.
It is administrator@application by default.

Does the email send from the operating system (sendmail ) or from the IAS?
If its from the ias , then its in the httpd.conf.
If its from the Operating system then I dont rememeber
If you have a non windows platform (like unix) easiest way will be to do a grep for "administrator@application "
Best Regards
Rajesh Alex

Messaging Server won't start up, or acts strangely

One of the config files has disappeared, or the Messaging Server
is acting "strangely".

Because of bugs in the Berkeley DB code, it is possible for a configuration
file to become corrupted. The Messaging Server will remove a severly
corrupted config file, but there is a threshold of corruption that may
impact server operation and may not cause files to be deleted.

If you notice that one of the config files is gone (your server won't start),
or that your server is acting strangely, DO NOT REPLACE IT WITH A BACKUP COPY.
This will most likely re-introduce the corruption. Instead, make note of
all the configuration changes you've made with the Messaging Server admin gui.
The easiest way to do this is to print out each page. Then replace the
config file with a clean one from the install directory or from the media.

Before re-starting the server, check each admin gui page to make sure it
matches your printout, and make any necessary changes. Then start the server.

The installed configuration files are located in the message spool area,
by default: /var/spool/postoffice/config and they are: 

Account-Handler 
Account-Manager 
AutoReply-Handler 
Configuration-Manager 
Dispatch 
Error-Handler 
Finger-Server 
IMAP4-Server 
MTA-Accounts 
Mailbox-Deliver 
POP3-Server 
Program-Deliver 
SMTP-Accept 
SMTP-Deliver 
SMTP-Router 
UNIX-Deliver 

Un-configured copies of all these files may be found under the directory
you installed the server at:

/install/server/data 

The fresh files will all have a .install appended to them.

Shut the computer dow, remove the power cord and all peripherals, wait for 30 seconds, replace the power cod and press the start button at the same time.
If you do not have the iSight, try the steps in [this|http://docs.info.apple.com/article.html?artnum=300908] Apple article.

OS X 10.9 Server Mail Domain Whitelisting

I just cannot understand why this isn't working.
I've added gmail, googlemail, mac, me, icloud to the whitelist, but emails from those domains still get greylisted:
$ sudo serveradmin settings Mail | grep whitelist
Mail:postfix:add_whitelist_domain:_array_index:5 = "gmail.com"
Mail:postfix:add_whitelist_domain:_array_index:6 = "googlemail.com"
Mail:postfix:add_whitelist_domain:_array_index:7 = "mac.com"
Mail:postfix:add_whitelist_domain:_array_index:8 = "me.com"
Mail:postfix:add_whitelist_domain:_array_index:9 = "icloud.com"
Mail:postfix:domain_whitelist:_array_index:5 = "gmail.com"
Mail:postfix:domain_whitelist:_array_index:6 = "googlemail.com"
Mail:postfix:domain_whitelist:_array_index:7 = "mac.com"
Mail:postfix:domain_whitelist:_array_index:8 = "me.com"
Mail:postfix:domain_whitelist:_array_index:9 = "icloud.com"
I tried:
$ sudo serveradmin settings Mail:postfix:whitelist_enabled = yes
2014-05-02 02:56:37.103 serveradmin[2894:507] Error: servermgr_mail: postconf read error: /usr/sbin/postconf: warning: whitelist_enabled: unknown parameter
2014-05-02 02:56:37.104 serveradmin[2894:507] unable to save key: whitelist_enabled (unknown parameter)
I've tried restarting the mail service and restarting the computer.
Has anyone been successful in whitelisting a domain on 10.9 Server?
May 2 02:37:47 example.com postfix/smtpd[1398]: connect from mail-oa0-f48.google.com[209.85.219.48]
May 2 02:37:47 example /usr/libexec/postfix/greylist.pl[1403]: Temporary message rejection to: <[email protected]> from: <[email protected]> sent from: [209.85.219.48] for: 60 seconds due to greylisting
May 2 02:37:48 example.com postfix/smtpd[1398]: NOQUEUE: reject: RCPT from mail-oa0-f48.google.com[209.85.219.48]: 450 4.7.1 <[email protected]>: Recipient address rejected: Service is unavailable; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mail-oa0-f48.google.com>
May 2 02:37:48 example.com postfix/smtpd[1398]: disconnect from mail-oa0-f48.google.com[209.85.219.48]

#!/usr/bin/perl
use DB_File;
use Fcntl;
use Sys::Syslog qw(:DEFAULT setlogsock);
# Usage: greylist.pl [-v]
# Demo delegated Postfix SMTPD policy server. This server implements
# greylisting. State is kept in a Berkeley DB database. Logging is
# sent to syslogd.
# How it works: each time a Postfix SMTP server process is started
# it connects to the policy service socket, and Postfix runs one
# instance of this PERL script. By default, a Postfix SMTP server
# process terminates after 100 seconds of idle time, or after serving
# 100 clients. Thus, the cost of starting this PERL script is smoothed
# out over time.
# To run this from /etc/postfix/master.cf:
# policy unix - n n - - spawn
# user=nobody argv=/usr/bin/perl /usr/libexec/postfix/greylist.pl
# To use this from Postfix SMTPD, use in /etc/postfix/main.cf:
# smtpd_recipient_restrictions =
# reject_unauth_destination
# check_policy_service unix:private/policy
# NOTE: specify check_policy_service AFTER reject_unauth_destination
# or else your system can become an open relay.
# To test this script by hand, execute:
# % perl greylist.pl
# Each query is a bunch of attributes. Order does not matter, and
# the demo script uses only a few of all the attributes shown below:
# request=smtpd_access_policy
# protocol_state=RCPT
# protocol_name=SMTP
# helo_name=some.domain.tld
# queue_id=8045F2AB23
# [email protected]
# [email protected]
# client_address=1.2.3.4
# client_name=another.domain.tld
# instance=123.456.7
# sasl_method=plain
# sasl_username=you
# sasl_sender=
# size=12345
# [empty line]
# The policy server script will answer in the same style, with an
# attribute list followed by a empty line:
# action=dunno
# [empty line]
# greylist status database and greylist time interval. DO NOT create the
# greylist status database in a world-writable directory such as /tmp
# or /var/tmp. DO NOT create the greylist database in a file system
# that can run out of space.
# In case of database corruption, this script saves the database as
# $database_name.time(), so that the mail system does not get stuck.
$database_name="/Library/Server/Mail/Data/gldb/greylist.db";
$whitelist_host_file="/Library/Server/Mail/Data/gldb/whitelist_host";
$whitelist_domain_file="/Library/Server/Mail/Data/gldb/whitelist_domain";
$whitelist_db_name="/Library/Server/Mail/Data/gldb/whitelist.db";
$greylist_delay=60;
# Auto-whitelist threshold. Specify 0 to disable, or the number of
# successful "come backs" after which a client is no longer subject
# to greylisting.
$auto_whitelist_threshold = 10;
# Syslogging options for verbose mode and for fatal errors.
# NOTE: comment out the $syslog_socktype line if syslogging does not
# work on your system.
$syslog_socktype = 'unix'; # inet, unix, stream, console
$syslog_facility="mail";
$syslog_options="pid";
$syslog_priority="info";
sub add_whitelist {
 # check for null host name
 my ($_host_name) = $attr{"host_name"};
 if ($_host_name eq "") {
 syslog $syslog_priority, "Warning: missing whitelist host name attribute";
 return 0;
 # Open the database on the fly.
 open_whitelist_db() unless $whitelist_db_obj;
 # Is host already in white list
 $value = read_whitelist_db($attr{"host_name"});
 # Add host if not in database
 if ($value == 0) {
 syslog $syslog_priority, "adding host: %s to whitelist host", $attr{"host_name"} if $verbose;
 update_whitelist_db($attr{"host_name"}, 1);
 open WHITELIST_FILE, ">> $whitelist_host_file" or
 syslog $syslog_priority, "Error: unable to open whitelist host file: %s", $whitelist_host_file;
 print WHITELIST_FILE "$attr{\"host_name\"}\n";
 close WHITELIST_FILE;
sub add_whitelist_domain {
 # check for null host name
 my ($_domain_name) = $attr{"domain_name"};
 if ($_domain_name eq "") {
 syslog $syslog_priority, "Warning: missing whitelist domain name attribute";
 return 0;
 # Open the database on the fly.
 open_whitelist_db() unless $whitelist_db_obj;
 # Is domain already in white list
 $value = read_whitelist_db($attr{"domain_name"});
 # Add domain if not in database
 if ($value == 0) {
 syslog $syslog_priority, "adding domain: %s to whitelist doman", $attr{"domain_name"} if $verbose;
 update_whitelist_db($attr{"domain_name"}, 1);
 open WHITELIST_FILE, ">> $whitelist_domain_file" or
 syslog $syslog_priority, "Error: unable to open whitelist domain file: %s", $whitelist_domain_file;
 print WHITELIST_FILE "$attr{\"domain_name\"}\n";
 close WHITELIST_FILE;
# Demo SMTPD access policy routine. The result is an action just like
# it would be specified on the right-hand side of a Postfix access
# table. Request attributes are available via the %attr hash.
sub smtpd_access_policy {
 my($key, $time_stamp, $now, $count, $domain);
 # Open the database on the fly.
 open_database() unless $database_obj;
 # Open the whitelist database on the fly.
 open_whitelist_db() unless $whitelist_db_obj;
 # Check if domain is whitelisted
 $domain = get_domain_name($attr{"client_name"});
 $count = read_whitelist_db($domain);
 if ($count > 0) {
 syslog $syslog_priority, "domain: %s is whitelisted", $domain if $verbose;
 return "dunno";
 # Check if host is whitelisted
 $count = read_whitelist_db($attr{"client_name"});
 if ($count > 0) {
 syslog $syslog_priority, "host: %s is whitelisted", $attr{"client_name"} if $verbose;
 return "dunno";
 # Search the auto-whitelist.
 if ($auto_whitelist_threshold > 0) {
 $count = read_database($attr{"client_address"});
 if ($count > $auto_whitelist_threshold) {
 return "dunno";
 # Lookup the time stamp for this client/sender/recipient.
 $key =
 lc $attr{"client_address"}."/".$attr{"sender"}."/".$attr{"recipient"};
 $time_stamp = read_database($key);
 $now = time();
 # If this is a new request add this client/sender/recipient to the database.
 if ($time_stamp == 0) {
 $time_stamp = $now;
 update_database($key, $time_stamp);
 # The result can be any action that is allowed in a Postfix access(5) map.
 # To label mail, return ``PREPEND'' headername: headertext
 # In case of success, return ``DUNNO'' instead of ``OK'' so that the
 # check_policy_service restriction can be followed by other restrictions.
 # In case of failure, specify ``DEFER_IF_PERMIT optional text...''
 # so that mail can still be blocked by other access restrictions.
 syslog $syslog_priority, "request age %d", $now - $time_stamp if $verbose;
 if ($now - $time_stamp > $greylist_delay) {
 # Update the auto-whitelist.
 if ($auto_whitelist_threshold > 0) {
 update_database($attr{"client_address"}, $count + 1);
 return "dunno";
 } else {
 # Apple
 syslog $syslog_priority, "Temporary message rejection to: <$attr{\"recipient\"}> from: <$attr{\"sender\"}> sent from: [$attr{\"client_address\"}] for: $greylist_delay seconds due to greylisting";
 return "defer_if_permit Service is unavailable";
# You should not have to make changes below this point.
sub LOCK_SH { 1 }; # Shared lock (used for reading).
sub LOCK_EX { 2 }; # Exclusive lock (used for writing).
sub LOCK_NB { 4 }; # Don't block (for testing).
sub LOCK_UN { 8 }; # Release lock.
# Log an error and abort.
sub fatal_exit {
 my($first) = shift(@_);
 syslog "err", "fatal: $first", @_;
 exit 1;
# Open hash database.
sub open_database {
 my($database_fd);
 # Use tied database to make complex manipulations easier to express.
 $database_obj = tie(%db_hash, 'DB_File', $database_name,
 O_CREAT|O_RDWR, 0644, $DB_BTREE);
 if ( !$database_obj ) {
 # don't prevent mail deliveries due to corrupt database
 my $db_backup = $database_name . "." . time();
 syslog $syslog_priority, "Warning: open failed for: %s : backing up to: %s",
 $database_name, $db_backup;
 rename $database_name, $db_backup ||
 fatal_exit "Can't save %s as %s: $!", $database_name, $db_backup;
 # try again
 $database_obj = tie(%db_hash, 'DB_File', $database_name,
 O_CREAT|O_RDWR, 0644, $DB_BTREE) ||
 fatal_exit "Cannot open database %s: $!", $database_name;
 $database_fd = $database_obj->fd;
 open DATABASE_HANDLE, "+<&=$database_fd" ||
 fatal_exit "Cannot fdopen database %s: $!", $database_name;
 syslog $syslog_priority, "open %s", $database_name if $verbose;
# Open hash whitelist database.
sub open_whitelist_db {
 my($whitelist_db_fd);
 # Use tied database to make complex manipulations easier to express.
 $whitelist_db_obj = tie(%db_hash, 'DB_File', $whitelist_db_name,
 O_CREAT|O_RDWR, 0644, $DB_BTREE);
 if ( !$whitelist_db_obj ) {
 # don't prevent mail deliveries due to corrupt database
 my $db_backup = $whitelist_db_name . "." . time();
 syslog $syslog_priority, "Warning: open failed for: %s : backing up to: %s",
 $whitelist_db_name, $db_backup;
 rename $whitelist_db_name, $db_backup ||
 fatal_exit "Can't save %s as %s: $!", $whitelist_db_name, $db_backup;
 # try again
 $whitelist_db_obj = tie(%db_hash, 'DB_File', $whitelist_db_name,
 O_CREAT|O_RDWR, 0644, $DB_BTREE) ||
 fatal_exit "Cannot open database %s: $!", $whitelist_db_name;
 $whitelist_db_fd = $whitelist_db_obj->fd;
 open WHITELIST_DB_HANDLE, "+<&=$whitelist_db_fd" ||
 fatal_exit "Cannot fdopen database %s: $!", $whitelist_db_name;
 syslog $syslog_priority, "open %s", $whitelist_db_name if $verbose;
# Read database. Use a shared lock to avoid reading the database
# while it is being changed. XXX There should be a way to synchronize
# our cache from the on-file database before looking up the key.
sub read_database {
 my($key) = @_;
 my($value);
 flock DATABASE_HANDLE, LOCK_SH ||
 fatal_exit "Can't get shared lock on %s: $!", $database_name;
 # XXX Synchronize our cache from the on-disk copy before lookup.
 $value = $db_hash{$key};
 syslog $syslog_priority, "lookup %s: %s", $key, $value if $verbose;
 flock DATABASE_HANDLE, LOCK_UN ||
 fatal_exit "Can't unlock %s: $!", $database_name;
 return $value;
# Read database. Use a shared lock to avoid reading the database
# while it is being changed. XXX There should be a way to synchronize
# our cache from the on-file database before looking up the key.
sub read_whitelist_db {
 my($key) = @_;
 my($value);
 flock WHITELIST_DB_HANDLE, LOCK_SH ||
 fatal_exit "Can't get shared lock on %s: $!", $whitelist_db_name;
 # XXX Synchronize our cache from the on-disk copy before lookup.
 $value = $db_hash{$key};
 syslog $syslog_priority, "whitelist lookup %s: %s", $key, $value if $verbose;
 flock WHITELIST_DB_HANDLE, LOCK_UN ||
 fatal_exit "Can't unlock %s: $!", $whitelist_db_name;
 return $value;
# Update database. Use an exclusive lock to avoid collisions with
# other updaters, and to avoid surprises in database readers. XXX
# There should be a way to synchronize our cache from the on-file
# database before updating the database.
sub update_database {
 my($key, $value) = @_;
 syslog $syslog_priority, "store %s: %s", $key, $value if $verbose;
 flock DATABASE_HANDLE, LOCK_EX ||
 fatal_exit "Can't exclusively lock %s: $!", $database_name;
 # XXX Synchronize our cache from the on-disk copy before update.
 $db_hash{$key} = $value;
 $database_obj->sync() &&
 fatal_exit "Can't update %s: $!", $database_name;
 flock DATABASE_HANDLE, LOCK_UN ||
 fatal_exit "Can't unlock %s: $!", $database_name;
# Update database. Use an exclusive lock to avoid collisions with
# other updaters, and to avoid surprises in database readers. XXX
# There should be a way to synchronize our cache from the on-file
# database before updating the database.
sub update_whitelist_db {
 my($key, $value) = @_;
 syslog $syslog_priority, "store whitelist host %s: %s", $key, $value if $verbose;
 flock WHITELIST_DB_HANDLE, LOCK_EX ||
 fatal_exit "Can't exclusively lock %s: $!", $whitelist_db_name;
 # XXX Synchronize our cache from the on-disk copy before update.
 $db_hash{$key} = $value;
 $whitelist_db_obj->sync() &&
 fatal_exit "Can't update %s: $!", $whitelist_db_name;
 flock WHITELIST_DB_HANDLE, LOCK_UN ||
 fatal_exit "Can't unlock %s: $!", $whitelist_db_name;
# Parse hostname to obtain domain name
sub get_domain_name {
 my($in_host_name) = @_;
 my($value);
 my($count) = 0;
 @tokens = split(/\./, $in_host_name);
 $count = $#tokens;
 $value=$tokens[$count-1] . "." . $tokens[$count];
 return $value;
# Signal 11 means that we have some kind of database corruption (yes
# Berkeley DB should handle this better). Move the corrupted database
# out of the way, and start with a new database.
sub sigsegv_handler {
 my $backup = $database_name . "." . time();
 rename $database_name, $backup ||
 fatal_exit "Can't save %s as %s: $!", $database_name, $backup;
 fatal_exit "Caught signal 11; the corrupted database is saved as $backup";
 my $wl_backup = $whitelist_db_name . "." . time();
 rename $whitelist_db_name, $wl_backup ||
 fatal_exit "Can't save %s as %s: $!", $whitelist_db_name, $wl_backup;
 fatal_exit "Caught signal 11; the corrupted database is saved as $wl_backup";
$SIG{'SEGV'} = 'sigsegv_handler';
# This process runs as a daemon, so it can't log to a terminal. Use
# syslog so that people can actually see our messages.
setlogsock $syslog_socktype;
openlog $0, $syslog_options, $syslog_facility;
# We don't need getopt() for now.
while ($option = shift(@ARGV)) {
 if ($option eq "-v") {
 $verbose = 1;
 } else {
 syslog $syslog_priority, "Invalid option: %s. Usage: %s [-v]",
 $option, $0;
 exit 1;
# Unbuffer standard output.
select((select(STDOUT), $| = 1)[0]);
# Receive a bunch of attributes, evaluate the policy, send the result.
while (<STDIN>) {
 if (/([^=]+)=(.*)\n/) {
 $attr{substr($1, 0, 512)} = substr($2, 0, 512);
 } elsif ($_ eq "\n") {
 if ($verbose) {
 for (keys %attr) {
 syslog $syslog_priority, "Attribute: %s=%s", $_, $attr{$_};
 if ( $attr{"request"} eq "smtpd_access_policy" ) {
 $action = smtpd_access_policy();
 } elsif ( $attr{"request"} eq "whitelist" ) {
 $action = add_whitelist();
 } elsif ( $attr{"request"} eq "whitelist_domain" ) {
 $action = add_whitelist_domain();
 } else {
 fatal_exit "unrecognized request type: '%s'", $attr{request};
 syslog $syslog_priority, "Action: %s", $action if $verbose;
 print STDOUT "action=$action\n\n";
 %attr = ();
 } else {
 chop;
 syslog $syslog_priority, "warning: ignoring garbage: %.100s", $_;

Sun Java(tm) System Messaging Server 6.3-0.15 outgoing mail issue

Hi,
We are running Sun Java(tm) System Messaging Server 6.3-0.15 (built Feb 9 2007).
with this java code if i change email.setFrom(SenderEmial);   to any other email address than the mail server will send email form that email instead of authenticated which is a problem for us so that any one can misuse it. i need help regarding this issue.I think its due to lack of SSL security so i want to know that how i can enable SSL.
Email email = new SimpleEmail();
    email.setSmtpPort(25);
    email.setAuthenticator(new DefaultAuthenticator("[email protected]","myPass"));
    email.setDebug(false);
    email.setHostName("mail.sunjavamail.com");
    email.setFrom(SenderEmial); //By changing this my mail server is sending emails from any email address.
    email.setSubject("Hi");
    email.setMsg("Test Mail");
    email.addTo("[email protected]");
      // email.setTLS(true);
   // email.setSSL(true);
    email.send();
    System.out.println("Done");
Thanks..

Hi,
I do not think this is unusual. Out of the box there are no restrictions on From: addresses, they're not required to match the domain of the sender or match up with DNS results. You can configure various restrictions or even modify the from address based on the users authenticated credentials, but not by default.
See the following documentation for details on restricting From: addresses:
https://wikis.oracle.com/display/CommSuite/Mail+Filtering+and+Access+Control#MailFilteringandAccessControl-FROMACCESSDescription
https://wikis.oracle.com/display/CommSuite/Handling+Forged+Email+by+Using+the+Sender+Policy+Framework

Windows 7 or Windows Server 2008 R2 domain join displays error "Changing the Primary Domain DNS name of this computer to "" failed...."

Hi,
Windows 7 or Windows Server 2008 R2 domain join displays error "Changing the Primary Domain DNS name of this computer to "" failed...."
DC:windows Server 2008 R2
Domain functional level:Windows Server 2003
When Winxp join domain, have no this error message.
I checked http://support.microsoft.com/kb/2018583?wa=wsignin1.0 does't work.
There have 3 suggestion in this article:
1.The "Disable NetBIOS over TCP/IP" checkbox has been disabled in the IPv4 properties of the computer being joined.
Doesnt's work.
2.Connectivity over UDP port 137 is blocked between client and the helper DC servicing the join operation in the target domain.
On my DC, I run netstat -an, reslut as below:
UDP 192.168.20.3:137 *:*
3.The TCP/IPv4 protocol has been disabled so that the client being joined or the DC in the destination domain targeted by the LDAP BIND is running TCP/IPv6 only.
We are not using IPV6.
This server recently updated from Windows Server 2003 to Windows Server 2008 R2. Before upgrade, when Win7 and Win2008 join this domain, also have the same error message.
Please help to check this issue.
Thank you very much.
BR
Guo YingHui

Hi Guo Ying,
I have faced this critical error which makes over-writes the host names in the domain when you join.
For example: Already you had a host name called as PC.domain.com in the domain.com Domain.
When you try to add the another host name called as PC in the domain.com Domain, it doesn't give you the duplicate name error on the network it does over-write the existing host name called as PC.domain.com & it will add the new host name into the domain.
Host name which got over-written will get removed from the domain. I faced this issue in my project. My DPM host name got removed from the Domain & new host name got joined into the domain which halted my backups for one day.
Final Resolution is as follows:
You need to start the dns console on the DC & drop down the domain name.
Select the _msdcs when you click on _msdcs it will show the Name Server's list on the right hand side.
You need to add the Domain Naming Master under the _msdcs or add all the domain controllers which you had.
After you add the Name server's try joining the PC OR Laptop to the domain which is successfully joins it.
Regards
Anand S
Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

JES Messaging Server 6.0 will not accept mail alternate address

JES Messaging Server 6.0 will not accept mail alternate address
I have installed the Sun ONE Messaging server 6.0 as part of an evaluation of the Java Enterprise System. This was installed along with Directory Server 5.2 and Identity Server 6.1. During the installation I created a top level organization (o=internet) knowing that I would want to create multiple email domains within it and a default domain. After the installation was complete I used the User Management Utility (/opt/SUNWcomm/bin/commadmin) to create some users within the default domain. I provided each user with a primary email address ([email protected]) and an alternate email address (mailAleternateAddress = [email protected]).
In testing the system I find that the Messaging Server will not accept messages sent to the alternate email address whether sent from the same server (via Messenger Express) or from an external server. It returns the error message: 550 5.1.1 unknown or illegal alias.
In attempting to trouble shoot this problem I have watched the Directory Server's access log when such an email is sent. It shows a query using [email protected] even though the email message was sent to [email protected] In any event the DS finds the user, but the Messaging server rejects the message.
[date_time] conn=120 op=11 msgId=12 - SRCH base="o=domain.com,o=internet" scope=2 filter="(mail=[email protected])" attrs="preferredLanguage mail mailEq
uivalentAddress"
[date_time] conn=120 op=11 msgId=12 - RESULT err=0 tag=101 nentries=1 etime=0
[date_time] conn=120 op=12 msgId=13 - SRCH base="o=internet" scope=2 filter="(&(objectClass=sunManagedOrganization)(|(associatedDomain=host.domain.com)(sunPreferredDomain=host.domain.com)))" attrs=ALL
[date_time] conn=120 op=12 msgId=13 - RESULT err=0 tag=101 nentries=0 etime=0
Any suggestions to eliminate this problem would be appreciated.

Both the primary and alternate email addresses are the same as the domain of the user.
Here is what I want to do. Email is sent to a primary email server (not this machine). Mail for some users stays on that server to be read and mail for other users is moved to a geographically separate server (the one in question) by specifying that the mail be forwarded to the specific host: [email protected] > [email protected]
On this second server I want to host two (or more) independent email domains. I do not want one of the domains to be a subdomain of the other. So during the installation I used o=internet as the root suffix and then used a different default domain (representing one of the registered internet domains). After installation I used the commadmin tool to create a second domain so now I have what looks something like this:
o=internet,
__ou=People
__ou=Groups
__o=domain1
____ou=People
____ou=Groups
__o=domain2
____ou=People
____ou=Groups
I then created some users under domain1 and some under domain2 so one user's dn is:
uid=user, ou=people, o= domain1.com, o=internet.
Mail sent locally to user@ domain1.com gets delivered correctly, but sending to [email protected] does not.
host2.domain1.com is the fully qualified domain name of the server.

Change of Mail Domain in SJS Messaging Server 2004Q2

Similar Messages

Maybe you are looking for