Re: Cannot assign requested address -- with "inet_protocol = ipv4" in main.cf

Wietse & Pau, Thank you for pointing out my configuration error. This was a struggle for me and I appreciate your patience. I corrected the configuration error and retested two configurations for the VM: (1) relay addresses as aliases (2) relay addresses as secondaries In both configuratio

Re: Cannot assign requested address -- with "inet_protocol = ipv4" in main.cf

>>> I had to change ip addresses in the middle of this issue -- as I mentioned above. <<< Here is data from the current VM configuration. ip addr = 3: ens4: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff inet 108.xxx.xxx.

Re: Cannot assign requested address -- with "inet_protocol = ipv4" in main.cf

Good Morning Wietse, The error message is the same in this configuration with ens4 NM_CONTROLLED="no" using Alias ip addresses: rhel8 r193/smtp[4988]: warning: smtp_connect_addr: bind 75.xxx.xxx.193: Cannot assign requested address Email is being relayed properly. I can configured the VM with e

Re: Cannot assign requested address -- with "inet_protocol = ipv4" in main.cf

> inet 74.xxx.xxx.192/29 brd 74.xxx.xxx.199 scope global noprefixroute > inet 74.xxx.xxx.193/29 brd 74.xxx.xxx.199 scope global secondary > inet 74.xxx.xxx.194/29 brd 74.xxx.xxx.199 scope global secondary > inet 74.xxx.xxx.195/29 brd 74.xxx.xxx.199 scope global secondary > inet

Re: Typo in postconf.proto: AAAAA

On Fri, Jun 26, 2020 at 06:26:06PM +0200, Christian Franke wrote: > See attached patch. Typo is also in RELEASE_NOTES-3.0, but I guess this > file should not be changed. And the first thought that came to mind wasn't that Postfix is the first MTA to support next-generation 160-bit IP addresses?

Re: OSX 10.15.5 #error "Unsupported Berkeley DB version"

On Fri, Jun 26, 2020 at 01:39:19PM +0100, Robert Chalmers (Author) wrote: > Trying to build 3.5.3 on OSX 10.15.5 and running into this problem again. > > dict_db.c:768:2: error: "Unsupported Berkeley DB version" > #error "Unsupported Berkeley DB version” On my laptop I have "homebrew", and the Be

Re: Relaying for internal servers

I think you're right, i will redirect using smtpd_recipient_restrictions, thanks guys :) On Fri, Jun 26, 2020 at 7:41 PM Noel Jones wrote: > On 6/26/2020 10:13 AM, Martin Terp Jensen wrote: > > Hi guys. > > > > I have some postfix servers running as a relay/gateway for internal > > mails, when t

Re: Relaying for internal servers

On 6/26/2020 10:13 AM, Martin Terp Jensen wrote: Hi guys. I have some postfix servers running as a relay/gateway for internal mails, when they want to go to the world wide web. These internal servers i trust, but sometimes mails from CRON gets send to me, i know, the best solution would be t

Typo in postconf.proto: AAAAA

See attached patch. Typo is also in RELEASE_NOTES-3.0, but I guess this file should not be changed. Regards, Christian diff -ru postfix-3.5.3.orig/proto/postconf.proto postfix-3.5.3/proto/postconf.proto --- postfix-3.5.3.orig/proto/postconf.proto 2020-05-09 17:51:27.0 +0200 +++ po

Re: Relaying for internal servers

On 26 Jun 2020, at 09:13, Martin Terp Jensen wrote: > These internal servers i trust, but sometimes mails from CRON gets send to > me, i know, the best solution would be to disable cron mails Uh… since cron send mails when action result in errors this seems like a bad idea. > So, for now i wan

Relaying for internal servers

Hi guys. I have some postfix servers running as a relay/gateway for internal mails, when they want to go to the world wide web. These internal servers i trust, but sometimes mails from CRON gets send to me, i know, the best solution would be to disable cron mails but that is more for the long ter

Re: Cannot assign requested address -- with "inet_protocol = ipv4" in main.cf

As was repeatedly pointed out to you, 74 is not the same as 75. On 2020-06-26 16:56, Greg Sims wrote: ip addr = 3: ens4: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff inet 108.xxx.xxx.45/29 brd 108.xxx.xxx.47 scope gl

Re: Cannot assign requested address -- with "inet_protocol = ipv4" in main.cf

Greg Sims: > Good Morning Wietse, > > The error message is the same in this configuration with ens4 > NM_CONTROLLED="no" using Alias ip addresses: > > rhel8 r193/smtp[4988]: warning: smtp_connect_addr: bind 75.xxx.xxx.193: > Cannot assign requested address You claim that you configured the follo

Re: OSX 10.15.5 #error "Unsupported Berkeley DB version"

Robert Chalmers (Author): > Trying to build 3.5.3 on OSX 10.15.5 and running into this problem again. > > dict_db.c:768:2: error: "Unsupported Berkeley DB version" > #error "Unsupported Berkeley DB version? What has changed since the last successful build? All Postfix 3.x releases support the sa

Re: Cannot assign requested address -- with "inet_protocol = ipv4" in main.cf

Greg Sims: > inet 74.xxx.xxx.192/29 brd 74.xxx.xxx.199 scope global noprefixroute > ens4:1 Helpfully, you did not provide the error message with the CURRENT configuration. Wietse

OSX 10.15.5 #error "Unsupported Berkeley DB version"

Trying to build 3.5.3 on OSX 10.15.5 and running into this problem again. dict_db.c:768:2: error: "Unsupported Berkeley DB version" #error "Unsupported Berkeley DB version” Build script. make -f Makefile.init dynamicmaps=yes CCARGS='-I/usr/local/Cellar/berkeley-db/18.1.32_1/include -DHAS_MYSQL

Re: Cannot assign requested address -- with "inet_protocol = ipv4" in main.cf

On 25.06.20 18:36, Greg Sims wrote: I am sorry Wietse. I needed to change my ip addresses as I exposed the previous set above. The following uses the new ip address set. The transports are now named r192, r193, ... r199 in the same pattern you see above. ens4 is the local public network inte