On Tue, Jul 15, 2014 at 08:31:26AM +0200, Stefan Foerster wrote:
> Question: Are there any legal requirements with regard to the Postfix
> license that I need to be aware of? Are there any limitations when using
> Postifx in an academic environment?
You won't get any legal advice on this list. Y
On Tue, Jul 15, 2014 at 02:31:59AM +, Viktor Dukhovni wrote:
> Actually, AUXLIBS should come before SYSLIBS, so the correct patch is:
>
> diff --git a/makedefs b/makedefs
Thanks. Works for me.
Any chance of using ${CC} for the linking stage as well? Perhaps
something along the lines of:
-
Hello world,
every summer, I'm volunteering to give a programming class at a local
university. The goal is to teach CS students about "real world" code,
i.e. making them aware of things like resource managament (prevent
runaway fork(2) calls) under heavy load or the need for good documentation.
T
On Mon, Jul 14, 2014 at 10:25:31PM -0700, Michael Carter wrote:
> I've been trying to build SASL into postfix for a couple days, and I've been
> seeing this error:
>
> Undefined symbols for architecture x86_64:
> "_sasl_set_path", referenced from:
> _xsasl_cyrus_server_init in libxsasl.a
Hello all,
I've been trying to build SASL into postfix for a couple days, and I've been
seeing this error:
Undefined symbols for architecture x86_64:
"_sasl_set_path", referenced from:
_xsasl_cyrus_server_init in libxsasl.a(xsasl_cyrus_server.o)
ld: symbol(s) not found for architecture x
My github Postfix repo:
https://github.com/vdukhovni/postfix
has a "tlsfallback" branch, which extends Postfix with two new
pairs (smtp and lmtp flavours) of parameters (postconf(5) documentation
snippets below). I am soliciting feedback on the interface and
any operational experience i
On Tue, Jul 15, 2014 at 01:29:22AM +, Viktor Dukhovni wrote:
> Right, you're building with dynamicmaps=no, but SHLIB_SYSLIBS
> variable was not set quite right, see patch below. I also took
> the liberty of adding the RPATH to the shared library and plugin
> build command-lines.
Actually, AU
On Mon, Jul 14, 2014 at 07:16:30PM +, Eray Aslan wrote:
> $ ./bin/postconf mail_version
> ./bin/postconf: error while loading shared libraries:
> libpostfix-global.so: cannot open shared object file: No such file or
> directory
This is expected. You need to run:
LD_LIBRARY_PATH=$(pwd)/l
I am getting undefined_symbol errors when using gold for linking.
1/
With bfd:
$ make tidy
$ make -j7 makefiles shared=yes dynamicmaps=no
shlib_directory=/usr/lib64/postfix/MAIL_VERSION DEBUG=
CC=x86_64-pc-linux-gnu-gcc 'OPT=-march=native -O2 -pipe -Wno-comment'
'CCARGS=-DHAS_PCRE -DHAS_LDAP -DUS
Am 14.07.2014 17:50, schrieb André Rodier:
> On 2014-07-14 16:45, Robert Schetterer wrote:
>> Am 14.07.2014 15:44, schrieb André Rodier:
>>> The purpose is not to fight spam, but to classify emails and ideally
>>> differentiate commercial emails from private or business emails
>>
>> Allready exists
On 2014-07-14 16:45, Robert Schetterer wrote:
Am 14.07.2014 15:44, schrieb André Rodier:
The purpose is not to fight spam, but to classify emails and ideally
differentiate commercial emails from private or business emails
Allready exists in mail archive solutions, but not free to my
knowledge
Am 14.07.2014 15:44, schrieb André Rodier:
> The purpose is not to fight spam, but to classify emails and ideally
> differentiate commercial emails from private or business emails
Allready exists in mail archive solutions, but not free to my knowledge.
In germany bigger companies have to archive a
On 2014-07-14 16:19, Wijatmoko U. Prayitno wrote:
On Mon, 14 Jul 2014 16:07:32 +0100
André Rodier wrote:
On 2014-07-14 15:43, Andreas Schulze wrote:
> you could use spamassassin for that purpose, too.
> write your own SA rules and your done.
>
I cannot see in the SpamAssassin rules documentati
On 7/14/2014 10:21 AM, Wietse Venema wrote:
>
> Note that the "/" appears only when there is an anomaly. Here, the
> number of "good" auth commands (0) differs from the total number
> of auth commands (10).
>
> In a logfile analyzer, anomalies would match 'disconnect.*=\d+/\d+'
> (perl or pcre sy
André Rodier:
> I cannot see in the SpamAssassin rules documentation a way to add
> headers.
point for you. Adding any header with SA isn't possible at a first view.
You may ask again on spamassasin-users
Andreas
> A "normal" ESMTP session with vrfy:
>
> ehlo=1/1 vrfy=1/1 quit=1/1
>
> An "abnormal" session that drops after 10 rejected AUTH commands:
>
> ehlo=1/1 auth=0/10
>
> The logging shows only counters for commands that were actually
> issued. To save space we could replace "n/n" (two ident
On Mon, 14 Jul 2014 16:07:32 +0100
André Rodier wrote:
> On 2014-07-14 15:43, Andreas Schulze wrote:
> > you could use spamassassin for that purpose, too.
> > write your own SA rules and your done.
> >
> I cannot see in the SpamAssassin rules documentation a
> way to add headers. I see a lot of o
On 7/14/2014 8:25 AM, Wietse Venema wrote:
> In response to Noel's followup, here is a proposal that can make
> Postfix trouble shooting / anomaly detection easier. This would
> reveal information that is currently available only by turning on
> verbose logging.
>
> Proposal:
>
> The Postfix SMT
André Rodier skrev den 2014-07-14 17:07:
I cannot see in the SpamAssassin rules documentation a way to add
headers. I see a lot of options to modify the scoring 'score' option.
perldoc Mail::SpamAssassin::Conf
Can you give me an example on how to add a header with a SA rule,
please?
http:/
On 2014-07-14 15:43, Andreas Schulze wrote:
André Rodier:
I am looking for a milter script (mail filter) that would classify
emails automatically. Something in Perl, for instance.
you could use spamassassin for that purpose, too.
write your own SA rules and your done.
Andreas
Hello Andreas,
On 7/14/2014 9:40 AM, Andreas Schulze wrote:
> Wietse Venema:
>> Since the stats would be logged at the end of a session, they can
>> be logged in the "disconnect" record.
>
> Hello Wietse,
>
> the proposal sounds good. Such intormation could be helpful.
>
> Do you think it should be logged alwa
André Rodier:
> I am looking for a milter script (mail filter) that would classify
> emails automatically. Something in Perl, for instance.
you could use spamassassin for that purpose, too.
write your own SA rules and your done.
Andreas
Wietse Venema:
> Since the stats would be logged at the end of a session, they can
> be logged in the "disconnect" record.
Hello Wietse,
the proposal sounds good. Such intormation could be helpful.
Do you think it should be logged always or only while debugging?
I use to "postconf -e "debug_peer
Hello everyone,
I am looking for a milter script (mail filter) that would classify
emails automatically. Something in Perl, for instance.
The purpose is not to fight spam, but to classify emails and ideally
differentiate commercial emails from private or business emails.
After execution, th
In response to Noel's followup, here is a proposal that can make
Postfix trouble shooting / anomaly detection easier. This would
reveal information that is currently available only by turning on
verbose logging.
Proposal:
The Postfix SMTP server maintains two counters for each known
command: one
25 matches
Mail list logo
