> Note that there is no call to policyd in your restrictions. This is why
> it's not working.
OK, that's fixed and solved. The problem (as always happens) was very
easy: I also had a smtp_recipient_restrictions parametee in my #SASL
section, which is _after_ #POLICYD section; so, the results o
Jordi Espasa Clofent wrote:
>> You have something in your config that is permitting the message BEFORE
>> policyd is called.
>
> Mmmm... maybe Amavisd-new ¿?¿?¿?
>
>> Send your current postconf -n again.
>> Just run postconf -n from the command line, not from a specific folder.
>> Your either
> You have something in your config that is permitting the message BEFORE
> policyd is called.
Mmmm... maybe Amavisd-new ¿?¿?¿?
> Send your current postconf -n again.
> Just run postconf -n from the command line, not from a specific folder.
> Your either editing an incorrect main.cf file or j
Jordi Espasa Clofent wrote:
> After all, the same:
>
> Aug 28 17:57:26 mail policyd: starting policyd v1.81
> Aug 28 17:57:26 mail policyd: DEBUG: fd: 0: rlimit: max: 4097 cur: 4097
> Aug 28 17:57:26 mail policyd: connecting to mysql database: 127.0.0.1
> Aug 28 17:57:26 mail policyd: connected..
After all, the same:
Aug 28 17:57:26 mail policyd: starting policyd v1.81
Aug 28 17:57:26 mail policyd: DEBUG: fd: 0: rlimit: max: 4097 cur: 4097
Aug 28 17:57:26 mail policyd: connecting to mysql database: 127.0.0.1
Aug 28 17:57:26 mail policyd: connected..
Aug 28 17:57:46 mail postfix/smtpd[31466
Benny Pedersen wrote:
> On Tue, August 28, 2007 12:26, Geert Hendrickx wrote:
>
>> That means that you're greylisting your sasl_authenticated users, which may
>> not be desirable (I suppose they are running Outlook and not an MTA).
>
> ups, policyd so need to stop greylistning sasl users
>
> no
Jordi Espasa Clofent wrote:
> Benny Pedersen escribió:
>> On Tue, August 28, 2007 11:52, Jordi Espasa Clofent wrote:
>>
>>> I want to use several features (greylisting, throttling...) but,
>>> obviosly, the main problem is I can test with it if policyd is not
>>> working fine.
>> smtpd_recipient_re
On Tue, August 28, 2007 13:40, Jordi Espasa Clofent wrote:
>> is postfix running behind a router ?
> yes.
postconf -e 'proxy_interfaces=wanipgoeshere'
>> your mynetworks have no wan ip, and you have no proxy_interface =
postfix need to have sign of the wan ip in one of them, but not both for
the
> is postfix running behind a router ?
yes.
> your mynetworks have no wan ip, and you have no proxy_interface =
>
> postfix need to have sign of the wan ip in one of them, but not both
>
> for the test
>
> smtpd_recipient_restrictions =
> reject_unlisted_recipient,
> check_policy_service in
On Tue, August 28, 2007 12:26, Geert Hendrickx wrote:
> That means that you're greylisting your sasl_authenticated users, which may
> not be desirable (I suppose they are running Outlook and not an MTA).
ups, policyd so need to stop greylistning sasl users
not a config error in postfix
> You
On Tue, August 28, 2007 12:14, Jordi Espasa Clofent wrote:
> Benny Pedersen escribió:
>> On Tue, August 28, 2007 11:52, Jordi Espasa Clofent wrote:
>>
>>> I want to use several features (greylisting, throttling...) but,
>>> obviosly, the main problem is I can test with it if policyd is not
>>> wor
On Tue, Aug 28, 2007 at 12:21:43PM +0200, Benny Pedersen wrote:
>
> On Tue, August 28, 2007 11:52, Jordi Espasa Clofent wrote:
>
> > I want to use several features (greylisting, throttling...) but,
> > obviosly, the main problem is I can test with it if policyd is not
> > working fine.
>
> smtpd
Benny Pedersen escribió:
> On Tue, August 28, 2007 11:52, Jordi Espasa Clofent wrote:
>
>> I want to use several features (greylisting, throttling...) but,
>> obviosly, the main problem is I can test with it if policyd is not
>> working fine.
>
> smtpd_recipient_restrictions =
> permit_mynetwork
On Tue, August 28, 2007 11:52, Jordi Espasa Clofent wrote:
> I want to use several features (greylisting, throttling...) but,
> obviosly, the main problem is I can test with it if policyd is not
> working fine.
smtpd_recipient_restrictions =
permit_mynetworks,
reject_unlisted_recipient,
check
> incoming mail would pass through policyd unless they were permitted by
> an earlier check which was not the case in your config.
> Post a postconf -n of your configuration and we can see if there are
> other bypasses. Also, you need to explain exactly what features your
> wanting to use (grey
Jordi Espasa Clofent wrote:
>> Note here your using permit_sasl_authenticated. A sasl authenticated
>> user will be permitted here and never reach the policy service. You
>> would need to move the policy check above the permit_sasl option.
>
> Ok, but it doesn't solve the problem. If I move th
> Note here your using permit_sasl_authenticated. A sasl authenticated
> user will be permitted here and never reach the policy service. You
> would need to move the policy check above the permit_sasl option.
Ok, but it doesn't solve the problem. If I move this config line I get
that _MY_ use
Note postconf -n works best.
Jordi Espasa Clofent wrote:
> Sorry Aslan, I've not seen "where" word; my complete main.cf is:
> # restictions
> smtpd_recipient_restrictions =
> permit_sasl_authenticated, #if you use sasl
> permit_mynetworks,
> reject_unauth_de
Sorry Aslan, I've not seen "where" word; my complete main.cf is:
# about names
mydomain = opengea.org
myhostname = mail.opengea.org
myorigin = $myhostname
# basics
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
debug_peer_level = 4
mail_owne
Yes, I've done:
# restrictions
smtpd_recipient_restrictions =
permit_sasl_authenticated, #if you use sasl
permit_mynetworks,
reject_unauth_destination,
check_policy_service inet:127.0.0.1:10031,
permit
smtpd_recipient_limit = 10
smtp
Hi Jordi,
Where did you put the line 'check_policy_service inet:127.0.0.1:10031'
at you main.cf?
best regards
--
Aslan Carlos de M. Ramos
Network Administrator
K8 Networks, Digirati Networks , Hostnet Web hosting
Phone : +55(21)2233-5950 tie-line:29
Mobile : +55(21)9989-4932
Skype : aslancarl
Thank you Cami; now this issue it's fixed but a problem remains: policyd
seems does not work.
I look at maillog file and I see that policyd is charged correctly:
[]
Aug 27 16:39:38 mail policyd: config: triplet timeout> 240
Aug 27 16:39:38 mail policyd: config: optin/optout> 0
Aug 27 16:39:3
Jordi Espasa Clofent wrote:
>
> #
> # port to bind to:
> #
> # port which the policy daemon will listen on
> #
> BINDPORT=10031
>
> I think this is correct and there is not any service in this port:
>
> [EMAIL PROTECTED] ~]# netstat -punta | grep LISTEN
> tcp0 0 127.0.0.1:10024
Hi all,
Useful info:
[EMAIL PROTECTED] ~]# uname -a
Linux mail 2.6.18-8.1.8.el5.centos.plusxen #1 SMP Sun Jul 15 12:38:24
EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
maillog file shows the next error:
Aug 27 11:56:28 mail policyd: fatal: bind(): Address already in use
Well, in my policyd.conf fil
24 matches
Mail list logo
