Hi Martin,
>> this bugreport is open for more than two years, I've just taken over
>> maintenance of
>> the package. I'm not sure which part of policyd-weight your bugreport is up
>> to
>> (documentation, setup-instructions, etc.)?
>
> Probably documentation.
It would be helpful if you could tell me what part of the documentation is
relevant.
I've just repackaged the latest policyd-weight version, it's already in
unstable. I've
grep'ed for "recipient", here's what I get:
changes.txt:- (change/new) Log outputs also recipient
changes.txt:- improved multirecipient awareness. It is now possible to build up
restriction
changes.txt:- X-policyd-weight header for multirecipient mail is now inserted
only once
changes.txt:- (fix) The special recipients postmaster and abuse pass now with
DUNNO instant.
documentation.txt: smtpd_recipient_restrictions =
documentation.txt: smtpd_recipient_restrictions =
LICENSE:gratis or for a fee, you must give the recipients all the rights that
LICENSE:want its recipients to know that what they have is not the original, so
LICENSE:and give any other recipients of the Program a copy of this License
LICENSE:Program), the recipient automatically receives a license from the
LICENSE:restrictions on the recipients' exercise of the rights granted herein.
man/man8/policyd-weight.8:multirecipient mail intact, i.e. provide the
functionality of selective usage
man/man8/policyd-weight.8:based on recipients.
man/man8/policyd-weight.8:smtpd_recipient_restrictions =
man/man8/policyd-weight.8:smtpd_recipient_restrictions =
policyd-weight:# smtpd_recipient_restrictions =
policyd-weight: '<to=' . $attr{recipient} . '>' ;
policyd-weight: my $rcpt = $attr{recipient} || '';
policyd-weight: if($attr{recipient} && $attr{recipient} =~
/^(postmaster|abuse)\@/)
policyd-weight: return('DUNNO mail for '.$attr{recipient});
policyd-weight: return ('DUNNO multirecipient-mail - already accepted by
previous query');
policyd-weight: return ($my_REJECTMSG.' (multirecipient mail)' );
Can you tell me, where the documentation problem resides?
>> >From the technical view policyd-weight inspects the sender address not the
>> >recipient
>> address. In the default settings in Postfix and in Debian
>> "smtpd_delay_reject = yes"
>> is set. With this setting Postfix waits until the RCPT TO command before
>> evaluating
>> $smtpd_client_restrictions, $smtpd_helo_restrictions and
>> $smtpd_sender_restrictions,
>> or wait until the ETRN command before evaluating $smtpd_client_restrictions
>> and
>> $smtpd_helo_restrictions. Therefor also policyd-weight is mostly configured
>> in the
>> smtpd_recipient_restrictions within the Postfix configuration.
>>
>> http://www.postfix.org/postconf.5.html#smtpd_delay_reject
>>
>> So, from the view of the postfix MTA it is mostly a
>> smtpd_recipient_restriction.
>
> I know Postfix very well, and I am familiar with
> $smtpd_delay_reject. I disagree, however, that this makes
> a restriction that looks at the sender address "mostly configured in
> the smtpd_recipient_restrictions".
> I would agree if you said: since Debian sets $smtpd_delay_reject by
> default, it doesn't matter where you put it. However, it remains
> a sender restriction.
Same here, i also know Postfix well and we have to reduce this bug to a common
denominator :)
Technically it remains a sender restriction which I don't negate. As
smtpd_delay_reject is set
in Debian per default it makes no difference where you put it in, correct.
kind regards,
Werner Detter
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
