DKIM won't sign for arbitrary "From" address
Les mainteneurs répondent en général sous 4 jours
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 8/100
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
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.
- Langage dominant
- Perl
- Étoiles
- 164
- Forks
- 167
- Merge moyen
- 6 j 7 h
- PR mergées (30 j)
- 27
Préparer son environnement
- Fournit un Dockerfile ou un fichier Docker Compose
- Aucun modèle de pull request
- Aucun guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de openwebwork/webwork2
-
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100
openwebwork/webwork2#3295 ·
Les mainteneurs répondent en général sous 4 jours
-
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100
openwebwork/webwork2#3290 ·
Les mainteneurs répondent en général sous 4 jours
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 62/100
openwebwork/webwork2#2997 ·
Les mainteneurs répondent en général sous 4 jours
-
Difficulté 2/5 1-3 heures Accessibilité débutants 56/100
openwebwork/webwork2#3276 ·
Les mainteneurs répondent en général sous 4 jours
-
Difficulté 4/5 3-5 jours Accessibilité débutants 52/100
openwebwork/webwork2#3272 · 6 commentaires ·
Les mainteneurs répondent en général sous 4 jours
Toutes les issues de openwebwork/webwork2
Issues similaires
-
nftables: "Display comment in rules list?" option has no effect, comments not shown in rules listOuverte
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 1 jour
-
Type: Bug
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
inverse-inc/packetfence#9707 ·
Les mainteneurs répondent en général sous 1 jour
-
Mailaddress phrase quotingOuverte
Difficulté 2/5 1-3 heures Accessibilité débutants 67/100
RotherOSS/otobo#6457 · 2 commentaires ·
Les mainteneurs répondent en général sous 1 jour
-
The reply-to for the pro user signup emails should be the email of the user instrad of the contact@ emailPeut-être pris @sisodiaumang l’a pris aujourd’hui. Ouverte🏭 producer platform - spam
Difficulté 2/5 1-3 heures Accessibilité débutants 66/100
openfoodfacts/openfoodfacts-server#15447 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100