Problem posting to fltk.general via email (rejected by Google)
10 views
Skip to first unread message
Albrecht Schlosser
Mar 6, 2023, 12:32:50 PM3/6/23
to fltk.coredev
Does anybody else have issues posting to fltk.general via email?
Last week I was on tour and my mail(s) to fltk.general were rejected by Google with the usual link to their more or less useless "help" information (see below).
I even tried to post via the Google Group web interface and my first attempt was rejected as well with "error message" saying just "message deleted"! Not very helpful. A second attempt succeeded then...
Now, back at home, I still can't post to fltk.general whereas posting to fltk.coredev works fine (about 30 mins ago), and if this mail arrives as well.
When my email is rejected I get this (edited) response mail:
```
```
Well, I could try to use the web interface again, but this is not only annoying but really ... (I don't know a word for this mess). :-(
Does anybody else have such issues? My last successful post (via email) to fltk.general was obviously on Feb 21 whereas I had to use the web interface two days ago on Mar 4, 2023.
Note that I'm using a mail domain of my provider (online.de) which I can't change in any way, i.e. I can't add any DNS settings etc..
Does anybody have an idea how to work around this - other than trying another mail address? And why does it work for fltk.coredev and not for fltk.general?
FTR: my answer to a question of today should have been the following mail which should IMHO not constitute a SPAM problem. If someone could be so kind to post it to fltk.general on my behalf I'd appreciate this. TIA.
Full contents of my original email posted to fltk.general (and rejected):
Which OS, which shell?
Probably history.
One reason might be the Windows problem that both the shared library stub archives and the static libraries have the same file type '.lib' which is a known and annoying issue causing problems in many contexts (particularly if someone - i.e. a library build system - tries to work around this and "invents" other naming conventions!).
Maybe we could build the shared libs in ./lib where *I* would expect them. This is done in CMake builds, BTW. However, we need to take care of the Windows naming issues mentioned above which exist also if you build with configure/make under MinGW/msys etc..
Last week I was on tour and my mail(s) to fltk.general were rejected by Google with the usual link to their more or less useless "help" information (see below).
I even tried to post via the Google Group web interface and my first attempt was rejected as well with "error message" saying just "message deleted"! Not very helpful. A second attempt succeeded then...
Now, back at home, I still can't post to fltk.general whereas posting to fltk.coredev works fine (about 30 mins ago), and if this mail arrives as well.
When my email is rejected I get this (edited) response mail:
```
|
|||||
|
The response was: Message rejected by Google Groups. Please visit http://mail.google.com/support/answer/188131?hl=en to review our Bulk Email Senders Guidelines. |
This link will take you to a third-party
site
Reporting-MTA: dns; googlemail.com Received-From-MTA: dns; <my-email>@online.de Arrival-Date: Mon, 06 Mar 2023 09:11:33 -0800 (PST) X-Original-Message-ID: <3a82434c-9519-77e8...@online.de> Final-Recipient: rfc822; fltkg...@googlegroups.com Action: failed Status: 5.0.0 Diagnostic-Code: smtp; Message rejected by Google Groups. Please visit http://mail.google.com/support/answer/188131?hl=en to review our Bulk Email Senders Guidelines. Last-Attempt-Date: Mon, 06 Mar 2023 09:11:34 -0800 (PST)
```
Well, I could try to use the web interface again, but this is not only annoying but really ... (I don't know a word for this mess). :-(
Does anybody else have such issues? My last successful post (via email) to fltk.general was obviously on Feb 21 whereas I had to use the web interface two days ago on Mar 4, 2023.
Note that I'm using a mail domain of my provider (online.de) which I can't change in any way, i.e. I can't add any DNS settings etc..
Does anybody have an idea how to work around this - other than trying another mail address? And why does it work for fltk.coredev and not for fltk.general?
FTR: my answer to a question of today should have been the following mail which should IMHO not constitute a SPAM problem. If someone could be so kind to post it to fltk.general on my behalf I'd appreciate this. TIA.
Full contents of my original email posted to fltk.general (and rejected):
On 3/6/23 16:35 HASM wrote:
Building a fresh clone of fltk master from github, passing --enable-shared to ./configure.
Which OS, which shell?
Any reason the shared libraries are created under ./src and not under ./lib?
Probably history.
One reason might be the Windows problem that both the shared library stub archives and the static libraries have the same file type '.lib' which is a known and annoying issue causing problems in many contexts (particularly if someone - i.e. a library build system - tries to work around this and "invents" other naming conventions!).
Maybe we could build the shared libs in ./lib where *I* would expect them. This is done in CMake builds, BTW. However, we need to take care of the Windows naming issues mentioned above which exist also if you build with configure/make under MinGW/msys etc..
Greg Ercolano
Mar 6, 2023, 1:54:14 PM3/6/23
to fltkc...@googlegroups.com
On 3/6/23 09:32, Albrecht Schlosser wrote:
Does anybody else have issues posting to fltk.general via email?
Last week I was on tour and my mail(s) to fltk.general were rejected by Google with the usual link to their more or less useless "help" information (see below).
I even tried to post via the Google Group web interface and my first attempt was rejected as well with "error message" saying just "message deleted"! Not very helpful. A second attempt succeeded then...
Now, back at home, I still can't post to fltk.general whereas posting to fltk.coredev works fine (about 30 mins ago), and if this mail arrives as well.
I haven't had issues myself, and I use the email interface to
both groups
exclusively.
But I haven't been posting much lately.
In the bounce emails, does it show the full email headers of the failed message,
and is there anything interesting in any fields related to authentication results,
and look for SPF pass/fail/etc status. Often google inserts error information
into the headers indicating what triggered the rejection.
When things are working properly, you'll see a lot of 'pass' msgs:
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass header.i=@fltkdev.fltk.org header.s=default header.b=oIRPJo5S;
spf=pass (google.com: best guess record for domain of
[..]
Authentication-Results: mx.google.com;
dkim=pass header.i=@foo.org header.s=default header.b=oIRPJo5S;
spf=pass (google.com: best guess record for domain of foo.org ...)
[..]
Received-SPF: pass (google.com: best guess record for domain of foo.org designates 1.2.3.4 as permitted sender)
If you're using thunderbird, double check what your email program is using
as the outbound email server, to make sure it's not taking a long route thru
some server that google doesn't trust because it's different than your return address.
exclusively.
But I haven't been posting much lately.
In the bounce emails, does it show the full email headers of the failed message,
and is there anything interesting in any fields related to authentication results,
and look for SPF pass/fail/etc status. Often google inserts error information
into the headers indicating what triggered the rejection.
When things are working properly, you'll see a lot of 'pass' msgs:
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass header.i=@fltkdev.fltk.org header.s=default header.b=oIRPJo5S;
spf=pass (google.com: best guess record for domain of
[..]
Authentication-Results: mx.google.com;
dkim=pass header.i=@foo.org header.s=default header.b=oIRPJo5S;
spf=pass (google.com: best guess record for domain of foo.org ...)
[..]
Received-SPF: pass (google.com: best guess record for domain of foo.org designates 1.2.3.4 as permitted sender)
If you're using thunderbird, double check what your email program is using
as the outbound email server, to make sure it's not taking a long route thru
some server that google doesn't trust because it's different than your return address.
Rob McDonald
Mar 6, 2023, 2:07:28 PM3/6/23
to fltk.coredev
I've been having similar problems with the web interface.
I was able to post via email by dropping the period in fltk.general. Usually google based products ignore the period and make it optional. However in this case, including it failed -- omitting it succeeded.
Rob
I was able to post via email by dropping the period in fltk.general. Usually google based products ignore the period and make it optional. However in this case, including it failed -- omitting it succeeded.
Rob
Greg Ercolano
Mar 6, 2023, 3:36:32 PM3/6/23
to fltkc...@googlegroups.com
On 3/6/23 10:54, Greg Ercolano wrote:
On 3/6/23 09:32, Albrecht Schlosser wrote:
Does anybody else have issues posting to fltk.general via email?
Last week I was on tour and my mail(s) to fltk.general were rejected by Google with the usual link to their more or less useless "help" information (see below).
I haven't had issues myself, and I use the email interface to both groups
exclusively.
But I haven't been posting much lately.
Ha, OK I just got one; after posting a few things to
fltk.general,
it seemed to 'randomly' reject one of my posts:
it looks like an SPF failure for an IPV6 address:
ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@seriss-com.20210112.gappssmtp.com header.s=20210112 header.b=cULoMtDX; spf=softfail (google.com: domain of transitioning er...@seriss.com does not designate 2607:f8b0:4864:20::1032 as permitted sender) smtp.mailfrom=er...@seriss.comSo in my case I guess this is an ipv6 issue where my domain SPF records
need to include the ipv6 addresses for google.
Albrecht Schlosser
Mar 6, 2023, 3:58:24 PM3/6/23
to fltkc...@googlegroups.com
[top-posting intentionally]
FTR: meanwhile I could send two messages to fltk.general (w/o changing anything in my setup). I sent details to Greg for review, but I didn't see any SPF fails or similar in my rejected mail.
For me (i.e. in my case) it looks like an intermittent issue in Google's servers or something like that.
Gregs case (below) seems different though, since there's a clear error message. Interesting that this happened at the same day ...
FTR: meanwhile I could send two messages to fltk.general (w/o changing anything in my setup). I sent details to Greg for review, but I didn't see any SPF fails or similar in my rejected mail.
For me (i.e. in my case) it looks like an intermittent issue in Google's servers or something like that.
Gregs case (below) seems different though, since there's a clear error message. Interesting that this happened at the same day ...
Reply all
Reply to author
Forward
0 new messages