Re: relay server - allow connections from DSL with dynamic IP

2016-05-29 Thread Rohit Shriwas
Ahh, crap. I just read your other thread about wanting to have an external relay on AWS heh 😂 You'll want to remove relayhost and everything smtp_ from the last email to achieve that on your AWS instance. Cheers! On Monday 30 May 2016 09:58 AM, Rohit Shriwas wrote: > Hey Zalezny, > > I have a sim

Re: relay server - allow connections from DSL with dynamic IP

2016-05-29 Thread Rohit Shriwas
Hey Zalezny, I have a similar setup where my local machine has a dynamic IP and needs to relay mail through an external SMTP server (smtp.zoho.com) to deliver anything outside. I have the following (relevant) configuration for this on my local Postfix instance: # /etc/postfix/main.cf inet_int

Re: Need clarification of lookup table result values

2016-05-29 Thread Peter
On 30/05/16 03:29, Michael Fox wrote: > Ah. O.K. My original post said that I'm trying to configure > postscreen_access.cidr, This is the name of a table, which has absolutely no bearing on what setting it is used for. You could point alias_maps to postscreen_access.cidr and then the expected re

RE: Need clarification of lookup table result values

2016-05-29 Thread Michael Fox
> The access(5) manpage is for the Postfix SMTP DAEMON. It says so > on the first line of the manpage, and it says so again in the first > paragraph. > > The postscreen_access_list parameter, as the name suggests, is for > the POSTSCREEN DAEMON. This name is as explicit as it can be, without > chan

relay server - allow connections from DSL with dynamic IP

2016-05-29 Thread Zalezny Niezalezny
hi, my local MTA using DSL with dynamic IP address so I need to forward my messages to some external relay server with static IP. Unfortunately I`m not able to setup, my dynamic IP on the relay server in the network_table (or in the mynetworks). Base on the (ONLY) username and password (SASL) I w

Re: resolve local domain with MX records

2016-05-29 Thread Zalezny Niezalezny
Perfect! Thank You very much! On Sun, May 29, 2016 at 9:15 AM, Wietse Venema wrote: > Zalezny Niezalezny: > > Hallo Wietse, > > > > yes I understand Your point. > > > > In my internal host, dns lookup is disabled. I simply would like to know > > how may I specified some additional hosts in case

Re: Need clarification of lookup table result values

2016-05-29 Thread Wietse Venema
Michael Fox: > > > What is a valid result depends on what the result is used for: an > > access table expects results as described in the access(5) manpage, > > a virtual aliases table expects the results as described in the > > virtual(5) manpage, a transport table expects results as described

Re: resolve local domain with MX records

2016-05-29 Thread Wietse Venema
Zalezny Niezalezny: > Hallo Wietse, > > yes I understand Your point. > > In my internal host, dns lookup is disabled. I simply would like to know > how may I specified some additional hosts in case of accidents one of them. IF you can't rely on DNS, list all gateway IP addresses in /etc/hosts.

RE: Need clarification of lookup table result values

2016-05-29 Thread Christian Kivalo
On 2016-05-29 06:34, Michael Fox wrote: What is a valid result depends on what the result is used for: an access table expects results as described in the access(5) manpage, a virtual aliases table expects the results as described in the virtual(5) manpage, a transport table expects results as d

Re: resolve local domain with MX records

2016-05-29 Thread Zalezny Niezalezny
I`m sorry, I sent my last email too fast. example.com:[192.168.2.10, 192.168.2.11] Will it be possible something like this ? Thanks in advance for Your support. Zalezny On Sun, May 29, 2016 at 10:44 AM, Zalezny Niezalezny < zalezny.niezale...@gmail.com> wrote: > Hallo Wietse, > > yes I u

Re: resolve local domain with MX records

2016-05-29 Thread Zalezny Niezalezny
Hallo Wietse, yes I understand Your point. In my internal host, dns lookup is disabled. I simply would like to know how may I specified some additional hosts in case of accidents one of them. For example, in the transport table we have something like this: *example.com