Thanks,
Rob
Rob Tanner
UNIX Services Manager
Linfield College
McMinnville, Oregon
Caution, any properly implemented MTA will cope with any recipient
count limit. It just remembers where it had to stop, sends the
message content, and then it sends another batch of recipients
followed by message content until it is done.
A sender-dependent limit requires different IP addresses for
different senders.
/etc/postfix/master.cf:
1.2.3.4:smtp ...... smtpd -o smtpd_recipient_limit=nnn
1.2.3.5:smtp ...... smtpd -o smtpd_recipient_limit=mmm
In theory, many parameters could be changed to accept lookup tables
that are indexed by client etc. info, but it adds a great deal of
complexity to Postfix.
Wietse
> Both incoming and on-campus mail hit the same postfix server. Since a lot
> of the SPAM we get are singles messages addressed to a bunch of people, I
> would like to set the smtpd_recipient_limit to a very low value (around
> 25).
That won't help, since an MTA will split mail to lots of people
according to the recipient limit. (1000 = 25 x 40)
> But folks on campus often send mail to addressed to far more
> recipients than that.
They send the mail to your internal Postfix (no or a large limit)
which then will send the mail out, chunked to 25 recipients.
> Is there a way I can treat mail on-campus mail (mail originating in
> $mydomain)
mynetworks!
> different from incoming mail with regard to the
> smtpd_recipient_limit?
Use another smtpd, listening on an internal interface with different
settings.
--
Ralf Hildebrandt Ralf.Hil...@charite.de
my current spamtrap partmap...@charite.de
http://www.arschkrebs.de/postfix/ Tel. +49 (0)30-450 570-155
The doctrine of human equality reposes on this: that there is no man
really clever who has not found that he is stupid.