Skip to content
This repository has been archived by the owner on Feb 23, 2021. It is now read-only.

Sending invitations results in error #6

Closed
opnoack opened this issue Jul 16, 2015 · 4 comments
Closed

Sending invitations results in error #6

opnoack opened this issue Jul 16, 2015 · 4 comments

Comments

@opnoack
Copy link

opnoack commented Jul 16, 2015

Hello,

sending an invitation after default installation results in an error in log:

2015-07-16T06:57:32.206Z - error: Could not send invitation for me@you.com in conference joyfully-cool-share Error: Can not get a valid email send
    at /home/user/meetings/node_modules/om-email-invitation/lib/module.js:56:25
    at /home/user/meetings/node_modules/om-email-invitation/lib/module.js:39:14
    at Promise.sendResponse (/home/user/meetings/node_modules/mongoconfig/index.js:26:14)
    at Promise.<anonymous> (/home/user/meetings/node_modules/mongoose/node_modules/mpromise/lib/promise.js:177:8)
    at Promise.emit (events.js:95:17)
    at Promise.emit (/home/user/meetings/node_modules/mongoose/node_modules/mpromise/lib/promise.js:84:38)
    at Promise.fulfill (/home/user/meetings/node_modules/mongoose/node_modules/mpromise/lib/promise.js:97:20)
    at Object.cb (/home/user/meetings/node_modules/mongoose/lib/query.js:1153:30)
    at Object._onImmediate (/home/user/meetings/node_modules/mongoose/node_modules/mquery/lib/utils.js:137:16)
    at processImmediate [as _immediateCallback] (timers.js:345:15)

How can sending emails be configured properly?

Thanks in advance!

@ddolcimascolo
Copy link
Contributor

Hello,

This information is indeed missing from the README.md file, we will add it soon.
To configure the mail feature, you need to create a document in the mongo collection configuration, as below:

{
    "_id" : "mail",
    "mail" : {
        "noreply" : "noreply@yourserver.com"
    },
    "transport" : {
        "type" : "SMTP",
        "config" : {
            "host" : "smtp.yourserver.com",
            "secureConnection" : false,
            "port" : 25
        }
    },
    "feedback" : {
        "rcpt" : [ 
            "hublin@yourserver.com"
        ]
    }
}

Where smtp.yourserver.com must be replaced by an actual SMTP server that you have access to, optionally defining an authentication if required by the SMTP server.
hubl.in is actually using nodemailer to send emails, so you'll find all possible confifuration settings on the project page @ https://github.com/andris9/nodemailer-smtp-transport.

The feedback.rcpt property is used by the feedback form on the home page. Feedback emails will be sent to these recipients.

Regards,

@opnoack
Copy link
Author

opnoack commented Jul 16, 2015

Thank you very much for providing this information. Sending invitations is now working.

Sadly the URLs in the email are forwarding me to hubl.in and not to the host I am running hublin on. Is there a way to dynamically adjust the URL and not make it static? I ask because we want to start some test instances of hublin on randomly generated subdomains.

@ddolcimascolo
Copy link
Contributor

Unfortunately, this is not currently configurable :(
But don't worry, we'll add this to the mongo configuration very soon (you can watch the Jira ticket https://ci.open-paas.org/jira/browse/MEET-265 to know when this is done).

In the meantime, the only thing you can do is sed the file templates/email/invitation/html.jade and replace all occurrences of hubl.in in links to something else.

Regards,

@opnoack
Copy link
Author

opnoack commented Jul 16, 2015

Thank you again for this information. I will use the workaround until it gets fixed.

@opnoack opnoack closed this as completed Jul 16, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants