Pete McEvoy wrote:
> When I point this out to the vendors of the application, they reply
> saying it works everywhere else, this is a local problem at my end, and
> point to urls such as:
>
> http://www.logicprobe.org/proj/logicmail/ticket/116
Slap them over the head and tell them this link has nothing to do with
RCPT time and instead is about stupid programs not following simple
standards which is actually admitted in the text.
Getting around this minor sync issue is easily done if you know the IP
address of the misbehaving host and you actually want to talk to them.
Use control=no_enforce_sync in the connect ACL.
> RCPT TO:<user.1@???>;<user.2@???>
is in no way valid, as you show in the string you linked from RFC 5321.
If that works with other mail servers, then they are broken.
> RCPT TO:<forward-path> [ SP <rcpt-parameters> ] <CRLF>
If they are unable to wrap their head around it, you may just have to
make exim accept such a malformed address, however you may feel
confident that they are in fact wrong.
The easiest solution would be set the stupid application to send to one
recipient and branch it out on the mail server. I suspect that's what
everyone else on the planet has done after hearing such a stupid reply
from the vendor.
--
The Exim Manual
http://www.exim.org/docs.html
http://docs.exim.org/current/
