Terry Carmen wrote:
Hello,
I've been trying to setup postfix with tls and smtp auth (dovecot sasl).
I'm now stuck with the smtp auth part, with a strange error. For a few
days I've tried to search information about similar problems, but found
none. Now I'm hoping somebody here could help me
Wietse Venema wrote:
Juha Pahkala:
Apr 24 15:42:30 server postfix/smtpd[8126]: name_mask: noanonymous
Apr 24 15:42:30 server postfix/smtpd[8126]:
xsasl_dovecot_server_connect: Connecting
Apr 24 15:42:40 server postfix/smtpd[8126]:
xsasl_dovecot_server_connect: auth reply: status
Apr 24
freebsd 7.1 and 7.0
postfix mail_version = 2.4.10
When traffic triggers postfix to log:
postfix/smtpd[4]: warning: problem talking to server 127.0.0.1:10041:
Operation timed out
... I see that the process qty of policy-to-postfix pegs at 201.
As long as that qty stays below 200, there
On Thursday 23 April 2009 10:02:29 Jørn Odberg wrote:
I can now see that the recieving side has an ESTABLISHED connection from
the sender, even after the sender tell me it has lost the connection
with the reciever. So it seems like something in the middle is forcing
the connection to a
Hi,
I am running Postfix on Ubuntu 9.04.
I have a primary MX server which does antispam/av etc, and the Postfix system
which is receiving the messages for the mailing lists etc.
I want to stop people from sending directly to the Postfix server, and only
allow connections to the relevant
Scott Haneda wrote:
As a test, I have disabled authenticated SMTP on port 25. I just fired
up thunderbird, set the SMTP port to 25, and enabled SSL. Sending a
test email, and I get an error back from the Thunderbird.
Thunderbird chewed on this for a long time. My concern is what was in
Andrew Hodgson wrote:
Hi,
I am running Postfix on Ubuntu 9.04.
I have a primary MX server which does antispam/av etc, and the Postfix
system which is receiving the messages for the mailing lists etc.
I want to stop people from sending directly to the Postfix server, and
only
On Sat, Apr 25, 2009 at 02:03:43PM -0500, Len Conrad wrote:
freebsd 7.1 and 7.0
postfix mail_version = 2.4.10
When traffic triggers postfix to log:
postfix/smtpd[4]: warning: problem talking to server 127.0.0.1:10041:
Operation timed out
... I see that the process qty of
Noel Jones wrote:
Use a check_client_access map to control what IPs can send mail to your
server.
# main.cf
smtpd_client_restrictions =
check_client_access cidr:/etc/postfix/allowed_clients
# reject all unlisted clients
reject
Andrew, is your server listed as a secondary MX for the
Wolfgang Zeikat wrote:
Noel Jones wrote:
Use a check_client_access map to control what IPs can send mail to
your server.
[...]
Andrew, is your server listed as a secondary MX for the domains in question?
No, the primary MX server is the only server listed in the MX table. However,
it
Noel Jones wrote:
Andrew Hodgson wrote:
Hi,
I am running Postfix on Ubuntu 9.04.
I have a primary MX server which does antispam/av etc, and the Postfix
system which is receiving the messages for the mailing lists etc.
I want to stop people from sending directly to the Postfix server, and
freebsd 7.1 and 7.0
postfix mail_version = 2.4.10
When traffic triggers postfix to log:
postfix/smtpd[4]: warning: problem talking to server 127.0.0.1:10041:
Operation timed out
... I see that the process qty of policy-to-postfix pegs at 201.
As long as that qty stays
Len Conrad:
As long as that qty stays below 200, there are no postfix timeouts.
I can't find any param in the policy process/docs or postfix/docs that is
200.
Where is this 200?
Most likely default_process_limit, put a 0 in the process limit column
of the master.cf entry for the
Wietse Venema wrote:
Juha Pahkala:
Wietse Venema wrote:
Juha Pahkala:
Apr 24 15:42:30 server postfix/smtpd[8126]: name_mask: noanonymous
Apr 24 15:42:30 server postfix/smtpd[8126]:
xsasl_dovecot_server_connect: Connecting
Apr 24 15:42:40 server postfix/smtpd[8126]:
14 matches
Mail list logo
