DKIM won't sign for arbitrary "From" address
Maintainer antworten meist innerhalb von 4 Tagen
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 8/100
Rechercherichtung
The payload names no source files, tests or entry points, so there is no obvious starting file. The reporter's open question is which address the server should send mail from so that DKIM signing passes: a generic sender with Reply-To set to the student, or some other design. Settling that question with the maintainers is the first step, since no code change is clear yet. Done would mean an agreed sender policy and a passing DKIM check, and the thread has been silent for about two and a half years.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
I have a situation with the RS server that many WW server admins would not run into. For most other installations, all user emails have the same @domain.edu, and it is a domain where the WW server is a subdomain. With the RS server, this is not the case.
For some institutions, emails from the WW server are rejected if they are not DKIM signed. Normally, it's easy to sign because there is just one domain.edu to worry about, and it's actually a domain you have authority with. But when the "From" address is a student's [email protected] then I can't (shouldn't?) set things up to give a DKIM signature for all the possibilities for whatever.edu.
I've tested in a RS WW course, that if I set my email address to [email protected] and send a message to a mail testing service, it is not DKIM signed. But if I change my email to [email protected] then it will be signed. This makes sense...opendkim is configured to sign for webwork-hosting.runestone.academy :)
So the issue is that I need the WW server to send emails from a webwork-hosting.runestone.academy address, but there are two immediate issues with that.
- The reply-to should be the sender's actual email address. OK, we can probably make that happen.
- The recipient (usually the instructor) is going to see they have an email from
[email protected]instead of from the student. How confusing will this be for them?
As I think about this, it starts to seem "wrong" that we send emails that are "from" an institution.edu address. Of course it's fine when you work at that institution and the institutional mail server is actually the mail server you are using, and the admin supports your cause. But RS is using postfix to send mail, and can't be the only WW server where this DKIM signing issue is an issue.
Note that most RS subscribing schools have "low" standards and the emails do get through, even without a DKIM signature. It's a few (but growing number) that are bouncing the messages back.
Unless people have good ideas, I think I will have to alter the RS WW server to send from some generic webwork-hosting.runestone.academy address and make sure the reply-to is the student address.
- Vorherrschende Sprache
- Perl
- Sterne
- 164
- Forks
- 167
- Ø Merge
- 6 T. 7 Std.
- Gemergte PRs (30 T.)
- 27
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Kein Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus openwebwork/webwork2
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
openwebwork/webwork2#3295 ·
Maintainer antworten meist innerhalb von 4 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
openwebwork/webwork2#3290 ·
Maintainer antworten meist innerhalb von 4 Tagen
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 62/100
openwebwork/webwork2#2997 ·
Maintainer antworten meist innerhalb von 4 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 56/100
openwebwork/webwork2#3276 ·
Maintainer antworten meist innerhalb von 4 Tagen
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 52/100
openwebwork/webwork2#3272 · 6 Kommentare ·
Maintainer antworten meist innerhalb von 4 Tagen
Alle Issues in openwebwork/webwork2
Ähnliche Issues
-
nftables: "Display comment in rules list?" option has no effect, comments not shown in rules listOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Maintainer antworten meist innerhalb von 1 Tag
-
Type: Bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
inverse-inc/packetfence#9707 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 67/100
RotherOSS/otobo#6457 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
The reply-to for the pro user signup emails should be the email of the user instrad of the contact@ emailEvtl. vergeben @sisodiaumang hat das heute übernommen. Offen🏭 producer platform - spam
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
openfoodfacts/openfoodfacts-server#15447 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100