On 17 Aug 2016, at 11:34, Zhang Huangbin wrote:
Dear all,
I got a problem with my own Postfix policy server (written in Python).
Postfix usually works fine with it, but sometimes it raised error like
this:
Aug 17 08:32:52 mail1 postfix/smtpd[24298]: warning: problem talking
to server 127.0
> On Aug 17, 2016, at 4:02 PM, Wietse Venema wrote:
>
> Make the default Postfix instance a local submission-only MTA:
For a more detailed overview:
http://www.postfix.org/MULTI_INSTANCE_README.html#split
http://www.postfix.org/MULTI_INSTANCE_README.html#quick
--
Viktor.
On 18/08/16 10:46, Noel Jones wrote:
On 8/17/2016 7:26 PM, Zhang Huangbin wrote:
On Aug 18, 2016, at 12:17 AM, Noel Jones wrote:
Have you defined a time limit as described in
http://www.postfix.org/SMTPD_POLICY_README.html#client_config
The default time limit of 1000s may be too short.
My pol
> On Aug 18, 2016, at 8:46 AM, Noel Jones wrote:
>
> There was an example on the link I sent earlier.
>
> # main.cf
> 127.0.0.1:1234_time_limit = 3600
Seems this setting is not ok for me: The example in Postfix doc does have a
transport (127.0.0.1:9998) defined in master.cf, but i don't have
> On Aug 18, 2016, at 8:46 AM, Noel Jones wrote:
>
> # main.cf
> 127.0.0.1:1234_time_limit = 3600
"postfix check" reported "unused parameter: 127.0.0.0:1234_time_limit=3600s", i
thought it was illegal parameter.
I added this one and restarted Postfix, let's see whether or not it fixes my
issu
On 8/17/2016 7:26 PM, Zhang Huangbin wrote:
>
>> On Aug 18, 2016, at 12:17 AM, Noel Jones wrote:
>>
>> Have you defined a time limit as described in
>> http://www.postfix.org/SMTPD_POLICY_README.html#client_config
>> The default time limit of 1000s may be too short.
>
> My policy server is a ine
> On Aug 18, 2016, at 12:17 AM, Noel Jones wrote:
>
> Have you defined a time limit as described in
> http://www.postfix.org/SMTPD_POLICY_README.html#client_config
> The default time limit of 1000s may be too short.
My policy server is a inet server (check_policy_service inet:127.0.0.1:1234),
On 17/08/2016 09:43 μμ, Noel Jones wrote:
http://www.postfix.org/postconf.5.html#reject_unknown_client_hostname
Caution: this restriction is known to reject legit mail. Be
prepared to whitelist clients labeled "unknown" that you want mail
from.
You can "test drive" this restriction by using "w
Robert Dahlem:
>
> On 17.08.2016 20:58, Wietse Venema wrote:
>
> >> I have this in main.cf:
> >> inet_interfaces = 127.0.0.1, 192.168.x.x, 80.y.y.y
> >
> > Why not: "inet_interfaces = all"?
>
> Because I intend to run a second instance on the same machine with a
> different IP address. If the p
On 17.08.2016 20:58, Wietse Venema wrote:
>> I have this in main.cf:
>> inet_interfaces = 127.0.0.1, 192.168.x.x, 80.y.y.y
>
> Why not: "inet_interfaces = all"?
Because I intend to run a second instance on the same machine with a
different IP address. If the primary instance listens on all inte
Robert Dahlem:
> Hi,
>
> I have this in main.cf:
> inet_interfaces = 127.0.0.1, 192.168.x.x, 80.y.y.y
Why not: "inet_interfaces = all"?
Wietse
> The latter addresses are virtual IPs which are loaded by pacemaker
> before Postfix gets started.
>
> Sometimes I need to generate mail local
On 8/17/2016 1:34 PM, Aggelos wrote:
> How can I reject incoming (spam) mail from hosts that identify like
> the following?
> (see last line where it says "Received:...")
>
> From - Wed Aug 17 21:05:26 2016
> X-Account-Key: account7
> X-UIDL: 2ba28084e6838282
> X-Mozilla-Status: 0001
> X-Mozilla-S
How can I reject incoming (spam) mail from hosts that identify like the
following?
(see last line where it says "Received:...")
From - Wed Aug 17 21:05:26 2016
X-Account-Key: account7
X-UIDL: 2ba28084e6838282
X-Mozilla-Status: 0001
X-Mozilla-Status2:
X-Mozilla-Keys:
Return-Path:
X-O
On 8/17/2016 10:34 AM, Zhang Huangbin wrote:
> Dear all,
>
> I got a problem with my own Postfix policy server (written in Python).
> Postfix usually works fine with it, but sometimes it raised error like this:
>
> Aug 17 08:32:52 mail1 postfix/smtpd[24298]: warning: problem talking to
> server
Hi,
I have this in main.cf:
inet_interfaces = 127.0.0.1, 192.168.x.x, 80.y.y.y
The latter addresses are virtual IPs which are loaded by pacemaker
before Postfix gets started.
Sometimes I need to generate mail locally during the boot phase by using
sendmail. The virtual IP addresses are not loade
Dear all,
I got a problem with my own Postfix policy server (written in Python). Postfix
usually works fine with it, but sometimes it raised error like this:
Aug 17 08:32:52 mail1 postfix/smtpd[24298]: warning: problem talking to server
127.0.0.1:1234: Connection reset by peer
Aug 17 08:34:05 m
Peter:
> Why is transport taking precedence over mydestination? Or perhaps I am
> overlooking something here?
transport_maps takes precedence over (mydestination, local_transport),
(virtual_mailbox_domains, virtual_transport), and (relay_domains,
relay_transport). Otherwise, it would be useless.
Hello everyone,
I want my postfix to deliver locally for: 1.me.com and 2.me.com and so I
put these into mydestination.
However, I also want 3.me.com to be relayed somewhere else and
everything else to be sent yet outside therefore I got the following
/etc/postfix/transport file:
3.me.com
18 matches
Mail list logo
