Difference between revisions of "Membermatters"
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
* we should look for ways to find out why the emails are rejected by some servers | * we should look for ways to find out why the emails are rejected by some servers | ||
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers | * we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers | ||
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected. | |||
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address | |||
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end. | |||
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring | |||
= certbot = | = certbot = | ||
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day | * juul used pipx to install, and then had to manually make a systemd job to check it twice a day | ||
Revision as of 21:31, 2 June 2025
this is the notes for the membermatters installation
to create a new user
github
- changes juul made to add sendmail as an option
- are using the sudoroom branch in our docker
- we are working on mounting the docker image with git on the server, so we can make changes to production and try them
we are not spam
- emails sent by this system for people to validate their account, or reset their password, are important
- emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
- we should look for ways to find out why the emails are rejected by some servers
- we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
- Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
- emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
- we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
- we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring
certbot
- juul used pipx to install, and then had to manually make a systemd job to check it twice a day