Re: Apologies for spam - we will blacklist that account right away

[Harish Pillay]

[we are getting way off topic here]

On Dec 27, 2007 9:02 PM, GWMobile <[EMAIL PROTECTED]> wrote:
>
> I strongly disagree with you here.
> Email should be instanteous and if the specs haven't been updated to
> call for that then the specs are outdated.

http://www.faqs.org/rfcs/rfc2821.html section 4.5.4.1 on "Sending Strategy"
says:

  "The general model for an SMTP client is one or more processes that
   periodically attempt to transmit outgoing mail.  In a typical system,
   the program that composes a message has some method for requesting
   immediate attention for a new piece of outgoing mail, while mail that
   cannot be transmitted immediately MUST be queued and periodically
   retried by the sender.  A mail queue entry will include not only the
   message itself but also the envelope information.

   The sender MUST delay retrying a particular destination after one
   attempt has failed.  In general, the retry interval SHOULD be at
   least 30 minutes; however, more sophisticated and variable strategies
   will be beneficial when the SMTP client can determine the reason for
   non-delivery.

   Retries continue until the message is transmitted or the sender gives
   up; the give-up time generally needs to be at least 4-5 days.  The
   parameters to the retry algorithm MUST be configurable."

> I don't stay on groups with email delays because it is impossible to
> have a conversation.

It would more appropriate if the right tools were used for the right job.
If you need to have "instantaneous conversations", email was never
meant for that.  IRC and instant messaging is what you need.  Email
is great for threads of discussions that can be archieved, searched
and worked on.

However, if you think it is important that email be instantaneous like
IRC, do please work on updating RFC2821.

Regards.
---
Harish Pillay [EMAIL PROTECTED] gpg id: 74609E3
fingerprint: F7F5 5CCD 25B9 FC25 303E 3DA2 0F80 27DB 7468 09E3

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Subject prefix for e-mails

[Galevsky]

On Dec 27, 2007 5:45 PM, Mikhail Gusarov <[EMAIL PROTECTED]> wrote:
> Colan Schwartz <[EMAIL PROTECTED]> writes:
>
> > Would it be possible to add a descriptive prefix to each e-mail sent
> > to this list?
>
> List-Id: List for OpenMoko community discussion 
>
> Isn't this header enough for you?
>

I agree, all the info are already provided, and you have to setup your
MUA to fit your needs. (sort your mails by sender, List-Id,
...whatever you want)

Gal'

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Subject prefix for e-mails

[Mikhail Gusarov]

Colan Schwartz <[EMAIL PROTECTED]> writes:

> Would it be possible to add a descriptive prefix to each e-mail sent
> to this list?

List-Id: List for OpenMoko community discussion 

Isn't this header enough for you?

-- 
JID: [EMAIL PROTECTED]

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Subject prefix for e-mails

[Ted Lemon]

On Dec 27, 2007, at 11:24 AM, Colan Schwartz wrote:
Would it be possible to add a descriptive prefix to each e-mail sent  
to

this list?  I don't mind getting a lot of e-mail, but if it's from a
list, I'd like to know where it's coming from.


Suggestion: hack your tool to sort on the List-Id: header.   Redundant  
sorting info in the subject line is unnecessary, and also makes it  
harder yo see the entire subject line.



___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Subject prefix for e-mails

[Colan Schwartz]

Hi all,

Would it be possible to add a descriptive prefix to each e-mail sent to
this list?  I don't mind getting a lot of e-mail, but if it's from a
list, I'd like to know where it's coming from.

I've got this working for all of my Mailman lists, so I know it's
possible.  (IIRC it needs to be set on the list config page.)  How about
something like "[OMCommunity]".  I don't really care what it is exactly,
as long as it's identifiable.

Thanks,
-c.
--
Colan Schwartz
Internet Consultant  |  Openject Consulting  |  http://www.openject.com/

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Case Schematics

[Jeremiah Flerchinger]

I have no clue why dimensional drawings or 3D models of the Neo haven't 
been released either.  People have been requesting them for quite some 
time to explore alternate case designs 
(http://wiki.openmoko.org/wiki/Hardware:Neo1973:Alternate_Cases).  I 
myself would be happy with something as simple as a Wavefront object 
file, since almost any CAD tool can import these.


Joe Pfeiffer wrote:

Gabriel Ambuehl writes:
  

On Wednesday 26 December 2007 21:11:18 Michael Shiloh wrote:


The main reason IIRC is that some of the chips came with NDAs that
prevent us from doing so.

  

You have chips in the case? oOOOo



Well, the original request was phrased strangely -- the case wouldn't
*have* schematics!  Presumably what was meant was dimensional drawings
(which also haven't been released, for reasons that escape me).


___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

  
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Turning Off The Display

[Nick Guenther]

On 12/26/07, Thomas Gstädtner <[EMAIL PROTECTED]> wrote:
> Hey there,
>
> does somebody know if it is possible to turn off the Neo's display?
> Currently only the backlight is disabled and the display still stays on
> (what's totally useless and a waste of energy).
> I tried to use xset, but the driver seems not to support dpms.
> Any hints?
> To recognize that the display stays on when the backlight is off you need a
> high-contrast background (the screenlock-background has nearby no contrast,
> so you won't see it, but you can open the vkeyboard which stays opened even
> if the Neo is locked) and a flashlight. :)

The display goes off under QTopia, so it's possible.. I don't know how
to do it under OM.

-Nick

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Apologies for spam - we will blacklist that account right away

[François TOURDE]

Le 13874ième jour après Epoch,
GWMobile écrivait:

> Email should be instanteous and if the specs haven't been updated to
> call for that then the specs are outdated.

??? Why eMail *should* be instantaneous?

> I don't stay on groups with email delays because it is impossible to
> have a conversation.

Try Jabber or IRC, if you need conversations. In ML we don't tell that
conversations but threads.

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Announce nightly build and source code packages

[John Lee]

Hi,

The nightly build is automatic now and could be found under
http://buildhost.openmoko.org/daily/

It pulls from monotone.openmoko.org, which means it will be a couple
days behind the mainline OE with some fixes to make sure OM builds.
It will also have moko-autorev enabled so it will always build the
latest OM related packages.  So, if you want to use packages on the
bleeding edge, you could direct your ipkg to pull from here.

If a developer want to retrieve the source code of an existing
application inside OM, he/she had to check the OE recipes to find out
the exact download location, version and the patches on it to fix
bugs/compiling errors before.  Now the orig and diff source tarballs
will be generated along with the nightly build.  They could be found
under

http://buildhost.openmoko.org/daily/tmp/deploy/glibc/source/

Please report any bugs/feedbacks.  Thanks!

Regards,
John

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Apologies for spam - we will blacklist that account right away

[GWMobile]

Just don} worry about spam so much.
It has rarely been a problem on this or mos t groups and fighting it 
isn't worth the inconvience.


It just isn't a problem.
I find it far easier simply to scroll past the occasionally bit of spam 
that deal with the "solutions" that make me jump through hoops just to 
post a message.


The solutions are much worse than the problem.
Just don't worry about it.


On Wed, 26 Dec 2007 11:17 am, Thomas Szukala wrote:

Harish Pillay wrote:

May I make a suggestion to whoever is running this mailing list to add
the greylist technique to it as well?  I have had milter-greylist 
running on

my main email servers for over 12 months now, and the amount of spam
reaching my users/mailing lists has gone down to almost zero.


I know greylisting works and is stopping spam very effective (for now).
However this behaviour puts high volume mailservers in a lot of stress. 
Also I am experiencing, that spammers are adapting to greylisting and 
are connecting multiple times to mailservers. Supposedly in order to 
pass greylisting.
Thus, the administrators of these high volume mailservers  have to get 
rid of several thousands incoming connections per minute from a single 
spammer (think of a botnet DDoS you) and delayed outgoing connections 
for your customers.
You therefore have a higher deferr rate outgoing  (doubling outgoing 
connections) and therefore have a bigger mailqueue, additionally you 
have more incoming connections (spam) blocking your available TCP ports 
permanently only for the cause to reject them.


So my advice would be to not use greylisting, as it pushes the problem 
to other parts of the internet and is effective only for a limited time 
(if anyone is using it).


My thought is, that it would be much more effective to block 
subscription by sophisticated captchas (take care of XSS 
vulnerabilities ) . Also it might be effective to block subscriptions 
by using lists of compromised hosts like CBL 
().
Try to identify which IPs are causing trouble and do match them with 
several blacklists. The lists do not always work in the same way as it 
does for others. Sometimes also only a mix of several lists are 
working.  might help you there.


If you dont have enough samples, be conservative. It is more a hassle 
to gain legitimate listmembers back, who you have been lost during 
subscription, as blocking fake accounts afterwards.


Have an eye on your subscriptions. Too many new listmembers is 
certainly not a cause of marketing.


I might have come a little off topic, but perhaps it helps someone.

I am now getting back to my cookies, ice cream, cake and teas ;-)

Cheers Thomas


___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


www.GlobalBoiling.com for daily images about hurricanes, globalwarming 
and the melting poles.


www.ElectricQuakes.com daily solar and earthquake images.

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Apologies for spam - we will blacklist that account right away

[GWMobile]

I strongly disagree with you here.
Email should be instanteous and if the specs haven't been updated to 
call for that then the specs are outdated.


I don't stay on groups with email delays because it is impossible to 
have a conversation.



Perhaps I should mention here for completeness that, I had to spend 
some
minimal time reinforcing the idea that email is NOT instantaneous and 
that
one has to expect delays.  The SMTP protocol amply explains this 
principle.
We have gotten spoilt thinking that email is immediate, when it is best 
efforts.



www.GlobalBoiling.com for daily images about hurricanes, globalwarming 
and the melting poles.


www.ElectricQuakes.com daily solar and earthquake images.

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re:

[Marcin Juszkiewicz]

Dnia czwartek, 27 grudnia 2007, rakshat hooja napisał:

>  Just wanted to inquire  if anyone on this list has managed  to get
> poky linux  and sato to work with the Neo 1973.

Poky Linux with Sato interface is what I have on my older Neo. To build it 
you need to have Poky working and then build 'poky-image-sato' 
for 'fic-gta01' MACHINE. Keep in mind that this image will not contain 
phone apps.

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

  Monday is a hard way to spend one-seventh of your life.



___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re:

[rakshat hooja]

Hi,
 Just wanted to inquire  if anyone on this list has managed  to get
poky linux  and sato to work with the Neo 1973.

thanks in advance

Rakshat
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community