Hi,
I have to route mail by /sender/ domain.
I found out about
sender_dependent_relayhost_maps =
pcre:/etc/postfix/sender_dependent_relayhost_map
with:
/.*@domain.de$/ special-mailgw
Works.
But: I observed postfix falling back to the MX for "domain.de" if
"special-mailgw"
is
Hi all,
I am trying to lower the concurrency for emails sent to *.rr.com
domains. I have configured the following, can anyone please tell me what
I am missing? Thanks in advance!
In main.cf:
transport_maps = hash:/etc/postfix/transport
default_destination_concurrency_limit = 2
slow_destinati
Russell Jones:
> Hi all,
>
> I am trying to lower the concurrency for emails sent to *.rr.com
> domains. I have configured the following, can anyone please tell me what
> I am missing? Thanks in advance!
>
> In main.cf:
>
> transport_maps = hash:/etc/postfix/transport
> default_destination_con
Christian Recktenwald:
> Hi,
>
> I have to route mail by /sender/ domain.
>
> I found out about
> sender_dependent_relayhost_maps =
> pcre:/etc/postfix/sender_dependent_relayhost_map
> with:
> /.*@domain.de$/ special-mailgw
>
> Works.
>
> But: I observed postfix falling back to t
Hi
I'm building my 1st Postfix server and working on getting Postscreen setup.
I RTFM here
http://www.postfix.org/POSTSCREEN_README.html
Where it says
The third layer performs light-weight content inspection with the Postfix
built-in header_checks and body_checks. This can block unaccepta
* bi...@sent.at :
> Hi
>
> I'm building my 1st Postfix server and working on getting Postscreen setup.
>
> I RTFM here
>
> http://www.postfix.org/POSTSCREEN_README.html
>
> Where it says
>
> The third layer performs light-weight content inspection with the Postfix
> built-in header_checks
Hi Patrick
Thanks for the reply.
> To clarify: postscreen never sees a message body. It probes the client IP and
> fakes a few SMTP commands, but that's it.
Ok, took me a couple of rereads, but it's not postscreen doing the check. It's
that postscreen is "part 1" of several checks.
> The righ
Save the message to a file. And test like this:
% postmap -q - pcre:/etc/postfix/body_checks.pcre
So does this.
cat << EOF > /tmp/testfile
TEST BAD CONTENT
EOF
postmap -q - pcre:/etc/postfix/body_checks.pcre You could use the message file from your imap server or look at the raw
message i
bi...@sent.at:
> postconf -n | grep body_checks
> body_checks = /etc/postfix/body_checks.pcre
That's your problem. You have SPACE before body_checks.
Wietse
Hi Wietse
On Mon, Jan 18, 2016, at 01:20 PM, Wietse Venema wrote:
> bi...@sent.at:
> > postconf -n | grep body_checks
> > body_checks = /etc/postfix/body_checks.pcre
>
> That's your problem. You have SPACE before body_checks.
No sorry . That's just me. I indented output 'vs' input like I al
Re-looking at my config, I set up Postfix to
1) receive via postfix
2) hand off what passes postscreen and the body_checks to amavis
So I have
master.cf
[mx.example.com]:25 inet n - n - 1 postscreen
-o smtpd_service_name=ps-int
ps-int pass - - n - - smtpd
-o recei
On 1/18/2016 3:28 PM, bi...@sent.at wrote:
> Hi Wietse
>
> On Mon, Jan 18, 2016, at 01:20 PM, Wietse Venema wrote:
>> bi...@sent.at:
>>> postconf -n | grep body_checks
>>> body_checks = /etc/postfix/body_checks.pcre
>>
>> That's your problem. You have SPACE before body_checks.
>
> No sorry .
Hi Noel
> Or just a really bad job of cut/paste?
Damn. Here I am trying to keep things all tidy-like and f'ing it all up with
cp-n-paste. Sorry. Typo.
Without any monkeying by me,
postconf -n body_checks
body_checks = pcre:/etc/postfix/body_checks.pcre
postconf -n | grep body_checks
body_ch
Hi,
seems you are using amavis in before-queue mode?. As i remember, a
proxy-smtpd, doesn't do any header- and body-checks
The more interresting master.cf lines are the ones who get the mail from
amavis. Do you have somthing like
-o receive_override_options=no_header_body_checks
or
Hi Wilfried
> seems you are using amavis in before-queue mode?
Yep, at this first step it's before-queue
> As i remember, a proxy-smtpd, doesn't do any header- and body-checks
Ok, so I must have missed that :-/ I don't yet grok all the details of
before-VS-after queuing. WOrkinf on that - it
* bi...@sent.at :
> Hi Patrick
>
> Thanks for the reply.
>
> > To clarify: postscreen never sees a message body. It probes the client IP
> > and
> > fakes a few SMTP commands, but that's it.
>
> Ok, took me a couple of rereads, but it's not postscreen doing the check.
> It's that postscreen i
Am 18.01.2016 um 23:21 schrieb bi...@sent.at:
> So now when I send email with the test string in it it gets rejected, I get
> this in the reject message
>
> : host mx.example.com[###.###.###.###]
> said: 550 5.7.1 id=04518-01 - Rejected by next-hop MTA on relaying,
> from
>
Hi Wilfried
> As i understand, amavis is putting the "from MTA(smtp
> [127.0.0.1]:50100)" into the reject message. I assume, postfix can't
> filter this message out, because it's all happening during the smtp
> dialog, while getting the mail from sending outside server. You will
> have to rewrite
> One thing, that reject message has the IP/Port (smtp:[127.0.0.1]:50100)
> of the next-hop MTA in it.
>
> Can I quiet that message down somewhere to NOT include that info?
> Just include the REJECT, but not the IP/Port, maybe referring to
> it by its 'syslog_name' or something like that?
Postfix
Hi Wietse
> > Can I quiet that message down somewhere to NOT include that info?
> > Just include the REJECT, but not the IP/Port, maybe referring to
> > it by its 'syslog_name' or something like that?
>
> Postfix 2.7 and later have an smtp_reply_filter feature, but
> that was implemented in the P
Hi Wietse,
Thanks for replying! I have not set that. Everything I have set for this
I provided in my initial email. I double checked to see if I had
anything set for "destination_concurrency" and I do not.
On 1/18/2016 11:02 AM, Wietse Venema wrote:
Russell Jones:
Hi all,
I am trying to
Russell Jones:
> Hi Wietse,
>
> Thanks for replying! I have not set that. Everything I have set for this
> I provided in my initial email. I double checked to see if I had
> anything set for "destination_concurrency" and I do not.
I was NOT talking about destination_CONCURRENCY.
You need to re
Sorry that was a typo, I meant I checked for
"destination_recipient_limit" and did not have anything set with that
name in main.cf.
On 1/18/2016 6:32 PM, Russell Jones wrote:
Hi Wietse,
Thanks for replying! I have not set that. Everything I have set for
this I provided in my initial email
Just to be clear that I do indeed know how to read, I was searching for
anything with "destination_recipient_limit" in the name, including
looking for slow_destination_recipient_limit. :-)
On 1/18/2016 6:49 PM, Russell Jones wrote:
Sorry that was a typo, I meant I checked for
"destination_re
24 matches
Mail list logo
