On Tue, Jan 29, 2013 at 12:22:35PM +0100, M. Fioretti wrote:
> of course, any comment on this is still welcome, as well as on any
> weakness in my server postconf -n output.
The original issue was to be able to relay from a dynamic residential
IP address on your server. Your solution, adding the
there are times when a refreshing, if a bit embarrassing "shock" from
others is the only way out of a problem.
I can't remember how many times I DID check that string I had typed to be
sure there were no typos before posting for help, but of course, it was
159, not 59, sorry.
Thanks!
of course, a
On 01/29/2013 12:14 PM, M. Fioretti wrote:
I have no idea if it is relevant and what it may mean, but I have found
out just now that:
1) the control panel of my modem says my public IP address is 2.39.122.159
2) which is the same address that postfix in the server sees, cfr the log
above
3) but
On Tue, January 29, 2013 11:43 am, M. Fioretti wrote:
> Greetings,
>
> my home computer (CLIENT) has postfix configured to relay all outgoing
> email to my actual email SERVER, that is running on a VPS. The current
> outputs of postconf -n for both boxes are below.
>
> For reasons not really relev
On 29/01/2013 10:43, M. Fioretti wrote:
which looks like postfix on the SERVER was not aware that now 2.39.122.159
IS in mynetworks. Why?
mynetworks = 127.0.0.0/8, 212.48.186.219, 2.39.122.59
2.39.122.159 <--- does not match --^
Mark
--
http://mark.goodge.co.uk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/29/2013 11:43 AM, M. Fioretti wrote:
>
> which looks like postfix on the SERVER was not aware that now
> 2.39.122.159 IS in mynetworks. Why? Any help to figure out what is
> happening is
> myn
Greetings,
my home computer (CLIENT) has postfix configured to relay all outgoing
email to my actual email SERVER, that is running on a VPS. The current
outputs of postconf -n for both boxes are below.
For reasons not really relevant here, a while ago I had configured the
SERVER to only relay for
