-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2.2 #560
Comments
Added new message option Install with transport.sendMail({
raw: 'Content-Type: text/plain\r\nSubject: Test\r\n\r\nHello world!',
// envelope needs to be set as raw is not processed
envelope: {
from: '[email protected]',
to: '[email protected]'
}
}); |
Released v2.2.0-beta.1 that adds new message option var message = {
from: '"Sender Name" <[email protected]>',
to: '"Receiver Name" <[email protected]>',
subject: 'Calendar invite',
text: 'This message contains a calendar event',
icalEvent: {
method: 'request',
// content can be a string, a buffer or a stream
// alternatively you could use `path` that points to a file or an url
content: 'BEGIN:VCALENDAR\r\nPRODID:-//ACME/DesktopCalendar//EN\r\n...'
}
}; |
Released v2.2.0-beta.2 that adds support for proxied sockets. See full example for using SOCKS5 here. Nodemailer does not have built-in knowledge about different proxy protocols. Instead it provides a mechanism for using custom sockets which can be created with some proxy module, eg. socks. transporter.getSocket = function(options, callback){
getNewSocketSomehow(options.port, options.host, function(err, socket){
if(err){
return callback(err);
}
callback(null, {
connection: socket
});
});
}; |
v2.2.0-beta.5 has support for List-* headers var mailOptions = {
list: {
// List-Help: <mailto:[email protected]?subject=help>
help: '[email protected]?subject=help',
// List-Unsubscribe: <http:https://example.com> (Comment)
unsubscribe: {
url: 'http:https://example.com',
comment: 'Comment'
},
// List-Subscribe: <mailto:[email protected]?subject=subscribe>
// List-Subscribe: <http:https://example.com> (Subscribe)
subscribe: [
'[email protected]?subject=subscribe',
{
url: 'http:https://example.com',
comment: 'Subscribe'
}
],
// List-Post: <http:https://example.com/post>, <mailto:[email protected]?subject=post> (Post)
post: [
[
'http:https://example.com/post',
{
url: '[email protected]?subject=post',
comment: 'Post'
}
]
]
}
}; |
I'm not sure anymore that the List-* thing should be built into Nodemailer, I should probably consider moving it into a plugin instead. |
Released v2.2.0-beta.1 with simple configuration verifier // verify connection configuration
transporter.verify(function(error, success) {
if (error) {
console.log(error);
} else {
console.log('Server is ready to take our messages');
}
}); |
I have closed all the issues related to v2.2, so I can publish a rc version. Probably going to wait until tomorrow with the rc in case I'm going to have some new ideas of what to put into this release. |
Released v2.2.0-rc.7. Expected stable release date: February 19. |
v2.2.0-rc.11 makes the dependency tree a bit smaller as there is no need for clone anymore. Instead a more simpler homegrown method is used that only makes shallow copies |
Stable release was planned for tomorrow but I don't have time for it then, so I published v2.2.0 already today. Release blog post can be found here |
How to convert List-* headers now ? |
I am not able to add a comment containing an accent to my List-Unsubscribe header, I do not see how to encode it with the current version of nodemailer. |
This is the tracking issue for the next Nodemailer version, v2.2.0.
Planned release date: N/A
Planned features/updates (might change):
Add new transport type: IMAP. Useful when uploading sent messages to the Sent folder in IMAP.this should be handled by an external plugin, related issue: Add new transport type: IMAP #561The text was updated successfully, but these errors were encountered: