thaume/docpad-plugin-contactify

docpad-plugin-contactify's Issues

Receivers needs to be a string and not an array

It seems that nodemailer is expecting a comma delimited string in the "to" field and not an array. When the receiver array is passed I get the 'RecipientError' and '501 5.5.4 Invalid Email Address. If I concat the enquiry.email and config.to then the error goes away

Redirect config option does not work

Doesn't matter what is put in the redirect config option the page is always redirected to the root of the web site. Code should be 'config.redirect' rather than 'enquiry.redirect'.

empty dir after npm install

After running the npm install

npm install --save docpad-plugin-contactify
npm http GET https://registry.npmjs.org/docpad-plugin-contactify
npm http 304 https://registry.npmjs.org/docpad-plugin-contactify
npm http GET https://registry.npmjs.org/nodemailer
npm http 304 https://registry.npmjs.org/nodemailer
npm http GET https://registry.npmjs.org/mailcomposer
npm http GET https://registry.npmjs.org/simplesmtp
npm http 304 https://registry.npmjs.org/simplesmtp
npm http 304 https://registry.npmjs.org/mailcomposer
npm http GET https://registry.npmjs.org/rai
npm http GET https://registry.npmjs.org/xoauth2
npm http GET https://registry.npmjs.org/mimelib
npm http GET https://registry.npmjs.org/mime/1.2.9
npm http 304 https://registry.npmjs.org/mime/1.2.9
npm http 304 https://registry.npmjs.org/rai
npm http 304 https://registry.npmjs.org/xoauth2
npm http 304 https://registry.npmjs.org/mimelib
npm http GET https://registry.npmjs.org/encoding
npm http GET https://registry.npmjs.org/addressparser
npm http 304 https://registry.npmjs.org/encoding
npm http 304 https://registry.npmjs.org/addressparser
npm WARN package.json [email protected] No repository field.
npm http GET https://registry.npmjs.org/iconv-lite/0.2.7
npm http 304 https://registry.npmjs.org/iconv-lite/0.2.7
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
[email protected] node_modules\docpad-plugin-contactify
└── [email protected] ([email protected], [email protected])

When running docpad I get

Error: Cannot find module 'C:\myproj\node_modules\docpad-plugin-contactify\out\contactify.plugin.js

The file out\contactify.plugin.js does not exist

Can't stop the destination email address being sent to the sender

In mail options there is no way to stop the enquiry.email value being added to the "to" option of "mailOptions".

receivers.push(enquiry.email, config.to)

            mailOptions = {
                to: receivers.join(","),
                from: config.from or enquiry.email,
                subject: 'Enquiry from ' + enquiry.name + ' <' + enquiry.email + '>',
                text: enquiry.message,
                html: '<p>' + enquiry.message + '</p>'
            }

The reason you might want to prevent this is because of spam. If a spammer sends a message via contactify then they will automatically receive an email containing your "config.to" email address in the header. I'm getting a lot of spam and every email has both mine and the spammer's (admittedly false) email address in the "to" field.