On Wed, Apr 12, 2000 at 04:57:37AM +, Juan E Suris wrote:
John White writes:
BTW, when you're ready to scale, check out cubix for their SBC based
chassis. 8 machines in 7U! Add redundant power, a layer 4 switch,
and a multi-host RAID 1+0 to act as the queue, and you're cooking.
On Mon, Apr 10, 2000 at 07:20:03PM -0400, blue wrote:
I am looking at purchasing a new machine to set-up qmail. We are estimating
a build up to
appx 250,000 emails a day. What kind of system (PC) would you recommend for
this
kind of traffic ?
A simple PII/350 with 128mbyte will do just
On Tue, Apr 11, 2000 at 03:25:45PM +0200, Peter van Dijk wrote:
On Mon, Apr 10, 2000 at 07:20:03PM -0400, blue wrote:
I am looking at purchasing a new machine to set-up qmail. We are estimating
a build up to
appx 250,000 emails a day. What kind of system (PC) would you recommend for
Im also in the process of spec'in out some machines.
Hmm. Would that depend on whether the 250K are mostly in or outbound?
If my mails are mostly inbound, (usr dirs over nfs).
It might also depend on what they are using to access the email, if it's
qpopper and /var/mail then I'd want
On Tue, Apr 11, 2000 at 12:30:49PM -0400, Jeff Commando Sherwin wrote:
Im also in the process of spec'in out some machines.
Hmm. Would that depend on whether the 250K are mostly in or outbound?
If my mails are mostly inbound, (usr dirs over nfs).
It might also depend on what
I'd think that the CPU and memory will be fine, but I'd
suggest he gets a couple of spindles so that he can
separate out the queue.
ah! ok. this is the big question. multiple queues.
He said multiple spindles, not multiple queues.
Multiple spindles simply means that
I think you need to give us a better idea of the big picture. The first post
made it sound like a single machine, now you talk about NFS servers, multiple
IP addresses, separate access server, etc.
Fair enough, I thought i was going to be able to sneak this one in as a
small question. I
On Tue, Apr 11, 2000 at 01:01:33PM -0400, Jeff Commando Sherwin wrote:
I think you need to give us a better idea of the big picture. The first post
made it sound like a single machine, now you talk about NFS servers, multiple
IP addresses, separate access server, etc.
Fair enough, I
Ok, some of this is above my head (which obviously needs to be resolved
:) ), but maybe i can clarify more here.
For inbound SMTP you don't need a load balancer or layer 4 switch, simply
use multiple MX entries. Let the DNS do the "load balancing" and let the
sending MTAs figure out when a
For inbound SMTP you don't need a load balancer or layer 4 switch, simply
use multiple MX entries. Let the DNS do the "load balancing" and let the
sending MTAs figure out when a server isn't available.
If you have internal people sending to SMTP servers, that's a case that
can
Is the front end SMTP server doing anything more than relaying? If it's only
relaying then take it out of the picture. It's only adding a point of failure
for you.
no, the front end is not smtp relaying its like an f5 box, essentially
port forwarding to one of many internal ip addresses.
On Tue, Apr 11, 2000 at 02:51:50PM -0400, Jeff Commando Sherwin wrote:
Is the front end SMTP server doing anything more than relaying? If it's only
relaying then take it out of the picture. It's only adding a point of failure
for you.
no, the front end is not smtp relaying its like
Right. I don't see much point in it then for inbound SMTP. Let the DNS and
MX prefs do the job they were designed to do. IP address space isn't *that*
expensive.
its just that our current situation does not yeild me extra ip space. So I
dont have access to it. Therefore, Im useing an f5
On Tue, Apr 11, 2000 at 04:29:23PM -0400, Jeff Commando Sherwin wrote:
Right. I don't see much point in it then for inbound SMTP. Let the DNS and
MX prefs do the job they were designed to do. IP address space isn't *that*
expensive.
its just that our current situation does not yeild
On Tue, Apr 11, 2000 at 08:50:43PM -0700, John White wrote:
tcpserver lets you do this in a couple different ways. First off, you
can set up your tcpserver to load balance qmail instances by originating
IP address. This isn't that attractive unless you have specific stats
in hand on
John White writes:
BTW, when you're ready to scale, check out cubix for their SBC based
chassis. 8 machines in 7U! Add redundant power, a layer 4 switch,
and a multi-host RAID 1+0 to act as the queue, and you're cooking.
This sounds interesting to me. What would be a good example of a
I am looking at purchasing a new machine to set-up qmail. We are estimating
a build up to
appx 250,000 emails a day. What kind of system (PC) would you recommend for
this
kind of traffic ?
thanks !
td
17 matches
Mail list logo
