On May 25, 8:14 am, Joe Smith <
meticulous2...@gmail.com> wrote:
> I am the owner and manager of a Google Group and we use this predominantly
> to exchange emails within members of the group and also to archive
> messages, repository of group documents etc.
>
A late response here but maybe helpful.
Some mail systems will read the e-mail headers, the unseen data that
accompanies e-mail to show where it came from and other details. If
the receiving mail server is recognizing the message as coming from a
source that may have a block, the recipient may need to white list the
group address as well as your e-mail address as message originator.
Some mail systems will suppress messages sent to a list that a person
originates under a presumption that the sender has a copy in their
SENT mail box, and does not need to see their posting repeated again.
I was seeing this phenomena on a list not that long ago where my own
posts never came back to me after I sent them, but replies from others
would come fine.
While this is similar to your issue, it is not the same since you are
sending initial messages and the recipient is not seeing the primary,
but only the responses.
The suggestion here is that the recipient's mail server is blocking
that message for some reason, and needs to be white listed.
Occasionally a mail server may block a source of messages due to
spam. This is not a reflection on your list but is essentially
collateral damage if a spammer is sending mail through the same mail
server or access node (cable, DSL, dial-up, etc). Sometimes an ISP
will accept a block list from SORBS or similar services and wholesale
IP addresses and never update that list. In such a case manual
intervention is called for. I had my private domain blocked from a
cable service one time because the cable company blocked the IP
address of the access node and not the mail server that was
offending. The result was I could not get mail through to a single
person and had to open a Gmail address just for that. It seems the
Gmail headers suppressed the access node IP so it was able to get by
the block.
In any event, if all people on the list is getting the messages,
primary and responses, OK, the finger of blame has to rest with the
one person who is having the problem.
One thing to look at... check the sending and receiving addresses of
yourself and the person not getting the messages. If one of the mail
servers is using a subdomain (
xxx.yyy.com instead of
yyy.com) there
may be a mismatch or misspelling. I saw that problem some years back
and had to set up a sending and receiving account for the one person
with the different addresses. This should not be the case these days
but I did see that problem about 5 years back.
DMK