From: Jack <ostroffjh@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: ezmlm warning
Date: Wed, 02 Nov 2016 14:55:00 -0000 [thread overview]
Message-ID: <UFWg3K2Z/7xRL5KY26WGVt@Kqn1+95jL5B58RNfeMKsY> (raw)
In-Reply-To: <0b7200a7-fc6c-efb5-c4e6-cab33ae93047@redhat.com> (from eblake@redhat.com on Wed Nov 2 09:04:49 2016)
On 2016.11.02 09:04, Eric Blake wrote:
> On 11/02/2016 05:43 AM, Andrey ``Bass'' Shcheglov wrote:
>> Remote host said: 550-5.7.1 Unauthenticated email from vanav.org is
>> not accepted due to domain's > 550-5.7.1 DMARC policy. Please
>> contact the administrator of vanav.org domain if > 550-5.7.1 this
>> was a legitimate mail. Please visit > 550-5.7.1
>
> yahoo.com has already been doing this for a while, now gmail.com is
> doing it too :(
>
> In addition to the link you quoted:
>
> > https://support.google.com/mail/answer/2451690
>
> here's another one:
> https://wiki.list.org/DOC/What%20can%20I%20do%20about%20members%20being%20unsubscribed%20by%20bounces%20of%20Yahoo%20user's%20posts%20for%20DMARC%20policy%20reasons%3F
>
> The problem is that the mailman instance running the cygwin mailing
> list (and ALL lists hosted by sourceware, for that matter) needs to
> be reconfigured to cope with stricter DMARC rules. I'm not an admin,
> so you will need to redirect this request to the postmaster that
> manages cygwin's mailman instance.
>
> In the meantime, the only "workaround" is to subscribe to the list
> using an address that isn't quite as nasty about DMARC rules. It's
> sad that more and more sites are clamping down, but that's the price
> we pay for spammers.
I recently ran into the same problem sending to a KDE list. In my
case, I was using a sourceforge.net FROM: address, but actually sending
through my ISP (frontier.com). Sourceforge had the DMARC policy that
mail claiming to be from sourceforge.net should not be accepted if it
came from anywhere else. I think the final solution was for them to
drop that rule, since at least one of the uses of sourceforge is
exactly that type of aliasing. I don't think gmail will do the same.
You are using a gmail.com address, but it looks like you might have
sent it from vanav.org. In this case, I suspect your only solution
will be to actually send mail from gmail.com using the gmail.com smtp
server.
Eric's suggestion to resubscribe from an address at a site which is
less strict about DMARC rules would work, but I think the underlying
issue will arise again, as long as you use an smtp server other than
the one from the From: address you are using.
Jack
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-11-02 14:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 10:43 Andrey ``Bass'' Shcheglov
2016-11-02 13:05 ` cyg Simple
2016-11-02 13:05 ` Eric Blake
2016-11-02 13:13 ` cyg Simple
2016-11-02 14:52 ` Herbert Stocker
2016-11-02 14:55 ` Jack [this message]
[not found] <1557166949.6367.ezmlm-warn@cygwin.com>
2019-05-06 19:04 ` Chris Wagner
2019-05-06 19:26 ` Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2017-08-14 9:22 cygwin-help
2015-10-05 9:09 cygwin-help
2010-02-07 14:38 cygwin-help
2009-09-14 10:29 cygwin-help
2005-06-15 16:28 cygwin-help
2004-09-30 11:01 cygwin-help
2004-06-08 16:19 cygwin-help
2001-12-20 23:02 cygwin-help
[not found] <955193687.11707.ezmlm-warn@sourceware.cygnus.com>
2000-04-10 1:08 ` Don Sharp
2000-04-10 10:15 ` Chris Faylor
[not found] ` <006301bfa32a$cbeeec10$5f0f4dd1@TIMYX18EWDT6RQ>
2000-04-10 13:36 ` Chris Faylor
2000-04-10 13:44 ` Jeff Sturm
2001-04-16 6:30 ` Chris Faylor
2001-09-04 23:46 ` Chris Faylor
2001-09-05 4:06 ` Don Sharp
[not found] ` <38F1E5D0.262ED39B@sigma6.com>
2000-04-11 1:07 ` Don Sharp
[not found] ` <200004101712.NAA09157@rtl.cygnus.com>
2000-04-11 1:17 ` Don Sharp
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=UFWg3K2Z/7xRL5KY26WGVt@Kqn1+95jL5B58RNfeMKsY \
--to=ostroffjh@users.sourceforge.net \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).