> postscreen will query the DNS when the client connects after
> postscreen_dnsbl_ttl has expired. With Postfix 3.1 and later,
> that time is (also) determined by a TTL in the DNS response.
Thanks for the clarification Wietse. 2 questions:
1) Given that DNSBLs in postscreen_dnsbl_sites and smtp
Michael Fox:
> > postscreen will query the DNS when the client connects after
> > postscreen_dnsbl_ttl has expired. With Postfix 3.1 and later,
> > that time is (also) determined by a TTL in the DNS response.
>
> Thanks for the clarification Wietse. 2 questions:
>
> 1) Given that DNSBLs in post
Jerry Kemp:
[ Charset ISO-8859-1 converted... ]
> Yep, I'm replying to an old question.
> ...
>
> OP, just following up, were you able to resolve your issues?
>
> If so, can you post a summary please.
>
> Jerry
>
>
>
>
> On 01/15/15 12:59 PM, post...@outputservices.com wrote:
> > I am at
Some confusion here, probably because I have used the wrong
terminology. When I said I have a content filter that needs to
influence how a message is routed, I meant a content filter that is
implemented as an SMTP proxy sitting between two Postfix instances.
That said, Wietse's response led me to
Rob Maidment:
> Some confusion here, probably because I have used the wrong
> terminology. When I said I have a content filter that needs to
> influence how a message is routed, I meant a content filter that is
> implemented as an SMTP proxy sitting between two Postfix instances.
>
> That said, W
I have an existing email filtering program that currently uses Sendmail as the
MTA. I want to move to using Postfix instead. The filtering program is
implemented as an SMTP proxy. One of its features is to force a message to be
re-routed if it finds certain things in the content of the messag
> On Jun 3, 2016, at 6:48 AM, Rob Maidment wrote:
>
> The SMTP proxy can add an X-header indicating where the message should
> be routed.
> In the upstream Postfix instance I can configure header_checks to
> check for the X-header and return a FILTER response based on the
> header value using a
On 1 Jun 2016, at 9:29, @lbutlr wrote:
On May 31, 2016, at 8:30 PM, Steve Jenkins
wrote:
A quick way to do this is to download postwhite and add web.com to
the list of queried hosts. All their known (published) IPs and CIDRs
wlll be added to your Postscreen whitelist.
Post white looks inter
On 2 Jun 2016, at 12:45, Michael Fox wrote:
So, as I understand it: as long as the weight assigned to a DNSBL in
postscreen is >= postscreen_dnsbl_threshold, then there is no harm in
also
adding the same DNSBL to smtpd_*_restrictions.
True.
But this is not the whole story...
And, convers
The following main.cf, thanks to Noel, blocks mail whose
DNS is misconfigured as follows.
1.) IP -> nothing
2.) IP -> domain -> nothing
3.) IP -> domain -> IP2
It accepts only mail where
4.) IP -> domain -> IP
I find that 1 and 2 block most of the spam, an
I believe postfix uses the envelope From and To in order
determine what to block.
Is there a way to have postfix use the header From and To
instead?
Homer
CEO Lightlink Internet
Homer Wilson Smith Cl
We currently have DKIM signing set up for our servers via opendkim through
a milter interface, which first goes to amavis and then opendkim. However,
this milter is only triggered for mail tagged as "incoming" via a regex,
and that apparently does NOT happen when emails are created via the local
On 6/3/2016 6:39 PM, Homer Wilson Smith wrote:
>
> The following main.cf, thanks to Noel, blocks mail whose
> DNS is misconfigured as follows.
>
> 1.) IP -> nothing
>
> 2.) IP -> domain -> nothing
>
> 3.) IP -> domain -> IP2
>
> It accepts only mail where
>
> 4.)
On 6/3/2016 6:41 PM, Homer Wilson Smith wrote:
>
> I believe postfix uses the envelope From and To in order
> determine what to block.
>
> Is there a way to have postfix use the header From and To
> instead?
The check_sender_access and check_recipient_access maps can only
check the env
> > And, conversely, DNSBLs with
> > weights < postscreen_dnsbl_threshold should not be listed in
> > smtpd_*_restrictions because they could block an email on their own,
> > even
> > though they are not trusted to do so by postscreen.
>
> Not in all cases. Where postscreen by necessity offers lim
15 matches
Mail list logo
