sending email to smtp server in docker - email

I have just installed a docker image of inbucket (http://www.inbucket.org/). It is working ok and I can see in the docker command prompt that smtp is listening on TCP4 0.0.0.0.10025 and pop3 listening on TCP4 0.0.0.0.10110.
I can also access the web interface for the application on localhost:9000 so everything seems to be working ok.
I haven't used docker before so I'm unsure what email address I need to send it to so the docker smtp server will pick it up. I have tried addressed such as anyone#inbucket.com, anyone#inbucket.local, anyone#inbucket.org but I keep getting invalid address returned messages.
How should docker mailboxes work?

Related

How to specify port number when sending mail with postfix?

I've uncommented the 'submission' line in master.cf and I can 'telnet example.com 587' on my mail server with no problem but how do I send mail from the command line of the client to the postfix server over port 587?
My server is hosted as a digitalocean droplet (centos instance) on the internet and my client is my home laptop.
Each time I try to deliver a message with the 'mail user#example.com' command I instantly receive a rejection message because my isp blocks port 25.
Any help greatly appreciated :)
mail command will drop the mail to the SMTP server running on your home laptop and the SMTP server running on your home laptop is not configured i guess. So it is trying to deliver the mail by doing an MX lookup (i.e to port 25 of your MX server). If you want to do any smtp tests please try using swaks tool.
# For eg. to authenticate and send mail from your mail server, you will have to use
swaks -f you#example.com -t someone#yahoo.com -s example.com -p 587 --auth-user you#example.com --auth-pass somepass
# -f from
# -t to
# -s server
# -p port
# --auth-user username
# --auth-pass password
More info here Hope that helps.

Cannot get irssi to work on Bluehost dedicated IP address

I am trying to get irssi to work over SSH on my Bluehost dedicated IP server.
Bluehost support says port 6667 is open, but you have to have an app listening to it, so running nc -l on the server and then telnet'ing in works, but if I run irssi on the server then it can't connect to freenode.net - it says the connection timed out.
If you do nmap -v -sT then you see the 6667/TCP port, but it's listed as closed.
How can get irssi to run using an ssh shell on Bluehost?
It Would be great to have under a Screen session you could re-login to from anywhere.
Make sure that you ask them if 6667 is open outbound TCP and UDP.
Sometimes they can mistake it for inbound or only open TCP for example. You can telnet to your IRC host on port 6667 even if something is not listening on the Bluehost side, assuming IRC is up and accepting connections, and Bluehost has the port opened, a telnet from your Bluehost account to the IRC server will work fine.

Port 25 / 26 says "Could not open connection" using Telnet

I am currently troubleshooting an email problem with my server (IIS 7,5 , Windows server 2008 R2). When I run the "Telnet" command, I get the "Connecting to 127.0.0.1... Could not open the connection to the host, on port 25".
I've been running the commands:
"telnet 127.0.0.1 25"
"telnet 127.0.0.1 26"
"telnet localhost 25"
"telnet localhost 26"
All of these return the same message. If I run at port 80, I get a response.
I tried to turn off my firewall, which made no changes to the behavior (still could not open...).
Is this the usual behavior? Should sending emails still work, or are there something wrong?
Port 25 is for an MTA (message transfer agent) which passes email along as it goes from sender to recipient. If you don't have one installed and running locally then there is nothing listening on that local port. That sounds like the case.
Sending email is an outgoing connection (using some random local port) that can be done by connecting to an MTA on any machine accessible via the network; it doesn't have to use one on the local machine.

Problem with configuring Thunderbird with hMailServer

I installed hMailServer and did the following
1. Created a test.com domain
2. Added an user testuser
Now the hMailServer is running in my localhost.
When I install Mozilla thunder bird and try to configure it by entering the username and password, it fails giving
Thunderbird failed to find the settings for your email account.
How can I tell thunderbird about the hMailServer running in my local host? Where is thunderbird looking for the domain when I entered testuser#test.com?
I saw some messages like "Looking up in Mozilla ISP database". But the mail server is in my local machine.
Am I missing any configuration details?
UPDATE
I posted a video tutorial on YouTube on how to configure hMail and Thunderbird: https://www.youtube.com/watch?v=FMPfcVd6OOk
I found it pay attention to the IPv4 address -that is very important :
http://www.mjvanderwielen.com/?p=1632
Make sure:
Incoming is: ”IMAP”
Server hostname: local ip address server computer
Port: 143
SSL: None
Authentication: Normal password
Username: complete account name!!
Outgoing: ”SMTP”
Server hostname: as per your host
Port: as per your host
SSL: as per your host
Authentication: as per your host

EC2 Internal Sockets

I'm trying to have two process communicate through a socket connection. One of these is a python app, and the other is a php script.
I've created and tested the client/server combination on my home computer and it functions properly. However, when I deploy onto an EC2 instance (ubuntu 10.10 64bit ami + apache + php) I get an unable to connect to socket error (111 Connection Refused) from the php script. The python app is able to bind to the socket and listen to messages but the php script is unable to send messages.
I've opened the required ports in the amazon security group and I can connect to the port externally using telnet. However if I attempt to connect with telnet from within the server I get the same connection refused error.
How can I solve this issue?
Edit: Both processes are on the same instance
The issue had nothing to do with EC2 explicitly. I was not binding to localhost, but instead binding to my hostname. On a local network that was the same as my localhost ip, however on ec2 it was not. Switching to binding to localhost fixed the issue.