From my understanding of RFC 1870, there is nothing wrong with a message with a content of zero size.
One option to trap such messages would be to use the body_checks postfix filter, but that's "expensive". Another option that might be more efficient would be to use a procmail filter on the mail host side to check the message content. The following works if put in your .procmailrc file: :0 * ! B ?? ... zero-length-body-folder or if you want to just throw it away, :0 * ! B ?? ... /dev/null I'm not sure why you have a problem with zero-length messages in the first place -- is it a spam or DOS issue? --Tobias Benny Pedersen wrote: > On Thu, November 29, 2007 18:18, John Beaver wrote: > > >> Please start a new thread for new topics. >> > > i belive its related to the thread here > > >> Most MUA's do not report this (outlook, OE are two). You cannot (and >> should not) depend on the MUA's to provide this information. The only >> reliable way to use size is to call policyd after DATA. Search the >> postfix/policyd archives for the discussion on throttle by size for the >> details. >> > > so size= in data stage is done from what postfix see sent ?, i will have this > in mind on my own policy daemond > > optinal if sasl send a report back mail to users that have mua that sends with > size=0 to get the problem fixed > > still i belive its related to the thread > > ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
