This is a discussion on Re: [courier-users] SMTP Auth within the Courier-Imap forums, part of the Mail Servers and Related category; --===============0405896978== Content-Type: multipart/alternative; boundary="----=_Part_353_28160253.1208449988087" ------=_Part_353_28160253.1208449988087 Content-Type: text/plain; charset=ISO-8859-1 ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
--===============0405896978==
Content-Type: multipart/alternative; boundary="----=_Part_353_28160253.1208449988087" ------=_Part_353_28160253.1208449988087 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Ok that's good. But the problem that I'm seeing is someone externally can connect to this box and spam to our local domain. But to spam through this box you need to auth. Is it possible I am just missing a setting to say sendine internaly or externally needs to auth? Thanks, William On Thu, Apr 17, 2008 at 8:41 AM, Jay Lee <jlee@pbu.edu> wrote: > MrOzone wrote: > > > Im having a bit of trouble trying to configure smtp so Im not a open > > relay to send email externally but also internally too. > > I have a server setup for users on the outside to send email through > > it, but im trying to configure it so that everyone needs to do smtp > > authentication except 1 ip range. Is this possible? > > Users do need to smtp auth to send email through it, but the biggest > > problem is spammers can connect to it and spam our company (to send to our > > local domain you dont need to smtp auth). > > > > Requiring smtp auth to relay is the default for Courier. You can add a > range of IP's that are always allowed to relay by modifying the smtpaccess > file. See the man page at: > > http://www.courier-mta.org/makesmtpaccess.html > > for details on the format of smtpaccess files and the making the data > file. My suggestion though is to require auth for relaying on all but the > dumbest of smtp clients which don't support smtp authentication (i.e. leave > the smtpaccess file as a last ditch workaround). > > Jay > > -- > Jay Lee > Network/Systems Administrator > Information Technology Department > Philadelphia Biblical University > > ------=_Part_353_28160253.1208449988087 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline <div>Ok that's good. But the problem that I'm seeing is someone externally can connect to this box and spam to our local domain. But to spam through this box you need to auth. Is it possible I am just missing a setting to say sendine internaly or externally needs to auth?</div> <div> </div> <div>Thanks,</div> <div>William<br><br></div> <div class="gmail_quote">On Thu, Apr 17, 2008 at 8:41 AM, Jay Lee <<a href="mailto:jlee@pbu.edu">jlee@pbu.edu</a>> wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div> <div></div> <div class="Wj3C7c">MrOzone wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px; BORDER-LEFT: #ccc 1px solid">Im having a bit of trouble trying to configure smtp so Im not a open relay to send email externally but also internally too.<br> I have a server setup for users on the outside to send email through it, but im trying to configure it so that everyone needs to do smtp authentication except 1 ip range. Is this possible?<br> Users do need to smtp auth to send email through it, but the biggest problem is spammers can connect to it and spam our company (to send to our local domain you dont need to smtp auth).<br> </blockquote><br></div></div>Requiring smtp auth to relay is the default for Courier. You can add a range of IP's that are always allowed to relay by modifying the smtpaccess file. See the man page at:<br><br><a href="http://www.courier-mta.org/makesmtpaccess.html" target="_blank">http://www.courier-mta.org/makesmtpaccess.html</a><br> <br>for details on the format of smtpaccess files and the making the data file. My suggestion though is to require auth for relaying on all but the dumbest of smtp clients which don't support smtp authentication (i.e. leave the smtpaccess file as a last ditch workaround).<br> <br>Jay<br><font color="#888888"><br>-- <br>Jay Lee<br>Network/Systems Administrator<br>Information Technology Department<br>Philadelphia Biblical University<br><br></font></blockquote></div><br> ------=_Part_353_28160253.1208449988087-- --===============0405896978== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757...un.com/javaone --===============0405896978== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users --===============0405896978==-- |