Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #264989
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: lists |
| Date | 2023-12-20 17:10 +0100 |
| Message-ID | <HN7iV-eTC2-1@gated-at.bofh.it> (permalink) |
| References | <HN4l3-eRtO-1@gated-at.bofh.it> <HN4uK-eRML-5@gated-at.bofh.it> <HN4XM-eS0d-9@gated-at.bofh.it> <HN6wx-eT5d-7@gated-at.bofh.it> <HN79f-eTir-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On 12/20/23 10:50, Andy Smith wrote:
> Hello,
>
> On Wed, Dec 20, 2023 at 04:11:05PM +0100, Christoph Brinkhaus wrote:
>> I have heard that there is a countermeasure against spam run be big mail
>> providers by rejecting the first contact by SMTP and accepting the next
>> contact. Most spammers seem to try just once.
> I think you are talking about the practice of "greylisting". This
> involves giving a 4xx SMTP response to "new" correspondents, which
> is a temporary failure code that instructs the sending server to try
> again later. They usually will within just a few minutes, at which
> point it's not considered a "new" interaction and is allowed
> through.
>
> The purpose of this is to weed out compromised hosts sending email
> directly, rather than through a proper mail server. Such malware
> usually won't bother to implement a full mail server with queueing
> and retries, so will give up after even a temporary failure.
>
> There was a period of time when large spam runs using compromised
> hosts were prevalent, but in recent years spammers do tend to use
> rented hosts with proper mail servers on them, so greylisting has
> become less effective. Some people say it no longer has any
> noticeable benefit.
>
> Greylisting would not cause the symptoms that you and Pocket are
> experiencing; any sensible mailing list server including Debian's
> will cope with temporary failure.
>
> If we're not talking about greylisting, using a 5xx SMTP hard reject
> code on new interactions would not make a lot of sense as a form of
> antispam measure. There are some misguided people who use a sort of
> allowlist approach where every new correspondent gets an automated
> message telling them to visit a URL to prove they are human, before
> any mail is allowed through to the real recipient. These use
> non-delivery report emails ("bounces", NDRs) as opposed to SMTP
> rejects.
>
> If I were you I'd just email<listmaster@lists.debian.org> to ask
> them about it the next time you receive the notification about some
> emails being rejected. The human that will eventually answer your
> email will probably be happy to look in the logs to see what message
> your mail provider gave.
>
>> Please verify the content of the kick rate mail. I am quite sure that it
>> is not as serious as it sounds on the first impression.
> You are right that an occasional bounce probably isn't a lot to
> worry about, as the trigger level indeed is way above 2%. One way it
> can happen is if a spammy message reaches the list and is not
> detected by Debian, but is detected and rejected by your mail
> provider. That counts as "you" rejecting email from the list, even
> though that was the right thing for your provider to do. That sort
> of thing can just be ignored.
>
> In Pocket's case, they say they are actually being automatically
> unsubscribed from the list. That indicates a severe and ongoing
> problem with their mail delivery. If I were them I'd want to look
> into it.
>
> Thanks,
> Andy
I am looking into it,
The other debian mail lists I subscrie to are not and never have been an
issue.
I did find this which points to the debian mail list SMTP server
inal-Recipient: rfc822;pocket@columbus.rr.com
Original-Recipient:rfc822;pocket@columbus.rr.com
Action: failed
Status: 5.1.0
Remote-MTA: dns; pkvw-mx.msg.pkvw.co.charter.net
Diagnostic-Code: smtp; 550 5.1.0
<bounce-debian-user=pocket=columbus.rr.com@lists.debian.org> sender
rejected. Please see
https://www.spectrum.net/support/internet/understanding-email-error-codes
for more information. AUP#In-1310
Error code AUP#In-1310 is the following
Spectrum limits the number of concurrent connections from a sender, as
well as the total number of connections allowed. Limits vary based on
the reputation of the IP address. Reduce your number of connections and
try again later.
--
Hindi madali ang maging ako
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
lists Pocket <pocket@columbus.rr.com> - 2023-12-20 14:00 +0100
Re: lists Andy Smith <andy@strugglers.net> - 2023-12-20 14:10 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 14:40 +0100
Re: lists Andy Smith <andy@strugglers.net> - 2023-12-20 14:50 +0100
Re: lists <tomas@tuxteam.de> - 2023-12-20 14:50 +0100
Re: lists Marco Moock <mm@dorfdsl.de> - 2023-12-20 16:10 +0100
Re: lists Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-12-20 16:20 +0100
Re: lists Marco Moock <mm@dorfdsl.de> - 2023-12-20 16:20 +0100
Re: lists Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-12-20 16:30 +0100
Re: lists Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-20 16:50 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 16:30 +0100
Re: lists Jeffrey Walton <noloader@gmail.com> - 2023-12-20 16:40 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 16:50 +0100
Re: lists Andy Smith <andy@strugglers.net> - 2023-12-20 17:00 +0100
Re: lists Jeffrey Walton <noloader@gmail.com> - 2023-12-20 17:00 +0100
Re: lists "Thomas Schmitt" <scdbackup@gmx.net> - 2023-12-20 17:30 +0100
Re: lists Marco Moock <mm@dorfdsl.de> - 2023-12-20 17:40 +0100
Re: lists Andy Smith <andy@strugglers.net> - 2023-12-20 17:00 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 17:10 +0100
Re: lists Marco Moock <mm@dorfdsl.de> - 2023-12-20 17:20 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 17:20 +0100
Re: lists <tomas@tuxteam.de> - 2023-12-20 17:30 +0100
Re: lists Marco Moock <mm@dorfdsl.de> - 2023-12-20 17:40 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 17:40 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 17:50 +0100
Re: lists <tomas@tuxteam.de> - 2023-12-20 17:50 +0100
Re: lists Marco Moock <mm@dorfdsl.de> - 2023-12-20 17:50 +0100
Re: lists Andy Smith <andy@strugglers.net> - 2023-12-20 18:00 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 18:10 +0100
Re: lists Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-20 19:30 +0100
Re: lists Andy Smith <andy@strugglers.net> - 2023-12-20 17:50 +0100
Re: lists Andy Smith <andy@strugglers.net> - 2023-12-20 17:40 +0100
Re: lists <tomas@tuxteam.de> - 2023-12-20 17:50 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 18:10 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 17:50 +0100
Re: lists Nicolas George <george@nsup.org> - 2023-12-20 19:30 +0100
Re: lists Andy Smith <andy@strugglers.net> - 2023-12-20 17:40 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 17:40 +0100
Re: lists Joe <joe@jretrading.com> - 2023-12-20 17:00 +0100
Re: lists Marco Moock <mm@dorfdsl.de> - 2023-12-20 17:20 +0100
Re: lists <tomas@tuxteam.de> - 2023-12-20 17:30 +0100
Re: lists Joe <joe@jretrading.com> - 2023-12-20 17:50 +0100
Re: lists Marco Moock <mm@dorfdsl.de> - 2023-12-20 18:00 +0100
Re: lists Joe <joe@jretrading.com> - 2023-12-20 18:00 +0100
Re: lists gene heskett <gheskett@shentel.net> - 2023-12-20 18:00 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 18:10 +0100
Re: lists Greg Wooledge <greg@wooledge.org> - 2023-12-20 19:20 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 19:30 +0100
Re: lists Hanno 'Rince' Wagner <wagner@debian.org> - 2023-12-20 19:50 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 20:10 +0100
Re: lists Marco Moock <mm@dorfdsl.de> - 2023-12-20 20:20 +0100
Re: lists Jeffrey Walton <noloader@gmail.com> - 2023-12-20 21:00 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 21:10 +0100
Re: lists Marco Moock <mm@dorfdsl.de> - 2023-12-20 21:30 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-20 21:50 +0100
Re: lists gene heskett <gheskett@shentel.net> - 2023-12-21 00:00 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-21 00:20 +0100
Re: lists John Hasler <john@sugarbit.com> - 2023-12-21 00:50 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-21 01:00 +0100
Could we please cease this thread now? [WAS Re: lists] "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-21 11:40 +0100
Re: Could we please cease this thread now? [WAS Re: lists] Pocket <pocket@columbus.rr.com> - 2023-12-21 11:50 +0100
Re: Could we please cease this thread now? [WAS Re: lists] Andy Smith <andy@strugglers.net> - 2023-12-21 12:40 +0100
Re: Could we please cease this thread now? [WAS Re: lists] Pocket <pocket@columbus.rr.com> - 2023-12-21 13:40 +0100
Re: Could we please cease this thread now? [WAS Re: lists] Byung-Hee HWANG <soyeomul@doraji.xyz> - 2023-12-21 14:20 +0100
Re: Could we please cease this thread now? [WAS Re: lists] Andy Smith <andy@strugglers.net> - 2023-12-21 14:50 +0100
Re: Could we please cease this thread now? [WAS Re: lists] Pocket <pocket@columbus.rr.com> - 2023-12-21 15:00 +0100
Re: Could we please cease this thread now? [WAS Re: lists] Andy Smith <andy@strugglers.net> - 2023-12-21 15:10 +0100
Re: Could we please cease this thread now? [WAS Re: lists] Hanno 'Rince' Wagner <wagner@debian.org> - 2023-12-21 15:20 +0100
Re: Could we please cease this thread now? [WAS Re: lists] Pocket <pocket@columbus.rr.com> - 2023-12-21 15:30 +0100
Re: lists gene heskett <gheskett@shentel.net> - 2023-12-20 23:40 +0100
Re: lists Pocket <pocket@columbus.rr.com> - 2023-12-21 00:00 +0100
Re: lists Richard Hector <richard@walnut.gen.nz> - 2023-12-21 00:10 +0100
Re: wireless broadband providers exist (was: lists) Felix Miata <mrmazda@earthlink.net> - 2023-12-21 01:50 +0100
Re: wireless broadband providers exist The Wanderer <wanderer@fastmail.fm> - 2023-12-21 01:50 +0100
Re: wireless broadband providers exist Pocket <pocket@columbus.rr.com> - 2023-12-21 02:10 +0100
Re: wireless broadband providers exist Jeffrey Walton <noloader@gmail.com> - 2023-12-21 02:50 +0100
Re: wireless broadband providers exist Pocket <pocket@columbus.rr.com> - 2023-12-21 03:30 +0100
Re: wireless broadband providers exist John Hasler <john@sugarbit.com> - 2023-12-21 05:30 +0100
Re: wireless broadband providers exist John Hasler <john@sugarbit.com> - 2023-12-21 05:20 +0100
Re: wireless broadband providers exist Pocket <pocket@columbus.rr.com> - 2023-12-21 02:00 +0100
Re: wireless broadband providers exist Felix Miata <mrmazda@earthlink.net> - 2023-12-21 02:30 +0100
Re: wireless broadband providers exist Pocket <pocket@columbus.rr.com> - 2023-12-21 02:40 +0100
csiph-web