Mx google com выдал это сообщение об ошибке

Очень нехорошо иметь офисный NAT и почтовый сервер на одном IP. Скорей всего, кто-то в офисной сети подхватил троянца, через который идет активная рассылка спама, поэтому IP блеклистят, причем поскольку он является частью ботнета, то блеклистят как IP конечных пользователей, что скорей всего надолго. Репутация IP скорей всего убита, на ее восстановление у разных почтовых провайдеров может потребовать от недели до бесконечности.

Закройте доступ из локальной сети наружу по 25му порту. Это следовало сделать сразу, чтобы не подставлять почтовый сервер в подобных ситуациях + обязательно установите рейтлимиты по пользователям на самом почтовом сервере, чтобы нельзя было активно спамить через него, обязательно следите за превышениями рейтлимитов / блокируйте скомпрометированных пользователей.
После этого два варианта:
1. Ждать пока репутация восстановится, параллельно вынося себя из известных RBL’ей
2. Попросить у провайдера выделить дополнительный IP адрес или небольшую сеть и назначить отдельный IP почтовому серверу.

Last week on a client SBS2011 box the SKY business broadband went down and I had to switch the server gateway to a BT ADSL with static for a few hours to keep things running.

Once the connection restored I went to switch back, (192.168.1.253 to .254) but the process hung and when I opened DNS it was not populated.  I checked the DNS Server service and it was stuck closing down but it did eventually close and after restarting
I could see all my DNS info and all seemed ok.

That is until I started to get users sending me bounce-backs like this:

mx.google.com rejected your message to the following e-mail addresses:

‘clientemail@gmail.com’ (clientemail@gmail.com)

mx.google.com gave this error:
[2a02:c7d:464:7200:346e:dc36:8ea6:6540] Our system has detected that this message does not meet IPv6 sending guidelines regarding PTR records and authentication. Please review

https://support.google.com/mail/?p=ipv6_authentication_error for more information. uh16si30692310wjb.8 — gsmtp

Your message wasn’t delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.

Here are the headers:
Diagnostic information for administrators:

Generating server: CLIENTSVR.CL.local

clientemail@gmail.com
mx.google.com #550-5.7.1 [2a02:c7d:464:7200:346e:dc36:8ea6:6540] Our system has detected that 550-5.7.1 this message does not meet IPv6 sending guidelines regarding PTR 550-5.7.1 records and authentication. Please review 550-5.7.1

https://support.google.com/mail/?p=ipv6_authentication_error for more 550 5.7.1 information. uh16si30692310wjb.8 — gsmtp ##

Original message headers:
Received: from CLIENTSVR.CL.local ([fe80::25dd:f159:ecbf:ad7b]) by
CLIENTSVR.CL.local
([fe80::25dd:f159:ecbf:ad7b%14]) with mapi id 14.03.0301.000;
Mon, 8 Aug 2016 16:44:13 +0100
From: John Doe <John.Doe@myclient.co.uk>
To: «‘clientemail@gmail.com'» <clientemail@gmail.com>,

Subject: ‘Staircasing’ Valuation for Mr Smith
Thread-Topic: ‘Staircasing’ Valuation for Mr Smith
Thread-Index: AdHxi7YTFQNyDoO6T2m0yJBO5GinDQAAAAHA
Disposition-Notification-To:
John Doe <John.Doe@myclient.co.uk>
Date: Mon, 8 Aug 2016 15:44:13 +0000
Message-ID: <1e5c90cc-717c-4534-b2d7-315b1e754999@CLIENTSVR.CL.local>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.165]
Content-Type: multipart/alternative;
boundary=»_000_1e5c90cc717c4534b2d7315b1e754999CAB 002cglocal_»
MIME-Version: 1.0

I researched the issue and found that following the process hang switching gateway IP ALL the iPv4 and 6 NIC addresses in DNS had been ticked so I noted the 2 addresses for my actual NIC, unticked the rest and switched back to root hints as suggested by, ‘Fix
My Network’.

I also noted that in all outgoing SMTP headers they now contain the iPv6 info
fe80::25dd:f159:ecbf:ad7b instead of iPv4 192.168.1.1.

Can anyone advise how to resolve this?

Kind regards,
Andrew

Last week on a client SBS2011 box the SKY business broadband went down and I had to switch the server gateway to a BT ADSL with static for a few hours to keep things running.

Once the connection restored I went to switch back, (192.168.1.253 to .254) but the process hung and when I opened DNS it was not populated.  I checked the DNS Server service and it was stuck closing down but it did eventually close and after restarting
I could see all my DNS info and all seemed ok.

That is until I started to get users sending me bounce-backs like this:

mx.google.com rejected your message to the following e-mail addresses:

‘clientemail@gmail.com’ (clientemail@gmail.com)

mx.google.com gave this error:
[2a02:c7d:464:7200:346e:dc36:8ea6:6540] Our system has detected that this message does not meet IPv6 sending guidelines regarding PTR records and authentication. Please review

https://support.google.com/mail/?p=ipv6_authentication_error for more information. uh16si30692310wjb.8 — gsmtp

Your message wasn’t delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.

Here are the headers:
Diagnostic information for administrators:

Generating server: CLIENTSVR.CL.local

clientemail@gmail.com
mx.google.com #550-5.7.1 [2a02:c7d:464:7200:346e:dc36:8ea6:6540] Our system has detected that 550-5.7.1 this message does not meet IPv6 sending guidelines regarding PTR 550-5.7.1 records and authentication. Please review 550-5.7.1

https://support.google.com/mail/?p=ipv6_authentication_error for more 550 5.7.1 information. uh16si30692310wjb.8 — gsmtp ##

Original message headers:
Received: from CLIENTSVR.CL.local ([fe80::25dd:f159:ecbf:ad7b]) by
CLIENTSVR.CL.local
([fe80::25dd:f159:ecbf:ad7b%14]) with mapi id 14.03.0301.000;
Mon, 8 Aug 2016 16:44:13 +0100
From: John Doe <John.Doe@myclient.co.uk>
To: «‘clientemail@gmail.com'» <clientemail@gmail.com>,

Subject: ‘Staircasing’ Valuation for Mr Smith
Thread-Topic: ‘Staircasing’ Valuation for Mr Smith
Thread-Index: AdHxi7YTFQNyDoO6T2m0yJBO5GinDQAAAAHA
Disposition-Notification-To:
John Doe <John.Doe@myclient.co.uk>
Date: Mon, 8 Aug 2016 15:44:13 +0000
Message-ID: <1e5c90cc-717c-4534-b2d7-315b1e754999@CLIENTSVR.CL.local>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.165]
Content-Type: multipart/alternative;
boundary=»_000_1e5c90cc717c4534b2d7315b1e754999CAB 002cglocal_»
MIME-Version: 1.0

I researched the issue and found that following the process hang switching gateway IP ALL the iPv4 and 6 NIC addresses in DNS had been ticked so I noted the 2 addresses for my actual NIC, unticked the rest and switched back to root hints as suggested by, ‘Fix
My Network’.

I also noted that in all outgoing SMTP headers they now contain the iPv6 info
fe80::25dd:f159:ecbf:ad7b instead of iPv4 192.168.1.1.

Can anyone advise how to resolve this?

Kind regards,
Andrew