|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Throttling outbound mail rates on a per-user basis
From: Alex van den Bogaerdt (alex
ergens.op.het.net)
Date: Wed Nov 03 2004 - 03:30:33 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> > > > > [alex]
> > > > > This is why the policy daemon would need to remember. The documentation
> > > > > seems to indicate it can do so.
> > > >
> > > > [cami]
> > > > How exactly? Each 'call to the policy daemon' is a completely
> > > > new connection.
> > >
> > > [wietse]
> > > The Postfix policy client will reuse a connection if possible.
> > > However, the policy server may terminate, or the connection between
> > > Postfix and policy server may time out.
> > [alex]
> > I will rephrase my question:
> >
> > What does
> > The "instance" attribute value can be used to correlate different
> > requests regarding the same message delivery.
> > mean?
>
> [wietse]
> Which part is not clear.
I am not sure if it is not clear at all. What certainly is not clear
to me is _if_ I interpret the whole line correct. This in combination
with your replies on the subject.
I think it is best to repeat an example I tried, then ask some questions:
A partial smtpd conversation :
input> mail from:<sender>
call to policy daemon
input> rcpt to:<recipient1>
call to policy daemon
input> rcpt to:<recipient2>
call to policy daemon
input> rcpt to:<recipient3>
call to policy daemon
input> data
call to policy daemon
input> email headers and body
input> .
call to policy daemon (the proposed end_of_smtpdata stage)
Will the instance attribute be the same during all of these calls
to a policy daemon? (note: "a policy daemon", not necessarily the
same one)
Will the instance attribute be different when other messages are
processed (either by the same policy daemon or by another instance)
A more pragmatic question: Will above example allow the process around
the policy daemon to gather the following information about a message:
- its sender
- all of its recipients
- the content of the message (provided the proposed addition is available)
Why need I ask? Well, from the documentation I seem to learn it is
possible to track a single message during multiple calls to _a_ policy
daemon. Your replies on this subject are confusing, at least for me.
You seem to indicate tracking a message is either impossible or at least
unreliable. For instance see the top of this post.
So, either I interpret your answer the wrong way, or I interpret the
documentation the wrong way.
Thank you,
Alex
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]