Hello,
Could anyone please help with a Postfix/Spamassassin configuration problem.
I have a small debian wheezy server running Fetchmail 6.3.21-4, Postfix
2.9.6-2 Spamassassin 3.3.2-5.
I have set the always_bcc in the main.cf as below and this works fine
without spamassassin. With spamassassin
pappin:
Hello,
Could anyone please help with a Postfix/Spamassassin configuration problem.
I have a small debian wheezy server running Fetchmail 6.3.21-4, Postfix
2.9.6-2 Spamassassin 3.3.2-5.
I have set the always_bcc in the main.cf as below and this works fine
without spamassassin.
Thanks very much for the prompt reply.
I tried as you suggested
smtp inet n - - - - smtpd
-o content_filter=spamassassin
-o receive_override_options=no_address_mappings
I am now getting an error in my email log
postfix/qmgr[7975]: warning: connect to
Homer:
Two steps eliminated this problem for us:
1) Accounts with more than 6 failed login attempts in a 10 minute period
are disabled for 10 minutes. This makes brute force methods to find
passwords almost impossible.
2) Limit to 200 outgoing messages per day per user. We'll raise it to
pappin:
Thanks very much for the prompt reply.
I tried as you suggested
smtp inet n - - - - smtpd
-o content_filter=spamassassin
-o receive_override_options=no_address_mappings
I am now getting an error in my email log
postfix/qmgr[7975]:
The maillog says this, and I believe it:
Mar 5 08:22:02 ns5.arlut.utexas.edu sendmail[5427]: s25EM0Zg005419:
to=u...@xxx-.com, delay=00:00:01, xdelay=00:00:00, mailer=relay,
pri=1081946, relay=ns2.arlut.utexas.edu. [146.6.211.1], dsn=5.1.3, stat=Service
unavailable
But the user's bounce
On 3/6/2014 11:08 AM, Jay G. Scott wrote:
The maillog says this, and I believe it:
Mar 5 08:22:02 ns5.arlut.utexas.edu sendmail[5427]: s25EM0Zg005419:
to=u...@xxx-.com, delay=00:00:01, xdelay=00:00:00, mailer=relay,
pri=1081946, relay=ns2.arlut.utexas.edu. [146.6.211.1], dsn=5.1.3,
On 06 Mar 2014, at 18:04, Adam Moffett adamli...@plexicomm.net wrote:
Two steps eliminated this problem for us:
1) Accounts with more than 6 failed login attempts in a 10 minute period are
disabled for 10 minutes. This makes brute force methods to find passwords
almost impossible.
2)
You were quite right - typo !! - all working now - thanks very much.
pappin
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-Spamassassin-and-always-bcc-tp65835p65844.html
Sent from the Postfix Users mailing list archive at Nabble.com.
Am 06.03.2014 18:04, schrieb Adam Moffett:
Two steps eliminated this problem for us:
1) Accounts with more than 6 failed login attempts in a 10 minute period are
disabled for 10 minutes. This makes
brute force methods to find passwords almost impossible.
that is fine
2) Limit to 200
I wanted users to have the choice between connecting via TLS or not.
By default, users would require TLS unless they choose otherwise.
There is an existing userbase where some users use SSL/TLS, and others
do not.
We use dovecot for authentication. The auth protocol as mentioned at
Nathan Coulson:
In testing, we were seeing the following results:
smtpd_tls_security_level=may
AUTH#0111#011PLAIN#011service=smtp#011nologin#011lip=1.6.0.5#011rip=1.6.41.1#011resp=
smtpd_tls_security_level=encrypt
On 14-03-06 11:25 AM, Wietse Venema wrote:
Nathan Coulson:
In testing, we were seeing the following results:
smtpd_tls_security_level=may
AUTH#0111#011PLAIN#011service=smtp#011nologin#011lip=1.6.0.5#011rip=1.6.41.1#011resp=
smtpd_tls_security_level=encrypt
The source code does not lie. I suppose someone down-stream improved it.
Wietse
On 14-03-06 12:15 PM, Nathan Coulson wrote:
On 14-03-06 11:25 AM, Wietse Venema wrote:
Nathan Coulson:
In testing, we were seeing the following results:
smtpd_tls_security_level=may
AUTH#0111#011PLAIN#011service=smtp#011nologin#011lip=1.6.0.5#011rip=1.6.41.1#011resp=
15 matches
Mail list logo
