non DNSSEC destination?

2014-08-31 Thread Peter Bauer
Hello, I tried to run DANE on my postfix 2.11.0 server, but it does not make DANE verifications by connecting on different servers which have officially switched to DNSSEC & DANE. I tested it with the following configuration: smtp_use_tls = yes smtp_tls_fingerprint_digest = sha1 smtp_tls_policy_

Re: non DNSSEC destination?

2014-08-31 Thread Patrick Ben Koetter
Peter, * Peter Bauer : > Hello, > > I tried to run DANE on my postfix 2.11.0 server, but it does not make DANE > verifications by connecting on different servers which have officially > switched to DNSSEC & DANE. Postfix can only use DANE verification, if the underlying system is able to tell DN

Re: non DNSSEC destination?

2014-08-31 Thread Ralf Hildebrandt
* Patrick Ben Koetter : > If you don't see it, you resolver cannot authenticated DNSSEC enabled domains. > Then you need to change that. One solution would be to install "unbound" as local caching resolver and then let resolv.conf point to 127.0.0.1 -- [*] sys4 AG http://sys4.de, +49 (89) 30 9

Re: non DNSSEC destination?

2014-08-31 Thread Viktor Dukhovni
On Sun, Aug 31, 2014 at 12:33:36PM +0200, Ralf Hildebrandt wrote: > * Patrick Ben Koetter : > > > If you don't see it, you resolver cannot authenticated DNSSEC enabled > > domains. > > Then you need to change that. > > One solution would be to install "unbound" as local caching resolver > and th

Re: non DNSSEC destination?

2014-08-31 Thread Benny Pedersen
On 31. aug. 2014 12.34.04 Ralf Hildebrandt wrote: > Then you need to change that. One solution would be to install "unbound" as local caching resolver and then let resolv.conf point to 127.0.0.1 Post bind9 options section, maybe its needs change to enable it? man named.conf is it enabled Ral

Re: non DNSSEC destination?

2014-08-31 Thread Peter Bauer
On Sun, Aug 31, 2014 at 11:35:40AM +0200, Patrick Ben Koetter wrote: > p@x240:~$ dig SOA +dnssec sys4.de > > ; <<>> DiG 9.9.5-3-Ubuntu <<>> SOA +dnssec sys4.de > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61650 > ;; flags: qr rd ra ad; QUERY: 1,

Re: non DNSSEC destination?

2014-08-31 Thread Peter Bauer
On Sun, Aug 31, 2014 at 11:35:40AM +0200, Patrick Ben Koetter wrote: > ; <<>> DiG 9.9.5-3-Ubuntu <<>> SOA +dnssec sys4.de > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61650 > ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 3

Re: non DNSSEC destination?

2014-08-31 Thread /dev/rob0
On Sun, Aug 31, 2014 at 09:06:24PM +0200, Peter Bauer wrote: > As resolver I have Bind: > # cat /etc/resolv.conf > nameserver 10.0.3.1 > > And on 10.0.3.1 I have this: > forwarders { > 213.133.98.98; > 213.133.99.99; > 213.133.100.100; > }; Do

Postfix ignores main.cf changes

2014-08-31 Thread Adam Courville
I apologize if this problem has been reported before, but I am having no luck determining a resolution through online searches. Environment: Fedora Core 20 on a NATted server (private, static LAN IPs through a router to the Internet). Postfix installed through yum method and is latest availab

Re: Postfix ignores main.cf changes

2014-08-31 Thread Noel Jones
On 8/31/2014 7:40 PM, Adam Courville wrote: > I apologize if this problem has been reported before, but I am > having no luck determining a resolution through online searches. > > > > Environment: Fedora Core 20 on a NATted server (private, static LAN > IPs through a router to the Internet).

RE: Postfix ignores main.cf changes

2014-08-31 Thread Adam Courville
Understood and thanks, but that doesn't answer why it is not reading the main.cf file. Viewing the system journal created, I can see test emails using the default system settings for hostname and domainname instead of those specified in the main.cf file. I will try the -o parameter next to see if

RE: Postfix ignores main.cf changes

2014-08-31 Thread Adam Courville
Okay, I see now that use of the postconf -x myyadayada reveals the actual changes. Perhaps I am not understanding this properly. My server hostname is say mail.internal so right now any mail going out ends up with the from field populated as user@mail.internal which will not fly with most relay

Re: Postfix ignores main.cf changes

2014-08-31 Thread Noel Jones
On 8/31/2014 10:33 PM, Adam Courville wrote: > Okay, I see now that use of the postconf -x myyadayada reveals the actual > changes. Perhaps I am not understanding this properly. My server hostname > is say mail.internal so right now any mail going out ends up with the from > field populated as >

*canonical_classes not behaving as expected with local mail submission

2014-08-31 Thread Valdemar Jakobsen
Dear Postfix-Users, I’m using sender_canonical_maps to ensure that my envelope addresses comply with SPF policies and also allow for a valid bounce address in the event of non-delivery. My gateway mail servers are configured using sender_canonical_maps with "sender_canonical_classes = envelope

Re: *canonical_classes not behaving as expected with local mail submission

2014-08-31 Thread Matthias Andree
Am 01.09.2014 um 06:57 schrieb Valdemar Jakobsen: > Dear Postfix-Users, > > I’m using sender_canonical_maps to ensure that my envelope addresses > comply with SPF policies and also allow for a valid bounce address in > the event of non-delivery. > > My gateway mail servers are configured using se