[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Force independent smtp delivery sessions?

On Fri, Aug 30, 2002 at 02:21:19PM -0600, Daryle A. Tilroe wrote:
> Is there a way (in scheduler.conf?) to force independent delivery
> sessions to a particular domain/mx?  I.E. if I have a message going
> to 5 recipients @fu.bar I would like to force the scheduler to deliver
> it with 5 separate sessions to mx.fu.bar with 1 recipient rather than
> 1 session to mx.fu.bar with 5 recipients.

  At scheduling level we can not do that.  Rewriting parts of routing
  might do that, though.  -- 10 seconds latter I realized that no, that
  can't be done.  (channel/host/user/privilege -quad, the 'host'
  part must be the user's destination domain.  It can't be the full
  recipient address, which would take care of parallellizing
  each recipient address just fine...)

  The "EZMLM" tricks in smtp transport agent are related to what
  you are looking for, although those don't do 5 parallel sessions
  either, merely 5 successive deliveries of the same message with
  separate MAIL FROM addresses.


    1) New code at SMTP-ta to enable the 'host' part to be full
       user address, and make changes into router scripts to have
       them produce the address quad as channel/user/user/priv
       This gives parallel deliveries to the system.

    2) New code at SMTP-ta to control behaviour somewhat alike
       the present "ezmlm" to split deliveries into N ( << 100 )
       rcpt per transmission.  Also to limit the number of delivered
       messages per connection...

  All those are what I call "anti-performance" features, but out
  there are a few ISP sites which presume they can e.g. limit
  the number of messages delivered in single connection.

  Of course the _spammers_ send single recipient single message
  per session, only weird systems running busy lists send
  multirecipient multi-messages per connection...

  For the  2)  there needs to be some better way to make
  parametrization, than at scheduler's command line..
  I have though of a few ways, including something which
  does greatly resemble  scheduler.conf  file syntax...

> -- 
> Daryle A. Tilroe

/Matti Aarnio	<mea@nic.funet.fi>
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi