-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dominik George said the following on 01/10/2013 07:22:
> Yes, I also face that issue and have forced IPv4 on known Google domains.
> Google have been ignoring my support tickets about that for several weeks
> now.
Same here. At the beginning I though
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>Needless to say, that if I use IPv4 Google accepts every mail.
>
>Dis this happened to anyone else?
Yes, I also face that issue and have forced IPv4 on known Google domains.
Google have been ignoring my support tickets about that for several weeks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have started to configure IPv6 on a couple of servers, both with IPv6 rDNS
resolution on their name
Sometimes (say over about 10 messages/day), Google rejects IPv6 mails with
this error:
<{google_recipient}>: host aspmx.l.google.com[2a00:1450:4001:
On 9/30/2013 5:21 AM, no@s...@mgedv.net wrote:
> hi,
>
> my postfix should be the 1st entry point for a multi-domain-environment.
> i want postfix to do recipient verification in order to avoid mails being
> relayed to
> the internal host for users, which do not exists (actually, legal compliance
Am 30.09.2013 12:59, schrieb no@s...@mgedv.net:
>> normally you would have internal and external DNS views
>>
>> however, dnsmasq can use /etc/hosts and forward all other requests to a
>> specific DNS and so you would point /etc/resolv.conf to 127.0.0.1
>
> i know it's possible to fake DNS recor
Am 30.09.2013 12:21, schrieb no@s...@mgedv.net:
> syslog entries as follows:
> postfix/smtpd 2013-09-30 10:45:23 NOQUEUE: reject: RCPT from
> mail.xxx.yyy[222.222.222.222]: 450 4.1.1 : Recipient address
> rejected: unverified address: Address verification in progress;
> from= to= proto=ESMTP hel
