I learned more about this issue. It would appear that sendmail simply passes along the ORCPT request from the client to the remote MTA. So, sendmail is not actually generating the invalid ORCPT, the client that submitted the mail to sendmail is the one that is wrong.
Unfortunately, the client happens to be a java app with a large team of developers and a rigid deployment cycle. I could probably rattle some cages and override it if I have to, but if there is a way to make sendmail ignore this param from the client, I would take that too. Any ideas? thanks, -wes On Tue, Jun 2, 2009 at 12:53 PM, wes <[email protected]> wrote: > I have encountered an apparent oddity in my Sendmail configuration. Please, > hold off on the "switch to postfix/etc" suggestions - that is in the future > plans, but for today I am stuck with Sendmail and I need to fix this issue. > > When communicating with a remote MTA, trying to submit new mail, my > installation of Sendmail on openSUSE 10.3 is giving a bogus RCPT command. > Like so: > > RCPT To:<[email protected]> NOTIFY=FAILURE ORCPT=rfc822; > > when it should look like so: > > RCPT To:<[email protected]> NOTIFY=FAILURE ORCPT=rfc822;<[email protected]> > > I'm not entirely certain whether the <>s are supposed to be present in the > ORCPT command, but in any case, there's nothing there. > > Any idea where I can start to look for why it's blank? > > SMTP transaction snippet (via packet captures): > > local.58189-remote.00025: RCPT To:<[email protected]> NOTIFY=FAILURE ORCPT=rfc822; > DATA > remote.00025- local.58189: 501 5.5.4 Invalid arguments > remote.00025- local.58189: 503 5.5.2 Need rcpt command > > > thanks, > -wes > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
