Qmail
[Top] [All Lists]

Re: two instance of smtp (port 25 and port 587)

To: qmail@list.cr.yp.to
Subject: Re: two instance of smtp (port 25 and port 587)
From: "Suhaime Raeze" <suhaime@ramunia.com>
Date: Sun, 20 May 2007 02:10:32 +0800 (MYT)
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-qmail@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list qmail@list.cr.yp.to
Importance: Normal
In-reply-to: <200705191648.42850.ar-djblists@nwdb.co.uk>
Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
References: <464EC8A4.2060909@oliwel.de> <55802.60.53.25.11.1179585842.squirrel@mail.ramunia.com> <200705191648.42850.ar-djblists@nwdb.co.uk>
Reply-to: suhaime@ramunia.com
User-agent: SquirrelMail/1.4.9a
Hi...

thanks for clearing it up.....however can u provide ways how to go about
on how to implement it...


THanks

> On Saturday 19 May 2007 15:44, Suhaime Raeze wrote:
>> it's been awhile since i post a question...i was reading an article
>> the use of submission port 587 for smtp. Question is can we run two
>> instance of smtp (port 25 and port 587) on a qmail server?
>>
>>
>> Port 25 for internal user
>> Port 587 for mobile user to connect to the qmail
>>  server
>>
>> im running qmail on a fc4 using qmailrocks as a guide..
>
> Yes, it's no problem to have multiple SMTP instances.
>
> Periodically this list gets questions from people using qmailrocks who
> have run into problems, with qmailrocks being perhaps too ambitious
> in including too many patches (or using ones that aren't robust). You
> may like to consider using a life-with-qmail type setup instead.
>
> cheers,
>
> Andrew.
> --
> ======================================================================
>      Network Design & Build          http://www.nwdb.co.uk/
>
>  * Custom email solutions * Systems Administration * Networking
> ======================================================================
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>



<Prev in Thread] Current Thread [Next in Thread>