Skip to content

John McEleney / mailutils

Go to a project
Toggle navigation
Toggle navigation pinning
Commit 366977ac 366977aca3eda1775cbe1522bd467afbb1a016bb by Sam Roberts
Options

Updated now that smtp mailer is working.

1 parent 3ea5d904
Inline Side-by-side
Showing 1 changed file with 15 additions and 12 deletions
...@@ -104,11 +104,15 @@ Some possible use cases the API must support are: ...@@ -104,11 +104,15 @@ Some possible use cases the API must support are:
104 104
105 /sbin/sendmail isn't always sendmail... sometimes its a sendmail-compatible 105 /sbin/sendmail isn't always sendmail... sometimes its a sendmail-compatible
106 wrapper, so assume /sbin/sendmail understands only a recipient 106 wrapper, so assume /sbin/sendmail understands only a recipient
107 list, -f, -F, -t, and -oi, these seem to be pretty basic. Cross fingers. 107 list, -f and -oi, these seem to be pretty basic. Cross fingers.
108 108
109 Pipe to "/sbin/sendmail -oi [-f from] <to|-t>", supplying -f if there 109 Pipe to "/sbin/sendmail -oi [-f from] [to...]", supplying -f if there
110 was a from, and supplying either the recipient list from the to, 110 was a from, and supplying the recipient list from the to (if there
111 or the -t flag. 111 is no recipient list, assume it will read the message contents for
112 the recipients).
113
114 Note: do we need to supply -t to sendmail to force it to read the
115 message contents to find the recipients?
112 116
113 Note: since the stdout and stderr of sendmail is closed, we have no 117 Note: since the stdout and stderr of sendmail is closed, we have no
114 way of ever giving feedback on failure. Also, what should the return 118 way of ever giving feedback on failure. Also, what should the return
...@@ -117,14 +121,13 @@ which is less than descriptive! ...@@ -117,14 +121,13 @@ which is less than descriptive!
117 121
118 @subheading The SMTP mailer. 122 @subheading The SMTP mailer.
119 123
120 This is very rundamentary right now, all of what sendmail does must be 124 This mailer does NOT canonicalize the message. This must be done before
121 implemented. 125 sending the message, or it may be assumed that the MTA will do so.
126
127 It does blind out the Bcc: header before sending, though.
122 128
123 Actually, I think some things (like date and message-id being inserted) 129 Note: mutt always puts the recipient addresses on the command line, even
124 will be done by the receiving SMTP MTA. However, the specs say we 130 bcc ones, do we strip the bcc before forwarding with SMTP?
125 are supposed to canonicalize the mail before sending it, not rely
126 on the receiving SMTP agent to patch up our mail. Hmm... which is
127 the right way?
128 131
129 @subheading Non-RFC822 addresses. 132 @subheading Non-RFC822 addresses.
130 133
...@@ -132,7 +135,7 @@ An address that has no domain is not and RFC822 email address. What ...@@ -132,7 +135,7 @@ An address that has no domain is not and RFC822 email address. What
132 do I do with them? Should the user of the API be responsible for 135 do I do with them? Should the user of the API be responsible for
133 determining what is mean by email to "john" means? Or should the 136 determining what is mean by email to "john" means? Or should the
134 be able to configure sendmail to decide globally what this means. If so, we 137 be able to configure sendmail to decide globally what this means. If so, we
135 can pass the address to sendmail, but we have to decide for SMTTP! So, 138 can pass the address to sendmail, but we have to decide for SMTP! So,
136 right now these addresses are rejected. This could be changed. 139 right now these addresses are rejected. This could be changed.
137 140
138 141
......