DKIM won't sign for arbitrary "From" address
I maintainer di solito rispondono entro 4 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 8/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Perl
- Stelle
- 164
- Fork
- 167
- Merge medio
- 6g 7h
- PR unite (30g)
- 27
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di openwebwork/webwork2
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
openwebwork/webwork2#3295 ·
I maintainer di solito rispondono entro 4 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
openwebwork/webwork2#3290 ·
I maintainer di solito rispondono entro 4 giorni
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 62/100
openwebwork/webwork2#2997 ·
I maintainer di solito rispondono entro 4 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 56/100
openwebwork/webwork2#3276 ·
I maintainer di solito rispondono entro 4 giorni
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 52/100
openwebwork/webwork2#3272 · 6 commenti ·
I maintainer di solito rispondono entro 4 giorni
Tutte le issue di openwebwork/webwork2
Issue simili
-
nftables: "Display comment in rules list?" option has no effect, comments not shown in rules listAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Type: Bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
inverse-inc/packetfence#9707 ·
I maintainer di solito rispondono entro 1 giorno
-
Mailaddress phrase quotingAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
RotherOSS/otobo#6457 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
The reply-to for the pro user signup emails should be the email of the user instrad of the contact@ emailForse già presa @sisodiaumang l’ha presa oggi. Aperta🏭 producer platform - spam
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
openfoodfacts/openfoodfacts-server#15447 ·
I maintainer di solito rispondono entro 1 giorno
-
Harden argument handling in deploy-contract.shForse già presa @Asta-wizard l’ha presa 1 giorno fa. ApertaStellar Wave
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Feyisara2108/stellargive#1377 · 3 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno