This repository was archived by the owner on Nov 16, 2025. It is now read-only.
forked from riegel/node.js-SMTP-server
-
Notifications
You must be signed in to change notification settings - Fork 8
This repository was archived by the owner on Nov 16, 2025. It is now read-only.
No data received? #1
Copy link
Copy link
Open
Description
Hi there,
Just tried out your master version of node-smtp (0.0.5) and I'm running into a problem with your example code.
I tried:
var smtp = require('smtp')
smtp.createServer(function(connection) {
connection.on('DATA', function(message) {
console.log('Message from ' + message.sender)
message.on('data', function(data) {
console.log("DATA: " + data)
})
message.on('end', function() {
console.log('EOT')
})
})
}).listen(25)
console.log("SMTP server running on port 25")
as well as a totally simple case:
var smtp = require('smtp')
smtp.createServer().listen(25)
console.log("SMTP server running on port 25")
And I'm not getting a sane response when I get to the data portion of smtp "conversation":
220 hostname.unconfigured ESMTP node.js
EHLO blah
250-hostname.unconfigured
250 HELP
MAIL FROM: <[email protected]>
250 MAIL FROM looks good enough for me.
RCPT TO: <[email protected]>
250 RCPT TO ...I hope that's right. I didn't check.)
DATA
a.
a.sd
.asd
.
..
.as
d.a
sd.
.
It just never responds..
I noticed there's a In.pause() in smtp.js in the handler for DATA. I commented that out.. and I at least get my data handlers being fired, but the client never sees: Out.out('354 Enter mail, end with "." on a line by itself'), nor am I ever able to finish the data off via "\r\n.\r\n".
When I revert to 0.0.3, this is not a problem. Works fine. Just thought I'd give you a heads up.
Luke G
Metadata
Metadata
Assignees
Labels
No labels