On 6 Jan 2015, at 23:18, Viktor Dukhovni wrote:
> My email server, for example, specifically does not support the ISC DLV.
Yay!
> With the root zone and most TLDs signed, I don't think it makes sense to use
> it anymore.
+1000.
DLV has always been a *remarkably* bad idea. It actually hinder
On Wed, Jan 07, 2015 at 12:45:53AM +0100, Jean Bruenn wrote:
> What happens if I send an email to your Mailserver if there is
> no DS-record for my domain in eu (which is why I use dlv - I added
> the dnskey of a .eu testdomain there) the same as explained
> below (no mail loss)?
DANE plays no r
> Am 07.01.2015 um 00:18 schrieb Viktor Dukhovni :
>
>> On Tue, Jan 06, 2015 at 11:36:08PM +0100, Jean Bruenn wrote:
>>
>> I'd like to use DANE but since my registrar has no support for DNSSEC
>> stuff yet (they're working on that) I am using DLV (dlv.isc.org) for now.
>> Now I'd like to use th
On Tue, Jan 06, 2015 at 11:36:08PM +0100, Jean Bruenn wrote:
> I'd like to use DANE but since my registrar has no support for DNSSEC
> stuff yet (they're working on that) I am using DLV (dlv.isc.org) for now.
> Now I'd like to use that with Postfix and for that to work I assume that
> other sites
On Tue, Jan 06, 2015 at 11:59:44PM +0100, Benny Pedersen wrote:
> >-o smtp_header_checks=pcre:$config_directory/header_checks_smtp_out
> >-o inet_protocols=ipv6
> >-o inet_interfaces=2001:470:1f0b:bd0::3
> >
> >If I omit the last line, it fails...
>
> try again without chroot
Let's a
On 6. jan. 2015 15.08.00 Thomas Leuxner wrote:
# postconf -Mf smtp-ipv6
smtp-ipv6 unix - - - - - smtp
chroot
-o smtp_header_checks=pcre:$config_directory/header_checks_smtp_out
-o inet_protocols=ipv6
-o inet_interfaces=2001:470:1f0b:bd0::3
If I o
Hello,
I have a few questions not directly related to Postfix
and hope it is fine to ask here. I'd like to use
DANE but since my registrar has no support for
DNSSEC stuff yet (they're working on that) I am
using DLV (dlv.isc.org) for now.
Now I'd like to use that with Postfix and for
that to wor
Roman Gelfand:
> 2 client machines connect via telnet to postfix smtp server on port 25.
> All machines are on the same subnet. One machine gets helo
> instantaneously. The other it takes roughly 20-30 secs. I had similar
That is surely the result of DNS or /etc/hosts configuration issues.
Post
Am 06.01.2015 um 22:52 schrieb James B. Byrne:
On Tue, January 6, 2015 15:08, Roman Gelfand wrote:
I do run dns server on both client machines.
The dig response of the client machine from the client machine that
connects immediately has one more entry. It is bringing back an A
record of the
On Tue, January 6, 2015 15:08, Roman Gelfand wrote:
> I do run dns server on both client machines.
>
> The dig response of the client machine from the client machine that
> connects immediately has one more entry. It is bringing back an A
> record of the client machine.
>
> As it turns out that wa
On Tue, January 6, 2015 12:41, Roman Gelfand wrote:
> 2 client machines connect via telnet to postfix smtp server
> on port 25. All machines are on the same subnet. One machine
> gets helo instantaneously. The other it takes roughly 20-30
> secs. I had similar problem in the past where dns reve
* Viktor Dukhovni 2015.01.06 17:25:
> Do this instead:
>
> main.cf:
> ipv4_interfaces = 188.138.4.217
> ipv6_interfaces = 2001:470:1f0b:bd0::3
> inet_interfaces = $ipv4_interfaces, $ipv6_interfaces
> inet_protocols = ipv4, ipv6
>
> master.cf:
> smtp-ipv6 u
* Wietse Venema 2015.01.06 17:16:
> > # postconf -Mf smtp-ipv6
> > smtp-ipv6 unix - - - - - smtp
> > -o smtp_header_checks=pcre:$config_directory/header_checks_smtp_out
> > -o inet_protocols=ipv6
> > -o inet_interfaces=2001:470:1f0b:bd0::3
> >
> > If I
2 client machines connect via telnet to postfix smtp server on port 25.
All machines are on the same subnet. One machine gets helo
instantaneously. The other it takes roughly 20-30 secs. I had similar
problem in the past where dns reverse resolution was problem. However,
here there is reverse r
On Tue, Jan 06, 2015 at 10:53:42AM +0100, Thomas Leuxner wrote:
> # postconf -n | grep inet
> inet_interfaces = 188.138.4.217, 2001:470:1f0b:bd0::3
> inet_protocols = ipv4, ipv6
Do this instead:
main.cf:
ipv4_interfaces = 188.138.4.217
ipv6_interfaces = 2001:470:1f0b:bd0::3
Thomas Leuxner:
Checking application/pgp-signature: FAILURE
-- Start of PGP signed section.
> * Wietse Venema 2015.01.06 14:35:
>
> > IF you want to use IPv6 address syntax in inet_interfaces or elsewhere,
> >
> > THEN you must enable IPv6 protocol support in main.cf or master.cf
> > with inet_
* Wietse Venema 2015.01.06 14:35:
> IF you want to use IPv6 address syntax in inet_interfaces or elsewhere,
>
> THEN you must enable IPv6 protocol support in main.cf or master.cf
> with inet_protocols=all, inet_protocols=ipv4,ipv6, or inet_protocols=ipv6.
>
> I hope this clarifies that there is
Thomas Leuxner:
> * Wietse Venema 2015.01.06 12:52:
>
> > Postfix supports the protocol addresses that you specify
> > with inet_protocols.
>
> Agree. But unless I give it the address to use, in addition to
>
> -o inet_protocols=ipv6
>
> ...it does not use the IPv6 addr. I have to add it a
* Wietse Venema 2015.01.06 12:52:
> Postfix supports the protocol addresses that you specify
> with inet_protocols.
Agree. But unless I give it the address to use, in addition to
-o inet_protocols=ipv6
...it does not use the IPv6 addr. I have to add it as -o inet_interfaces in
master.cf a
Thomas Leuxner:
> > Why are you surprised? You disable a IPv6 in inet_protocols,
> > but you require IPv6 in inet_interfaces.
>
> Hi Wietse,
>
> because the option was not part of the original stanza which I
> deemed comprehensive. Maybe my impression was postfix internally
> knows which format i
* Wietse Venema 2015.01.06 12:36:
> Why are you surprised? You disable a IPv6 in inet_protocols,
> but you require IPv6 in inet_interfaces.
Hi Wietse,
because the option was not part of the original stanza which I deemed
comprehensive. Maybe my impression was postfix internally knows which for
Thomas Leuxner:
> # postconf -n | grep inet
> inet_interfaces = 188.138.4.217, 2001:470:1f0b:bd0::3
> inet_protocols = ipv4, ipv6
...
> Unlike the original recipe
> http://postfix.1071664.n5.nabble.com/smtp-IPv4-IPv6-map-td61342.html, the
> transport fails with _only_ 'inet_protocols=ipv6' (or ipv
* Koko Wijatmoko 2015.01.06 11:22:
> set above to "= all" (default), and try to set:
>
> smtp_bind_address = 188.138.4.217
> smtp_bind_address6 = 2001:470:1f0b:bd0::3
>
> test it by sending to gmail again.
Unfortunately this yields the same problem.
signature.asc
Description: Digital signatu
On Tue, 6 Jan 2015 10:53:42 +0100
Thomas Leuxner wrote:
> # postconf -n | grep inet
> inet_interfaces = 188.138.4.217, 2001:470:1f0b:bd0::3
> inet_protocols = ipv4, ipv6
>
set above to "= all" (default), and try to set:
smtp_bind_address = 188.138.4.217
smtp_bind_address6 = 2001:470:1f0b:bd0::3
Following a recipe for selective transports on this list I have added a
transport map to a server with IPv4 *and* IPv6 interfaces.
# postconf mail_version
mail_version = 2.11.3
# postconf -n | grep inet
inet_interfaces = 188.138.4.217, 2001:470:1f0b:bd0::3
inet_protocols = ipv4, ipv6
# postcon
25 matches
Mail list logo
