On 26.08.2010 02:47, Security Admin (NetSec) wrote:
Is there an existing file or a weblink that would list the current accepted
global root CAs? Since the only one in the exchange.pem file is from my
Exchange Server, I could append to this file all the necessary trusted root
CAs.
Don't do
* Wietse Venema wie...@porcupine.org:
Noel Jones:
As I see it, there are two complementary paths we can take
with DNS whitelists, each with a slightly different purpose.
While these are both useful, neither depends on the other, so
postfix can implement either or both.
I'll read the
On Wed, Aug 25, 2010 at 11:27 PM, Wietse Venema wie...@porcupine.org wrote:
dnswl1.example.com=127.0.0.2*weight1, dnswl2.example.com=127.0.0.1*weight2
dnsbl3.example.com=127.0.0.3*weight3, dnsbl4.example.com=127.0.0.1*weight4
What about wildcarding? dnswl.org currently returns 127.0.n.[0-3],
On Wed, 25 Aug 2010 16:47:46 -0700
Security Admin (NetSec) secad...@netsecdesign.com articulated:
smtp_tls_CAfile = /etc/postfix/exchange.pem
You can list more CAs in this file if you wish.
Is there an existing file or a weblink that would list the current
accepted global root CAs?
Matthias Leisi:
On Wed, Aug 25, 2010 at 11:27 PM, Wietse Venema wie...@porcupine.org wrote:
?dnswl1.example.com=127.0.0.2*weight1, dnswl2.example.com=127.0.0.1*weight2
?dnsbl3.example.com=127.0.0.3*weight3, dnsbl4.example.com=127.0.0.1*weight4
What about wildcarding? dnswl.org currently
Thanks for taking the time to try to assist my limited brain in
understanding this Noel. It is frustrating, because I thought I at least
had a decent handle on how these checks worked...
Noel Jones wrote:
smtpd_recipient_restrictions is not the last section; the message
still must pass
Wietse Venema put forth on 8/25/2010 4:27 PM:
Noel Jones:
As I see it, there are two complementary paths we can take
with DNS whitelists, each with a slightly different purpose.
While these are both useful, neither depends on the other, so
postfix can implement either or both.
I'll read
On 8/26/2010 6:31 AM, Charles Marcus wrote:
If you've specified smtpd_reject_unlisted_recipient=yes, that check
is also after smtpd_recipient_restrictions.
Since smtpd_reject_unlisted_recipient=yes is the default, it happens
after the recipient_restrictions *without* my having to specify it,
Noel Jones put forth on 8/25/2010 10:11 PM:
In that case, don't use an access table with FILTER; use content_filter
or smtpd_proxy_filter to filter all mail.
(For wildcard access tables, use a regexp table. But for this
application, use content_filter.)
Let me try to make this really
Hello,
Got some error in my logs below:
Aug 25 21:22:16 mail local[29944]: fatal: execvp /usr/bin/vacation: No
such file or directory
Aug 25 21:22:16 mail postfix/local[29867]: EF319BF1087:
to=us...@my.domain.com, relay=local, delay=0.07, delays=0.05/0/0/0.02,
dsn=4.3.0, status=deferred
Daniel Prieto:
Is there a substitute 'vacation' feature from Sendmail for Postfix for
all my users? Is Postfix.admin the best bet?
I compiled vacation on my linux box and enable my .forward file with
\user1, |/usr/bin/vacation user1 but the sender doesn't get a
'vacation' message back. Is
On 8/22/2010 11:42 AM, p...@alt-ctrl-del.org wrote:
On Sunday, August 22, 2010 at 16:01 CEST,
p...@alt-ctrl-del.org wrote:
Reading RESTRICTION_CLASS_README confused me as to whether
adding a Restriction (or a defined smtpd_restriction_classes
group), to the right side of an access table,
On 8/26/2010 11:26 AM, Udo Rader wrote:
On 08/26/2010 04:39 PM, Daniel Prieto wrote:
Hello,
Got some error in my logs below:
Aug 25 21:22:16 mail local[29944]: fatal: execvp /usr/bin/vacation: No
such file or directory
Aug 25 21:22:16 mail postfix/local[29867]: EF319BF1087:
On 8/26/2010 4:14 PM, Wietse Venema wrote:
The more precise solution is to implement wildcards with ranges:
example.com=127.0.[0-128].3*1
example.com=127.0.[0-5,6-9].3*1
Noel Jones:
I like the range idea. You want proto docs reflecting that
syntax?
Yes, that would help everyone to
Updated Proposal for weighted dnsXl support in postscreen.
(Change parameter names to all start with postscreen_dns* for
easy reading in postconf. Get rid of negative site weight
values [the client dnsxl score total may still be negative].
Add filter octet range docs.)
(The weight ranges
Except that this is sending to our internal Exchange 2003 server, not
outgoing.
Here's the scenario:
We have 2 servers that act as incoming mail server. One is to receive mails
from the Internet, a Barracuda box. This box is running well.
Another box, this is the problematic one, is to relay
Lie, Jafaruddin:
There's an ASA 5500 inbetween, but the SMTP fixup protocol has been turned
off,
Prove it.
Wietse
17 matches
Mail list logo
