Re: problem with sending emails from second IP'

[Poliman - Serwis]

Thank you for answer. You understand me wrong. I can't believe that I made
a typo there and left comma. I know that comma is a form of whitespace. ;)
But I am curious why set smtp_bind_address=X.X.X.X in master.cf like docs
say didn't work in my case. I added it to main.cf then it works.

2018-04-16 16:28 GMT+02:00 /dev/rob0 :

> On Mon, Apr 16, 2018 at 07:23:34AM +0200, Poliman - Serwis wrote:
> > Yea, that's right. Unbeliveable that there is no comma. :D Now
> > I have smtp_bind_address in main.cf and master.cf. :)
>
> After being here awhile you'll get that Postfix is all about the
> Principle of Least Astonishment.  Names of postconf(5) settings
> suggest what will be accepted there.
>
> In the case of an "*_address" setting, you would expect to see an
> address.  For an "_address6" setting, that would take an ipv6
> address.  Note also that it's in singular form, "address", as opposed
> to plural, "addresses".
>
> Commas, as described in the leading part of the postconf(5) manual,
> the part on general syntax, are a form of whitespace.  Also, commas
> are not part of normal ipv4 nor ipv6 address syntax.
>
> Therefore it should be quite believable that a comma would have no
> place in smtp_bind_address.
> --
>   http://rob0.nodns4.us/
>   Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
>



-- 

*Pozdrawiam / Best Regards*
*Piotr Bracha*

Re: Postfix error (warning: problem talking to server 127.0.0.1:20040: Connection timed out)

[Wietse Venema]

Emanuel:
[ Charset windows-1252 converted... ]
> Hello, i see this error:
> 
> Apr 16 13:13:51 host02 postfix/smtpd[32761]: warning: problem talking to 
> server 127.0.0.1:20040: Connection timed out
> Apr 16 13:13:52 host02 postfix/smtpd[32491]: warning: problem talking to 
> server 127.0.0.1:20040: Connection timed out
> Apr 16 13:13:53 host02 postfix/smtpd[355]: warning: problem talking to 
> server 127.0.0.1:20040: Connection timed out
> Apr 16 13:13:54 host02 postfix/smtpd[32584]: warning: problem talking to 
> server 127.0.0.1:20040: Connection timed out
> Apr 16 13:13:54 host02 postfix/smtpd[366]: warning: problem talking to 
> server 127.0.0.1:20040: Connection timed out
> Apr 16 13:13:55 host02 postfix/smtpd[32495]: warning: problem talking to 
> server 127.0.0.1:20040: Connection timed out
> 
> check_policy_service inet:127.0.0.1:20040
> 
> /etc/postfix/main.cf
> 
> smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:20040
> 
> any ideas?

1) http://www.postfix.org/postconf.5.html#inet_interfaces
An incorrect setting will prevent Postfix from connecting
to some network addresses.

2) Missing firewall rule. Needs no clarification.

Wietse

Postfix error (warning: problem talking to server 127.0.0.1:20040: Connection timed out)

[Emanuel]

Hello, i see this error:

Apr 16 13:13:51 host02 postfix/smtpd[32761]: warning: problem talking to 
server 127.0.0.1:20040: Connection timed out
Apr 16 13:13:52 host02 postfix/smtpd[32491]: warning: problem talking to 
server 127.0.0.1:20040: Connection timed out
Apr 16 13:13:53 host02 postfix/smtpd[355]: warning: problem talking to 
server 127.0.0.1:20040: Connection timed out
Apr 16 13:13:54 host02 postfix/smtpd[32584]: warning: problem talking to 
server 127.0.0.1:20040: Connection timed out
Apr 16 13:13:54 host02 postfix/smtpd[366]: warning: problem talking to 
server 127.0.0.1:20040: Connection timed out
Apr 16 13:13:55 host02 postfix/smtpd[32495]: warning: problem talking to 
server 127.0.0.1:20040: Connection timed out


check_policy_service inet:127.0.0.1:20040

/etc/postfix/main.cf

smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:20040

any ideas?

--

Re: problem with sending emails from second IP'

[/dev/rob0]

On Mon, Apr 16, 2018 at 07:23:34AM +0200, Poliman - Serwis wrote:
> Yea, that's right. Unbeliveable that there is no comma. :D Now
> I have smtp_bind_address in main.cf and master.cf. :)

After being here awhile you'll get that Postfix is all about the 
Principle of Least Astonishment.  Names of postconf(5) settings 
suggest what will be accepted there.

In the case of an "*_address" setting, you would expect to see an 
address.  For an "_address6" setting, that would take an ipv6 
address.  Note also that it's in singular form, "address", as opposed 
to plural, "addresses".

Commas, as described in the leading part of the postconf(5) manual, 
the part on general syntax, are a form of whitespace.  Also, commas 
are not part of normal ipv4 nor ipv6 address syntax.

Therefore it should be quite believable that a comma would have no 
place in smtp_bind_address.
-- 
  http://rob0.nodns4.us/
  Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:

How to bypass all rules

[Teeles]

Hello

I would like to bypass all rules in postfix config for some recipients. I
almost did id, but i have problem with header and body checks. I don't know
why, but don't work receive_override_options=no_header_body_checks in
additional instance of smtpd. Main cleanup process always block my email.
Only when I disable header and body checks in main.cf, the message is not
blocked.

Part of the main.cf

content_filter = smtp-amavis:[127.0.0.1]:10024

smtpd_client_restrictions = 
check_recipient_access pcre:/etc/postfix/recipient_checks.pcre,
...
permit

smtpd_helo_restrictions =
check_recipient_access pcre:/etc/postfix/recipient_checks.pcre,
...
permit

smtpd_sender_restrictions =
check_recipient_access pcre:/etc/postfix/recipient_checks.pcre,
...
permit

smtpd_recipient_restrictions =
check_recipient_access pcre:/etc/postfix/recipient_checks.pcre,
...
permit

smtpd_data_restrictions = 
check_recipient_access pcre:/etc/postfix/recipient_checks_2.pcre,
...
permit

header_checks = pcre:/etc/postfix/header_checks.pcre
body_checks = pcre:/etc/postfix/body_checks.pcre

/etc/postfix/recipient_checks.pcre
/addr...@domain.com/permit

/etc/postfix/recipient_checks_2.pcre (bypass amavisd)
/addr...@domain.com/FILTER smtp:[127.0.0.1]:10026

Thanks for help



--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html