Hi.
It could be tcp table or mysql table or similar:
*main.cf*
transport_maps=mysql:/etc/postfix/select_ipaddress.cf
*/etc/postfix/select_ipaddress.cf*
hosts = 127.0.0.1
dbname = information_schema
user = postfix
password = changeme
query = select concat('mail', LPAD(ROUND((RAND()*(16-1))+1),
Thank you.
2. "source@emal"
Can source email (mail from) lookup be disabled when using
transport_maps? Any ideas? As I understand transport_maps should rely on
destination address when sender depended transport maps are not used.
15.05.2018 20:48, Viktor Dukhovni пишет:
2. "source@emal"
Hello.
I have 'transport_maps = mysql:/etc/postfix/transport.cf' in
configuration and want to understand the reason of every db lookup as I
have some actions in mysql server based on queries count. Please explain
them.
When sending single email these lookups are made:
1. "*"
2.
Wietse Venema пишет:
Bokhan Artem:
Wietse Venema ?:
Artem Bokhan:
Hi, can someone give me a hint how to randomly spread outgoing smtp
traffic over pool of ip-addresses?
Use network address translation, to map the source IP
address+port across a range of IP addresses.
Bokhan Artem:
I
KLaM Postmaster пишет:
Artem Bokhan:
Hi, can someone give me a hint how to randomly spread outgoing smtp
traffic over pool of ip-addresses
==
Why do you want to do this?
What problem are you trying to solve?
JLA
The main reason that some systems have too high limits, so legitimate mail
In the next example postfix does not pass HELO from XCLIENT line to the milter if
EHLO spike.porcupine.org is ommited.
It looks like bug.
220 server.example.com ESMTP Postfix
EHLO client.example.com
250-server.example.com
250-PIPELINING
250-SIZE 1024
250-VRFY
250-ETRN
250-XCLIENT NAME ADDR
So how postfix interprets NAME and REVERSE_NAME?
I want to understand, how not to break, for example, reject_unknown_client_hostname and
reject_unknown_reverse_client_hostname behavior, when passing names via XCLIENT but not
via postfix resolver.
Wietse Venema пишет:
Artem Bokhan:
XCLIENT
