Looking for advise regarding MTA/IMAP/POP server

I've been trying to find the time to install a
Postfix/Cyrus-IMAP server
for a year now.  I currently have one Postfix/Courier-IMAP
server where
I like Postfix.  Courier does it's job but I don't
particularly care
for it.  I have another Sendmail/IMAP-UW server where I
don't *like*
anything but can get along with Sendmail.  IMAP-UW is, well,
IMAP-UW.

The biggest issue is the migration of the data from three
existing
servers.  In the interests of just getting it done, I've
been looking at
commercial alternatives.

I've run across SurgeMail by NetWin which is only $670 for
the
license level that we would need.  Their Anti-Virus add on
license is
slightly more expensive, but I already have a cluster of
Barracuda
Networks Spam Firewall boxes sitting out in front.  NetWin
has been
around a while and they claim to have an auto-migration
feature.

Unfortunately, they don't seem to have a high opinion of
FreeBSD 4
through 6 for server processes such as their's which use
both forking
and threads.

So, I'm looking for other ISP's experiences with SurgeMail,
preferably
on FreeBSD, or similar type packages that make migration
simple.  We
have around 8,000 e-mail accounts and have about a little
under 200
domains.

How do you like the logs for finding out which of your users
is infected
with the mass-mailing virus of the week, or being able to
tell the
customer that the message they claim is lost on the server
was received
at blah blah time and the customer's work computer, with IP
address
blither, deleted the message from the server at blah blah
time.

One of our existing mail servers, which came from an
acquisition, has
lots of logs but it is almost impossible to follow a message
completely
through the system. 

-- 
Scott Lambert                    KC5MLE                     
 Unix SysAdmin
lambertlambertfam.org

_______________________________________________
freebsd-ispfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to
"freebsd-isp-unsubscribefreebsd.org"

Hi Scott,
I do not have any experience with SurgeMail.
Recently I used imapsync (http://www.f
reshports.org/mail/imapsync/)
to migrate about 250 mailboxes from courier imap to
dovecot.
I wrote a little perl skript to fetch the login credentials
from MySQL  
and then sync each mailbox.
Canīt say much about performance or scalability, but I have
read of  
people migrating/syncing about 20k+ mailboxes with it.

Regards

Leander

> I've been trying to find the time to install a
Postfix/Cyrus-IMAP  
> server
> for a year now.  I currently have one
Postfix/Courier-IMAP server  
> where
> I like Postfix.  Courier does it's job but I don't
particularly care
> for it.  I have another Sendmail/IMAP-UW server where I
don't *like*
> anything but can get along with Sendmail.  IMAP-UW is,
well, IMAP-UW.
>
> The biggest issue is the migration of the data from
three existing
> servers.  In the interests of just getting it done,
I've been  
> looking at
> commercial alternatives.
>
> I've run across SurgeMail by NetWin which is only $670
for the
> license level that we would need.  Their Anti-Virus add
on license is
> slightly more expensive, but I already have a cluster
of Barracuda
> Networks Spam Firewall boxes sitting out in front. 
NetWin has been
> around a while and they claim to have an auto-migration
feature.
>
> Unfortunately, they don't seem to have a high opinion
of FreeBSD 4
> through 6 for server processes such as their's which
use both forking
> and threads.
>
> So, I'm looking for other ISP's experiences with
SurgeMail, preferably
> on FreeBSD, or similar type packages that make
migration simple.  We
> have around 8,000 e-mail accounts and have about a
little under 200
> domains.
>
> How do you like the logs for finding out which of your
users is  
> infected
> with the mass-mailing virus of the week, or being able
to tell the
> customer that the message they claim is lost on the
server was  
> received
> at blah blah time and the customer's work computer,
with IP address
> blither, deleted the message from the server at blah
blah time.
>
> One of our existing mail servers, which came from an
acquisition, has
> lots of logs but it is almost impossible to follow a
message  
> completely
> through the system.
>
> -- 
> Scott Lambert                    KC5MLE                
      Unix  
> SysAdmin
> lambertlambertfam.org
>
> _______________________________________________
> freebsd-ispfreebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-isp
> To unsubscribe, send any mail to
"freebsd-isp-unsubscribefreebsd.org"

_______________________________________________
freebsd-ispfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to
"freebsd-isp-unsubscribefreebsd.org"

On Friday 15 February 2008, Leander wrote:
> Hi Scott,
> I do not have any experience with SurgeMail.
> Recently I used imapsync
> (http://www.f
reshports.org/mail/imapsync/) to migrate about
> 250 mailboxes from courier imap to dovecot. I wrote a
little
> perl skript to fetch the login credentials from MySQL
and then
> sync each mailbox.
> Canīt say much about performance or scalability, but I
have
> read of people migrating/syncing about 20k+ mailboxes
with it.

We used dovecots PostLoginScripting with 
courier-dovecot-migrate.pl to convert the Mailboxes at the
first 
login time. See http://wik
i.dovecot.org/Migration/Courier. 
170'000 mailboxes were migrated from courrier to dovecot
this 
way.

For other Systems have a look at 
http://wiki.dovecot
.org/Migration

Have fun,

Michael
_______________________________________________
freebsd-ispfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to
"freebsd-isp-unsubscribefreebsd.org"

Hi, All

I have a problem redirecting com2/console on scale outs from
Rackable  
systems and kicking those boxes.
If any body could shed some light how to do that.

here is my problem:

I have a project kicking freebsd 7.0 using tftp, i have
successfully  
done it on vmware, every thing works fine as expected.
but when i am kicking scale out tftp not calling rest of the
files  
after 'pxeboot', in contrary i can see vmware pulling
pxeboot and then  
config files and then kernel.

with scale out it's just stops at pxeboot. i am looking at
the logs of  
tftp servers.
Scale out is remotely located, and if i can't find solution
i would  
have to drive to far away :-(.
another problem is com2 redirection, but i think it's not
even getting  
to that point.

So, here is the question if any one have had any experiences
with  
freebsd and rackables scale outs, please share your
experiences.

Thanks.
--Edward
_______________________________________________
freebsd-ispfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to
"freebsd-isp-unsubscribefreebsd.org"