Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [milter-greylist] technical quality of yahoo mailinglists, feedback on moving to another service

2016-12-14 by Greg Troxel

"Marcus Schopen lists-yahoogroups@... [milter-greylist]"
<milter-greylist@yahoogroups.com> writes:

> Hi,
>
> in a lot of cases I get temp fails from yahoo's servers and mails sent 
> to this list are delayed for hours, because their servers are too busy:
>
> ------
> Dec 12 20:27:19 lillith sm-mta[3090]: uBCHB0HJ020512: 
> to=<milter-greylist@yahoogroups.com>, delay=02:16:17, xdelay=00:00:01, 
> mailer=esmtp, pri=2191280, relay=fo-mx-groups.mail.am0.yahoodns.net. 
> [66.218.74.235], dsn=4.0.0, stat=Deferred: 451 Resources temporarily not 
> available - Please try again later [#4.16.5].
> ------
>
> see: https://sg.help.yahoo.com/kb/xx-smtp-error-codes-sln26151.html
>
> Another grotesque point for a discussion list about greylisting is, that 
> yahoo's common pool servers have to be whitelisted, because they don't 
> retry. Is that a place to be?
>
> A plan could be to move to another service. Subscribed users would be 
> migrated (btw: who is the list owner?). Emmanuel Dreyfus asked me to 
> post this plan to the list and call for opposition.

Moving would be a good thing.

> Any suggestions for another service, e.g. google mailing lists?

But, I think Free Software projects should be hosted by charitable
organizations with free software as a goal.   Google lists in particular
are not friendly to those who decline to accept google's terms and have
a google login.  (While they can be made to work, the group pages do not
give instructions for signing up without an account.)

So, I would be inclined to have the project on a FSFE server, or on
savannah.nongnu.org, or someplace like that.

However, I'm not volunteering, so take this with a grain of salt.

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.