I have been trying to create my own server using cyberpanel on vultr I already created my email and issue ssl and configured my dns and my reverse dns but when I login to my rainloop my message would be sent but won’t deliver but if I send a mail to my rainloop mail account I get it quickly but can’t reply from my rainloop,I have tried setting up my imap and pop3 in the rainloop admin to connect it with gmail still the same way please what should I do
Have you verified the ports are open? These ports are blocked by default at Vultr. You may request removing the blocks by opening a support ticket.
TCP port 25 (SMTP)
TCP & UDP port 137
TCP & UDP port 138
TCP & UDP port 139
TCP & UDP port 445
TCP port 1688 (KMS, inbound only)
There are three SSL options on CyberPanel, you need to select email SSL for your email to work
Every provider blocks port 25 to control spam. Contact your ISP or if you are hosting your server on Digital Ocean or AWS request them to unblock port 25 ( They never agree, at least for me )
Related
Before anything else, I have read about 30+ StackOverflow answers and none of them seem to address my particular flavour of this problem. Below I list all the answers I have already tried before asking for more advice.
I am trying to access my ec2 instance via socket in PHP from a different machine via fsockopen, pointed at my ec2 public IP (I have an Elastic fixed IP address 54.68.166.28) and designated port.
Behaviour: I can access the instance and the ChatScript application running inside from within the instance, via the public IP directly on the browser. But if I run the exact same webpage with the exact same socket call on an external machine targeting my instance's IP address (double checked it is the correct one) I get a 500 Internal Server Error when connecting on port 1024 (for my custom TCP connection), another 500 on port 443 (HTTPS). On port 80 (HTTP) it hangs 20+ seconds then gives me status 200 success, except it does not connect properly to the application and responds with nothing.
Troubleshooting:
I have set up my security group rules to accept incoming TCP from anywhere:
HTTP (80) TCP 80 0.0.0.0/0
HTTP (80) TCP 80 ::/0
HTTPS (443) TCP 443 0.0.0.0/0
HTTPS (443) TCP 443 ::/0
Custom (1024) TCP 1024 0.0.0.0/0
Custom (1024) TCP 1024 ::/0
Outbound rules span port range 0 - 65535 with destination 0.0.0.0/0, so should work.
I ssh every time without problems into the instance on port 22. SCP also works fine.
Checked $sudo service httpd status: running, which is why my UI displays there fine.
Checked $sudo /sbin/iptables -L and all my policies are set to ACCEPT with no rules
Checked $ netstat --listen -p and the app I am targeting is listening on port 0.0.0.0.0:1024.
Checked Network Utility and ports 80 and 1024 are registered as open. Port 443 is not. Pinging did not work for any of them, with 100% packet loss.
Checked my instance is associated to the security group with all the permissions - it is. IP is clearly correct or I could neither ssh nor serve webpages... which I can.
I stopped and restarted the instance.
I replaced the instance.
I think this is due diligence before asking for help... now I need it!
I realised my configuration was correct: the problem was that the hosted domain I used for the GUI, like most hosted domains, does not open custom ports, so tcp did not work.
I can't connect to my queue on azure account using java code. It seems that the problem is the network. I can to connect with my private network but not with the company network.
I have this message error:
Exception in thread "main" http://com.microsoft.azure .servicebus.primitives.ServiceBusException: Error{condition=amqp:connection:framing-error, description='connection aborted', info=null}.
Any hints?
It seems that the problem is the network. I can to connect with my private network but not with the company network.
Yes, you are right. I also find the simlar issue on the github. It seems that your company firewall restriction which blocks all traffic on ports 5671 and 5672. We could get more information from AMQP 1.0 in Azure Service Bus and Event Hubs protocol guide.
Azure Service Bus requires the use of TLS at all times. It supports connections over TCP port 5671, whereby the TCP connection is first overlaid with TLS before entering the AMQP protocol handshake, and also supports connections over TCP port 5672 whereby the server immediately offers a mandatory upgrade of connection to TLS using the AMQP-prescribed model. The AMQP WebSockets binding creates a tunnel over TCP port 443 that is then equivalent to AMQP 5671 connections.
If possible, you could ask permission to open 2 ports in your company firewall.
I have Cisco 2801 router with public IP and NAT enabled effectively providing Internet access to users behind it.
How to publish Exchange server behind the router using above mentioned Public IP so users can send/receive emails while not in the office using Outlook as well as with OWA and Mobile ActiveSync.
BR,
Oleg
You will need to open ports that are required for Inbound access on the Cisco 2801. Assuming that you want to open port 443 for the OWA on server 10.1.1.1, you will enter something like the following
ip nat inside source static tcp 10.1.1.1 443 interface Fa 0/0 443
Where Fa 0/0 is the Interface connected to the Internet.
Be careful when you open ports; you need to have good understanding of Firewalls and Security design of your Network.
You will add Destination nat on cisco router for users can access to your Exchange server from internet. and you must create Access list for open necessary port for Exchange server like https, smtp, pop3, imap , TCP/587, tcp/993, tcp/995 and by default other things will block with hidden rule on ACL.
Destination NAT
ip nat inside source static
Access list
ip access-list extended OUTSIDE-TO-INSIDE_AL
10 permit tcp any eq 443
.
.
.
.
You can use Zone-Base firewall, if your device and IOS are support it.
I made an application who send many emails for different actions, i tested with Mailtrap.io. Everything is going well with this test service but when i tried to migrate the the real smtp from my domain. Nothing happen.
MAIL_DRIVER=smtp
MAIL_HOST=smtp.mydomain.eu
MAIL_PORT=25
MAIL_USERNAME=null
MAIL_PASSWORD=null
MAIL_ENCRYPTION=null
When i put MAIL_PORT = 25 i have no exception but any mails is send. When i put the port 565 i get
Connection could not be established with host
smtp.mydomain.eu [Connection refused #111]
If i put the username and password from the mail adresse i configured in the plesk it's change nothing.
The serveur use SSH maybe the error comes from this ?
Hope someone could help me .. thanks a lot in advance.
port "565" ? Pls. make sure, that the actual used port in your script is actually the one you would like to connect to!
#25 smtp (TCP)
#110 pop3 (TCP)
#143 imap (TCP)
#465 smtps (TCP)
#993 imaps (TCP)
#995 pop3s (TCP)
AND
#587 mail message submission (TCP)
It is port 587 with ssl encryption,
But you must active port 587 in your plesk domein.
You must check the option "Enable SMTP on port 587 for all IP addresses" Then you can send mail from port 587.
The check option is location in your default mail settings, not your domein settings.
I am using SNMP to access the remote system data. According to the requirement I am encoding the SNMP request data to OAMPDU packet format and sending to remote system. The remote system receives the OAMPDU packet, decodes it and sends the snmp request to snmp agent through UDP socket which is bound to port 161. But I am unable to receive the response from snmp agent. I have created a UDP socket which is bound to 161 port to receive the response.
If I use any other free port number other than 161 for receiving SNMP agent does not send responses to that port.
Can anyone please suggest me how to overcome this problem?
Can we configure the different ports for tx,rx ???
How do we know on which port does snmp sends the response ???
Each UDP packet has a source port and a destination port. An SNMP manager sends out an SNMP request using any source port, and destination port 161. The agent will reply to the source port on the manager. For example:
Manager Agent
source port: <random number>
dest port: 161
content: what is your sysUpTime
source port: 161
destination port: <same random number>
content: sysUpTime is 42 seconds
Replies arrive on random number port, not port 161. So a manager listening on port 161 is unlikely to receive many replies. Instead of listening on port 161, listen on the same socket you used to send out the request. That socket will remember the source port it chose for sending.
P.S. When you use SNMP to query, SNMP's manager is UDP's client, and SNMP's agent is UDP's server.