Dominik George wrote:
if i would be you i would *not* use v=spf1 mx ~all
here you go for ipv6
http://www.openspf.org/SPF_Record_Syntax#ip6
Jeez, I don't believe it. The problem is that the mx mechanism simply
only enumerates A records of MXs. That's broken ...
Wietse wrote:
That's
He made the same claim, however, but never backed it up. How are you
reaching your conclusion?
Because this only mentions A records and IPv4 prefixes?
http://www.openspf.org/SPF_Record_Syntax#mx
Quick testing:
m...@staticsafe.ca - @gmail.com account
Received-SPF: pass (google.com: domain of
On 10/19/2013 01:45, DTNX Postmaster wrote:
On Oct 19, 2013, at 00:13, Dominik George n...@naturalnet.de wrote:
if i would be you i would *not* use v=spf1 mx ~all
If I were [...] ...
here you go for ipv6
http://www.openspf.org/SPF_Record_Syntax#ip6
Jeez, I don't believe it. The problem
He made the same claim, however, but never backed it up. How are you
reaching your conclusion?
Because this only mentions A records and IPv4 prefixes?
http://www.openspf.org/SPF_Record_Syntax#mx
Quick testing:
m...@staticsafe.ca - @gmail.com account
Received-SPF: pass (google.com:
be seen here:
http://postfix.1071664.n5.nabble.com/disable-ipv6-when-sending-to-gmail-td60672.html
It is Wietse's idea to re-write the response code into temporary, so that
Postfix will attempt delivery again. My fix was merely an enhancement to an
existing solution to compensate the changes
HQJaTu writes:
Google chose to change the wording in their 550 error.
550-5.7.1 [2001:-my-IPv6-address-here-16] Our system has detected
550-5.7.1 that this message does not meet IPv6 sending guidelines regarding
550-5.7.1 PTR records and authentication. Please review
550-5.7.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Mark Martinec mark.martinec+post...@ijs.si schrieb:
IMO, instead of working on workarounds, people's efforts would be
better spent
on setting up their DKIM and/or SPF, reverse DNS mapping, and making
sure that
postfix only binds to an intentionally
Am 18.10.2013 17:57, schrieb Dominik George:
Mark Martinec mark.martinec+post...@ijs.si schrieb:
IMO, instead of working on workarounds, people's efforts would be
better spent
on setting up their DKIM and/or SPF, reverse DNS mapping, and making
sure that
postfix only binds to an
Hi,
what about giving the real IP and output of ifconfig to give others
the chance to verify this for you instead say i took care
ok, here we go:
* sender address
Dominik George n...@naturalnet.de
* configuration
alias_database = hash:/etc/aliases
alias_maps =
Am 18.10.2013 23:52, schrieb Dominik George:
$ host 2a00:1828:2000:239::2
2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.9.3.2.0.0.0.0.2.8.2.8.1.0.0.a.2.ip6.arpa
domain name pointer shore.naturalnet.de.
$ host shore.naturalnet.de
shore.naturalnet.de has address 89.238.64.147
shore.naturalnet.de has
Hi,
if i would be you i would *not* use v=spf1 mx ~all
If I were [...] ...
here you go for ipv6
http://www.openspf.org/SPF_Record_Syntax#ip6
Jeez, I don't believe it. The problem is that the mx mechanism simply
only enumerates A records of MXs. That's broken ...
Thanks for the pointer to
Dominik George:
http://www.openspf.org/SPF_Record_Syntax#ip6
Jeez, I don't believe it. The problem is that the mx mechanism simply
only enumerates A records of MXs. That's broken ...
That's retarded. I wonder how many sites have been bitten by that bug.
Thanks for the pointer to the
On Oct 19, 2013, at 00:13, Dominik George n...@naturalnet.de wrote:
if i would be you i would *not* use v=spf1 mx ~all
If I were [...] ...
here you go for ipv6
http://www.openspf.org/SPF_Record_Syntax#ip6
Jeez, I don't believe it. The problem is that the mx mechanism simply
only
.nabble.com/disable-ipv6-when-sending-to-gmail-tp60672p62278.html
Sent from the Postfix Users mailing list archive at Nabble.com.
Hi,
that all sounds cool, but ...
Anyways, my users are happy. Their mail gets delivered. See my blog
post
http://blog.hqcodeshop.fi/archives/122-Fixing-Googles-new-IPv6-mail-policy-with-Postfix.html
about my fix.
could you please fix that to point to something more helpful than an
empty,
On Tue, Aug 20, 2013 at 02:23:21PM -0400, Wietse Venema wrote:
Nicolas KOWALSKI:
I am not able to have an IPv6 rDNS record with my ISP, only an IPv4 one.
I guess this is why it works when using IPv4 (tested by forcing
inet_protocols = ipv4), and does not work any more with IPv6.
Is
Nicolas KOWALSKI:
/etc/postfix/smtp_reply_filter:
# Postfix uses the last reply code in a multi-line reply.
/^5(\d\d .*your:ipv6:addr:here.*)/ 4$1
Then, Postfix will try to deliver to a different IP address.
I also tried this workaround, but it does not seem to work as
On Wed, Aug 21, 2013 at 06:44:55AM -0400, Wietse Venema wrote:
Argh. You need to replace the 5.X.X.
This pattern replaces both fives just to be sure.
/^5(\d\d )5(.*your:ipv6:addr:here.*)/ 4${1}4$2
I used this one ('-' instead of space):
/^5(\d\d-)5(.*2a01:e35:8ae7:65f0::2.*)/
Nicolas KOWALSKI:
On Wed, Aug 21, 2013 at 06:44:55AM -0400, Wietse Venema wrote:
Argh. You need to replace the 5.X.X.
This pattern replaces both fives just to be sure.
/^5(\d\d )5(.*your:ipv6:addr:here.*)/ 4${1}4$2
I used this one ('-' instead of space):
That is
On Wed, Aug 21, 2013 at 09:15:46AM -0400, Wietse Venema wrote:
Nicolas KOWALSKI:
On Wed, Aug 21, 2013 at 06:44:55AM -0400, Wietse Venema wrote:
Argh. You need to replace the 5.X.X.
This pattern replaces both fives just to be sure.
/^5(\d\d )5(.*your:ipv6:addr:here.*)/
On Wed, Aug 21, 2013 at 09:15:46AM -0400, Wietse Venema wrote:
Nicolas KOWALSKI:
On Wed, Aug 21, 2013 at 06:44:55AM -0400, Wietse Venema wrote:
Argh. You need to replace the 5.X.X.
This pattern replaces both fives just to be sure.
/^5(\d\d )5(.*your:ipv6:addr:here.*)/
Nicolas KOWALSKI:
On Wed, Aug 21, 2013 at 09:15:46AM -0400, Wietse Venema wrote:
Nicolas KOWALSKI:
On Wed, Aug 21, 2013 at 06:44:55AM -0400, Wietse Venema wrote:
Argh. You need to replace the 5.X.X.
This pattern replaces both fives just to be sure.
/^5(\d\d
Hello,
The gmail smtp server is now refusing mails from my system when IPv6 is
used, as shown in the log below:
Aug 20 06:25:08 petole postfix/smtp[27705]: Trusted TLS connection established
to gmail-smtp-in.l.google.com[2a00:1450:400c:c03::1b]:25: TLSv1.2 with cipher
ECDHE-RSA-RC4-SHA
Nicolas KOWALSKI:
I am not able to have an IPv6 rDNS record with my ISP, only an IPv4 one.
I guess this is why it works when using IPv4 (tested by forcing
inet_protocols = ipv4), and does not work any more with IPv6.
Is it possible to have outgoing mail to gmail (or another domain) sent
24 matches
Mail list logo
