On mx1.freebsd.org, we have a configuration that (vastly simplified)
looks something like this:
virtual_maps = hash:/usr/local/etc/postfix/virtual
transport_maps = hash:/usr/local/etc/postfix/transport
We have freebsd.org configured as a Postfix-style virtual domain
virtual:
freebsd.org v
On 4/8/2021 1:44 PM, Clifford Gonsalves wrote:
Hello Again,
The servers are 1 Exchange and 1 Zimbra.
Can this work?
1: First server delivery via transport map.
2: Second delivery via address rewrite (recipient _bcc maps ) then
transport map to the rewritten address.
3: At Zimbra rewrite add
On 2021-04-08 13:44, Clifford Gonsalves wrote:
The servers are 1 Exchange and 1 Zimbra.
Can this work?
1: First server delivery via transport map.
2: Second delivery via address rewrite (recipient _bcc maps ) then
transport map to the rewritten address.
3: At Zimbra rewrite address again and del
Clifford Gonsalves:
> Hello Again,
>
> The servers are 1 Exchange and 1 Zimbra.
>
> Can this work?
> 1: First server delivery via transport map.
> 2: Second delivery via address rewrite (recipient _bcc maps ) then
> transport map to the rewritten address.
> 3: At Zimbra rewrite address again and
Hello Again,
The servers are 1 Exchange and 1 Zimbra.
Can this work?
1: First server delivery via transport map.
2: Second delivery via address rewrite (recipient _bcc maps ) then
transport map to the rewritten address.
3: At Zimbra rewrite address again and delivery to local mailbox.
The soluti
Benny Pedersen:
> if anyone is willing to make c code to postfix it basicly SASL AUTH
> Blacklist so postscreen can use this ip list to active block port 25
> clients
Use something like fail2ban to update an lmdb-based postscreen_access_list,
or to update an rbldns service. No Postfix changes ne
Ralph Seichter:
> * Wietse Venema:
>
> > What does the milter do when data is unavailable?
>
> My understanding is that milter D is unable to decide whether or not to
> add its own flag header if the data is unavailable. There might be a
> default behaviour, but it would render the milter useless
On 2021-04-08 18:22, Rob McGee wrote:
Whitelisting in postscreen only affects postscreen itself, not any
other
ports nor services.
http://www.postfix.org/postconf.5.html#postscreen_access_list
fail2ban can make cidr list used in postscreen based on abuse on port
other then port 25, wake up
On 2021-04-08 09:12, Benny Pedersen wrote:
On 2021-04-08 15:56, Matus UHLAR - fantomas wrote:
On 2021-04-08 14:16, Matus UHLAR - fantomas wrote:
in addition to this, you can whitelist outlook's IP ranges at
postscreen
level, as they "likely" aren't what postscreen is supposed to stop -
bots.
* Wietse Venema:
> What does the milter do when data is unavailable?
My understanding is that milter D is unable to decide whether or not to
add its own flag header if the data is unavailable. There might be a
default behaviour, but it would render the milter useless. It would
require milter chan
On 2021-04-08 15:56, Matus UHLAR - fantomas wrote:
On 2021-04-08 14:16, Matus UHLAR - fantomas wrote:
in addition to this, you can whitelist outlook's IP ranges at
postscreen
level, as they "likely" aren't what postscreen is supposed to stop -
bots.
On 08.04.21 15:31, Benny Pedersen wrote:
th
On 2021-04-08 14:16, Matus UHLAR - fantomas wrote:
in addition to this, you can whitelist outlook's IP ranges at
postscreen
level, as they "likely" aren't what postscreen is supposed to stop -
bots.
On 08.04.21 15:31, Benny Pedersen wrote:
there is bots at microsoft, there servers try port 465
On 2021-04-08 14:16, Matus UHLAR - fantomas wrote:
in addition to this, you can whitelist outlook's IP ranges at
postscreen
level, as they "likely" aren't what postscreen is supposed to stop -
bots.
there is bots at microsoft, there servers try port 465, and 587
randomly, no mta would do thi
Ralph Seichter:
> * Wietse Venema:
>
> > Perhaps better, Milter D defers the message immrediately, and Postfix
> > retries a few minutes later, until the necessary data is available.
>
> Indeed. Having milter D block until the required data becomes available
> would tie up too many resources. Bet
* John Stoffel:
> So what happens if you get 1,000 emails coming into your system?
In one form or other, incoming messages flagged by milters A-C need to
be queued until milter D is ready for them. Like I wrote in my original
post, I am expecting a queue size of 1-5 million messages during peak
h
On April 8, 2021 8:29:09 AM GMT+02:00, Maurizio Caloro
wrote:
I have the issue with mail from Outlook, or Hotmail this Warning appair
and the mail don't deliver to me.
Apr 8 08:04:24 ail postfix/dnsblog[7379]: warning: dnsblog_query: lookup
error for DNS query 109.75.92.40.list.dnswl.org:
* Wietse Venema:
> Perhaps better, Milter D defers the message immrediately, and Postfix
> retries a few minutes later, until the necessary data is available.
Indeed. Having milter D block until the required data becomes available
would tie up too many resources. Better to make D reply with 4xx a
* Wietse Venema:
What problem are you trying to solve?
On 07.04.21 22:35, Ralph Seichter wrote:
Milters A, B and C in my example scenario can trigger asynchronous
actions in backend systems, the results of which become available only
after a delay caused by processing, which takes about 3 min
Clifford Gonsalves:
> Hello,
>
> We are planning to deploy a Postfix SMTP gateway which will sit behind our
> SPAM Firewall, how can I configure the Postfix SMTP gateway to delivery all
> incoming emails from the SPAM Firewall to 2 backend mail server (both
> active-active).
Postfix will deliver
Maurizio Caloro:
> >>You should not use public dns servers to query dnsbls as they are likely
> >>blocked due to excessive query volume at the dnsbl. Install and use >>a
> >>local resolver like unbound, knot, bind and use nameserver 127.0.0.1 in
> >>/etc/resolv.conf
>
> root@nmail:/etc/postfix#
Hello,
We are planning to deploy a Postfix SMTP gateway which will sit behind our
SPAM Firewall, how can I configure the Postfix SMTP gateway to delivery all
incoming emails from the SPAM Firewall to 2 backend mail server (both
active-active).
We run 2 backend mail server, one as primary (primary
>>You should not use public dns servers to query dnsbls as they are likely
>>blocked due to excessive query volume at the dnsbl. Install and use >>a local
>>resolver like unbound, knot, bind and use nameserver 127.0.0.1 in
>>/etc/resolv.conf
root@nmail:/etc/postfix# cat /etc/resolv.conf
nameser
Hello
I have the issue with mail from Outlook, or Hotmail this Warning appair and
the mail don't deliver to me.
Apr 8 08:04:24 ail postfix/dnsblog[7379]: warning: dnsblog_query: lookup
error for DNS query 109.75.92.40.list.dnswl.org: Host or domain name not
found. Name service error for name
On April 8, 2021 9:10:04 AM GMT+02:00, Maurizio Caloro
wrote:
>>>You should not use public dns servers to query dnsbls as they are
>likely blocked due to excessive query volume at the dnsbl. Install and
>use >>a local resolver like unbound, knot, bind and use nameserver
>127.0.0.1 in /etc/reso
On April 8, 2021 8:29:09 AM GMT+02:00, Maurizio Caloro
wrote:
>Hello
>
>I have the issue with mail from Outlook, or Hotmail this Warning appair
>and
>the mail don't deliver to me.
>
>
>
>Apr 8 08:04:24 ail postfix/dnsblog[7379]: warning: dnsblog_query:
>lookup
>error for DNS query 109.75.92
25 matches
Mail list logo
