I want to be able to monitor SASL users to get quick notification if something
is out of the ordinary - like a spammer using a compromised account to send
emails.
What tool(s) can be used to achieve this?
Thanks,
Michael
hello ladies and gents
I do not know if I am in error or in the real
i a file check_client_access hash:/etc/postfix/acces_client
cat /etc/postfix/acces_client
mx3.mail2000.com.tw REJECT
mx2.mail2000.com.tw REJECT
mx2.mail.tw.yahoo.com REJECT
I forbid the property
Michael put forth on 6/24/2010 3:07 AM:
I want to be able to monitor SASL users to get quick notification if
something
is out of the ordinary - like a spammer using a compromised account to send
emails.
What tool(s) can be used to achieve this?
Given the nature of your requirement,
* Stan Hoeppner s...@hardwarefreak.com:
Michael put forth on 6/24/2010 3:07 AM:
I want to be able to monitor SASL users to get quick notification if
something
is out of the ordinary - like a spammer using a compromised account to send
emails.
What tool(s) can be used to achieve
On Thu, 24 Jun 2010 20:41:59 Stan Hoeppner wrote:
Michael put forth on 6/24/2010 3:07 AM:
I want to be able to monitor SASL users to get quick notification if
something is out of the ordinary - like a spammer using a compromised
account to send emails.
What tool(s) can be used to
On Thu, 24 Jun 2010 10:09:35 +0200, fakessh fake...@fakessh.eu wrote:
hello ladies and gents
I do not know if I am in error or in the real
i a file check_client_access hash:/etc/postfix/acces_client
cat /etc/postfix/acces_client
mx3.mail2000.com.tw REJECT
mx2.mail2000.com.tw
On Thu, 24 Jun 2010 11:03:18 +0200, fakessh fake...@fakessh.eu wrote:
On Thu, 24 Jun 2010 10:09:35 +0200, fakessh fake...@fakessh.eu wrote:
hello ladies and gents
I do not know if I am in error or in the real
i a file check_client_access hash:/etc/postfix/acces_client
cat
On Thu, 24 Jun 2010 20:48:04 Patrick Ben Koetter wrote:
* Stan Hoeppner s...@hardwarefreak.com:
Michael put forth on 6/24/2010 3:07 AM:
I want to be able to monitor SASL users to get quick notification if
something is out of the ordinary - like a spammer using a compromised
account to
* Michael p...@nettrust.co.nz:
On Thu, 24 Jun 2010 20:48:04 Patrick Ben Koetter wrote:
* Stan Hoeppner s...@hardwarefreak.com:
Michael put forth on 6/24/2010 3:07 AM:
I want to be able to monitor SASL users to get quick notification if
something is out of the ordinary - like a
Hello guys,
I am trying to tunne our postfix installation. In our setup we receive
mails, pass them after an anti-virus milter to a internal mail
processing system that uses lmtp using a content filter, and then
forward the mail to the final destination.
Since I have full control over the
I don't see any easy fix to this.
A user has email forwarded from their address at domainA to their
address at domainB and also to their address at domainC, each running
on different mail servers (but maybe the same MTA software). The
catch is that domainA uses one recipient delimiter character
On Thu, Jun 24, 2010 at 11:43:57AM -0400, Phil Howard wrote:
I don't see any easy fix to this.
A user has email forwarded from their address at domainA to their
address at domainB and also to their address at domainC, each running
on different mail servers (but maybe the same MTA software).
On Thu, Jun 24, 2010 at 12:08, Victor Duchovni
victor.ducho...@morganstanley.com wrote:
In situations where mail is forwarded outside the environment that
supports the local recipient delimiter (e.g. Postfix-Exchange):
I set:
propagate_unmatched_extesion = canonical
overriding the
--On Wednesday, June 23, 2010 5:28 PM -0400 Victor Duchovni
victor.ducho...@morganstanley.com wrote:
http://www.postfix.org/ldap_table.5.html
BACKWARDS COMPATIBILITY
For backwards compatibility with Postfix version 2.0 and
So you leave your online documentation using the syntax
Hello Wietse,
Thx a lot for your quick reply.
I thought that the client side concurrency was defined by:
1) lmtp_destination_concurrency_limit
2) the number of lmtp processes
I have set them both to 1 now and still get the same error message. So I
am starting to believe that there must be
On Thu, Jun 24, 2010 at 09:39:05AM -0700, Quanah Gibson-Mount wrote:
--On Wednesday, June 23, 2010 5:28 PM -0400 Victor Duchovni
victor.ducho...@morganstanley.com wrote:
http://www.postfix.org/ldap_table.5.html
BACKWARDS COMPATIBILITY
For backwards compatibility with Postfix
--On Thursday, June 24, 2010 12:56 PM -0400 Victor Duchovni
victor.ducho...@morganstanley.com wrote:
Nothing of the sort, the documentation shows *current* syntax and briefly
documents any legacy syntax. Your tone is in the above is unnecessarily
hostile. Please don't go there...
Nothing in
On Thu, Jun 24, 2010 at 06:55:47PM +0200, Luciana Moreira wrote:
Hello Wietse,
Thx a lot for your quick reply.
I thought that the client side concurrency was defined by:
1) lmtp_destination_concurrency_limit
Per nexthop, provided the transport is called lmtp, and not something
else. Do
On Thu, Jun 24, 2010 at 10:06:58AM -0700, Quanah Gibson-Mount wrote:
fancy.cf:
...
search_base = dc=example, dc=com
query_filter = mail=%s
result_attribute = memberaddr
special_result_attribute = memberdn
On Thu, Jun 24, 2010 at 01:12:23PM -0400, Victor Duchovni wrote:
Note the above deprecated postmap -q syntax.
It is not deprecated, this never worked.
Index: proto/LDAP_README.html
*** proto/LDAP_README.html 6 Feb 2010 07:34:26 - 1.1.1.1
--- proto/LDAP_README.html 24 Jun
On Wed, Jun 23, 2010 at 09:47:04PM +0300, Oguz Yilmaz wrote:
I just wanted to ask If Is there a way to disable loops back to
myself errors in a case which is not actually a real loop back.
Yes, by sending to a port other than port 25.
--
Viktor.
Hello,
Thx again for the replies, I am starting to see the light at the end of
the tunnel :-)
I have tried to disable the lmtp connection caching by setting the
following variable on main.cf:
lmtp_cache_connection=no
but the same errors are happening.
Victor Duchovni wrote:
On Thu, Jun
On Thu, Jun 24, 2010 at 09:39:05AM -0700, Quanah Gibson-Mount wrote:
--On Wednesday, June 23, 2010 5:28 PM -0400 Victor Duchovni
victor.ducho...@morganstanley.com wrote:
http://www.postfix.org/ldap_table.5.html
BACKWARDS COMPATIBILITY
For backwards compatibility with Postfix
On Thu, Jun 24, 2010 at 15:30, /dev/rob0 r...@gmx.co.uk wrote:
Another drawback to having versioned documentation online is that El
Goog is as likely to find the wrong version of a document. If a
seeker ends up at http://www.postfix.org/documentation.html , all's
well, but not necessarily so
So you leave your online documentation using the syntax of a
release that is 6 years old? That seems fairly odd. Why not use
versioned documentation?
People can legitimately use Postfix over a span of many years.
Currently, the oldest supported release is Postfix version 2.4,
which was
Victor Duchovni a écrit :
On Thu, Jun 24, 2010 at 12:20:23AM +0200, mouss wrote:
This mail is coming from postini. if you use postini, there's nothing
you can do with the envelope (and even if you do content filtering, you
shouldn't reject mail. it's too late).
Postini implement an SMTP
Keld Simonsen:
For postfix proper, does postfix invoke the postfix sendmail command somewhere
in the process as an MTA to deliver a mail, - for aliases expansion?
The Postfix sendmail command RECEIVES mail INTO Postfix.
The Postfix sendmail command is not used to DELIVER mail.
Wietse
On Thu, 24 Jun 2010 21:51:55 Patrick Ben Koetter wrote:
Maybe he will. The OP could install the policyd policy server (v1) and
impose sender restrictions von sasl authenticated senders.
I will look into this thanks.
Is there a reason that v1 is better then v2 for this application?
On Thu, Jun 24, 2010 at 11:47:12PM +0200, mouss wrote:
Victor Duchovni a ?crit :
On Thu, Jun 24, 2010 at 12:20:23AM +0200, mouss wrote:
This mail is coming from postini. if you use postini, there's nothing
you can do with the envelope (and even if you do content filtering, you
29 matches
Mail list logo
