Qmail
[Top] [All Lists]

Re: port 587

To: Qmail mailing list <qmail@list.cr.yp.to>
Subject: Re: port 587
From: Matt Simpson <net-qmlist@jmatt.net>
Date: Thu, 8 Mar 2007 19:33:22 -0500
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
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
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=jmatt.net; b=Wg8cOCI7M4Z03Tskw8+m2ILIXhD3sv65kAtfj3eAatA7Abl5Vbe/Otw2Vk94GTgwBVSCOY8HXnMkkPqFGItjU1l18h8suaKl2kiBFRVFyO4BI02oxLLcmTdBY4eRAE+N6KfbGBZ6dilq4/VlQyXn6Gh7RxpBkatJd9A3ayHoCIA=; h=Received:Mime-Version:Message-Id:In-Reply-To:References:Date:From:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
Domainkey-status: bad
In-reply-to: <45F06F2B.4030201@sysec.com.mx>
Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
References: <45E84863.7000707@sysec.com.mx> <20070302180030.GA25184@nachos.phaseit.com> <p06240601c20e19204931@chowder.foxhunters.org> <45F06F2B.4030201@sysec.com.mx>
At 2:16 PM 3/8/07, Mario Salazar Baños wrote:
I have a question, could be used to spam this port?

Any port accepting SMTP traffic can be spammed if you don't take adequate precautions.

 or what is the benefit of use this port?

Well, technically, you can use it for anything you want. But its conventional use is an SMTP server used only to relay outbound mail from your clients. The benefit of this is that it separates your outbound traffic from the inbound traffic on port 25. It also allows your clients to relay mail through your server even if they are connecting through an ISP which blocks outbound port 25, which is becoming more common.

This allows you to use different control techniques on the different ports. For example, you could (and probably should) require any client connecting to port 587 to authenticate. You would probably not want to have such a restriction on port 25, unless you have some very unusual requirements for inbound mail.

If you require authentication on port 587, then you can eliminate some other spam control techniques that you might use on port 25 (such as RBL), if they are causing problems for your clients. If the client has authenticated, then you know you want to accept mail from him, even if he's in an IP block which has been accused of spamming.


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