The MaxMessageSize in sendmail applies to any message sendmail touches. Sendmail does not, for the most part, distinguish between inbound and outbound; messages are messages (the one place it does distinguish is in local address handling and local delivery).
POP does not fail with quotas, ipopd fails with quotas. ipopd copies the user's spool file then uses that copy, then copies it back. The default is to make this copy in the mail spool directory. Blech!!!!! First off, with large spool files that is a lot of CPU time spent copying files, and second the fact that it uses the mail spool file dir makes quotas unusable. The real fix for this is to use a POP server daemon that is more reasonable and can work off the actual spool file without making a copy. I use cucipop in part for this reason. You could patch and recompile the U of Washington source from the SRPM, but ipopd is just plain ugly and I prefer a better POP daemon that does not bring my (busy) mail servers to their knees with idiocy like file copies. I like quotas and tend to favor the combination of those with a MaxMessageSize. I have lots of wounds from the arrows slung when I have imposed quotas and message size limits, but in the end it has worked for the majority and penalized only the minority of abusers so it has been worth it. There are MTA's that will not accept if quotas are exceeded - try sending to a Yahoo account which has too much in the spool; the message is never accepted. I prefer to accept within limits then tell users that they will not receive until they clean up their act. Good luck. - rick warner _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
