You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,12 +8,12 @@ Many people seem to address this use case with `nullmailer` / `ssmtp` / `msmtp`
8
8
However, I found that many relay hosts put requirements on `{envelope,header}x{from,to}`.
9
9
10
10
For example, I found it tricky to impossible to configure above tools to relay through AWS SES,
11
-
where the IAM user is [restricted by various policies](https://docs.aws.amazon.com/ses/latest/dg/control-user-access.html).
11
+
where the IAM user is [restricted by various policies](https://docs.aws.amazon.com/ses/latest/dg/control-user-access.html) to certain sender & receiver addresses.
12
12
13
-
One approach to comply with such restrictions is to rewrite `{envelope,header}x{from,to}`.
14
-
However, I found that hard or impossible to configure with above tools.
13
+
To comply one would need to configure abice tools to rewrite `{envelope,header}x{from,to}`.
14
+
However, I found that hard or impossible to do, especially if the recipient address is restricted by the relayhost policy.
15
15
16
-
Hence, I wrote my this tiny `sendmail` replacement.
16
+
Hence, I wrote this tiny `sendmail` replacement.
17
17
Deploy it to your Debian using the instructions below.
0 commit comments