"The table was created many years ago over an extended period of
time,...::"
so, its outdated?
i think its better to use postscreen and a regular updated file like
DROP from spamhaus.
i refresh this DROP every hour. so maybe wrong listed candidates are
deleted in the refreshe
Mohsen Pahlevanzadeh:
> //
> ehlo localhost
> 250-plato.example.com
> 250-PIPELINING
> 250-SIZE 3072
> 250-VRFY
> 250-ETRN
> 250-STARTTLS
> 250-AUTH PLAIN LOGIN
> 250-AUTH=PLAIN LOGIN
> 250-ENHANCEDSTATUSCODES
> 250-8BITMIME
> 250 DSN
> ///
>
On Thu, Mar 28, 2013 at 11:15:02AM +0100, Marko Weber | ZBF wrote:
> "The table was created many years ago over an extended period of
> time,...::"
That was what Stan said, yes.
> so, its outdated?
Let's scroll down through the mass of quoting over which you
top-posted and see w
On 3/28/2013 12:12 AM, Noel Jones wrote:
> Yes, first match wins.
This needs to be *immediately* followed by what you stated way down
below, copied here:
> - each smtpd_*_restrictions section must resolve to "permit" (or
> empty) to accept mail. A "permit" in one smtpd_*_restrictions
> section
On Thu, Mar 28, 2013 at 1:19 PM, Stan Hoeppner wrote:
> I don't have the thread archived (it's been 8 years or so), so I'm
> guessing here, but IIRC it took at least a half dozen or more emails
> back-forth before I understood this lack or inheritance. Once I did,
> and realized how much I'd have
On 27 Mar 2013, at 8:32, Gaby L wrote:
Thanks
I have refered to split only postfix functions,but for it ,is need
create coherent users system.
For example if I create one user in gmail system,this user physical is
stored only one central machine then is accesed through diverse
distribute mec
On 3/28/2013 8:03 AM, /dev/rob0 wrote:
> "... maintaining it ..." see? I would think that something which is
> maintained generally isn't outdated. Depends how well the maintainer
> maintains it, of course.
Precisely. Let me add that ISPs introduce new consumer rDNS strings
very infrequently.
