master
have re-initialised the repository.. @andris9
Hi Guys,
i want to use nodemailer with sendmail but got:
{ Error: connect ECONNREFUSED 127.0.0.1:25
at Object.exports._errnoException (util.js:1018:11)
at exports._exceptionWithHostPort (util.js:1041:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
code: 'ECONNECTION',
errno: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 25,
command: 'CONN' }
telnet works
$ telnet 127.0.0.1 25
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
220 bla@blub.tld ESMTP Postfix (Ubuntu)
iptables is configured to accept allr outgoing
Okay my error still exists but i am able to send a mail from the guest os (docker container) through the host os postfix (MTA).
It seem to my that nodemailer tries to open a connection to the MTA of the guest os (docker container) which has no MTA installed.
My first assumption was that the nodemailer-sendmail-transport is not spawning the proper command and put a log out before to inspect the spawned command and args but this section is never reached.
So, is nodemailer open a connection to 127.0.0.1:25 during transport creation?
Can i configure this behavior?
Because i only need to spawn the sendmail command to get my sending a email issue working ... ?
Ah i forgot I am using the nodemailer version 2.7.0 and sendmail-transport 1.0.2
Can you guys please help me and provide an advice how to solve the last remaining config issue for my problem?
Okay now i upgraded to version 4.0.1 and use the internal sendmail feature.
This gives me the success callback but the mail is not send.
sendmail command spawned: /usr/sbin/sendmail [ '-i', '-f', 'blah@blub.de', 'test@gmail.com' ]
Result is:
Mail send { envelope:
{ from: 'blah@blub.de',
to: [ 'test@gmail.com' ] },
messageId: '18db223c-6e90-a629-4c2e-e6647a939bc6@blub.de',
response: 'Messages queued for delivery' }
i logged the spawned command then and use it manualy in the terminal and my mail was send.
...
This is a curious behaviour. (@.@)
Anyone have an idea about this?
I am developing a pure node App (without express or any other framework)
I stored some values in the req (request) object like this
req.token = uuid();
`
in another route, when I did this
console.log(req.token);
I get undefined. Please is there a sure way of saving value into the http request object for later use?
Hi all, I am wondering why the following:
from: req.params.name + ' <' + req.params.email + '>',
keeps returning the error: Domain of sender address XXXXXX@gmail.com> does not exist
[{
path: path + pdfFileName,
filename: pdfFileName,
contentType: 'application/pdf'
}]
[2018-06-21 12:32:20] DEBUG Creating transport: nodemailer (4.6.7; +https://nodemailer.com/; SMTP/4.6.7[client:4.6.7])
[2018-06-21 12:32:20] DEBUG Sending mail using SMTP/4.6.7[client:4.6.7]
[2018-06-21 12:32:20] INFO [lBg35Kf9cPY] Connection established to 40.101.70.18:587
[2018-06-21 12:32:20] INFO [lBg35Kf9cPY] Connection upgraded with STARTTLS
[2018-06-21 12:32:20] DEBUG [lBg35Kf9cPY] SMTP handshake finished
[2018-06-21 12:32:27] INFO [lBg35Kf9cPY] User "ben@synthbit.io" failed to authenticate
[2018-06-21 12:32:27] DEBUG [lBg35Kf9cPY] Closing connection to the server using "end"
[2018-06-21 12:32:27] ERROR Send Error: Invalid login: 535 5.7.3 Authentication unsuccessful [VI1PR0502CA0027.eurprd05.prod.outlook.com]
Can't find solution to this error
{ Error: connect ECONNREFUSED 127.0.0.1:465
at Object.exports._errnoException (util.js:1050:11)
at exports._exceptionWithHostPort (util.js:1073:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1093:14)
code: 'ECONNECTION',
errno: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 465,
command: 'CONN' }
I also tried using 587
but same error, there no process using the ports
var transporter = nodemailer.createTransport({
service: 'smtp.gmail.com',
port: 465,
auth: {
user: process.env.EMAIL,
pass: process.env.PWD
}
});