SMTP-AUTH but use more then one mysql server

2009-02-16 Thread Vahric MUHTARYAN
Hello, I configured my postfix with sasl-cyrus support and configured auth-smtp like below smtpd_sasl_auth_enable = yes smtpd_sasl_security_options=noanonymous smtpd_sasl_local_domain = broken_sasl_auth_clients=yes smtpd_recipient_restrictions = permit_sasl_authenticated, permit_myn

Re: SMTP-AUTH but use more then one mysql server

2009-02-16 Thread Andreas Winkelmann
> -- content of /usr/lib/sasl2/smtpd.conf -- > > pwcheck_method: auxprop > > mech_list: login plain > > auxprop_plugin: sql > > sql_hostnames: xx.xx.xx.xx > > sql_user: --- replaced --- > > sql_passwd: --- replaced --- > > sql_database: merakdb > > sql_select: select U_Password from users where U_M

RE: SMTP-AUTH but use more then one mysql server

2009-02-16 Thread Vahric MUHTARYAN
Hello, Thanks for information Andreas, For all postfix users be careful when you write down, it should be like below. sql_hostnames: (xx.xx.xx.xx:3306,yy.yy.yy.yy:3306) Regards Vahric -Original Message- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On B

Re: Yahoo and spams

2009-02-16 Thread Gerard
On Mon, 16 Feb 2009 05:01:21 +0100 (CET) "Benny Pedersen" wrote: > >On Sat, February 14, 2009 12:24, Robert Schetterer wrote: >> their Antispam systems are simply broken in my eyes > >http://rfc-ignorant.org/tools/lookup.php?domain=yahoo.com > >just dont use email that are rfc-i listed http://rf

postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread richard lucassen
When creating a db with 2.3.8 (Debian Etch), I get an error when reading the db file with 2.5.5 (Debian Lenny): postmap -q example.com hash:/tmp/valid_senders1 postmap: fatal: open database /tmp/valid_senders1.db: Invalid argument I have to explicitely build the db with the 2.5.5. version. Has so

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Ralf Hildebrandt
* richard lucassen : > When creating a db with 2.3.8 (Debian Etch), I get an error when reading > the db file with 2.5.5 (Debian Lenny): > > postmap -q example.com hash:/tmp/valid_senders1 > postmap: fatal: open database /tmp/valid_senders1.db: Invalid argument > > I have to explicitely build the

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread richard lucassen
On Mon, 16 Feb 2009 13:46:17 +0100 Ralf Hildebrandt wrote: > * richard lucassen : > > When creating a db with 2.3.8 (Debian Etch), I get an error when > > reading the db file with 2.5.5 (Debian Lenny): > > > > postmap -q example.com hash:/tmp/valid_senders1 > > postmap: fatal: open database /tmp

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Ralf Hildebrandt
* richard lucassen : > > So it's a Debian bug (maps need to be rebuilt). Or you could use cdb > > instead. > > Ok, thnx! It's our famous Linux downward compatability :-( Not really, it's you poor choice of a maptype :) But on the other hand it's really hard to predict the future. -- Ralf Hild

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread richard lucassen
On Mon, 16 Feb 2009 14:00:25 +0100 Ralf Hildebrandt wrote: > > Ok, thnx! It's our famous Linux downward compatability :-( > > Not really, it's you poor choice of a maptype :) Duh! :) > But on the other hand it's really hard to predict the future. If the future was predictable, I would certai

Limit the number of recipient

2009-02-16 Thread Marco Tchi Hong
Hello, I'd like to limit the number of recipient a user can specify when sending mail via our SMTP server. In other words, I'd like to refuse the mail if the number of recipients exceeds 10 for example. To do so, I set smtpd_recipient_limit to 10. To which value should I set smtpd_recipie

Re: Limit the number of recipient

2009-02-16 Thread Sahil Tandon
On Mon, 16 Feb 2009, Marco Tchi Hong wrote: > I'd like to limit the number of recipient a user can specify when sending > mail via our SMTP server. > > In other words, I'd like to refuse the mail if the number of recipients > exceeds 10 for example. > > To do so, I set smtpd_recipient_limit to 1

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Harakiri
--- On Mon, 2/16/09, Ralf Hildebrandt wrote: > From: Ralf Hildebrandt > Subject: Re: postmap changed between 2.3.8 and 2.5.5 > To: postfix-users@postfix.org > Date: Monday, February 16, 2009, 8:00 AM > * richard lucassen : > > > > So it's a Debian bug (maps need to be > rebuilt). Or you could

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Ralf Hildebrandt
* Harakiri : > the default for postfix is this: > > default_database_type = hash > > hash == berkly db? that would mean its a poor choice by postfix itself Not if you compile it yourself :) -- Ralf Hildebrandt (ralf.hildebra...@charite.de) snick...@charite.de Postfix - Einrichtung, B

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Wietse Venema
Harakiri: > --- On Mon, 2/16/09, Ralf Hildebrandt wrote: > > > From: Ralf Hildebrandt > > Subject: Re: postmap changed between 2.3.8 and 2.5.5 > > To: postfix-users@postfix.org > > Date: Monday, February 16, 2009, 8:00 AM > > * richard lucassen : > > > > > > So it's a Debian bug (maps need to

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Victor Duchovni
On Mon, Feb 16, 2009 at 10:14:21AM -0500, Wietse Venema wrote: > > hash == berkly db? that would mean its a poor choice by postfix itself > > There are plenty platforms where the on-disk format of Berkeley DB > database files is stable across many operating system releases. And the only sensible

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Harakiri
--- On Mon, 2/16/09, Wietse Venema wrote: > > There are plenty platforms where the on-disk format of > Berkeley DB > database files is stable across many operating system > releases. > > Wietse that seems correct - i cant verify the issue of the OP - i created a transport map db in e

Re: rbl clients.

2009-02-16 Thread Linux Addict
Thank you everyone!! Lot of information. On Fri, Feb 13, 2009 at 4:44 PM, Res wrote: > On Thu, 12 Feb 2009, Linux Addict wrote: > > reject_rbl_client blackholes.easynet.nl,reject_rbl_client >> cbl.abuseat.org,reject_rbl_client proxies.blackholes.wirehub.net, >> reject_rbl_client bl.spamc

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread richard lucassen
On Mon, 16 Feb 2009 07:20:58 -0800 (PST) Harakiri wrote: > that seems correct - i cant verify the issue of the OP - i created a > transport map db in etch, and verified it in lenny postfix 2.5.x - i > didnt have the issue. > > Seems like the OP doesnt have a full lenny upgrade?! A new install o

spams from live.com

2009-02-16 Thread bharathan kailath
hi is there anyway i can prevent spams from live.com with internal filters of postfix help appreciated thanks

Re: spams from live.com

2009-02-16 Thread Benny Pedersen
On Mon, February 16, 2009 21:49, bharathan kailath wrote: > is there anyway i can prevent spams from live.com with internal > filters of postfix help appreciated http://rfc-ignorant.org/tools/lookup.php?domain=live.com dont use rbl, there might be legit users at live.com :/ -- http://localhos

Re: spams from live.com

2009-02-16 Thread mouss
bharathan kailath a écrit : > hi > is there anyway i can prevent spams from live.com > with internal filters of postfix use a content filter (spamassassin, ... etc).

Re: spams from live.com

2009-02-16 Thread Michael J Wise
On Feb 16, 2009, at 12:49 PM, bharathan kailath wrote: hi is there anyway i can prevent spams from live.com with internal filters of postfix Do you have any examples to share? And yes, SpamAssassin would probably be a good thing to read up on. You might want to also look at milter-spamc and

Re: spams from live.com

2009-02-16 Thread postfix
At 03:49 PM 2/16/2009, bharathan kailath wrote: hi is there anyway i can prevent spams from live.com with internal filters of postfix help appreciated thanks if you just have a specific site, you can always use something like check_client_access under smtpd_recipient_restrict