On Thu, Mar 15, 2012 at 8:07 AM, Francesco Gennai
<francesco(_dot_)gennai(_at_)isti(_dot_)cnr(_dot_)it> wrote:
Is this really a big enough problem to be worth solving? I can't
recall a single instance where I received IETF list with a problematic
attachment.
i travel to places with very poor bandwidth. it is a problem.
and the vast majority of users just do not get it. "we send 20mb
documents around the office all the time. suck it up."
for who has problem in attachment downloading the solution should be
at the delivery Message Store level, where the strip of the attachment could
be
done accordingly to an user configurable mailbox parameter
(as we do on our server, where we call it Easy Delivery).
Francesco
randy
A proposal: what about something configurable? Everyone already has a
personal "setup" page for his/her own mailman account. It would
suffice to add an option "send attachment as link," possibly with a
configurable threshold. Honestly, I do not anything about the
internal structure of mailman, so I do not know if this would be a
huge change (wrt the "pure link" solution) or not. But, you know,
"nothing is impossible if you do not have to do it..." :)
For me, I like the idea of using the link since, depending on where I
am, I work with different PCs. Because of this, I read the mail via
web services and I do not download it on my local disk. Large
attachments clog up my quota (do you see why I am using a gmail
account?). However, I understand the "dual" situation where people
download the mail on local disk and the "physical" attachment would
allow them to have the attachment even when offline.
Letting each one doing his/her choice looks like a good compromise to me.
Riccardo