[Mimedefang] Re: Simplified single purpose mimedefang-filter

[reader at newsguy.com]

"Paul Murphy" <pjm at ousekjarr.org> writes:

> How much work is it to add a switch to the startup file?
>
> Plus, if you are trying to work out why external messages are failing, none
> of this helps - the only information you need is in the Sendmail log, where
> it confirms that the external relay accepted the message.  From that point
> on, they accept responsibility for delivering it - follow it up with them.

I'm starting to catch on a little here I guess.  In this  case I
already know that ISP mail hub accepts the message.  Just the verbose
output of mailx -v confirms that much.

The `follow it up with them' is probably a non starter.  The ISP is
sbcglobal and calling as a user and expecting to get detailed
information from their mail logs seems like quite a long shot.

I had hoped to see someting in the full smtp conversation with
sbcglobal that might cause trouble further along.  I think sbcglobal
pretty much accepts what ever I send as long as authentication is
correct.

For example ... in this SMTP conversation:

  Leaving my machine:

>>> MAIL From:<reader at reader.local.lan> SIZE=80 AUTH=reader at reader.local.lan
250 2.1.0 <reader at reader.local.lan>... Sender ok
>>> RCPT To:<bobbie at lydia-productions.com>
>>> DATA
250 2.1.5 <bobbie at lydia-productions.com>... Recipient ok
354 Enter mail, end with "." on a line by itself
>>> .

   Connecting to smtp smarthost

  050 <bobbie at lydia-productions.com>... Connecting to smtp.sbcglobal.yahoo.com via relay...
  050 220 smtp101.sbc.mail.mud.yahoo.com ESMTP
  050 >>> EHLO reader.local.lan
  
         reader.local.lan is a home lan IP not a real internet IP so
         any lookups would fail... apparently none are done because
         the incoming smtp has the correct authentication.
  
   
  050 250-smtp101.sbc.mail.mud.yahoo.com
  050 250-AUTH LOGIN PLAIN XYMCOOKIE
  050 250-PIPELINING
  050 250 8BITMIME
  050 >>> AUTH LOGIN
  
               Authorization is accepted below
              
  050 334 VXNlcm5hbWU6
  050 >>> aHByZWFkZXJAc2JjZ2xvYmFsLm5ldA==
  050 334 UGFzc3dvcmQ6
  050 >>> amlueDIxNw==
  
               We are given the go ahead.
             
  050 235 ok, go ahead (#2.0.0)
  050 >>> MAIL From:<reader at reader.local.lan> AUTH=<>
  050 250 ok
  050 >>> RCPT To:<bobbie at lydia-productions.com>
  050 >>> DATA
  050 250 ok
  050 354 go ahead
  

So the mail is passed on by smart host but must still contain envelope
sender which is not something that can pass any type of lookup.

99% of my mail works fine its just one kind of scenario that doesn't
and with my meager knowledge of all this I'm having a time debugging it.