Thanks for reply

Tried it a couple of ways - results were consistent
        * It was noticed - client was CC'ing to this server
        * Tried CC'ing to GMail, same result
        * with CC, defered, without CC, went straight through

All good, I agree - a recipient server issue
Thanks for letting me bounce it off you

Cheers

David Bray
e. [email protected]

September 5, 2020 12:32 PM, "Eric Broch" <[email protected] 
(mailto:[email protected]?to=%22Eric%20Broch%22%20<[email protected]>)>
 wrote:
        I would think that this is a recipient server issue.

        Is the CC'd address going to the same server?
On 9/4/2020 7:31 PM, David Bray wrote: Hi
With this message, I'm right to think that:
        * this is nothing to do with the sending side,
        * It has to be the serving side that is issuing this message,
        * there is no possible way that adding a CC address (or any other 
address, even an additional to address) could affect sending to the primary 
recipient
Cheers

David Bray
e. [email protected] (mailto:[email protected])

September 3, 2020 2:00 PM, "David Bray" <[email protected] 
(mailto:[email protected]?to=%22David%20Bray%22%20<[email protected]>)> 
wrote:

Hi

I have an issue where
        * A client sends an email to a remote server
        * and cc's a copy to someone else

 under these circumstance I get:

delivery 3555: deferral: 
<ip>_does_not_like_recipient./Remote_host_said:_451_relay_not_permitted!/Giving_up_on_<ip>./

it does eventually go through but the delay is several hours
        * If I test without the CC it goes through straight away
        * The CC'ed mail is delivered staright away
        * it only affects this server

 Their server has a signature if this helps:
        * signature spamexpert-2.servers.netregistry.net ESMTP Exim 
20200825.1020 Thu, 03 Sep 2020 06:57:02 +0300
Cheers

David Bray
e. [email protected] (mailto:[email protected])

Reply via email to