Re: postsceen and smtpd_recipients_restrictions

2017-02-27 Thread Den1
Peter van der Does wrote
> Spamhaus and others limit the replies they get from large DNS
> providers[1], like Wietse said.
> 
> You can overcome this issue by running a local forwarding DNS server
> locally on your network and use this as a DSN resolver for your network.
> 
> Peter
> 
> [1] https://www.spamhaus.org/faq/section/DNSBL%20Usage#365

That's a pretty cool idea. Will take a closer look. Thank you!



--
View this message in context: 
http://postfix.1071664.n5.nabble.com/postsceen-and-smtpd-recipients-restrictions-tp89110p89132.html
Sent from the Postfix Users mailing list archive at Nabble.com.


Re: postsceen and smtpd_recipients_restrictions

2017-02-27 Thread Den1
Wietse Venema wrote
> zen.spamhaus.org provides a service that depends the DNS client IP
> address. Low-volume DNS clients get free service, but high-volume
> DNS clients have to pay for a subscription.
> 
> For example, if you use the resolver at a big ISP, or a public
> service like 8.8.8.8 or 4.4.4.4, then zen.spamhaus.org won't work
> well for you, if at all.
> 
>   Wietse

Thank you so much once again for being of assistance. It's utmost clear now.
Much obliged.




--
View this message in context: 
http://postfix.1071664.n5.nabble.com/postsceen-and-smtpd-recipients-restrictions-tp89110p89131.html
Sent from the Postfix Users mailing list archive at Nabble.com.


Re: postsceen and smtpd_recipients_restrictions

2017-02-27 Thread Peter van der Does
> Thank you so much for your directions and guidance. I really do appreciate.
> 
> Although I am getting a bit lost. Is it possible for different clients to
> have the same IP address in such a short period of time as per my logs
> posted?
> 

Spamhaus and others limit the replies they get from large DNS
providers[1], like Wietse said.

You can overcome this issue by running a local forwarding DNS server
locally on your network and use this as a DSN resolver for your network.

Peter

[1] https://www.spamhaus.org/faq/section/DNSBL%20Usage#365


Re: Generate passw with Postfixadmin to add mysql ?

2017-02-27 Thread /dev/rob0
On Mon, Feb 27, 2017 at 07:48:00AM +0100, Maurizio Caloro wrote:
> My setup running with Postfix+Dovecot+Roundcube+Mysql
> 
> Now I need to add the Password function to roundcube and are 
> available now with the Passwd plugin, but I need to know
> 
> with what hash I need to do this? How will postfixadmin
> generate the passwort to add mysql db.

Postfixadmin is a mysql/pgsql frontend which is not a part of 
Postfix, not supported on this list.  I think they have a web
forum for user-to-user support.
-- 
  http://rob0.nodns4.us/
  Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:


RE: postsceen and smtpd_recipients_restrictions

2017-02-27 Thread L . P . H . van Belle
He is multiple times listed. 

See : 
http://multirbl.valli.org/lookup/46.22.210.2.html  
Spamhaus ( listed in DBL Advisory. ) ( aerial.astogle.us.dbl.spamhaus.org ) 

The remote server probley sends "listed at zen.spamhaus.org" but is using DBL 
also. 
https://www.spamhaus.org/dbl/ 


Greetz, 

Louis


> -Oorspronkelijk bericht-
> Van: wie...@porcupine.org [mailto:owner-postfix-us...@postfix.org] Namens
> wie...@porcupine.org
> Verzonden: maandag 27 februari 2017 13:07
> Aan: Postfix users
> Onderwerp: Re: postsceen and smtpd_recipients_restrictions
> 
> Den1:
> > Wietse Venema wrote
> > > Den1:
> > >> 22:19:13 postfix/postscreen[14390]: CONNECT from [46.22.210.20]:58953
> to
> > >> [1.1.1.1]:25
> > >> 22:19:13 postfix/dnsblog[14391]: addr 46.22.210.20 listed by domain
> > >> zen.spamhaus.org as 127.0.0.3
> > >> 22:19:17 postfix/postscreen[14390]: DNSBL rank 1 for
> [46.22.210.20]:58953
> > >> 22:19:17 postfix/postscreen[14390]: DISCONNECT [46.22.210.20]:58953
> > >
> > > The client is listed at zen.spamhaus.org. The client does not talk to
> > > the Postfix SMTP daemon (smtpd).
> > >
> > >> 22:19:18 postfix/postscreen[14390]: CONNECT from [46.22.210.20]:53440
> to
> > >> [1.1.1.1]:25
> > >> 22:19:22 postfix/postscreen[14390]: PASS NEW [46.22.210.20]:53440
> > >> 22:19:22 postfix/smtpd[14403]: connect from
> > >> construct.baladle.us[46.22.210.20]
> > >
> > > The client is NOT LISTED at zen.spamhaus.org, or more likely, you
> > > use multiple DNS servers, some of which get service from spamhaus.org,
> > > and some of which don't get service from spamhaus.org.
> > >
> > >   Wietse
> >
> > Thank you so much for your directions and guidance. I really do
> appreciate.
> 
> That's a nice way of saying you did not understand 99% of the reply.
> 
> > Although I am getting a bit lost. Is it possible for different clients
> to
> > have the same IP address in such a short period of time as per my logs
> > posted?
> 
> zen.spamhaus.org provides a service that depends the DNS client IP
> address. Low-volume DNS clients get free service, but high-volume
> DNS clients have to pay for a subscription.
> 
> For example, if you use the resolver at a big ISP, or a public
> service like 8.8.8.8 or 4.4.4.4, then zen.spamhaus.org won't work
> well for you, if at all.
> 
>   Wietse




Re: postsceen and smtpd_recipients_restrictions

2017-02-27 Thread Wietse Venema
Den1:
> Wietse Venema wrote
> > Den1:
> >> 22:19:13 postfix/postscreen[14390]: CONNECT from [46.22.210.20]:58953 to
> >> [1.1.1.1]:25
> >> 22:19:13 postfix/dnsblog[14391]: addr 46.22.210.20 listed by domain
> >> zen.spamhaus.org as 127.0.0.3
> >> 22:19:17 postfix/postscreen[14390]: DNSBL rank 1 for [46.22.210.20]:58953
> >> 22:19:17 postfix/postscreen[14390]: DISCONNECT [46.22.210.20]:58953
> > 
> > The client is listed at zen.spamhaus.org. The client does not talk to
> > the Postfix SMTP daemon (smtpd).
> > 
> >> 22:19:18 postfix/postscreen[14390]: CONNECT from [46.22.210.20]:53440 to
> >> [1.1.1.1]:25
> >> 22:19:22 postfix/postscreen[14390]: PASS NEW [46.22.210.20]:53440
> >> 22:19:22 postfix/smtpd[14403]: connect from
> >> construct.baladle.us[46.22.210.20]
> > 
> > The client is NOT LISTED at zen.spamhaus.org, or more likely, you
> > use multiple DNS servers, some of which get service from spamhaus.org,
> > and some of which don't get service from spamhaus.org.
> > 
> > Wietse
> 
> Thank you so much for your directions and guidance. I really do appreciate.

That's a nice way of saying you did not understand 99% of the reply.

> Although I am getting a bit lost. Is it possible for different clients to
> have the same IP address in such a short period of time as per my logs
> posted?

zen.spamhaus.org provides a service that depends the DNS client IP
address. Low-volume DNS clients get free service, but high-volume
DNS clients have to pay for a subscription.

For example, if you use the resolver at a big ISP, or a public
service like 8.8.8.8 or 4.4.4.4, then zen.spamhaus.org won't work
well for you, if at all.

Wietse


Re: postfix/amavis not scanning email

2017-02-27 Thread chaouche yacine
> 1) On the Lenny server, the main.cf content_filter sent mail to 10028, the
> relay port for dkim_proxy_out, and this system worked!  I might be able to
> accept sending to the listening port, but the relay port just doesn't make
> sense to me.

Unless you have the old config and log files, we can only make (likely false) 
assumptions, so it won't help here. Also, if that system is gone, you can't 
test assumptions by changing this or that. A dead end IMHO.

> 2) On the current system, the main.cf content_filter configured for 10024 or
> 10028 seems to be totally inert, 

Because mail gets caught by pickup before it has a chance to go through the 
content filter on port 10024. I don't know if this behavior can be changed (I'm 
thinking about filters vs milters ?). 

> not doing anything at all for mail received
> from the outside.  It's only when I loop back to 10024 after the pickup
> filter that messages are scanned.

pickup comes very early in the pipe. These are handwritten notes I took when I 
was learning how e-mail works, it would be nice to have feedback on them ? 
http://imgur.com/a/Asyqr

-- Yassine