Re: [Users] membership disabled due to bouces again..
On 01/22/2014 11:37 PM, Gianluca Cecchi wrote:
Already spotted this problem before... I just found that I lose e-mails from Tue Jan 21 11:45:10 EST 2014 to Wed Jan 22 15:35:51 EST 2014
And received only some minutes ago (22/Jan/2014 21:26 Italy Time) an e-mail regarding my disabled membership apparently occurred at Mon, Jan 20, 2014 at 4:11 PM so that I didn't either know before ....
Any way to solve this? I have to mix e-mail received and archives...
Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
moving to infra. yes, it takes a few emails that gmail rejects (rather than move-to-spam-folder) for the mail server to disable. infra - any progress/thoughts on this? Gianluca - the sure alternative is any other provider than gmail temporarily (not a good answer, i know)
On Sun, Jan 26, 2014 at 09:40:40PM +0200, Itamar Heim wrote:
On 01/22/2014 11:37 PM, Gianluca Cecchi wrote:
Already spotted this problem before... I just found that I lose e-mails from Tue Jan 21 11:45:10 EST 2014 to Wed Jan 22 15:35:51 EST 2014
And received only some minutes ago (22/Jan/2014 21:26 Italy Time) an e-mail regarding my disabled membership apparently occurred at Mon, Jan 20, 2014 at 4:11 PM so that I didn't either know before ....
Any way to solve this? I have to mix e-mail received and archives...
moving to infra. yes, it takes a few emails that gmail rejects (rather than move-to-spam-folder) for the mail server to disable.
infra - any progress/thoughts on this? Gianluca - the sure alternative is any other provider than gmail temporarily (not a good answer, i know)
Karsten fixed forward and reverse DNS records for linode01, but I'm not sure what their policy is on a reverse pointing to a CNAME. $ host 2600:3c01::f03c:91ff:fe93:4b0d d.0.b.4.3.9.e.f.f.f.1.9.c.3.0.f.0.0.0.0.0.0.0.0.1.0.c.3.0.0.6.2.ip6.arpa domain name pointer lists.ovirt.org. $ host lists.ovirt.org lists.ovirt.org is an alias for linode01.ovirt.org. linode01.ovirt.org has address 173.255.252.138 linode01.ovirt.org has IPv6 address 2600:3c01::f03c:91ff:fe93:4b0d Their policy[1] on IPv6 doesn't mention it specifically: * The sending IP must have a PTR record (i.e., a reverse DNS of the sending IP) and it should match the IP obtained via the forward DNS resolution of the hostname specified in the PTR record. Otherwise, mail will be marked as spam or possibly rejected. * The sending domain should pass either SPF check or DKIM check. Otherwise, mail might be marked as spam. [1]: https://support.google.com/mail/?p=ipv6_authentication_error
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/26/2014 01:08 PM, Ewoud Kohl van Wijngaarden wrote:
Karsten fixed forward and reverse DNS records for linode01, but I'm not sure what their policy is on a reverse pointing to a CNAME.
Should I change the reverse back to linode01.ovirt.org instead of lists.ovirt.org? - -- Karsten 'quaid' Wade .^\ CentOS Engineering Manager http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLsKKUACgkQ2ZIOBq0ODEFtBQCgzktQ0CcB4vhQhoEDDwlpUlyc 0x4Anj6gqW0D22xFHjvEmoptLmoMptxG =HopB -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I don't think that was the root issue. I suspect that Google is going to take some time to recognise that we've changed something - if only we knew exactly why Google was bouncing the emails, that would help. Gah. Cheers, Dave. On 01/31/2014 11:50 PM, Karsten Wade wrote:
On 01/26/2014 01:08 PM, Ewoud Kohl van Wijngaarden wrote:
Karsten fixed forward and reverse DNS records for linode01, but I'm not sure what their policy is on a reverse pointing to a CNAME.
Should I change the reverse back to linode01.ovirt.org instead of lists.ovirt.org?
-- Karsten 'quaid' Wade .^\ CentOS Engineering Manager http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
- -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS+z1pAAoJECd1qeknDCggPVIIAKEVsiXpPUotTFyPbxSK6P7T eJqbbvynnTyxwdVZLQJuHDffGGUe2Nx8s0XXZ5RCU2tlYh6aDXguo8HvEzvRq8WU bnhZ7Mu5KGJdr4XX1vntt4K9oCblXjIXx1QO9NwGcU8tRB6iuvMDKJ6bUrkqc2Lu 0lSBPLg5UXt3SBiRwY8wPG7+IX9f0jNR4bQjOf+E5fOEcdXtl2bfTI5d06cXI/OW OM4+SpRJaMDup3vu1dQWQCdu2bPtDrghcJCCX+R+fW/WqwhuEo9Loi82SL8fpN6v ZKNjL2xzFwt6UwMG8ltca0QSFKpI/+9DNw22/pTlB+kLy0rsgEOnTALnuUTRt04= =6FNA -----END PGP SIGNATURE-----
On 02/12/2014 11:22 AM, Dave Neary wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I don't think that was the root issue. I suspect that Google is going to take some time to recognise that we've changed something - if only we knew exactly why Google was bouncing the emails, that would help.
I haven't seen any more span detection by google recently for us. I think the problem was many email accounts from google.com not flagging as not-spam (which would be hard considering the increasing email traffic). the fact they all got disabled by mailman, and only those that need it re-enabled will hopefully keep it clean for a few months...
Hi, Let me re-enable gmail accounts once more (with the Mailman helper script reset_bounce as Rydekull described here: https://www.mail-archive.com/infra@ovirt.org/msg03075.html) Cheers, Dave. On 02/14/2014 05:10 PM, Itamar Heim wrote:
On 02/12/2014 11:22 AM, Dave Neary wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I don't think that was the root issue. I suspect that Google is going to take some time to recognise that we've changed something - if only we knew exactly why Google was bouncing the emails, that would help.
I haven't seen any more span detection by google recently for us. I think the problem was many email accounts from google.com not flagging as not-spam (which would be hard considering the increasing email traffic). the fact they all got disabled by mailman, and only those that need it re-enabled will hopefully keep it clean for a few months...
-- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
On 02/14/2014 07:57 PM, Dave Neary wrote:
Hi,
Let me re-enable gmail accounts once more (with the Mailman helper script reset_bounce as Rydekull described here: https://www.mail-archive.com/infra@ovirt.org/msg03075.html)
I think having those really following the emails enabling them, and everyone not using them being disabled, will reduce the spam for those tracking it...
Cheers, Dave.
On 02/14/2014 05:10 PM, Itamar Heim wrote:
On 02/12/2014 11:22 AM, Dave Neary wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I don't think that was the root issue. I suspect that Google is going to take some time to recognise that we've changed something - if only we knew exactly why Google was bouncing the emails, that would help.
I haven't seen any more span detection by google recently for us. I think the problem was many email accounts from google.com not flagging as not-spam (which would be hard considering the increasing email traffic). the fact they all got disabled by mailman, and only those that need it re-enabled will hopefully keep it clean for a few months...
On Sun, 26 Jan 2014, Itamar Heim wrote:
moving to infra.
infra - any progress/thoughts on this?
The A record and PTR are now set -- as setting ipv6 PTR records are not supported to conform to RFC appraoches at linnode, we are blocked there We _could_ disable ipv6 sending, but this 'feels wrong'. We could also use a 'smart relay' approach to a outbound forwarder whithch had a better ipv6 approach. This seems like solving the issue at the wrong place, though Perhaps we should add a SPF, but in the case of Gmail,. it does not seem to have an effect (based on testing, rather than reading their doco) A user of gmail, as I indicated in my post on the 'user' list, ** must ** set a whitelist entry up. That has to happen on the end user side, and is not under infra's control, any more than the user's choice of email services provider I do not see that there is anything remaining that infra can do -- Russ herrold
On Sun, Jan 26, 2014 at 04:42:56PM -0500, R P Herrold wrote:
On Sun, 26 Jan 2014, Itamar Heim wrote:
moving to infra.
infra - any progress/thoughts on this?
The A record and PTR are now set -- as setting ipv6 PTR records are not supported to conform to RFC appraoches at linnode, we are blocked there
Not sure what you mean by this.
Perhaps we should add a SPF, but in the case of Gmail,. it does not seem to have an effect (based on testing, rather than reading their doco)
We already have an SPF record for ovirt.org.
participants (5)
-
Dave Neary -
Ewoud Kohl van Wijngaarden -
Itamar Heim -
Karsten Wade -
R P Herrold