🚀 go-pugleaf

In article <840048160snx@trmphrst.demon.co.uk>
           nikki@trmphrst.demon.co.uk "Nikki Locke" writes:

> The .wrk file contains at least 3 lines of routing information - the
> destination domain, the fully qualified sender name, and the fully
> qualified recipient name(s). There can be any number of recipient lines -
> the message body is delivered once to the MX address for the
> destinanation domain. The MX machine is told the person on the second line
> is the sender. The remaining lines are sent to the MX machine as RCPT 
> commands - i.e. addresses to which the mail should be sent.

Thanks for the reply, but these wrk/txt files are not those
whose structure I was asking about :-(, but rather those
produced by ka9q/216d for re-routeing *incoming* mail (which
whilst named similarly are structured differently); apologies
if I didn't make that clear in the original post.

The most complex .wrk file I've found to date has the form:

  From: someone@domain.somewhere
  To: localuser

That's it!  However, looking at the way in which ka9q deals
with (direct) mail delivery, it appears possible that such
file could conceivably contain:

  From: someone@domain.somewhere
  To: localuser
  To: anotherlocaluser
  To: someoneelse@anotherdomain.elsewhere
  To: someone%hack@mydomain.here
  To: ...etc. (various combs of above)

To date, I haven't managed to create such a file (by sending
mail to myself!).  However, I've been using ka9q (+pcelm) for
these test postings, so the question was more whether other
MTAs could coerce ka9q's smtp server into creating a .wrk
file anything like the 2nd example.

Any thoughts on that?
-- 
Pete