"Rob Hines Jr." <[EMAIL PROTECTED]> writes:
> I sent an email about problems with my users reaching my SMTP server via
> Earthlink dialup. Several responded and from that I found that Earthlink
> was blocking SMTP except to their mail server.
>
> My immediate idea for a solution was to run a second qmail-smtpd on
> another port that Earthlink is not blocking. My question is, can I run
> multiple instances of qmail-smtpd concurrently on different ports
> through supervise and tcpserver, or do I need to do something wierd to
> make this work?
My first question is why? Is there any GOOD reason why your users
can't just use Earthlink's own SMTP server? That's the way it's meant
to work. The only good reason I know of to not use the server your
ISP intends you to use is if they stop you using non-provider From:
headers. Earthlink doesn't do that.
Well, OK, two other reasons (good or otherwise) that I hear are,
firstly, so that all dialup users' configurations can be set up the
same, and secondly, to make support easier (so you don't get blamed
for the ISP's problems).
If you HAVE to do it, then there should be no reason why you can't run
tcpserver/qmail-smtpd from several different ports. After all, a new
qmail-smtpd is invoked for each connection, so it already handles
concurrency.
I hope for your sake that you are using a GOOD method of ensuring your
email servers are not open relays.
-Matt
--
| Matthew J. Brown - Senior Network Administrator - NBCi Shopping |
| 1983 W. 190th St, Suite 100, Torrance CA 90504 |
| Phone: (310) 538-7122 | Work: [EMAIL PROTECTED] |
| Cell: (714) 457-1854 | Personal: [EMAIL PROTECTED] |
