Re: Looking for advise regarding MTA/IMAP/POP server



Hi Scott,
I do not have any experience with SurgeMail.
Recently I used imapsync (http://www.freshports.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
lambert@xxxxxxxxxxxxxx

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

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



Relevant Pages

  • Re: Exchange 2003 Private Store Corruption
    ... I think you're on the right track with creating a new mailbox store. ... Moving mailboxes is one option. ... Online Diagnostic Utility says "Correctable Memory Threshold Exceeded" ... get the server back up and running without the faulty memory installed. ...
    (microsoft.public.exchange.admin)
  • Re: Move Exch. 2000 Ent. to New Hardware
    ... This should help you troubleshoot the PF replication problems. ... Do you have to point the Private Info. Stores to the Public Store on ... > new server BEFORE you replicate the Public Folders from the old server to ... can I do this and then gradually move all of my mailboxes? ...
    (microsoft.public.exchange2000.setup.installation)
  • RE: is there a windows or exchange equivalent of fetchmail?
    ... SBC email account and put it on a local exchange mailbox. ... In SBS Server, we can use the POP3 Connector to ... retrieve incoming email from ISP POP3 mailboxes. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problems with Outlook after Moving Mailboxes
    ... mailboxes from storage group to storage group on the same server, ... We use the Symantec AV for Exchange as well. ... If we move the mailboxes back to the old ...
    (microsoft.public.exchange.admin)
  • Re: Restoring emails from .edb & .stm files
    ... with step-by-step details on how to recover MS Exchange ... of the old server: ... MAKE SURE - YOU DO NOT CREATE MAILBOXES FOR THE USERS ON THIS SERVER ... and Public folder stores.. ...
    (microsoft.public.exchange2000.admin)