On Mon, 2005-11-28 at 20:14 +0100, Arnaud Taddei wrote:
> I meant that I have concrete examples of painful abuse of users adding
> too large attachments to mails and there was no way to prevent that to
> happen.
All that's needed for preventing abuse is for server to have a "maximum
message size" setting. The capability would only be helpful for some
client software to show a friendly error message..
I'm not all that sure that it's such useful. It could work just as well
by:
1 APPEND box {105906176}
1 NO [ALERT] Sorry, we have a 100MB message size limit. Couldn't save
your message.
But sure, literal+ extension is a problem since it can't give the
failure immediately but first has to read the 100+MB of mail before
doing it. Or I guess it could send the error back immediately and then
just disconnect.
BTW. Are other people also getting these messages twice? Looks like this
server keeps re-posting messages to imapext:
Received: from xms.co.za ([196.211.28.218]) by above.proper.com
(8.12.11/8.12.9) with ESMTP id jASJ0btN099957 for <ietf-imapext@xxxxxxx>;
Mon, 28 Nov 2005 11:00:53 -0800 (PST) (envelope-from
imap-protocol-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx)
Received: from mail pickup service by xms.co.za with Microsoft SMTPSVC;
Mon, 28 Nov 2005 21:00:58 +0200
Looks like only messages crossposted to both imap-proto and imapext have
that problem.
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Imap-protocol mailing list Imap-protocol@xxxxxxxxxxxxxxxx https://mailman1.u.washington.edu/mailman/listinfo/imap-protocol