550 5.7.1 Unable to relay to certain provider

I'm having trouble sending e-mail to a certain provider in the NL (KPN) where our e-mail bounces with a 550 5.7.1 error.
I have tried in vein to contact someone at this provider who knew anything about their e-mail/anti spam servers so that is a dead end.
We are relaying our e-mail through a postfix server which is acting as border gateway, there is also an exchange server relaying through this gateway which is unaffected, which means the 'problem' is with GW. (obviously this provider has their servers configured in a poor way or I would not be able to e-mail the rest of the world..)
The e-mail bounces before it gets to the DATA bit and I have narrowed it down to the RCPT TO: line.

RCPT TO:<xxxx@yyyy.nl> NOTIFY=SUCCESS,FAILURE ORCPT=rfc822;groupwise-xxxx@yyyy.nl:1:1

More specifically to the ':1:1' bit. Does anyone have any idea what GWIA setting causes it to add this ? I'm pretty sure there are more GroupWise systems in this country that do not seem to be affected or it would be a known issue .. When i look at Exchange it does not add anything after the RCPT TO address.

This is our agents/share/gwia.cfg (with info edited out)

--home /var/opt/novell/groupwise/mail/domain/wpgate/gwia
--dhome /var/opt/novell/groupwise/mail/domain/wpgate/gwia
--hn GroupWise.domain.nl
--smtp
--nosmtpversion
--mime
--mudas 2
--sd 8
--rd 16
--p 10
--te 2
--tg 5
--tc 5
--tr 5
--td 3
--tt 10
--pt 10
--it 10
--ldapthrd 10
--st 4
--rt 4
--dsn
--dsnage 4
--mh w.x.y.z
--httpport 9850
--xspam

Tags:

  • Hi.

    On 10.10.2013 16:06, Conz wrote:
    > The e-mail bounces before it gets to the DATA bit and I have narrowed it
    > down to the RCPT TO: line.
    >
    > RCPT TO:<xxxx@yyyy.nl> NOTIFY=SUCCESS,FAILURE
    > ORCPT=rfc822;groupwise-xxxx@yyyy.nl*:1:1*
    >
    > More specifically to the ':1:1' bit. Does anyone have any idea what GWIA
    > setting causes it to add this ?


    > --dsn
    > --dsnage 4


    These two. the ORCPT= line is a result of DSN alias Delivery Status
    Notification being enabled. I assume you can safely disable it.

    CU,
    --
    Massimo Rosen
    Novell Knowledge Partner
    No emails please!
    http://www.cfc-it.de
  • Turning off DSN removed the NOTIFY= bit and the :1:1 bit
    Testing this is a bit tricky as I can't just send test e-mails to random people their home e-mails :-)

    I'm still not sure what that :1:1 bit is .. I'm really thinking that's the actual problem and not the notify= part.
  • On 15.10.2013 16:16, Conz wrote:
    >
    > Turning off DSN removed the NOTIFY= bit and the :1:1 bit


    You mean it doesn't remove the orcpt line entirely? In this case, it
    must be created by your relay.

    CU,
    --
    Massimo Rosen
    Novell Knowledge Partner
    No emails please!
    http://www.cfc-it.de
  • mrosen;2288335 wrote:

    You mean it doesn't remove the orcpt line entirely? In this case, it
    must be created by your relay.


    You are correct, the ORCPT part is added by the relay if it has not been added by GW.

    GWIA w/o DSN delivers as:
    RCPT TO:<xxxx@yyyy.nl>

    GWIA w DSN delivers as:
    RCPT TO: <xxxx@yyyy.nl> ORCPT=rfc822;groupwise-xxxx@yyyy.nl:1:1 NOTIFY=SUCCESS,FAILURE

    the :1:1 bit is the problem though, I have no idea where that's coming from.. I can't find any evidence in the smtp rfc's that its a valid thing to be there... all I know its being added to the string that is validated to check if its a valid recipient address by some mail server setting on what I *think* is exchange and then failing this test.

    I can't find any evidence that this :1:1 bit serves any purpose, I can find evidence that its a common thing in GW, I found another post on these forums where :2:1 was added.