[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Mail incorrectly getting flagged down as spam
From: |
Chris Punches |
Subject: |
Re: Mail incorrectly getting flagged down as spam |
Date: |
Wed, 14 Apr 2021 20:42:34 -0400 |
User-agent: |
Evolution 3.36.5 (3.36.5-2.fc32) |
Hey Bob,
This is a test message. I'll also try again with a test reply on the
gcc mailing list to see if it goes through. I outsource my postfix
service because im a big dumby with that specific service, so, if it is
an issue with my email service I definitely want to know.
--hey this is interesting, I am now able to post. Hrm. It must have
been transient.
Thanks for your expertise and input on this, I'll start with my mail
service first next time.
-C
On Wed, 2021-04-14 at 18:33 -0600, Bob Proulx wrote:
> Hello Chris,
>
> Chris Punches wrote:
> > My name is Chris Punches and I was referred to you by Greg Farough
> > while I've been trying to chase down this issue.
>
> Sure! But I (and we here) take care of the other mailing lists and
> not the GCC lists. Therefore I have CC'd the team GNU mailing list
> team on my reply. I am thinking we will need help from Ian.
>
> You see the GCC team is somewhat separate from most of the rest of
> the
> GNU Project. GCC is a big project and they have a lot of their own
> infrastructure. It might be a problem there on that side of things.
>
> > For some reason as of this morning, my posts to gnu.org mailing
> > lists,
> > particualrly gcc, goes to "spam@localhost" after being rejected,
> > and I
> > get back messages indicating that it's getting routed by some kind
> > of
> > spam filter. I was able to post fine until this morning.
> >
> > Can you please provide some insight into why this is suddenly
> > happening
> > and how I can fix it?
>
> The spam@localhost sounds like something that is happening on your
> client end and won't be anything we have any control over. That
> would
> be a problem on your end.
>
> If you are getting a rejection from gnu.org then that part might need
> help from one of the FSF sysadmins (CC'd) to look at the logs and
> determine what is happening. Let's get them all of the information
> they will need to take a look at things. I'll copy and comment.
>
> > Reporting-MTA: dns; sourceware.org
> > X-Postfix-Queue-ID: 62B1A3858012
> > X-Postfix-Sender: rfc822; chris.punches@silogroup.org
> > Arrival-Date: Wed, 14 Apr 2021 14:26:56 +0000 (GMT)
> >
> > Final-Recipient: rfc822; spam@localhost
> > Action: failed
> > Status: 5.2.2
> > Diagnostic-Code: x-unix; input/output error
>
> I think 62B1A3858012 is the queue id from your system. Which makes
> it
> less than useful. It's how your system is filing bounce rejections.
>
> I looked in the archive and it appears your most recent message to
> the
> mailing list was this one.
>
> Date: Mon, 12 Apr 2021 19:09:24 -0400
> Message-ID: <
> 2601b4644a3a0965552d07f2e82ef20fe05582d1.camel@silogroup.org>
> From: Chris Punches <chris.punches@silogroup.org>
>
> Everything looks to be the same as on this message. And you emailed
> me using my rwp@gnu.org address which also nicely tests that you can
> email through to the same incoming mail exchange that
>
> Date: Wed, 14 Apr 2021 19:20:00 -0400
> Message-ID: <
> e4e49324f2f78bd5c3c060b357992e2428d9bf26.camel@silogroup.org>
> From: Chris Punches <chris.punches@silogroup.org>
>
> I am listing those hoping it is easier for FSF sysadmin to grep
> through the logs and figure out why you were recently rejected.
> I assume "Wed, 14 Apr 2021 14:26:56 +0000" is near the time it was
> sent so hopefully sysadmin will find a rejection near then in the
> logs
> and that will be the information needed.
>
> For a test would you please reply to this message? I have set the
> Reply-To header so that it should go to the mailman@gnu.org address.
> I am sure that will work but if so then I do not have any idea why
> your most recent message was rejected.
>
> Was there something unusual about your most recent message? Was it
> very large, perhaps too large? Was the content of it including
> something that might have triggered a content filter?
>
> Bob