Daniel L. Miller:
Wietse Venema wrote:
Daniel L. Miller:
On a whim, I tried something else. I tried telnet'ing to the two
listeners - but used the EHLO command to see what was reported. I do
get different responses. Does this mean anything significant? I notice
The
On Fri, Mar 6, 2009 at 8:52 AM, Wietse Venema wie...@porcupine.org wrote:
1) One tcpdump for client-before-proxy postfix smtpd
2) One tcpdump for before-proxy postfix smtpd-proxy
3) One tcpdump for proxy-after-proxy postfix smtpd
Then we have the evidence to decide which program responds
Daniel L. Miller wrote:
Magnus Bäck wrote:
On Thursday, March 05, 2009 at 00:25 CET,
Daniel L. Miller dmil...@amfes.com wrote:
What I have/had now was the following:
master.cf:
192.168.0.11:smtp inet n - - - -
smtpd
-o relayhost=[192.168.0.10]:225
Noel Jones wrote:
Looks as if the proxy filter has gotten out of sync with postfix.
I would suggest starting using it as a content_filter. Once you get
that working, you can see if it works with smtpd_proxy_filter.
I find it handy to use -o syslog_name=postfix-something in
master.cf to
Daniel L. Miller wrote:
Noel Jones wrote:
Looks as if the proxy filter has gotten out of sync with postfix.
I would suggest starting using it as a content_filter. Once you get
that working, you can see if it works with smtpd_proxy_filter.
I find it handy to use -o
Noel Jones wrote:
Daniel L. Miller wrote:
Noel Jones wrote:
Looks as if the proxy filter has gotten out of sync with postfix.
I would suggest starting using it as a content_filter. Once you get
that working, you can see if it works with smtpd_proxy_filter.
I find it handy to use -o
Daniel L. Miller a écrit :
[snip]
Mar 4 23:21:33 mailserver postfix/smtpd[20964]: warning: proxy
inet:192.168.0.10:225 rejected DATA: 250 2.1.5 Ok
This is the thing to look at. did the proxy send 5xx 250 2.1.5 Ok?
Mar 4 23:21:33 mailserver postfix/smtpd[20964]: warning: non-SMTP
command
OK - here's what I see now using telnet. First, connecting directly to
the ASSP listener via telnet:
r...@mailserver:/etc/postfix# telnet 192.168.0.10 225
Trying 192.168.0.10...
Connected to 192.168.0.10.
Escape character is '^]'.
220 Postfix-ASSP.amfeslan.local ESMTP Postfix (Ubuntu)
helo
Daniel L. Miller wrote:
OK - here's what I see now using telnet. First, connecting directly
to the ASSP listener via telnet:
r...@mailserver:/etc/postfix# telnet 192.168.0.10 225
Trying 192.168.0.10...
Connected to 192.168.0.10.
Escape character is '^]'.
220 Postfix-ASSP.amfeslan.local ESMTP
Daniel L. Miller:
Mar 4 23:21:33 mailserver postfix/smtpd[20964]: warning: proxy
inet:192.168.0.10:225 rejected DATA: 250 2.1.5 Ok
Your proxy replies with 250 2.1.5 Ok to the DATA command.
250 Is an incorrect reply. It should be 354 for success,
5xx or 4xx for failure.
And because 250 is
Wietse Venema wrote:
Daniel L. Miller:
Mar 4 23:21:33 mailserver postfix/smtpd[20964]: warning: proxy
inet:192.168.0.10:225 rejected DATA: 250 2.1.5 Ok
Your proxy replies with 250 2.1.5 Ok to the DATA command.
250 Is an incorrect reply. It should be 354 for success,
5xx or 4xx for
Daniel L. Miller:
[ Charset ISO-8859-1 unsupported, converting... ]
Wietse Venema wrote:
Daniel L. Miller:
Mar 4 23:21:33 mailserver postfix/smtpd[20964]: warning: proxy
inet:192.168.0.10:225 rejected DATA: 250 2.1.5 Ok
Your proxy replies with 250 2.1.5 Ok to the DATA
Wietse Venema wrote:
Daniel L. Miller:
[ Charset ISO-8859-1 unsupported, converting... ]
Wietse Venema wrote:
Daniel L. Miller:
Mar 4 23:21:33 mailserver postfix/smtpd[20964]: warning: proxy
inet:192.168.0.10:225 rejected DATA: 250 2.1.5 Ok
Your proxy replies
Daniel L. Miller wrote:
Wietse Venema wrote:
Daniel L. Miller:
[ Charset ISO-8859-1 unsupported, converting... ]
Wietse Venema wrote:
Daniel L. Miller:
Mar 4 23:21:33 mailserver postfix/smtpd[20964]: warning: proxy
inet:192.168.0.10:225 rejected DATA: 250 2.1.5 Ok
Daniel L. Miller:
You can log the conversation between SMTP client, Postfix and the
proxy filter by adding one -v option on the smtpd command line in
master.cf, or by using debug_peer_list and debug_peer_level in
main.cf.
I tried the -v option (wow - lot of stuff goes on behind the
Daniel L. Miller wrote:
Here's the other weird thing. If, after I enter the DATA command and
get that bogus 2.1.5, if I enter a second DATA command - it works.
smtpd -v log excerpt - with the first DATA:
Mar 5 18:54:01 mailserver local/smtpd[25237]:
Daniel L. Miller:
Here's the other weird thing. If, after I enter the DATA command and
get that bogus 2.1.5, if I enter a second DATA command - it works.
It does not matter. What matters is that the PROXY filter gives
the wrong reply to the first DATA command.
Wietse
smtpd -v log
Daniel L. Miller:
On a whim, I tried something else. I tried telnet'ing to the two
listeners - but used the EHLO command to see what was reported. I do
get different responses. Does this mean anything significant? I notice
The only thing that matters is that the proxy replies with 2xx
Wietse Venema wrote:
Daniel L. Miller:
You can log the conversation between SMTP client, Postfix and the
proxy filter by adding one -v option on the smtpd command line in
master.cf, or by using debug_peer_list and debug_peer_level in
main.cf.
I tried the -v option (wow - lot of
Wietse Venema wrote:
Daniel L. Miller:
On a whim, I tried something else. I tried telnet'ing to the two
listeners - but used the EHLO command to see what was reported. I do
get different responses. Does this mean anything significant? I notice
The only thing that matters is that
Ok - now that I've fixed my idiotic routing errors (don't have two NIC's
on the same network unless you know what you're doing - which I clearly
don't!), I can get back to Postfix.
From my prior configuration questions in ages past, I have been trying
to make most of my changes in master.cf,
Daniel L. Miller a écrit :
Ok - now that I've fixed my idiotic routing errors (don't have two NIC's
on the same network unless you know what you're doing - which I clearly
don't!), I can get back to Postfix.
From my prior configuration questions in ages past, I have been trying
to make most
Daniel L. Miller wrote:
Ok - now that I've fixed my idiotic routing errors (don't have two NIC's
on the same network unless you know what you're doing - which I clearly
don't!), I can get back to Postfix.
From my prior configuration questions in ages past, I have been trying
to make most of
Noel Jones wrote:
Define content_filter in main.cf pointing to the spam processing
machine, define a new smtpd listener in master.cf listening on a
different port.
http://www.postfix.org/FILTER_README.html
Amavisd-new is software often used as a postfix content_filter. Even
if you're using
mouss wrote:
to setup a Postfix listener for local SMTP connections, which will then
forward to a relayhost for spam processing (in this case, primarily
auto-whitelisting). That relayhost will then send the message back to
Postfix on another connection, and THAT listener will not have a
On Thursday, March 05, 2009 at 00:22 CET,
Daniel L. Miller dmil...@amfes.com wrote:
Noel Jones wrote:
Define content_filter in main.cf pointing to the spam processing
machine, define a new smtpd listener in master.cf listening on a
different port.
On Thursday, March 05, 2009 at 00:25 CET,
Daniel L. Miller dmil...@amfes.com wrote:
What I have/had now was the following:
master.cf:
192.168.0.11:smtp inet n - - - - smtpd
-o relayhost=[192.168.0.10]:225
192.168.0.11:125 inet n - -
Magnus Bäck wrote:
On Thursday, March 05, 2009 at 00:25 CET,
Daniel L. Miller dmil...@amfes.com wrote:
What I have/had now was the following:
master.cf:
192.168.0.11:smtp inet n - - - - smtpd
-o relayhost=[192.168.0.10]:225
192.168.0.11:125
28 matches
Mail list logo
