[Oeva-list] list management question

[S. Jain]

Tweetyourmail.com is owned by a friend of mine. If you have any feature requests, send them to me and i'll forward them on!
My first test post were the Nissan LEAF vids Patrick posted.

thx, Shashi



________________________________
From: "patrick0101 at gmail.com" <patrick0101 at gmail.com>
To: OEVA <oeva-list at oeva.org>
Sent: Fri, December 18, 2009 9:21:11 PM
Subject: Re: [Oeva-list] list management question

tweetyourmail.com is one simple way to share a large email. You it to them, they make into a webpage and give you a link that you can share. Readers do not need to join. I had looked in to wuala a long time ago, it was not as simple, but maybe it is better now.

Here are a couple tweetyourmail examples: 
http://www.tweetyourmail.com/mails/18861/SmartGridSeminar2010.aspx
http://www.tweetyourmail.com/mails/18860/NevertakeGRANDMAtoCOURTSundaysnicker.aspx

However, I am OK with any email less than 1GB :)
 
Regards,
Pat
With Great Power, Comes Great Current and High Voltage   =D~



On Fri, Dec 18, 2009 at 12:35 PM, Alan Batie <alan at batie.org> wrote:

>
>With modern mail being what it is, I'm considering substantially
>>relaxing content limits on the list, and wanted to find out what the
>>group thought was appropriate.  This shorepower newsletter is a good
>>example of both issues:
>
>>1.  It's relatively commercial.  Do people want that here?
>>2.  Actually, it's not bad size wise, so it's not really a good example
>>there, but how big is too big for people?  I'll make a plug for
>wuala.com as a really easy to use app for sharing large items with web
>>links...
>
>>These questions seem to pop up here more often than other lists I
>>manage, so I thought I'd revisit it...
>
>
>http://hosted.verticalresponse.com/443717/2c074e0677/1740501003/c02bd726ef/
>
>
>_______________________________________________
>>Oeva-list mailing list
>Oeva-list at oeva.org
>http://www.rdrop.com/mailman/listinfo/oeva-list
>
>



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20091218/3931a0ec/attachment.html