Re: Different SMTP AUTH options and credentials for different clients

2016-06-23 Thread Wietse Venema
Rob Maidment: > > In master.cf: > > > > smtp inet . . . . . postscreen -o smtpd_service_name=blah > > blah pass . . . . . smtpd > > > > See postscreen(8) and postconf(5) manpages for details. > > > > Wietse > > Thanks, I don't know how I didn't spot that. > > Do you think it's fe

Re: Different SMTP AUTH options and credentials for different clients

2016-06-23 Thread Rob Maidment
> In master.cf: > > smtp inet . . . . . postscreen -o smtpd_service_name=blah > blah pass . . . . . smtpd > > See postscreen(8) and postconf(5) manpages for details. > > Wietse Thanks, I don't know how I didn't spot that. Do you think it's feasible to enhance postscreen to hand o

Re: How to correctly blacklist an IP for postscreen?

2016-06-23 Thread Wietse Venema
Quanah Gibson-Mount: > --On Wednesday, June 22, 2016 11:08 PM -0700 Quanah Gibson-Mount > wrote: > > > I added an IP to the postscreen blacklist, but it still gets passed to > > SMTPD? > > Never mind, blacklist action was set to ignore instead of enforce... Fixed. Yes, the "try before you buy"

Re: postconf(5) typo

2016-06-23 Thread Wietse Venema
Stefan Jakobs: > Hi Wietse, > > At the beginning (line 10) of the postconf manual it says: > > "The expressions "${name:value}" and "${name?{value}}" are replaced with > "value" when "$name" is empty." > > I guess it should be (? replaced by a :): > > "The expressions "${name:value}" and "${na

postconf(5) typo

2016-06-23 Thread Stefan Jakobs
Hi Wietse, At the beginning (line 10) of the postconf manual it says: "The expressions "${name:value}" and "${name?{value}}" are replaced with "value" when "$name" is empty." I guess it should be (? replaced by a :): "The expressions "${name:value}" and "${name:{value}}" are replaced with "va