From: Chris Brannon <chris@the-brannons.com>
To: Kevin Carhart <kevin@carhart.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] jdb redirect (fwd)
Date: Tue, 19 Sep 2017 20:31:26 -0700 [thread overview]
Message-ID: <87mv5qrqpd.fsf@prgmr.com> (raw)
In-Reply-To: <alpine.LRH.2.03.1709181709230.13618@carhart.net> (Kevin Carhart's message of "Mon, 18 Sep 2017 17:16:59 -0700 (PDT)")
Kevin Carhart <kevin@carhart.net> writes:
> Uh oh, maybe the problem was the attachment? I sent this yesterday.
> In fact, I sent several in a row. Are attachments prohibited on the
> list? I should have thought of that. I don't think it's hitting a
> size threshhold, because it's 100k zipped.
>
> Karl, in lieu of an attachment, could you download it from:
> http://carhart.net/~kevin/third.js.2017091702.zip
I wouldn't be surprised if the list was dropping attachments.
I have some pretty restrictive settings on the mailing list. I am a bit
surprised that the dropped messages didn't land in my inbox. I usually
get "dropped message" notifications for this list, 99.9% of which are
attempted spam.
-- Chris
next prev parent reply other threads:[~2017-09-20 3:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 0:16 Kevin Carhart
2017-09-20 3:31 ` Chris Brannon [this message]
2017-09-21 0:02 ` Kevin Carhart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv5qrqpd.fsf@prgmr.com \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=kevin@carhart.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).