On 02/07/2013 04:51 PM, Robert Schetterer wrote:
Am 07.02.2013 07:20, schrieb (HT) Simon Walter:
Hi all,
I have the situation where a spammer knows the username and password of
an account and is sending spam via that account. I can change the
password, however, this account is shared amongst
Am 07.02.2013 09:18, schrieb Simon Walter:
On 02/07/2013 04:51 PM, Robert Schetterer wrote:
Am 07.02.2013 07:20, schrieb (HT) Simon Walter:
Hi all,
I have the situation where a spammer knows the username and password of
an account and is sending spam via that account. I can change the
Robert Schetterer skrev den 2013-02-07 08:39:
sanesecurity signatures are added to the clamd signature base
so using clamsmtpd should be ok, no need for milter, however
you better only choose sources in the sanesecurity download script
which
are not known to produce to much false positives
Unfortunately I am not using clamav-milter, only clamsmtpd. This doesn't
exclude clamav-milter as a potential solution though.
The huge weakness of clamsmtpd is that the developer says there is now way to
release false positives.
Len
Em 06-02-2013 14:00, Marcio Merlone escreveu:
Could anybody advice me how to achieve a sometimes_bcc, which should
work as an always_bcc only when certain criteria is matched, based on
subject and/or destination, like a sieve script?
Greetings,
I think I'm best rephrasing my previous
On 2/7/2013 6:14 AM, Marcio Merlone wrote:
it must be transparent, based on subject.
So, to work on incoming and outgoing mails regardless of rcpts it
has to be implemented on postifx. Can someone advice me on how can I
solve this?
Regardless of how you state the problem, it should already
Em 07-02-2013 11:19, Noel Jones escreveu:
Regardless of how you state the problem, it should already be clear
that postfix does not have native capability to do selective BCC based
on the subject.
Yes, it was already.
You might be able to find a milter that can do this; I haven't looked.
Am 07.02.2013 14:38, schrieb Marcio Merlone:
Em 07-02-2013 11:19, Noel Jones escreveu:
Regardless of how you state the problem, it should already be clear
that postfix does not have native capability to do selective BCC based
on the subject.
Yes, it was already.
You might be able to find a
* Robert Schetterer r...@sys4.de:
Am 07.02.2013 14:38, schrieb Marcio Merlone:
Em 07-02-2013 11:19, Noel Jones escreveu:
Regardless of how you state the problem, it should already be clear
that postfix does not have native capability to do selective BCC based
on the subject.
Yes, it was
Am 2013-02-07 14:19, schrieb Noel Jones:
On 2/7/2013 6:14 AM, Marcio Merlone wrote:
it must be transparent, based on subject.
So, to work on incoming and outgoing mails regardless of rcpts it
has to be implemented on postifx. Can someone advice me on how can I
solve this?
Regardless of how
On 2/7/2013 8:29 AM, Michael Storz wrote:
How about using a smtp_header_checks with FILTER action which routes
such emails to another postfix instance which will then bcc all emails?
Nice thought. smtp_header_checks can't change the destination, but
you could use FILTER with regular
I'm running SpamAssassin as a content_filter on incoming mail which ads
4 spam-headers, one of them being X-Spam-Level:. The precise
header varies, depending on the spamscore. SpamAssassin ads one * for
each spampoint, so a example-header could be:
X-Spam-Level:
I would like
On 2/7/2013 7:38 AM, Marcio Merlone wrote:
Em 07-02-2013 11:19, Noel Jones escreveu:
Your only sure bet is to have postfix BCC everything and use a
sieve script after delivery to discard the unwanted messages.
I have only a couple hundred users, and one ongoing project with
such need. But
Em 07-02-2013 13:08, Noel Jones escreveu:
On 2/7/2013 7:38 AM, Marcio Merlone wrote:
I have only a couple hundred users, and one ongoing project with
such need. But that solution doesn't scale well. This probably will
become a standard for oncoming projects. Besides my small scale,
consider
Hi list
Im looking to activate a smarthost in my postfix, and for this I need to
use the function smtp_sasl_password_maps. I have and old server 2.5.5
and Im not sure if was supported in this old version. Where can I see
the changelogs to confirm this?
Thanks
* deconya deco...@riseup.net:
Hi list
Im looking to activate a smarthost in my postfix, and for this I need to
use the function smtp_sasl_password_maps. I have and old server 2.5.5
and Im not sure if was supported in this old version. Where can I see
the changelogs to confirm this?
On 2/7/2013 8:58 AM, Titanus Eramius wrote:
I'm running SpamAssassin as a content_filter on incoming mail which ads
4 spam-headers, one of them being X-Spam-Level:. The precise
header varies, depending on the spamscore. SpamAssassin ads one * for
each spampoint, so a example-header could be:
Am 07.02.2013 15:55, schrieb Noel Jones:
On 2/7/2013 8:29 AM, Michael Storz wrote:
How about using a smtp_header_checks with FILTER action which routes
such emails to another postfix instance which will then bcc all emails?
Nice thought. smtp_header_checks can't change the destination, but
On 2/7/2013 9:30 AM, deconya wrote:
Hi list
Im looking to activate a smarthost in my postfix, and for this I
need to use the function smtp_sasl_password_maps. I have and old
server 2.5.5 and Im not sure if was supported in this old version.
Where can I see the changelogs to confirm this?
On 2/7/2013 10:12 AM, Robert Schetterer wrote:
Am 07.02.2013 15:55, schrieb Noel Jones:
On 2/7/2013 8:29 AM, Michael Storz wrote:
How about using a smtp_header_checks with FILTER action which routes
such emails to another postfix instance which will then bcc all emails?
Nice thought.
Hi List,
i recently discovered that my Postfix, LDAP, Dovecot, Sieve, amavis Howto
translates rather pretty using google translate, so you might have some
feedback:
https://www.21x9.org/e-mail-server-1-ldap-debian-wheezy/
https://www.21x9.org/e-mail-server-2-dovecot-debian-wheezy/
Hi
appears
smtp_sasl_password_maps = hash:/etc/postfix/relay_passwd
but not works, everytime resolves the Ip but appears a message how
message nots authenticated in the server and relay is not permited. I
don't know where's the problem.
my postconf is:
default_transport = smtp
Am 07.02.2013 18:22, schrieb deconya:
smtp_sasl_password_maps = hash:/etc/postfix/relay_passwd
but not works, everytime resolves the Ip but appears a message how message
nots authenticated in the server and
relay is not permited. I don't know where's the problem
additionally to postconf
On Thu, Feb 07, 2013 at 06:22:40PM +0100, deconya wrote:
smtp_sasl_password_maps = hash:/etc/postfix/relay_passwd
relayhost = [smtp.puc.rediris.es]:25
Don't append :25 set:
relayhost = [smtp.puc.rediris.es]
smtp_sasl_auth_enable = no
You've disabled SASL.
Hi
Thanks for your help Viktor, i comment inside mail:
El 07/02/13 19:15, Viktor Dukhovni escribió:
On Thu, Feb 07, 2013 at 06:22:40PM +0100, deconya wrote:
smtp_sasl_password_maps = hash:/etc/postfix/relay_passwd
relayhost = [smtp.puc.rediris.es]:25
Don't append :25 set:
relayhost
On Thu, Feb 07, 2013 at 09:34:00PM +0100, deconya wrote:
smtp_sasl_auth_enable = no
You've disabled SASL.
In main.cf appears
smtpd_sasl_auth_enable = yes, why can appear no?
You're not paying attention:
smtpd != smtp
smtp_sasl_password_maps =
Hi
Well, thanks to advise me about the diference. But how I can change it?
I understand taht all my rules are misspelled and I need to correct all
of this with smtp_ ?
Thanks for your time and patience :-)
El 07/02/13 23:03, Viktor Dukhovni escribió:
On Thu, Feb 07, 2013 at 09:34:00PM +0100,
On 02/07/2013 05:28 PM, Robert Schetterer wrote:
Am 07.02.2013 09:18, schrieb Simon Walter:
On 02/07/2013 04:51 PM, Robert Schetterer wrote:
Am 07.02.2013 07:20, schrieb (HT) Simon Walter:
Hi all,
I have the situation where a spammer knows the username and password of
an account and is
Simon Walter:
academic value to me to know if this is possible, I think being able to
apply two or more criteria to for a single restriction could also be
useful. For example:
sender_restrictions = (criteria_a AND criteria_b)_reject, criteria_c_reject,
criteria_d_accept, reject
Use
On 02/08/2013 09:30 AM, Wietse Venema wrote:
Simon Walter:
academic value to me to know if this is possible, I think being able to
apply two or more criteria to for a single restriction could also be
useful. For example:
sender_restrictions = (criteria_a AND criteria_b)_reject,
On Thu, Feb 07, 2013 at 11:08:11PM +0100, deconya wrote:
Well, thanks to advice me about the diference. But how I can change it?
When configuring the Postfix SMTP client set the parameters documented
to work with smtp(8) and not those documented to work with smtpd(8).
Don't confuse the two
31 matches
Mail list logo
