On 11/22/2014 07:41 AM, Wietse Venema wrote:
A. Schulze:
So instead implementing strange workarounds, one should search, find,
understand and fix the real problem.
Google bounced my mail because of a temp error. I changed nothing
in my DNS or DKIM. It's their bug, not mine.
And with mine, I
Robert Moskowitz:
Google bounced my mail because of a temp error. I changed nothing
in my DNS or DKIM. It's their bug, not mine.
And with mine, I needed an spf record to make them happy:
htt-consult.com. IN TXT v=spf1 mx ~all
Now when my wife sends emails to her employer, yby.org,
On 11/24/2014 08:42 AM, Wietse Venema wrote:
Robert Moskowitz:
Google bounced my mail because of a temp error. I changed nothing
in my DNS or DKIM. It's their bug, not mine.
And with mine, I needed an spf record to make them happy:
htt-consult.com. IN TXT v=spf1 mx ~all
Now when my wife
On 11/22/2014 9:45 AM, Robert Schetterer wrote:
Am 22.11.2014 um 14:50 schrieb A. Schulze:
wietse:
A. Schulze:
So instead implementing strange workarounds, one should search, find,
understand and fix the real problem.
Google bounced my mail because of a temp error. I changed nothing
in my
I forgot to add that the PTR records for both 74.nnn.nnn.178 and
2001:470:dead:beef:nn::178 point to smtp.my.domain which matches the
rest of my setup.
Zitat von John j...@klam.ca:
On 11/22/2014 9:45 AM, Robert Schetterer wrote:
Am 22.11.2014 um 14:50 schrieb A. Schulze:
wietse:
A. Schulze:
So instead implementing strange workarounds, one should search, find,
understand and fix the real problem.
Google bounced my mail because of a temp
John:
however, I had a similar problem a while back, Google would randomly
reject email for, to me, no good reason.
It turned out that with IPv6 postfix was not consistent in binding an
address for sending.
Please do not spread unnecessary confusion.
If you had read this tread more
On 11/23/2014 9:50 AM, wie...@porcupine.org (Wietse Venema) wrote:
John:
however, I had a similar problem a while back, Google would randomly
reject email for, to me, no good reason.
It turned out that with IPv6 postfix was not consistent in binding an
address for sending.
Please do not
On 11/23/2014 9:59 AM, John wrote:
If you can explain why adding the stanzas to master cures the problem
I am all ears!
It didn't. Some other factor (e.g., path or load problems with HE's
nameservers) is the real culprit. Google's DNS lookup paths are overly
sensitive to resolution delays.
John:
[ Charset windows-1252 converted... ]
On 11/23/2014 9:50 AM, wie...@porcupine.org (Wietse Venema) wrote:
John:
however, I had a similar problem a while back, Google would randomly
reject email for, to me, no good reason.
It turned out that with IPv6 postfix was not consistent in
Peter:
Unfortunately the above solution assumes that all recipients that use
the google MX servers will have email addresses with google.com or
gmail.com domains.
(@Wietse: correct me, if I'm wrong)
that's a general consequence of postfix design.
postfix is destination domain centric. It
A. Schulze:
So instead implementing strange workarounds, one should search, find,
understand and fix the real problem.
Google bounced my mail because of a temp error. I changed nothing
in my DNS or DKIM. It's their bug, not mine.
Wietse
wietse:
A. Schulze:
So instead implementing strange workarounds, one should search, find,
understand and fix the real problem.
Google bounced my mail because of a temp error. I changed nothing
in my DNS or DKIM. It's their bug, not mine.
I don't expect your setup is obviously broken and
Am 22.11.2014 um 14:50 schrieb A. Schulze:
wietse:
A. Schulze:
So instead implementing strange workarounds, one should search, find,
understand and fix the real problem.
Google bounced my mail because of a temp error. I changed nothing
in my DNS or DKIM. It's their bug, not mine.
I
Zitat von A. Schulze s...@andreasschulze.de:
wietse:
A. Schulze:
So instead implementing strange workarounds, one should search, find,
understand and fix the real problem.
Google bounced my mail because of a temp error. I changed nothing
in my DNS or DKIM. It's their bug, not mine.
I
Robert Schetterer:
Hi Andreas , there a wide reports that google sometimes fails somehow
with ipv6, i investigated in this hardly , it simply looks its their
bug, my best speculation goes in sometimes not working spf ipv6 stuff at
their site
My domain has no SPF, but it signs all mail with
Am 22.11.2014 um 17:19 schrieb Wietse Venema:
Robert Schetterer:
Hi Andreas , there a wide reports that google sometimes fails somehow
with ipv6, i investigated in this hardly , it simply looks its their
bug, my best speculation goes in sometimes not working spf ipv6 stuff at
their site
On 11/21/2014 07:02 AM, Wietse Venema wrote:
/etc/postfix/master.cf:
forced-ipv4 unix - - n - - smtp
-o inet_protocols=ipv4
/etc/postfix/transport:
google.comforced-ipv4:
gmail.com forced-ipv4:
/etc/postfix/main.cf:
Actually, all people who use google MX will have google.com or gmail.com
in their domains.
They can use other email servers on their devices. However, those
servers will not be google.com or gmail.com email addresses. They can
publish their google.com or gmail.com addresses as their return
On 11/22/2014 04:32 PM, L. D. James wrote:
Actually, all people who use google MX will have google.com or gmail.com
in their domains.
Wrong, and this is easy to disprove:
$ dig pajamian.dhs.org MX +short
0 ASPMX.L.GOOGLE.COM.
10 ALT1.ASPMX.L.GOOGLE.COM.
10 ALT2.ASPMX.L.GOOGLE.COM.
20
On 11/21/2014 11:14 PM, Peter wrote:
On 11/22/2014 04:32 PM, L. D. James wrote:
Actually, all people who use google MX will have google.com or gmail.com
in their domains.
Wrong, and this is easy to disprove:
$ dig pajamian.dhs.org MX +short
0 ASPMX.L.GOOGLE.COM.
10 ALT1.ASPMX.L.GOOGLE.COM.
10
Zitat von wie...@porcupine.org:
Robert Moskowitz:
Perhaps this should go to the bind list, but all of my checking shows my
ipv6 ptr record is working.
This started, I think, last week. I was running an old mailserver and
sent many an email to the cubieboard list.
I had one email bounce
On 11/20/2014 12:50 AM, Robert Schetterer wrote:
Am 20.11.2014 um 01:46 schrieb Wietse Venema:
Robert Moskowitz:
Perhaps this should go to the bind list, but all of my checking shows my
ipv6 ptr record is working.
This started, I think, last week. I was running an old mailserver and
sent
Robert Moskowitz:
On 11/20/2014 12:50 AM, Robert Schetterer wrote:
Am 20.11.2014 um 01:46 schrieb Wietse Venema:
Robert Moskowitz:
Perhaps this should go to the bind list, but all of my checking shows my
ipv6 ptr record is working.
This started, I think, last week. I was running an
Am 20.11.2014 um 18:54 schrieb Robert Moskowitz:
On 11/20/2014 12:50 AM, Robert Schetterer wrote:
Am 20.11.2014 um 01:46 schrieb Wietse Venema:
Robert Moskowitz:
Perhaps this should go to the bind list, but all of my checking
shows my
ipv6 ptr record is working.
This started, I think,
Perhaps this should go to the bind list, but all of my checking shows my
ipv6 ptr record is working.
This started, I think, last week. I was running an old mailserver and
sent many an email to the cubieboard list.
Just today I finally upgraded my mailserver, but still get the bounce.
My
Robert Moskowitz wrote:
Perhaps this should go to the bind list, but all of my checking shows
my ipv6 ptr record is working.
This started, I think, last week. I was running an old mailserver and
sent many an email to the cubieboard list.
Just today I finally upgraded my mailserver, but still
Robert Moskowitz:
Perhaps this should go to the bind list, but all of my checking shows my
ipv6 ptr record is working.
This started, I think, last week. I was running an old mailserver and
sent many an email to the cubieboard list.
I had one email bounce last week. Looks like they handle
This is kind of what I was thinking was the case...
On 11/19/2014 07:28 PM, Mark Martinec wrote:
Robert Moskowitz wrote:
Perhaps this should go to the bind list, but all of my checking shows
my ipv6 ptr record is working.
This started, I think, last week. I was running an old mailserver and
On 11/19/2014 07:46 PM, Wietse Venema wrote:
Robert Moskowitz:
Perhaps this should go to the bind list, but all of my checking shows my
ipv6 ptr record is working.
This started, I think, last week. I was running an old mailserver and
sent many an email to the cubieboard list.
I had one
Am 20.11.2014 um 01:46 schrieb Wietse Venema:
Robert Moskowitz:
Perhaps this should go to the bind list, but all of my checking shows my
ipv6 ptr record is working.
This started, I think, last week. I was running an old mailserver and
sent many an email to the cubieboard list.
I had
31 matches
Mail list logo
