From: hansolofalcon@worldnet.att.net (Gregg C Levine)
Subject: [TUHS] Question for the List Manager/Owner
Date: Mon, 24 Jan 2005 01:28:43 -0500 [thread overview]
Message-ID: <000001c501dd$f7927d20$6401a8c0@who5> (raw)
In-Reply-To: <20050124061632.GA48398@minnie.tuhs.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2545 bytes --]
Hello from Gregg C Levine
Warren that makes sense. Can you send me, off list of course, the
dates when the delivery failed for just this address?
Here's the really strange part: I know reasonably close to certain,
that practically nothing went wrong with my ISP's mail services during
the time period covering this month, the previous three weeks. I
believe nothing went wrong at all during the entire month of December.
Oh, and I'm not doubting your talents, or your system's efforts, its
for my ISP so they can properly convince their network management
people, e-mail, and other stuff regarding things going wrong, or not.
Incidentally two of the lists that I subscribe to, are configured to
send out messages that invite people to confirm a numerical string
that activates their subscription, which was disabled do to bounces.
(However, typically nothing of a sort has happened. The Owner is
having problems managing those two lists, and has no idea of what else
to do.)
-------------------
Gregg C Levine hansolofalcon at worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke." Obi-Wan Kenobi
> -----Original Message-----
> From: Warren Toomey [mailto:wkt at tuhs.org]
> Sent: Monday, January 24, 2005 1:17 AM
> To: Gregg C Levine
> Cc: The Unix Heritage Society
> Subject: Re: [TUHS] Question for the List Manager/Owner
>
> On Sun, Jan 23, 2005 at 11:21:21PM -0500, Gregg C Levine wrote:
> > Hello from Gregg C Levine
> > Question: Will the list server drop subscribers, if they have not
> > posted anything to the list? Or are other reasons taken into
> > circumstances?
> >
> > Consider this, for any number of reasons, two of my e-mail
addresses
> > for this ISP are subscribed to this list, some time ago a posting
> > arrived at Address #2, but Address #1 didn't receive it.
>
> Mailman drops people from a list if repeated attempts to deliver
e-mail
> to that address fail. There is no other reason that an address would
> get dropped.
>
> > So when you have the time to look into the matter, can you
> > investigate. FYI, the address in doubt is this one.
> > -------------------
> > Gregg C Levine hansolofalcon at worldnet.att.net
> > ------------------------------------------------------------
>
> Both of these addresses are registered, none are marked as
unsubscribed
> or removed. The maillog records show delivery to both addresses:
> <<Registration references deleted for privacy reasons.>>
> Cheers,
> Warren
prev parent reply other threads:[~2005-01-24 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 4:21 Gregg C Levine
2005-01-24 6:16 ` Warren Toomey
2005-01-24 6:28 ` Gregg C Levine [this message]
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='000001c501dd$f7927d20$6401a8c0@who5' \
--to=hansolofalcon@worldnet.att.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).