Ok, getting closer. After I did the reboot and found the above iptables rules, I checked the bastille-firewall config file, and realized that...
After a reboot, I get the following from iptables: The first line is suspicious to me. iptables -L Chain INPUT (policy DROP) target prot...
That's the funny thing: :~$ sudo iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain...
Hi, I followed the Perfect Server guide for Debian Wheezy + Nginx + Dovecot and have almost everything working. I'm a little baffled by ports...
fixed by adding IP address here: inet_interfaces = 66.66.66.66,127.0.0.1 and by commenting these lines: #default_transport = error...
Wondering if the mynetworks parameter needs adjusting? alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases alias_database =...
This is a dedicated box at a hosting center. The hosting support confirmed no firewall outside of the box and ran this: Not shown: 981 closed...
This is weird. What else could be blocking this? Going to check with service provider to see if a hardware firewall is in place somewhere....
I stopped bastille and tried ufw, then stopped that too but still cannot telnet to 587 at all. I can telnet to 22, 110 but not any of the smtp...
I stopped bastille, with no luck, I may need to check if the hostname is properly set in all places though, if any setting got just topaz instead...
FYI, google just sent a delivery status: Technical details of temporary failure: The recipient server did not accept our requests to connect....
My ISP is most certainly blocking port 25 but I'm using port 587 (TLS) and disconnected my phone from my home wifi as I know my cell phone...
I thought that only the -f option need the FQDN. I modified it to have both, did a reboot to ensure it was picked up but still unable to connect...
I followed this wheezy howto to setup my Debian Wheezy server. I made an alteration in also installing apache2 and configuring nginx to reverse...
Separate names with a comma.
