Migrate server mail files

Due to mail problems - filtering etc - I am considering rebuilding my server from scratch. The problem is I have a number of users who have iOS devices and use their server mail files as data depoistories - you have very powerful mail search functions of you server databases for IMAP mail on iOS.
The question is how do I restore / rebuild the existing mail databases for each user - I think all mail is stored in /Library/server/mail/data/mail/<user directory> although I don't know how you access or work out which directory belongs to which user?
Anyone tried this or know of a way of migrating the mail databases?

I bought a new Mac mini server running MLS and restored all did a complete restore of the time machine backup of my broken SL Server. This restored everything under the MLS operating system but as you know broke a number of things - Sieve, mail authentication etc. Many of these I have fixed except for Sieve. I need some kind of Server side mail filtering for the users who only have iOS devices with no client filtering - plan was to use your Roundcube/manage sieve approach.
Secondly, I tried, using the second hard disk in the new server for now, to do a clean install and reset up the ML Server from scratch rebuilding a subset of users and then copying the mail store directories from the time machine backup of the SL Server to the new Server.   I failed to find a way to associate the mail store directories and permission for the newly set up users. The server just built new mail stores and I could not find a way to transfer or combine them with the old mail stores.
Finally I tried the 'target disk mode' route to build an SL disk on an external FireWire drive that would boot the ML Server hoping I could just rebuild the original server on the new hardware. I used a CoreDuo Mac Mini we have to do the build but have so far not been able to get the new server to boot.   It just hangs before getting to the log in screen. I have given up on this as I doubt I can ever get this stable enough with all the unsupported (by SLS) hardware in the new mini (e.g. Intel HD3000 graphics).
I have now run out of ideas on how o achieve my goal of a stable server, with my existing mail stores and users, with a server side spam filter.   Any ideas are very welcome!

Similar Messages

Migrate Server Mail IMAP to other server

Our Mac (Lion) Server is currently having issues and I'd like to wipe fresh and start again. We currently have IMAP with around 40 mailboxes set up on the server, and I'm wondering how to port the mail accounts and mailbox contents over to the fresh server with the least administrative effort.
Any ideas?

if your users and import them into the new server, them all users will retain their GUID.
All mailboxes are named with the user's GUID.
On new server, import users. Setup mail service from scratch.
Copy the GUID mailboxes from old server to new.
Reset permissions of the mailboxes.
Its pretty straightforward.
The key is to keep the same User/GUID list.

Migrate sql server dump file to Oracle database on a network

I have a sql server dump file provided to me by DBA's. I have to migrate this dump file to Oracle database on a network. Please suggest me the steps to do this.

5c1ab566-05d1-4cc9-894a-fd1fe724c752 wrote:
That would be a text file with around 100 records. I have migrate those records to oracle database. The firewall constraints doesn't allow me to create a link to that database. Will Migration workbench would be apt for this case. How can i capture the database offline in this case ?
regardless of the tool/technique you use, those bits have to get from machine running sqlserver to the machine running Oracle. Either over the network (through the firewall) or via 'sneakernet.' What, exactly, are the firewall constraints?
If the export is a simple text file (character delimited fields? fixed length fields?) and only 100 records ... Migration Workbench may be overkill, perhaps a simple sqlldr job. But you still have to get the bits from 'there' to 'here'.
============================================================================
BTW, it would be really helpful if you would go to your profile and give yourself a recognizable name. It doesn't have to be your real name, just something that looks like a real name. Who says my name is really Ed Stevens? But at least when people see that on a message they have a recognizable identity. Unlike the system generated name of 'ed0f625b-6857-4956-9b66-da280b7cf3a2', which is like going to the pub with a bag over your head.

Migrating Server To New Machine?

Has anyone here tried to clone a server configuration to a new machine (like completely different hardware)?
We currently have an eMac in the office running OS X Tiger Server (I know I know) as our directory server, mail, web, file, and home directory server. It's got a lot of e-mail, work files, web sites, users, etc on it. I just bought a new powermac to replace it but I'm wondering if it's possible for me to 'clone' (like say with CarbonCopyCloner) the e-mac into the powermac.
Will that work?
I'm finding lots of software migration guides (eg. upgrading to a new version of OS X Server) but no server hardware migration guides like upgrading to a whole new machine...
I'm sort of hoping that I could come in on a Saturday and transfer the server to a new machine and have everything be as it was, meaning the users wouldn't even notice. Except things might be a little faster/snappier for them of course.
Am I in fantasy land? Any help or experiences in this area would be much appreciated!
Technical Side Note: eMac is a G4 800Ghz, new (actually used) powermac is a dual G4 1.3Ghz

No problem cloning machine to machine as long as the OS supports the target machine. In your case, any 10.4 server will will run on the dual.
Clone away....
You could also run a test... boot the eMac in firewire target disk mode, then startup the Dual G4 from the eMac's hard drive (option key on boot). It should start-up and run just fine (although a bit slower considering firewire interface).
Once up and running, you could stop services and clone from the live eMac drive to a freshly erased Dual G4 internal drive.
Jeff

How can I transfer Mail files from 10.6.8 to 10.8

I've used three support calls in an attempt to save my OS10.6.8 Mail files to a new Powerbook Pro. Migration Assistant left me with so many odd artifacts that I earased the whole thing. Then I tried importing files and finally, I tried copying the contents of Library-Mail to the same place in Mountain Lion. All the mailbox labels appeard, but there was no mail in them. I can't see using Time Machine to do this, because it simply can deal with the apparent change in format.
Does anyone have a way to accomplish the transfer of 10.6.8 mail to Mountain Lion?

Open the Mac App Store and try purchasing Mountain Lion 10.8. If you get told it's incompatible, choose About this Mac from the Apple menu, check if the computer has at least a Core 2 Duo(not Core Duo) or better CPU with at least 2GB of RAM, and if it does, phone the online Apple Store and order a download code for Lion 10.7.
(83668)

Connecting to a local SQL server .mdf file

Hi all,
In doing some prototyping of my database I started working with a local copy of an SQL Server database since it so conveniently integrated with the Visual Studio .NET tools I use. Now that I have spent far too much time working on a local prototype, I would very much like to migrate it to our in-house database rather than rewrite the whole thing (it is quite large in terms of tables and constraints and none of our in-house tools generate code from ER diagrams).
Seeing that SQL Developer had a migration utility I pounced at a chance to use it. I installed it as well as the recommended JDBC driver; however, it occurs to me that I have no idea how to connect to a local database file using the host name and port fields given to me. Is there some convenient way to configure SQL Server 2005 to forward this file to some kind of local host? Or is there any other driver for use with a local .mdf file? Help would be greatly appreciated.

While it does come with a copy of SQL Server with it, visual studio suspiciously just asks for a file name, so I would assume it reads directly from the .mdf
I have a copy of SQL Server 05 on the machine, but I haven't done anything in the way of server side configuration before, so I can't even guess how to direct it to serve the file.
All software packages involved are:
Windows XP
SQL Server 2005
Visual Studio .NET 2005
SQL Developer 1.5.1
Oracle client 10g connecting to an Oracle 9i release 2 server
Any pointers to the right direction or alternate migration solutions would be great.
Edit: I am highly suspicious that Visual Studio was connecting to this file through SQL Server Express and not my standard edition copy, and it is therefore not attached to the database, the solution is not looking entirely easy, so an alternate migration may be a better choice. Thanks in advance for any help.
Edit: Well my suspicions were confirmed. I attempted several solutions. First of which being the MS SQL Express publishing wizard so that I could publish to SQL and run the script via Toad or SQL Plus; however, it only targets MS SQL Server 2000 or 2005 which would result in a lot of hand editing in terms of migration. Attempting to find a script converter did not help as they all either failed outright or demanded a connection to the datbase via ODBC or JDBC (which doesn't support SQL Express' less than clever attach on connection ideas). This led me to the alternate solution of trying to attach the file to my main database and connect to it; however, the SQL Server command prompt has some sort of permissions issue with my office security setting (though I can edit files fine) and results in failure.
I think it is about time to throw in the towel and just work it out by hand. This would be greatly expedited by any visual database tools that generate code from ER diagrams if you happen to know of a freeware solution. We lack an internal copy of Oracle Designer and the free license only permits a single prototype. So any suggestions on the front of freebie visual object relational tools and alternate migration ideas would be of great help. Until then I'll be grinding through it with moderate dissatisfaction.
Thanks again.

Mac File Migration Between Windows File Servers (NAS to SAN)

My company has upgraded our Windows based file server from a NAS to a SAN, and I need to know the best method to migrate our Mac files from the old Windows Server to the new Windows Server; do we have to use a Mac to preserve resource fork data?
The last time our IT provider attempted to initiate a Windows file transfer of our Mac files, all resource fork data was lost, zeroing out all fonts associated with job files (very bad).

Resource forks appear as normal files and directories to Windows systems. If you copy all your directories and files with complete content directly from the old server to the new server (which is much faster than copying them from one server to the other using a client machine), you also copy the resource forks.
I suggest copying (not moving) all data directly from server to server and check after that if the resource forks are still in good state. If not, you still have the (working) data on the old server and can try out other methods.

Mail file getting large. How to backup and remove?

My Mail file is 500 MB and I want to move, say, anything older than two years to a different location so I can search it and find attachments. The archive function seems to just create a copy of the mailbox. Is there some way to move messages like this?
I have deleted the trash, but the size of my mail file and attachments seems to be bogging Mail down and maybe the system a bit.
Benjamin Barrett
Seattle, WA

When I archive my e-mail, it's about 350 MB, and it seems like it's a bit of a burden on Mail.
It shouldn't be. Like I said, I'm almost at 350 MB and it's not a problem. I was able to make a smart mailbox showing everything more than 1 year old, and within seconds had a snappily-scrolling list of nearly 9,000 messages. Are all these e-mails still in your In box, or some other mailbox you use every day? Are they still on the server?
It's possible that I just need a new Mac--this one is about three years old
You're more accustomed to Windows, I bet. Three years isn't much in the Mac world. I've got a nearly 8-year-old Mac that was still in frequent use - and far more functional than any of the 3-year-old Windows machines at my wife's small business - until the hard drive failed a couple days ago. I'll probably replace the drive and let it chug right along for another few years. The only Mac I've ever owned, and used, for less than 7 years was the one I dropped on a concrete floor!
It's clear that Mail won't work for this purpose
Not at all... I'm sure there's something you can do to improve performance. Perhaps there's something wrong with your system or with your Mail data. It's hard to give more specific advice at this point, but the fact is, Mail does work for this purpose for me.

TS3276 server says file too big to send-file says 33MB server says 44MB

I cannot send a short video which is 33.1 MB in the description but the server won't process as it claims the file is too big(44MB) and it can handle only 41MB.
I've tried to compress it but still reads as "too big to send"

You seem focused on the difference between 33 megabytes binary and a 44 megabytes transfer — the messages have to be encoded as SMTP mail was never intended as a binary transfer mechanism — mail servers transfer printable text messages — and the text-encoded attached binary files are inherently going to be larger than the original files.
You're going to have to raise the mail server limits (which requires administrative access to the mail server), or find an alternate means of transferring the file — mail servers aren't very efficient at large transfers, large files tend to blow out mail server storage quotas, and blow out mail files. Or chunk up the file into smaller files, send the chunks independently, and then concatenate the file remotely. (There are tools around to do this — at the command line, have a look at the zipsplit tool — but I'd generally discourage this approach as it adds effort and complexity to the process.)
The usual approach is a file transfer service. Dropbox or SpiderOak or some other file hosting or file transfer service are the most common approaches here, and are also more efficient than the overhead involved with large attachments sent via a mail server. Many of these file-hosting services offer more than enough storage here, and often as part of a free service tier.
Some folks can and do run their own file-hosting services, but that generally involves configuring and managing a server system and the associated network connections.

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", $_;

Migrate only Mail

i recently did a full migration fro my g5 to macbook.
my question is, i now want to only migrate (only) my mail from g5 to macbook again, can i migrate only mail ? and if so, will it update or fully erase my mail and that is already there.
also the same for safari.
thank you

It will erase if you simply drag and drop the Mail and Mail downloads folder from one Users -> yourname -> Library folder to the next. If you import the mailboxes using Mail's File menu -> Import Mailboxes and navigate to the same folder, you shouldn't experience the same problem. Mind you, you will then have duplicate mail in from the import, if you didn't delete from the old machine the mail that you already copied over.
Note: Target Disk Mode is the preferred migration method between PowerPC and Intel ->
http://docs.info.apple.com/article.html?artnum=58583
as it is less likely to cause problems in the long run due to incompatible PowerPC drivers and plugins. This user tip explains how:
http://discussions.apple.com/thread.jspa?threadID=435350&tstart=0
You were fortunate the migration assistant worked off the bat, but it could have left something behind that you don't want.
Message was edited by: a brody
Message was edited by: a brody

How migrate all mail (boxes and accounts) from 10.6.8 on Mavericks (without Migration Assistant)?

How migrate all mail (boxes and accounts) from 10.6.8 on Mavericks (without Migration Assistant)? Install the system (10.9.1) on a blank disk, copied the program and set up manually. Mail accounts and folders does not work to install and configure. Migration Assistant does not want to use, as it copies everything, and you only need to e-mail. Read a lot, but nothing works.

Try reindexing the mailbox. This can take awhile if you have a lot of mail.
Reindex messages.
If that doesn't work try deleting MessageUidsAlreadyDownloaded3.
Quit the application.
You need to look in your user Library. Either hold down the option key while using the Finder “Go To Folder” command and select your user Library in your home folder or use the Finder “Go To Folder” command and enter ~/Library/Mail/V2/Mail Data/MessageUidsAlreadyDownloaded3. Move the file to your desktop.
Open the application and test. If it works okay, delete the file from the desktop.
If the application is the same, return thefile to where you got it from, overwriting the newer ones.
If you prefer to make your User library permanently visible, use the Terminal command found below.
Show User Library
You might want to bookmark the command. I had to use it again after I installed 10.8.5. I have also been informed that if you drag the user library to Finder it will remain visible.

Does anyone have a good server.xml file for tomcat?

I am trying to link apache and tomcat on a RedHat 9 computer. I previously posted a message stating that I could not get tomcat to "automagically" make the configuration files (mod_jk.conf-auto) that all the manuals promised it would. However, I found that my problem was the lack of an ApacheConfig tag in the server.xml file. After looking at my server.xml file, I found that it was much more simplistic than I would hoped = it did not have enough comments or commented out options. It had none of the directives that the manuals said it included by default.
In short, does anyone who has apache and tomcat linked have a server.xml file that I can look at so that I can figure out what I must add to mine to get tomcat working with apache? I would greatly appreciate it if you could copy and paste the whole thing here.
Thank you very much in advance.
Edward S. Rice

Hi!
I am having the Apache-Tomcat4.0 version installed on a Win2000 machine. I am pasting here my server.xml. Hope it will be useful to you. I even didnot do much modifications to my server.xml except for adding a context.
Please come back if problem persists.



<Server port="8005" shutdown="SHUTDOWN" debug="0">


<Service name="Tomcat-Standalone">


<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="60000"/>












<Engine name="Standalone" defaultHost="localhost" debug="0">



<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt"
timestamp="true"/>

<Realm className="org.apache.catalina.realm.MemoryRealm" />





<Host name="localhost" debug="0" appBase="webapps" unpackWARs="true">



<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="common"/>

<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_log." suffix=".txt"
     timestamp="true"/>



          <Context path="/vijay" docBase="D:\Java\servlets" debug="0"/>

<Context path="/manager" docBase="manager"
debug="0" privileged="true"/>

<Context path="/examples" docBase="examples" debug="0"
reloadable="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_examples_log." suffix=".txt"
     timestamp="true"/>
<Ejb name="ejb/EmplRecord" type="Entity"
home="com.wombat.empl.EmployeeRecordHome"
remote="com.wombat.empl.EmployeeRecord"/>

          
<Environment name="maxExemptions" type="java.lang.Integer"
value="15"/>
<Parameter name="context.param.name" value="context.param.value"
override="false"/>
<Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/EmployeeAppDb">
<parameter><name>user</name><value>sa</value></parameter>
<parameter><name>password</name><value></value></parameter>
<parameter><name>driverClassName</name>
<value>org.hsql.jdbcDriver</value></parameter>
<parameter><name>driverName</name>
<value>jdbc:HypersonicSQL:database</value></parameter>
</ResourceParams>
<Resource name="mail/Session" auth="Container"
type="javax.mail.Session"/>
<ResourceParams name="mail/Session">
<parameter>
<name>mail.smtp.host</name>
<value>localhost</value>
</parameter>
</ResourceParams>
</Context>
</Host>
</Engine>
</Service>


<Service name="Tomcat-Apache">
<Connector className="org.apache.catalina.connector.warp.WarpConnector"
port="8008" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="10" debug="0"/>

<Engine className="org.apache.catalina.connector.warp.WarpEngine"
name="Apache" debug="0" appBase="webapps">

<Logger className="org.apache.catalina.logger.FileLogger"
prefix="apache_log." suffix=".txt"
timestamp="true"/>

<Realm className="org.apache.catalina.realm.MemoryRealm" />
</Engine>
</Service>
</Server>

10.9 Server mail public folders missing after upgrade cannot get them back HELP

Help after upgrade my public folders dissapeared when using the same configuration used in previous ML server Mail would not work
Help Please.

Did you enable the ACL plugin (per instructions above) ?
create an ACL file
/Library/Server/Mail/Data/mail/public/dovecot-acl
with the contents something like this:
user=jeff lrwstipekxa
authenticated lri
This would give user jeff full access
authenticated users could drop files, but not read
Thats just an example.
Read-up on it here
http://wiki.dovecot.org/ACL
Make sure you give each subfolder an ACL.
Once setup, new folders created via imap will inherit the ACL from parent.

Migrating server hardware replacement oes11 to oes11sp2

This summer I will be replacing server hardware at one of my schools. Currently it has sles11sp1 / oes11 -- put in in 2012. The patches are up to date for this version, but I have not upgraded/migrated it to a newer version yet. I have played in a test environment with the yast2 wagon migration from sles11sp1/oes11 to sles11sp2/oes11sp1 -- no problems. However trying to find notes on how to do a migration and identity transfer from source server hardware to new target server hardware. Found oes11sp2 migration tool administration guide. I haven't found anything telling me how to setup sles on the target server box ie server name etc. Once I have the target sles server setup, I realize I need to install OES and select the "Novell pre-migration server" option during this installation.
Current source server = sles11sp1/oes11 and has iPrint, Nss and netstorage installed. Installed in tree with oes11 and oes11sp1 servers.
The main tree server has sles11sp2/oes11sp1 on it. We will need to upgrade it to sles11sp3/oes11sp2 this summer. I'm fine with doing the yast2 wagon migration on that server. We just haven't done server hardware replacements for OES-L yet.
Looking for some good (step by step) instructions. ;-)
Thanks
Patty

Originally Posted by amdsbnovell
Thanks Thomas. Just printed the document now. If my current sles11sp1/oes11 server is called testfs for instance, then I need to install the new target server as a sles11sp3 server called tempfs. Then install oes11sp2 into the tree in a temporary location in the tree as a premigration server (for the installation). Then I should be able to follow the instructions. When I do the identity transfer, I'm assuming it renames the sles11sp3 server from tempfs to testfs as well (as that is where oes gets the file server name from)?
Um, sorta. Let's pretend your server name is: OLD and the new one is NEW (temporary NEW name and temporary NEW IP)
OLD: OES11
NEW: OES11 SP2 (assuming you want latest stuff).
Do all your data transfer/consolidations/etc
Then when you do the ID transfer, it will literally transfer the eDir databases (well copy is more correct) from OLD to NEW, you shut off OLD, I think it restarts NEW and renames/changes the servername and IP to what OLD had.
You can choose to install the NEW server with the .ISO separately (ie: Install SLES11 SP3, then after you're done, Add On the OES11 SP2 .ISO), or you may choose to use the integrated DVD and do it all at once, or use the 2 separate ISO and do them at once (but depending upon your installation method, you may not be able to do the 2 separate ISO).
I hope that helps.
I'm about halfway through editing my docs for OES11 SP1 (of course, SP2 is out now) for migrations from OES2 SP3, but the same setup steps basically apply. I think the only things that changed from NW To OES (ie: OES2 to OES11) are DHCP and iPrint migration procedures.
--Kevin

Migrate server mail files

Similar Messages

Maybe you are looking for