4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] SMTP authentication
FromSent OnAttachments
Pavel M. RebrovMay 19, 2004 11:33 pm 
Robert HortonMay 20, 2004 8:48 am 
David NewallMay 20, 2004 11:53 am 
Robert HortonMay 20, 2004 1:06 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] SMTP authenticationActions...
From:Robert Horton (tre@agarithil-nost.com)
Date:May 20, 2004 1:06:44 pm
List:net.sourceforge.lists.courier-users

*facepalms*

Well...how embarrassing! Ok..THAT problem is closer to being solved. So now a followup : There is still one domain, ms[somenumber].hinet.net that courier still accepts and delivers email for. I have no idea who they are. I notice that the smptaccess files usually take IP addys, but can they also take named domains? In other words can I do:

*.hinet.net deny

and have it work?

Thanks! On Thursday, May 20, 2004, at 11:52 US/Pacific, David Newall wrote:

On Fri, 2004-05-21 at 01:18, Robert Horton wrote:

Quick question: If I set up SMTP so that users have to use a password to send mail, would that end the flood of spammers attempting to use me as a relay?

Sounds horribly like spammers are succeeding in using you as a relay! Courier, out of the box, doesn't relay mail. You have to add an entry to (a file in) smtpaccess, specifying the IP addresses that are allowed to use you as a relay, for example

a.b.c/n allow,RELAYCLIENT

Hope you haven't got RELAYCLIENT for all addresses!

If you /have/ to allow relaying from any address, perhaps because you have roaming users, then you posilutely must require authentication! Absotively!