August 2026 - Wine-Devel - list.winehq.org

Re: spam protection on the mailing list

by Elizabeth Figura

On Monday, 31 August 2026 06:03:41 CDT Gerald Pfeifer via Wine-Devel wrote: > On Mon, 31 Aug 2026, Jeremy Newman via Wine-Devel wrote: > > I've contacted the list provider to see if anything else can be done to > > prevent this > > One idea might be rate limiting, i.e., at most X mails per sender address > per day (if the software allows for that)? We don't use the list for Wine patch submissions anymore, but it may still end up in the CC for patch submissions to other things, e.g. the Linux kernel. Large series would run afoul of something like that.

Aug. 31, 2026

Re: spam protection on the mailing list

by Gerald Pfeifer

On Mon, 31 Aug 2026, Jeremy Newman via Wine-Devel wrote: > I've contacted the list provider to see if anything else can be done to > prevent this One idea might be rate limiting, i.e., at most X mails per sender address per day (if the software allows for that)? Another would be putting everybody on moderation initially and switch them to direct posting upon their first on topic message. I'd expect there to be a brief initial training period, and after a few weeks we'd have covered nearly all regular contributors. Gerald

Aug. 31, 2026

Re: spam protection on the mailing list

by THOMAS SMITH

Hello, I got hundreds of them. Comcast's spam filter did not catch them. > On 08/30/2026 7:22 PM PDT Jeremy Newman via Wine-Devel <wine-devel(a)list.winehq.org> wrote: > Just to verify, I checked the bigbuto and yassmminss emails against SpamHaus and StopForumSpam, and neither of these emails are listed in either place. So these were clearly a one-off pump and dump email address. We would not have caught it just by doing a manual check. > > These emails should have been caught by normal spam filters though, a Bayesian filter should have flagged them. valhalla2100(a)comcast.net

Aug. 31, 2026

Re: spam protection on the mailing list

by Jeremy Newman

Just to verify, I checked the bigbuto and yassmminss emails against SpamHaus and StopForumSpam, and neither of these emails are listed in either place. So these were clearly a one-off pump and dump email address. We would not have caught it just by doing a manual check. These emails should have been caught by normal spam filters though, a Bayesian filter should have flagged them. On Sunday, August 30th, 2026 at 9:03 PM, Jeremy Newman via Wine-Devel <wine-devel(a)list.winehq.org> wrote: > This user used a gmail address and sent through Google after subscribing themselves. I've contacted the list provider to see if anything else can be done to prevent this, and asked them what protections they use FFR. > > For now, I've switched the list to have new subscriptions need approval from an admin. We'll check the incoming email against spam dbs before approving. It is manual, and could be tedious. Even then no guarantee, a freshly created email like the gmail above would probably get approved. Normally, wine-devel doesn't get all that many subscription requests, so hopefully it doesn't overwhelm us. > > > On Sunday, August 30th, 2026 at 2:36 PM, Stefan Dösinger via Wine-Devel <wine-devel(a)list.winehq.org> wrote: > > > Am Sonntag, 30. August 2026, 22:20:25 Ostafrikanische Zeit schrieb Ty via > > Wine-Devel: > > > Do we not have any spam protection on the mailing lists? This is pretty bad > > > right now. > > > > > Normally we do. It must have failed somehow. > > > > > And to make matters worse it failed on a Sunday - Newman is surely out of the > > office > > > > > Cheers, > > Stefan

Aug. 31, 2026

Re: spam protection on the mailing list

by Jeremy Newman

This user used a gmail address and sent through Google after subscribing themselves. I've contacted the list provider to see if anything else can be done to prevent this, and asked them what protections they use FFR. For now, I've switched the list to have new subscriptions need approval from an admin. We'll check the incoming email against spam dbs before approving. It is manual, and could be tedious. Even then no guarantee, a freshly created email like the gmail above would probably get approved. Normally, wine-devel doesn't get all that many subscription requests, so hopefully it doesn't overwhelm us. On Sunday, August 30th, 2026 at 2:36 PM, Stefan Dösinger via Wine-Devel <wine-devel(a)list.winehq.org> wrote: > Am Sonntag, 30. August 2026, 22:20:25 Ostafrikanische Zeit schrieb Ty via > Wine-Devel: > > Do we not have any spam protection on the mailing lists? This is pretty bad > > right now. > > Normally we do. It must have failed somehow. > > And to make matters worse it failed on a Sunday - Newman is surely out of the > office > > Cheers, > Stefan

Aug. 31, 2026

Re: spam protection on the mailing list

by Stefan Dösinger

Am Sonntag, 30. August 2026, 22:20:25 Ostafrikanische Zeit schrieb Ty via Wine-Devel: > Do we not have any spam protection on the mailing lists? This is pretty bad > right now. Normally we do. It must have failed somehow. And to make matters worse it failed on a Sunday - Newman is surely out of the office Cheers, Stefan

Aug. 30, 2026

spam protection on the mailing list

by Ty

Do we not have any spam protection on the mailing lists? This is pretty bad right now.

Aug. 30, 2026

Wine staging 11.16 release

by Alistair Leslie-Hughes

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 11.15 (281 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * wined3d: fix vk swapchain rendering too dark by supporting UNORM to SRGB conversion for brightness similar to gl * wined3d: revert fix vk swapchain rendering too dark by supporting UNORM to SRGB conversion for brightness similar to gl * wintrust: Add parameter check in WTHelperGetProvCertFromChain Removed (No longer required). * None Added: * None Updated: * vkd3d-latest * ws2_32-af_unix Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

Aug. 22, 2026

Re: Wine staging 11.15 release

by Dean Greer

I’d advise against the patch from this MR being included as it firstly needs to be rebased and it’s already incomplete and incompatible with another wine-staging patchset. To even become useful it also requires changes in the DXMT side. On Sat, Aug 8, 2026 at 11:04 PM afifsworld132--- via Wine-Devel < wine-devel(a)list.winehq.org> wrote: > I wonder if the MR adding DXMT/D3DMetal patch would be worth having in > Staging? > https://gitlab.winehq.org/wine/wine/-/merge_requests/11257 > Currently, something like it is included in CrossOver but removed in every > other up-to-date releases, and no way to get DXMT or D3DMetal support > without compiling from source. It seems to be barred by some concerns for > future maintenance and not much else. >

Aug. 9, 2026

Re: Wine staging 11.15 release

by afifsworld132＠gmail.com

I wonder if the MR adding DXMT/D3DMetal patch would be worth having in Staging? https://gitlab.winehq.org/wine/wine/-/merge_requests/11257 Currently, something like it is included in CrossOver but removed in every other up-to-date releases, and no way to get DXMT or D3DMetal support without compiling from source. It seems to be barred by some concerns for future maintenance and not much else.

Aug. 9, 2026