On 2015-03-03 06:14 AM, Mike Owens wrote:
> Okay, I blocked the sqlite-users at sqlite.org address in the to address
> so if it is sent alone, it will be blocked.
This is working perfectly, thanks!
On Mon, 2015-03-02 at 21:10 -0600, Mike Owens wrote:
> The problem is that this is the very bone of contention in the reply-to
> religious war.
Religious as in there are strongly-held beliefs on both sides, but only
one is really based in logic and common sense? :)
> Is it not? I may be wrong,
On 2015-03-03 01:15 AM, Mike Owens wrote:
> For clarity, here is the currently policy for Reply-to as it is set in
> Mailman:
>
>
> - Should any existing Reply-To: header found in the original message be
> stripped? If so, this will be done regardless of whether an explict
>
On 2015-03-03 12:42 AM, Darren Duncan wrote:
> I think that what needs to be done is for each foo at sqlite.org to
> return an error/undeliverable message if someone sends a message to
> it, citing that all messages must be explicitly sent to the
> corresponding foo at
Okay, I blocked the sqlite-users at sqlite.org address in the to address
so if it is sent alone, it will be blocked.
On Mon, Mar 2, 2015 at 9:46 PM, Mike Owens wrote:
> Oh okay. I see. I'll look into it.
>
> On Mon, Mar 2, 2015 at 9:23 PM, Darren Duncan
> wrote:
>>
>> So in that case, still
Oh okay. I see. I'll look into it.
On Mon, Mar 2, 2015 at 9:23 PM, Darren Duncan
wrote:
> So in that case, still have the SQLite mail server reject messages to the
> old list rather than forwarding them, and let the problematic MUAs deal
> with it. The key thing is that by not forwarding but
The problem is that this is the very bone of contention in the reply-to
religious war. Is it not? I may be wrong, but I thought this is the very
setting that people get so defensive about changing. As we have it now,
people have a suitable default pointing back to the (correct) list but also
the
So far so good. I only got one copy of your test message. I also sent my own
message to just sqlite-users at sqlite.org and it was bounced as expected. --
Darren Duncan
On 2015-03-02 8:14 PM, Mike Owens wrote:
> Okay, I blocked the sqlite-users at sqlite.org address in the to address
> so if
On Mon, Mar 2, 2015 at 5:27 PM, R.Smith wrote:
>
> Ah, thank you, all makes sense now. If you change the first option to YES
> then nobody else's quirky reply-to headers will get into the list, and the
> second option remains as is (it should be setting the standard
> @mailinglists reply-to
On Mon, Mar 2, 2015 at 5:24 PM, Darren Duncan
wrote:
> As near as I can tell, the Reply-To header from this list only contains
> sqlite-users at mailinglists.sqlite.org and does not also contain
> sqlite-users at sqlite.org so therefore I don't see the problem you're
> stating. But if it
So in that case, still have the SQLite mail server reject messages to the old
list rather than forwarding them, and let the problematic MUAs deal with it.
The key thing is that by not forwarding but rejecting, the mail server isn't
sending out 2 copies of messages directly, and the rejecting is
On 2015-03-02 6:14 PM, Mike Owens wrote:
> On Mon, Mar 2, 2015 at 5:27 PM, R.Smith wrote:
>> Ah, thank you, all makes sense now. If you change the first option to YES
>> then nobody else's quirky reply-to headers will get into the list, and the
>> second option remains as is (it should be setting
On 2015-03-02 6:08 PM, Mike Owens wrote:
> On Mon, Mar 2, 2015 at 5:24 PM, Darren Duncan
> wrote:
>> As near as I can tell, the Reply-To header from this list only contains
>> sqlite-users at mailinglists.sqlite.org and does not also contain
>> sqlite-users at sqlite.org so therefore I don't see
For clarity, here is the currently policy for Reply-to as it is set in
Mailman:
- Should any existing Reply-To: header found in the original message be
stripped? If so, this will be done regardless of whether an explict
Reply-To: header is added by Mailman or not. : *NO*
- Where are
On 2015-03-02 3:04 PM, R.Smith wrote:
> On 2015-03-03 12:42 AM, Darren Duncan wrote:
>> I think that what needs to be done is for each foo at sqlite.org to return an
>> error/undeliverable message if someone sends a message to it, citing that all
>> messages must be explicitly sent to the
I think that what needs to be done is for each foo at sqlite.org to return an
error/undeliverable message if someone sends a message to it, citing that all
messages must be explicitly sent to the corresponding
foo at mailinglists.sqlite.org. That should handily solve the problem. --
Darren
Ok, I've found the source of the list duplications.
Some emails (Such as the one by J.K. Lowden 2-March-2015 re: Characters
corrupt after importing...) contains a "Reply-To" field in the header
with both list addresses which must have sneaked in there due to some
automatic list feature. (By
For what it is worth, the move to mailinglists.sqlite.org is a result of
the Mailman web interface having to be hosted under the following two
constraints:
1. It must be on port 80
2. It cannot be on sqlite.org port 80
I explained this reasoning in a previous email. The short version is
because
On Mon, 2015-03-02 at 12:45 +0200, R.Smith wrote:
> Ok, I've found the source of the list duplications.
>
> Some emails (Such as the one by J.K. Lowden 2-March-2015 re: Characters
> corrupt after importing...) contains a "Reply-To" field in the header
> with both list addresses which must have
On Sat, 2015-02-28 at 14:10 -0800, Darren Duncan wrote:
>
> My comment on "whoever" is meant to be plural.
>
> I think as a general principle that whenever people reply to list messages,
> they
> look at the headers of the message they are writing and make sure the list
> doesn't appear twice
On 27 Feb 2015 at 22:47, Simon Slavin wrote:
> On 27 Feb 2015, at 10:04pm, R.Smith wrote:
>
>> Ah, I think this is the answer probably. Maybe people hitting the "reply to
>> all" or such and it copies across lists. Simon is possibly not subscribed to
>> both, hence not getting duplicates.
>
>
On 2015-02-28 3:15 AM, R.Smith wrote:
> On 2015-02-28 05:02 AM, Darren Duncan wrote:
>> I'm seeing a lot of message duplication too, but the ones I see are due to
>> someone putting the list address twice as a recipient.
>>
>> For example a bunch of the "PhD student" messages say "To"
>>
On 2015-02-28 05:02 AM, Darren Duncan wrote:
> I'm seeing a lot of message duplication too, but the ones I see are
> due to someone putting the list address twice as a recipient.
>
> For example a bunch of the "PhD student" messages say "To"
> sqlite-users at mailinglists.sqlite.org plus "Cc"
On 2015-02-28 12:47 AM, Simon Slavin wrote:
> On 27 Feb 2015, at 10:04pm, R.Smith wrote:
>
>> Ah, I think this is the answer probably. Maybe people hitting the "reply to
>> all" or such and it copies across lists. Simon is possibly not subscribed
>> to both, hence not getting duplicates.
> I
On 2015-02-27 10:09 PM, Peter Aronson wrote:
> I've seen it too. All of the duplicate messages appear to have been sent to
> both sqlite-dev at mailinglists.sqlite.org and sqlite-dev at sqlite.org or to
> both sqlite-usersmailinglists.sqlite.org and sqlite-users at sqlite.org.
Ah, I think
On 27 Feb 2015, at 10:04pm, R.Smith wrote:
> Ah, I think this is the answer probably. Maybe people hitting the "reply to
> all" or such and it copies across lists. Simon is possibly not subscribed to
> both, hence not getting duplicates.
I confirm that I am not subscribed to the -dev list.
Me too, for about the last 7-10 days or so!
-Original Message-
From: R.Smith
Sent: Friday, February 27, 2015 9:38 PM
To: sqlite-users at mailinglists.sqlite.org
Subject: [sqlite] List duplication
Hi all,
Just a quick question, I've been getting duplicated mails via the forum
Hi all,
Just a quick question, I've been getting duplicated mails via the forum.
It seems very random, roughly 1 in 4 mails I receive in duplicate. Has
anyone else been getting duplicate mails?
It's not a biggie, I just delete the duplicates. Also, it might be my
email settings or setup being
On 27 Feb 2015, at 7:38pm, R.Smith wrote:
> Just a quick question, I've been getting duplicated mails via the forum. It
> seems very random, roughly 1 in 4 mails I receive in duplicate. Has anyone
> else been getting duplicate mails?
Not me.
Check back on the message-id and received headers
pear to have been sent to
> both sqlite-dev at mailinglists.sqlite.org and sqlite-dev at sqlite.org or to
> both sqlite-usersmailinglists.sqlite.org and sqlite-users at sqlite.org.
>
> Peter
>
>
> On Fri, 2/27/15, R.Smith wrote:
&
I've not been having problems with duplicates, but I have been randomly
having commoners end up in my spam bucket for one reason or another over
the last 48 hours or so. I've specifically set a filter in GMail that if
anything comes in for this mailing list to NOT go to spam, yet
On Fri, Feb
, R.Smith wrote:
Subject: [sqlite] List duplication
To: sqlite-users at mailinglists.sqlite.org
Date: Friday, February 27, 2015, 12:38 PM
Hi all,
Just a quick question, I've been getting duplicated mails
via the forum.
It seems very random, roughly 1 in 4 mails I receive in
duplicate
32 matches
Mail list logo