Re: OK, the list *really* needs to be fixed

Might have been a new email client. I dunno. Bob S > On Jan 5, 2017, at 14:23 , Stephen Barncard via use-livecode > wrote: > > On Thu, Jan 5, 2017 at 2:21 PM, Bob Sneidar via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> And visible on the list. BTW you *are* using plain text

Re: OK, the list *really* needs to be fixed

On Thu, Jan 5, 2017 at 2:21 PM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > And visible on the list. BTW you *are* using plain text for your email > format? Yes. I got the memo about 10 years ago. -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org __

Re: OK, the list *really* needs to be fixed

And visible on the list. BTW you *are* using plain text for your email format? I have been bounced because I had rich text formatting or HTML or an attachment before. Not sure if "hold for moderator" is the same as a bounce tho'. Bob S > On Jan 5, 2017, at 14:18 , Stephen Barncard via use-liv

Re: OK, the list *really* needs to be fixed

Even though I got the 'too many bounces' notification yet again today, I'm still subscribed (as of this moment). sqb On Thu, Jan 5, 2017 at 9:14 AM, Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > > Mailman is an active project and seemingly well supported. Most of the

Re: OK, the list *really* needs to be fixed

Stupid Spell Correct!!! Bob S On Jan 5, 2017, at 14:05 , Stephen Barncard via use-livecode mailto:use-livecode@lists.runrev.com>> wrote: SHH! Nobody answer! Just don't call me 'barnyard' please. -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org ___

Re: OK, the list *really* needs to be fixed

On Thu, Jan 5, 2017 at 2:02 PM, Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > SHH! Nobody answer! Just don't call me 'barnyard' please. -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org ___ use-livecode mailing lis

Re: OK, the list *really* needs to be fixed

SHH! Nobody answer! On Thu, Jan 5, 2017 at 4:46 PM, Stephen Barncard via use-livecode < use-livecode@lists.runrev.com> wrote: > testing. > > -- > Stephen Barncard - Sebastopol Ca. USA - > mixstream.org > > On Thu, Jan 5, 2017 at 9:14 AM, Richard Gaskin via use-livecode < > use-livecode@lists

Re: OK, the list *really* needs to be fixed

testing. -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org On Thu, Jan 5, 2017 at 9:14 AM, Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > Heather Laine wrote: > > > It is possible that the only real solution here is to stop using > > Mailman. This could be quite

Re: OK, the list *really* needs to be fixed

Heather Laine wrote: > It is possible that the only real solution here is to stop using > Mailman. This could be quite disruptive to all, but is something > we will take under consideration. To be fair, this list has been > running on this software for... 18 years? Its not surprising if > it ulti

Re: OK, the list *really* needs to be fixed

Folks, I have been monitoring the lists and its bounces for a few weeks. The problem does appear to be the notorious DMARC issue, which our list software does not deal well with. I have made a change to the way it handles DMARC mail which may or may not help with the problem. You can and I'm sur

Re: OK, the list *really* needs to be fixed

Just got kicked again. *sigh* Despite successfully receiving a boatload of messages from the list today. On Tue, Jan 3, 2017 at 11:03 AM, Bob Sneidar wrote: > Fair enough, except that list servers are supposed to be configured in > such a way so as to get around this. A list server *should* se

Re: Security in 2017 (was "OK, the list *really* needs to be fixed")

The limitation goes back to the time when routers cost upwards of $200 and hardly anyone had one. Things are getting better now for some manufacturers but still not all. I'm more concerned these days about malware that attacks routers and the inability to find out if your current one is vulner

Re: Security in 2017 (was "OK, the list *really* needs to be fixed")

You may want to spend more than $35 on a router. ;-) Bob S On Jan 3, 2017, at 14:54 , J. Landman Gay mailto:jac...@hyperactivesw.com>> wrote: On 1/3/17 3:42 PM, Richard Gaskin wrote: My favorite example is wifi routers. They ship with a default password and login published in the manual, and

Re: Security in 2017 (was "OK, the list *really* needs to be fixed")

On 1/3/17 3:42 PM, Richard Gaskin wrote: My favorite example is wifi routers. They ship with a default password and login published in the manual, and more than 75% are never changed. And almost all the routers I've had over the years won't even *let* you change the login name. It's always "a

Re: Security in 2017 (was "OK, the list *really* needs to be fixed")

Bob Sneidar wrote: > And redundant backups are just one more vector to your data. Indeed it is. The old adage "physical access = root" still applies. I have a friend I met through my local Linux user group who does security audits. One of the most common sets of problems he finds isn't with

Re: Security in 2017 (was "OK, the list *really* needs to be fixed")

Hi Bob, That is both a great and terrible story! One really can’t make this type of story up either because it’s too bizarre. Sorry to hear that it was a true one for you! Thanks for sharing... Rick > On Jan 3, 2017, at 4:16 PM, Bob Sneidar wrote: > > And redundant backups are just one more v

Re: Security in 2017 (was "OK, the list *really* needs to be fixed")

Rick Harrison wrote: > Hi Richard, > > Remember that if just one bit/blob on your encrypted hard > drive becomes unreadable, then you could lose > everything on that drive. That makes redundant > backups over time even more important! That was why I've been putting it off for so long. But so f

Re: Security in 2017 (was "OK, the list *really* needs to be fixed")

And redundant backups are just one more vector to your data. Really, security has to be balanced with usability. Absolute security is to never write, type, speak or otherwise store any information you want to protect, or which might give clues to any information you want to protect. This is of

Re: Security in 2017 (was "OK, the list *really* needs to be fixed")

Hi Richard, Remember that if just one bit/blob on your encrypted hard drive becomes unreadable, then you could lose everything on that drive. That makes redundant backups over time even more important! Have a great secure NewYear! Rick > > This year I want to take this further. I just turned

Security in 2017 (was "OK, the list *really* needs to be fixed")

Bob Sneidar wrote: > DON'T CLICK THE LINK! Amen, brother. A wise default. Click nothing in an email unless you're certain it is what it claims to be. This article was eye-opening for me: The human attack surface, counting it all up Humans have become the primary attack surface for cyber

Re: OK, the list *really* needs to be fixed

Fair enough, except that list servers are supposed to be configured in such a way so as to get around this. A list server *should* send a separate email to each user in a list, NOT one email to ALL the users in the list. The latter will definitely get "DMARC'd" as spam, especially if the address

Re: OK, the list *really* needs to be fixed

In reply to this >> On 12/31/16 9:53 pm, J. Landman Gay wrote: So far, at least in this round, the people who have been dropped are using gmail addresses. I've read about issues with gmail before. If there is a way to whitelist the LiveCode list, that could help. Since the drops are caused by th

Re: OK, the list *really* needs to be fixed

Found this explanation: https://mail.python.org/pipermail/mailman-users/2015-December/080211.html It includes this: Let us say you have 5 users on your list, user1 at aol.com, user2 at aol.com, user3 at aol.com user4 at aol.com and user5 at aol.com. user1 at aol.com posts a piece of mail to yo

Re: OK, the list *really* needs to be fixed

Folks, My Apple mail program lets me see the actual link before I click it, by hovering the mouse over the link and examining the destination. I have gotten phishing that looks exactly like an email my bank would send. This season I've gotten many emails trying to alert me to a package that coul

Re: OK, the list *really* needs to be fixed

Concerning getting malware and subsequently getting all your cashed and saved email addresses sent to demonic entities known as "spam houses", I suppose the moral to this story is... DON'T CLICK THE LINK! Unless it's from friends and family, in which case... DON'T CLICK THE LINK! Unless it's

Re: OK, the list *really* needs to be fixed

It is possible that someone's list address got harvested and is being actively used for populating spam headers, in which case Google spam filters would have no way of discerning that the address or entire server was viable. Bob S > On Dec 31, 2016, at 11:55 , Richmond Mathewson > wrote: >

Re: OK, the list *really* needs to be fixed

hahahahahahaha that's funny. You don't get past the level 1, and they are always throwing it back on the other guy On Sun, Jan 1, 2017 at 1:26 PM, J. Landman Gay wrote: > I assumed Gmail is bouncing emails because the error mailman returns to > the list member is "too many bounces". It could be

Re: OK, the list *really* needs to be fixed

I assumed Gmail is bouncing emails because the error mailman returns to the list member is "too many bounces". It could be something else though. Apparently it doesn't happen to all Gmail users, only some, and if I remember right, some AOL and Yahoo addresses do the same thing. It might be use

Re: OK, the list *really* needs to be fixed

FYI: I am signed on with gmail and am having no problems. Bill > On Dec 31, 2016, at 4:24 PM, Mike Kerner wrote: > > Is gmail actually bouncing them? I thought that everything suspicious > ended up in the spam folder. > > On Sat, Dec 31, 2016 at 5:54 PM, J. Landman Gay > wrote: > >> No, not e

Re: OK, the list *really* needs to be fixed

Is gmail actually bouncing them? I thought that everything suspicious ended up in the spam folder. On Sat, Dec 31, 2016 at 5:54 PM, J. Landman Gay wrote: > No, not entirely sure, but I've read about it before. Google changes its > algorithms and spam filters frequently, so it's possible they've

Re: OK, the list *really* needs to be fixed

No, not entirely sure, but I've read about it before. Google changes its algorithms and spam filters frequently, so it's possible they've tweaked it again. Here's one article I found: If you google "gmail bounces mailman emails" there are thousands

Re: OK, the list *really* needs to be fixed

On Sat, Dec 31, 2016 at 11:53 AM, J. Landman Gay wrote: > Since the drops are caused by the refusal of the receiving domain, I don't > think there is much that LiveCode can do. There may be a refusal at the receiving end, but it is the server at livecode's end that is dropping members from the

Re: OK, the list *really* needs to be fixed

are we sure that is the reason? This problem is recent. I've been a member of the list with the same gmail address since 2005 without having these issues. On Sat, Dec 31, 2016 at 2:55 PM, Richmond Mathewson < richmondmathew...@gmail.com> wrote: > Doesn't say much for Google. > > Richmond. > > O

Re: OK, the list *really* needs to be fixed

Doesn't say much for Google. Richmond. On 12/31/16 9:53 pm, J. Landman Gay wrote: On 12/31/16 2:16 AM, Richmond Mathewson wrote: Really: only 4? It is a bit farcical. Richmond. On 12/31/16 12:48 am, Dr. Hawkins wrote: This is about the fourth time I've been unsubscribed in the last few mon

Re: OK, the list *really* needs to be fixed

On 12/31/16 2:16 AM, Richmond Mathewson wrote: Really: only 4? It is a bit farcical. Richmond. On 12/31/16 12:48 am, Dr. Hawkins wrote: This is about the fourth time I've been unsubscribed in the last few months. So far, at least in this round, the people who have been dropped are using gm

Re: OK, the list *really* needs to be fixed

Really: only 4? It is a bit farcical. Richmond. On 12/31/16 12:48 am, Dr. Hawkins wrote: This is about the fourth time I've been unsubscribed in the last few months. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url

Re: OK, the list *really* needs to be fixed

A very popular listserve named “Mailman” does this. It comes with most VPS hosting service. Bill > On Dec 30, 2016, at 6:29 PM, Mike Kerner wrote: > > Unfortunately several newsgroups I belong to do something like this - and > the Valentina one, even helpfully sends me an email in the clear onc

Re: OK, the list *really* needs to be fixed

Unfortunately several newsgroups I belong to do something like this - and the Valentina one, even helpfully sends me an email in the clear once a month with my password, no matter what. Uncool. On Fri, Dec 30, 2016 at 8:48 PM, Kay C Lan wrote: > Yes same here, but what is far more concerning to

Re: OK, the list *really* needs to be fixed

Yes same here, but what is far more concerning to me is that the Notification I get to remedy the situation includes a link to log in AND my password. Is this not a security hole just waiting to be exploited? If I go to the link and I can't remember my password there should be a 'forgot password' l

OK, the list *really* needs to be fixed

This is about the fourth time I've been unsubscribed in the last few months. -- Dr. Richard E. Hawkins, Esq. (702) 508-8462 ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subsc