On 04/09/2015 02:34 PM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 23:03 schrieb Mike Wright:
On 04/09/2015 01:38 PM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 22:06 schrieb Andy Blanchard:
Yep. Get it on the same network as the server and run the command:
telnet 192.168.10.1 25
Now
Am 09.04.2015 um 23:03 schrieb Mike Wright:
On 04/09/2015 01:38 PM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 22:06 schrieb Andy Blanchard:
Yep. Get it on the same network as the server and run the command:
telnet 192.168.10.1 25
Now guess what - it says
telnet: Unable to connect to re
On 04/09/2015 01:38 PM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 22:06 schrieb Andy Blanchard:
Yep. Get it on the same network as the server and run the command:
telnet 192.168.10.1 25
Now guess what - it says
telnet: Unable to connect to remote host: No route to host
That's not good.
Am 09.04.2015 um 22:05 schrieb Mike Wright:
On 04/09/2015 01:01 PM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 21:53 schrieb Mike Wright:
On 04/09/2015 12:46 PM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 21:30 schrieb Mike Wright:
You can try running tcpdump to watch incoming con
Am 09.04.2015 um 22:06 schrieb Andy Blanchard:
Yep. Get it on the same network as the server and run the command:
telnet 192.168.10.1 25
Now guess what - it says
telnet: Unable to connect to remote host: No route to host
Of course I can ping from my laptop to my server and vice versa ...
Dis
On 09.04.2015, Peter Ulrich Kruppa wrote:
> I have some old laptop running debian. Can I do something with it - without
> setting up another mail server on it? :-)
Yes. Take it with you to a friend and run a tcptraceroute to your mailserver.
It will tell you exactly where it stops.
--
users m
On 04/09/2015 01:01 PM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 21:53 schrieb Mike Wright:
On 04/09/2015 12:46 PM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 21:30 schrieb Mike Wright:
You can try running tcpdump to watch incoming connections while you
send
yourself an email from
Yep. Get it on the same network as the server and run the command:
telnet 192.168.10.1 25
You *should* get a welcome banner from Postfix. If you do, type
"QUIT" to exit cleanly - this means the problem is almost certainly
with the router.
If you don't, and based on your previous reply to Mike W
Am 09.04.2015 um 21:53 schrieb Mike Wright:
On 04/09/2015 12:46 PM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 21:30 schrieb Mike Wright:
You can try running tcpdump to watch incoming connections while you send
yourself an email from gmail/yahoo etc. That will let you know if mail
is ar
Am 09.04.2015 um 20:52 schrieb Andy Blanchard:
Hi Peter,
0.0.0.0 is a "wildcard"; Postfix is definitely running and listening
for incoming connections on port 25 on any IP address on your server.
Do you have access to another PC or something on your internal network
that you can try connectin
On 04/09/2015 12:46 PM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 21:30 schrieb Mike Wright:
You can try running tcpdump to watch incoming connections while you send
yourself an email from gmail/yahoo etc. That will let you know if mail
is arriving and getting through your firewall.
tcpd
Am 09.04.2015 um 21:30 schrieb Mike Wright:
On 04/09/2015 11:36 AM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 18:18 schrieb Heinz Diehl:
On 09.04.2015, Peter Ulrich Kruppa wrote:
To me this looks as if port forwarding is all-right but Postfix does
not
react (?!?)
Take a look into the p
On 04/09/2015 11:36 AM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 18:18 schrieb Heinz Diehl:
On 09.04.2015, Peter Ulrich Kruppa wrote:
To me this looks as if port forwarding is all-right but Postfix does not
react (?!?)
Take a look into the postfix log.
I can see postfix/master has been
Hi Peter,
0.0.0.0 is a "wildcard"; Postfix is definitely running and listening
for incoming connections on port 25 on any IP address on your server.
Do you have access to another PC or something on your internal network
that you can try connecting from? At least that way you could
determine whet
Am 09.04.2015 um 18:18 schrieb Heinz Diehl:
On 09.04.2015, Peter Ulrich Kruppa wrote:
To me this looks as if port forwarding is all-right but Postfix does not
react (?!?)
Take a look into the postfix log.
I can see postfix/master has been started and I can see activities when I
write myself
Am 09.04.2015 um 19:05 schrieb Rick Stevens:
On 04/09/2015 07:22 AM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 15:32 schrieb Robert Nichols:
On 04/09/2015 05:07 AM, Peter Ulrich Kruppa wrote:
I set up a Postfix-Server on my Fedora 21 box, which is connected to
the internet via
some Netgear
On 04/09/2015 07:22 AM, Peter Ulrich Kruppa wrote:
Am 09.04.2015 um 15:32 schrieb Robert Nichols:
On 04/09/2015 05:07 AM, Peter Ulrich Kruppa wrote:
I set up a Postfix-Server on my Fedora 21 box, which is connected to
the internet via
some Netgear Router. My private LAN is 192.168.10.0/24 with
On 09.04.2015, Peter Ulrich Kruppa wrote:
> To me this looks as if port forwarding is all-right but Postfix does not
> react (?!?)
Take a look into the postfix log.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.or
Am 09.04.2015 um 15:32 schrieb Robert Nichols:
On 04/09/2015 05:07 AM, Peter Ulrich Kruppa wrote:
I set up a Postfix-Server on my Fedora 21 box, which is connected to
the internet via
some Netgear Router. My private LAN is 192.168.10.0/24 with the Fedora
box fixed on
192.168.10.1 . My Netgear t
Hi Peter,
At least there's some progress. I think the advice to check the
Postfix config should be your next step - as mentioned earlier by
Robert Nichols, Look for "inet_interfaces =" in /etc/postfix/main.cf.
FirewallD and iptables are mutually exclusive in Fedora, with the
default being Firewa
Am 09.04.2015 um 15:09 schrieb Frank Elsner:
On Thu, 09 Apr 2015 13:58:48 +0200 Peter Ulrich Kruppa wrote:
Hello!
Am 09.04.2015 um 13:20 schrieb Bala Vishwanathan Iyer:
Dear Mr. Kruppa
I have some futher querries :-
1. Is this server your mail server for your domain. meaning does the
mail ex
Hi,
Am 09.04.2015 um 14:22 schrieb Andy Blanchard:
SMTP from external IP addresses (e.g. anything other than 127.0.0.1)
is blocked by default by the Fedora firewall and I've not seen any
mention of checking that in the thread. I'm assuming you are using
the default firewall, FirewallD, rather t
On 04/09/2015 05:07 AM, Peter Ulrich Kruppa wrote:
I set up a Postfix-Server on my Fedora 21 box, which is connected to
the internet via
some Netgear Router. My private LAN is 192.168.10.0/24 with the Fedora
box fixed on
192.168.10.1 . My Netgear thing has got a fixed IP and hostname, let's say
On Thu, 09 Apr 2015 13:58:48 +0200 Peter Ulrich Kruppa wrote:
> Hello!
>
> Am 09.04.2015 um 13:20 schrieb Bala Vishwanathan Iyer:
> > Dear Mr. Kruppa
> >
> > I have some futher querries :-
> >
> > 1. Is this server your mail server for your domain. meaning does the
> > mail exchange record for you
SMTP from external IP addresses (e.g. anything other than 127.0.0.1)
is blocked by default by the Fedora firewall and I've not seen any
mention of checking that in the thread. I'm assuming you are using
the default firewall, FirewallD, rather than iptables?
If so:
"sudo firewall-cmd --get-servic
Dear Mr. Kruppa
you need create nat rule in your Netgear Router where in you specify
that your external ip address in your case 217.92.171.227 map to your
fedora box which is let us say 192.168.10.4 or 192.168.10.5. Since
SMTP would look for an actual server than just any machine whcih has
port 25
Hello!
Am 09.04.2015 um 13:20 schrieb Bala Vishwanathan Iyer:
Dear Mr. Kruppa
I have some futher querries :-
1. Is this server your mail server for your domain. meaning does the
mail exchange record for your domain point to this server or some
other server.
In case it it pointing to some othe
Am 09.04.2015 um 13:20 schrieb Frank Elsner:
On Thu, 9 Apr 2015 12:47:15 +0200 Peter Ulrich Kruppa wrote:
[ ... ]
Yes: when I use telnet on port 25 from my Fedora I get
# telnet localhost 25
Trying ::1...
telnet: connect to address ::1: Connection refused
On Thu, 9 Apr 2015 12:47:15 +0200 Peter Ulrich Kruppa wrote:
[ ... ]
> Yes: when I use telnet on port 25 from my Fedora I get
> # telnet localhost 25
> Trying ::1...
> telnet: connect to address ::1: Connection refused
> Trying 127.0.0.1...
> Conne
Dear Mr. Kruppa
I have some futher querries :-
1. Is this server your mail server for your domain. meaning does the
mail exchange record for your domain point to this server or some
other server.
In case it it pointing to some other server say Google mail server or
any other hosting provider. Th
Hi Heinz,
sorry - I still couldn't find the button for Inline-Answers in this
googlemail mess yet!
> but I can't receive mails from outside.
Do you have any DNS-record for your machine, is it reachable from the outside
world? If yes, you'll most likely have to forward the mail-port (usually 25)
Hi Frank,
sorry - I couldn't find the button for Inline-Answers in this
googlemail mess yet!
On Thu, 9 Apr 2015 12:07:53 +0200 Peter Ulrich Kruppa wrote:
> Hi everyone,
>
> please do excuse my unspecific subject - I don't really know what my
> problem is yet.
>
> I set up a Postfix-Server on my
On 09.04.2015, Peter Ulrich Kruppa wrote:
> but I can't receive mails from outside.
Do you have any DNS-record for your machine, is it reachable from the outside
world? If yes, you'll most likely have to forward the mail-port (usually 25) to
the internal IP your mailserver is listening on, as al
On Thu, 9 Apr 2015 12:07:53 +0200 Peter Ulrich Kruppa wrote:
> Hi everyone,
>
> please do excuse my unspecific subject - I don't really know what my
> problem is yet.
>
> I set up a Postfix-Server on my Fedora 21 box, which is connected to
> the internet via
> some Netgear Router. My private LAN
Hi everyone,
please do excuse my unspecific subject - I don't really know what my
problem is yet.
I set up a Postfix-Server on my Fedora 21 box, which is connected to
the internet via
some Netgear Router. My private LAN is 192.168.10.0/24 with the Fedora
box fixed on
192.168.10.1 . My Netgear thi
35 matches
Mail list logo
