Dear stackoverflowsians,
our Hubot has a XMPP adapter and sits in a XMPP chatroom.
Is it possible to fetch a list of all the other users in the chatroom to let hubot mention them?
For example:
me: hubot ping everyone
hubot: johndoe , joe , bob , alice ping
if the users johndoe,joe,bob and alice are in the chat.
Related
I have added the internal hubot to the live chat agent, but it doesn't response any message.
I have tested the internal hubot in other channels, it works well.
Has anyone encountered the same issue?
I am currently maintaining web applications available from a secure network. My users connect to the network within a VPN connection using L2TP/IPSec, to which they authenticate using their user id and password. When they access the web application, they also have to authenticate again with the same user id and password.
Since they have authenticated once to the VPN already, is it possible for the application to verify their authentication status and get their identity from the VPN?
Thank you!
It really depends on your VPN server and the capabilities of your web app. If your web app can access the VPN servers logs, current connections or API than yeah you might be able to set something up.
George
I am an email server noob. I own a domain 'mydomain.org' and I'd like to forward emails sent to that domain to other email address, perhaps at 'gmail.com' or 'university.edu'. I thought I set this up right, but my email log is giving me errors like this:
connect to mx1.university.edu[171.67.219.71]:25: Connection timed out
and
Dec 22 05:17:24 mail-server postfix/smtp[6370]: connect to alt1.gmail-smtp-in.l.google.com[2607:f8b0:400d:c00::1a]:25: Network is unreachable
I don't know too much about this, but I imagine there must be some kind of authentication that I need to set up, but I'm shy of the laundry list blog posts. Does this look like "authentication stuff"? If so, what do I need to set up next? If not, any idea why the receiving mail servers drop my server?
Yes, network issue. For future folks, Google does not allow outgoing connections for SMTP servers, maybe to prevent spam? Here's info about how to set that up: https://cloud.google.com/compute/docs/sending-mail
I have configured AWS SNS notification to call my HTTP endpoint. I need to open my firewall to allow AWS SNS to call it.
However, I cannot find any information about SNS HTTP(s) notification call IPs. I have caught a few IPs (54.240.194.1,54.240.194.65,54.240.194.129 ) by it's calls. But I'm not sure what's the full list of SNS HTTP notification source IPs.
I can open my firewall as 54.240.194.0/24. But no official information this is correct.
Thanks.
The list of IP addresses from which Amazon SNS notifications are sourced is provided in the Amazon SNS forums. We update this post as the IP information changes.
Please note that while notifications will usually be sourced from an IP in the same region where your topic was created, this is not guaranteed e.g., a notification sent from a topic created in US-EAST-1 may be sourced from either US-WEST-1 or EU-WEST-1. In other words, you should add all addresses on this list to your ingress rules, even if you only plan to use a single region.
In this situation SQS is probably more appropriate because you will be initiating the connection to Amazon instead of asking AWS to reach out to you. This means no changes to your firewall are required and you are not poking holes in your security...
If you need SNS notifications for other end points, you can pump SNS to SQS for this specific end point:
http://docs.aws.amazon.com/sns/latest/dg/SendMessageToSQS.html
Pretty sure you can't count on any particular IP address or range.
If you want to secure your endpoint, or at least ensure that any messages sent to it actually originate from AWS, this document may help:
...you can verify the authenticity of a notification,
subscription confirmation, or unsubscribe confirmation message sent by
Amazon SNS. Using information contained in the Amazon SNS message,
your endpoint can recreate the string to sign and the signature so
that you can verify the contents of the message by matching the
signature you recreated from the message contents with the signature
that Amazon SNS sent with the message.
http://docs.aws.amazon.com/sns/latest/dg/SendMessageToHttp.verify.signature.html
The accepted answer above is out of date/expired in the Amazon forum.
This link may be more help and, hopefully, permanent, but is for ALL IP ranges, evidently.
From
https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html....
AWS IP address ranges
Here's the tool to use to filter/search that massive file
https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html#filter-json-file
I have configured postfix over SSL and dovecot over SSL and it work fine if I send local relay , and it delivers to mailboxes within my domain name MX record point mail server.
mysysopmnds.com MX 10 mail.mysysopminds.com
However if I send an email to another domain , it bounces... and one of the error in the log is , as below
Jan 10 19:34:56 mail postfix/smtp[5334]: 37FADC28BB: to=, relay=none, delay=34, delays=34/0/0.01/0, dsn=5.4.6, status=bounced (mail for murugeshdomain.com loops back to myself)
what are key configuration that I should check or take care of to send email to other domains or any domains
TIA
hariharan
The is a good chance your internet serivice provider (ISP) is blocking out port 25 for outgoing email. I can tell you, mine is. This is also when i got the bounce message.
You can confirm this problem by typing:
telnet aspmx.l.google.com 25
If it does not generate Connected to aspmx.l.google.com but a timeout after half a minute or so than your ISP is blocking your outgoing traffic on port 25.
If this is the case you can solve it by redirecting your outgoing mail through for example a google mail account. You could use this link as guide to set the up the redirection.
It looks like this domain (murugeshdomain.com) has no MX record. For sending mails to another domain just take look in that domain has MX record. To check whether that domain has MX record dig MX domainname(in the case of linux command)