--
You received this message because you are subscribed to the Google Groups "Dixonary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dixonary/E743262B-ECFF-4AED-902B-603310076CAD%40verizon.net.
--
You received this message because you are subscribed to the Google Groups "Dixonary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dixonary/0c37837a-f27b-ed22-a8c7-dcfabfbd2477%40siam.co.uk.
--
You received this message because you are subscribed to the Google Groups "Dixonary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dixonary/90ff376a-3430-40ca-812b-a4e78434f9cbo%40googlegroups.com.
13. Deadlines are to be no less than 32 nor more than 48 hours from the time they are posted, and must specify a time zone (for example, EDT).
The 1990 rules say “no less than 24 nor more than 36 hours.” This is unequivocal, but precedent, especially since 2005, has modified it.
In the mid-90s, deadlines were generally close to 24 hours, except at weekends: there used to be an unwritten rule, now long irrelevant, that slowed or stopped the clock over weekends, to suit players who had online access only at work.
Email messages may encounter delays of a sort that were not possible with realtime CompuServe forum messages. Such delays make 24-hour deadlines less workable than they once were.
A 24-hour deadline that ends between 01h00 and 09h00 US Eastern Time is effectively 18 hours for the majority of players. In the early years of the game, nearly all the players lived in North America, and would have had no occasion to set such a deadline. That is no longer true.
For these reasons, many players now consider a 24-hour deadline unacceptably short.
Dealers have always felt free to extend the deadline beyond the 1990 rules’ 36-hour limit to take account of other demands on their time, or the likely availability of players. Deadlines of 48 hours or more on US and non-US holiday weekends have never evoked protest, but without such excuse, deadlines longer than 48 hours have done so.
The reworded rule attempts to capture the apparent current consensus that a deadline should not be shorter than 32 hours, for any reason; and also not much longer than 48 hours, without good reason. A 36-hour deadline is uncontroversial and remains within the letter of the 1990 rules.
I usually try to do 36 (minus an hour or so to collect/post/etc.) when I deal. The math is easy for determining the deadline.
I might disagree that the “weekend” reference is no longer relevant, at least in the current environment. WFH every day makes it harder to set work/home boundaries and I’ve been intentionally “unplugging” on the weekends. So I’m rather happy with the 48-hour weekend deadlines but 36 hour weekday deadlines.
To view this discussion on the web visit https://groups.google.com/d/msgid/dixonary/42080536-5A5E-4A2D-9FD6-B4D58BD0A6F6%40gmail.com.
--
You received this message because you are subscribed to the Google Groups "Dixonary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dixonary/1708887836.20200714141144%40isanybodyhome.com.
I notice that recently Mike has been doing the same thing - I
notice it particularly when anyone votes - "dixonary votes for" is
not informative
I have to hit 'reply' to see who it was who voted and then cancel
the 'reply'
Please can we post from our own addresses rather than from the
group
--
You received this message because you are subscribed to the Google Groups "Dixonary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dixonary/35bc4f8e-c57f-15cf-9730-c570857682c1%40john-barrs.co.uk.
This is correct, that the website has changed behavior, about a year ago. Google is trying to “protect” us from forged messages.
Basically, we don’t really know for sure that Efrem or Mike is actually the sender of their email messages to the group. Anyone could be sending those emails, because they are not properly authenticated.
Technical details involve DMARC policy, DKIM, and SPF, for those who want to google.
When sender authentication, the group changes how the sender appears, making it look like the mail is from the group itself and not an individual.
This is frustrating for multiple reasons, as email clients now think these senders own the dixonary group email, sometimes losing track of the group’s name, or losing track of the senders’ real email addresses. And some clients don’t even display the sender’s name. Without the signature “Mike” or a more modern client that interprets the headers, it gets really confusing.
I have searched and can find no settings on the group to change or disable this behavior.
The solution is for the senders to use a properly authenticated SMTP server authorized by the email address domain they are using.
In Efrem’s case, he is using a verizon.net email but sending via a yahoo SMTP server (probably smtp.mail.yahoo.com) which is not authorized for Verizon mail.
He should use a better one from this list: https://www.verizon.com/support/knowledge-base-17067/ , probably the outgoing.yahoo.verizon.net one.
Mike’s case is a little more complicated, as the header warns of authentication issues, related to a local network IP address. I’m not sure how the salsgiver.com email path is set up, but it needs fixing so google doesn’t think it’s forged.
Received-SPF: pass (google.com: domain of sta...@salsgiver.com designates 206.67.234.106 as permitted sender) client-ip=206.67.234.106;
Received: from [192.168.1.5] (216-221-10-19.dsl.salsgiver.com [216.221.10.19] (may be forged))
(authenticated bits=0)
by email.salsgiver.com (8.15.2/8.15.2) with ESMTPA id 06EK2rSC021816
for <dixo...@googlegroups.com>; Tue, 14 Jul 2020 16:02:54 -0400 (EDT)
(envelope-from sta...@salsgiver.com)
X-Authentication-Warning: email.salsgiver.com: Host 216-221-10-19.dsl.salsgiver.com [216.221.10.19] (may be forged) claimed to be [192.168.1.5]
If all else fails, setting up a gmail account (or a dixonary.net one!) just for the game, and processing all game email through it, should work.
From: Dixonary <dixo...@googlegroups.com>
Reply-To: Dixonary <dixo...@googlegroups.com>
Date: Tuesday, July 14, 2020 at 1:02 PM
To: Dixonary <dixo...@googlegroups.com>
Subject: Re: [Dixonary] Round 3088 word: FANA
I have not changed the way I have posted. It is the dixonary website that has changed.
--Mike
To view this discussion on the web visit https://groups.google.com/d/msgid/dixonary/aebf15c5-b146-e8e7-9d9e-c208fa3526cc%40salsgiver.com.
Thanks Dan
It is good to know that it is not us who are 'challenged'
To view this discussion on the web visit https://groups.google.com/d/msgid/dixonary/B7580C58-1D96-4CFC-9B04-35004E9EED7E%40dixonary.net.