2:18 a.m.
--=-8IypELm1jDXZvlCEJt6n
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Le vendredi 16 janvier 2015 =C3=A0 08:23 +0100, Sandro Bonazzola a =C3=A9cr=
it :
Il 15/01/2015 18:31, Michael Scherer ha scritto:
> Hi,
>=20
> Itamar, by the proxy of Brian, did asked me to look on the bounce issue
> we have on the users lists. So after a few hours of careful log reading=
,
> here is my finding.
>=20
> The bounce situation
> ---------------------
>=20
> We (ml admin) get on a regular basis people who get unsubscribed and
> message about bounce. People being unsubscribed automatically is
> bad(tm), and bounces are annoying.=20
>=20
>=20
> Investigation
> -------------
>=20
> A first look show that our mails are bounced as they are marked as spam
> by Google. Google doc on the matter do not give much, some people point
> to using dkim, spf, etc. But spf is not for us, but for the sender, and
> dkim is not ml friendly, afaik, and requires upstream support if I
> understood well.
>=20
> Not all mails are bounced, which is good. That mean the ip is not
> problematic.=20
>=20
> So I took a few hours to look on every bounce and roughly, there is 2
> groups.
>=20
> Group 1
> --------
>=20
> First group is that all mail from the same poster on the users list hav=
e
> bounced at Google. Out of the 16 mail he sent, 16 have been
rejected by
> Google. I have no idea why, I suspect the spf policy, but it did looked
> ok. None of the mail of answer had a issue, so that's likely not a
> content problem. =20
>=20
> However, the ip address of the sender is in the SORBS blacklist, so
> that's likely what trigger Google spam filter.
>=20
> Not much we can do, besides contacting him, which I will do.
>=20
> Group 2
> --------
> Roughly, that's mail in this thread :
> http://lists.ovirt.org/pipermail/users/2015-January/030494.html
>=20
> and the mails from Sandro :
> http://lists.ovirt.org/pipermail/users/2015-January/030420.html
> http://lists.ovirt.org/pipermail/users/2015-January/030423.html
>=20
> Common point, use of goo.gl and ur1.ca. It turn out that both domain ar=
e
> flagged as URI spam, since that's used by spammer to hide
their link. S=
o
> I suspect that Gmail started to "learn" about them as
spam, as the rest
> of the world did :
> http://multirbl.valli.org/lookup/ur1.ca.html
> http://multirbl.valli.org/lookup/goo.gl.html
>=20
> Again, not much we can do, besides asking to people to not use these
> services ( which is not gonna work I think ).
=20
I may try to use bit.ly red.ht instead of goo.gl.
Can we provide our own url shortener on ovirt.org? That should avoid blac=
klisting.
I do not think bit.ly is gonna change much. It is likely abused for the
same reason by the same people. And the url are too complicated to be
sent sometime, so we cannot just avoid them at all.
I also pondered about adding a url shortener on ovirt.org. Besides the
load on admin team it create, I think it would have the same issue as
the others after some time, and so we would need to add some
authentication, which start to make thing a bit complicated.=20
--=20
Michael Scherer
Open Source and Standards, Sysadmin
--=-8IypELm1jDXZvlCEJt6n
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAABAgAGBQJUuMlRAAoJEE89Wa+PrSK9HMoQAJfAN37HJRErlaxD8F9yHiot
F9XxSNxhVE9cDFLNN9XBoD6XIAnenLeHDzwwo1DzqWkLnW8f7kgcmyv/YCeqaJVK
Xf5uESJGi8bYsiviaS7RJy1FyIZhoCc0UmvAl0v6iZyiqMfqkT6mJMQDK7Awt9cM
jr3lu/l6ivjlfFD+ujhtFQzuqRVA0nNAlskMbdPhO98kLGTK5a1bI+RODTmtxRsW
XazD0bA9/O/7geEL1nMOIQDWmA6Kgx6bJrvwFZqeCg3d/FCUz5uJM5XeksGP/1Aw
f7pLgFniAKOLSM2wvvdjIG8rI03AsOfQ8zFx0RUa4RBceCbZnhL45ZSZZez6yJ+7
bxk3ADSvbNfrKh4s5Ty8xYEnVjB6fCNeB/UIhbE3KAqb9CARiB9VW4i81X41fG8b
jQA3PbrolT2UftPCMETeMfQEVOLogIrFypxMF0uvGN6U4wiWML3WqLXr8sBoBQb5
ArHvJQqHsvLGRdskI9S/mzy5v1II2Zm1sbzqeRT/1nvVXY35+GpmdldLok8VwJQI
9PEyVAVXN7tR27U3nhvTXeoJwy0KvrkGaeRFFPQw/WorNYgWV1ghSu6Bu0rFTAwY
tnVonP6SSz07myTb2z4evyoZYQ02wYVQAqjO2MvWYAwNKcaJYdtnBbVpGQE3kAXe
9pTVAihjdbyTC0yX7WM8
=5Wri
-----END PGP SIGNATURE-----
--=-8IypELm1jDXZvlCEJt6n--