headers
Marc MERLIN | 1 Apr 2002 02:44
Favicon

Re: [Exim] Spamassassin Problem

On Sun, Mar 31, 2002 at 01:16:25PM +0200, Patrick von der Hagen wrote:
> On my system, it does not.

Ok, so that's something for me to fix then.

> Which userid is running spamassassin? Is this user an "trusted user"?

On Sun, Mar 31, 2002 at 03:41:13PM -0600, dman wrote:
> I'm not using exim3 any more.  Do note that the user specified in the
> "user=" option on the transport must be a trusted user to set the
> envelope sender and to set the received_protocol.
>
> Are you using the recent config submitted by Nigel that uses BSMTP or
> are you using the old one that uses a shell and the "-f" option to
> exim?

Let me paste what I'm using again:
# Spam Assassin
spamcheckbatch:
    driver = pipe
    command = /usr/sbin/exim -oMr spam-scanned -bS
    transport_filter = /usr/bin/spamc -p 784
    bsmtp = all
    home_directory = "/etc/mail/spamassassin"
    current_directory = "/etc/mail/spamassassin"
    # must use a privileged user to set $received_protocol on the way back in!
    user = mail
    group = mail
    return_path_add = false
    log_output = true
(Continue reading)

Permalink | Reply | 4 comments |
headers
Patrice Fournier | 1 Apr 2002 03:10

Re: [Exim] Spamassassin Problem

Quoting Marc MERLIN <marc_news <at> vasoftware.com>:

> I'm sure that the older version with -f would work, but I'm getting a
> syntax error on it:
> spamcheck:
>     driver = pipe
>     command = "/usr/sbin/exim -i -oMr spam-scanned -f ${if {eq
> {${sender_address}}{}} {mailer-daemon} {${sender_address}} } --
> ${local_part}"

put the quotes only arround the -f option arg as so:

     command = /usr/sbin/exim -i -oMr spam-scanned -f "${if {eq
 {${sender_address}}{}} {mailer-daemon} {${sender_address}} }" --
 ${local_part}

As for the current setup you have, do you have any directors before
spamcheck that would set errors_to = postmaster to the message?

--
Patrice Fournier
pfournier <at> loups.net

--

## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 3 comments |
headers
Vadim Vygonets | 1 Apr 2002 03:28

Re: [Exim] I would just like to say

Quoth Greg Webster on Mon, Mar 25, 2002:
> For my part I apologize, I was just getting a little tired of exchanges
> that were basically the following:
>
> Me: "I want to learn how to do this."
> "No you don't."
> Me: "Yeah, I really kinda do."
> "No you don't, it's been done before and better by someone else."
> Me: "Aside from that, I'd really like to know how I'd go about doing
> this."
> "You are an idiot."

I was not posting for a couple of weeks, but I was mostly
following the thread.  People did explain to you why what you
want to do is really hard, and why such simple straight-minded
approach will not work.  And why spamassassin, in their opinion,
will solve your problem nicely, and why using it is simpler than
developing your own filter with the rules you mentioned.  You
failed to listen.  I haven't used spamassassin yet, so I don't
know whether what they said is correct, but from what I know
about the program they seem to be right.

Please see my signature.  And keep in mind that this list
provides free help, which means nobody owes anybody else
anything, and nevertheless some (I'm not saying all) people who
posted here tried to help you.

Vadik.

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marc MERLIN | 1 Apr 2002 03:31
Favicon

Re: [Exim] Spamassassin Problem

On Sun, Mar 31, 2002 at 08:10:20PM -0500, Patrice Fournier wrote:
> Quoting Marc MERLIN <marc_news <at> vasoftware.com>:
>
> > I'm sure that the older version with -f would work, but I'm getting a
> > syntax error on it:
> > spamcheck:
> >     driver = pipe
> >     command = "/usr/sbin/exim -i -oMr spam-scanned -f ${if {eq
> > {${sender_address}}{}} {mailer-daemon} {${sender_address}} } --
> > ${local_part}"
>
> put the quotes only arround the -f option arg as so:
>
>      command = /usr/sbin/exim -i -oMr spam-scanned -f "${if {eq
>  {${sender_address}}{}} {mailer-daemon} {${sender_address}} }" --
>  ${local_part}

Ahah, that was my problem. I didn't realize I needed quotes inside.
The transport now works, thanks, and this one doesn't set use_shell to avoid
all the fun exploits.
I'm pasting it here in case there is a reason to use it over the BSMTP one.

# Spam Assassin
spamcheck:
    driver = pipe
    command = /usr/sbin/exim -i -oMr spam-scanned -f "${if eq {${sender_address}}{} {mailer-daemon}
{${sender_address}} }" -- ${local_part}
    transport_filter = /usr/bin/spamc -p 784
    home_directory = "/etc/mail/spamassassin"
    current_directory = "/etc/mail/spamassassin"
(Continue reading)

Permalink | Reply | 2 comments |
headers
Suresh Ramasubramanian | 1 Apr 2002 04:08
Favicon

[Exim] Re: NDN options in exim4?

+++ Dave C. [31/03/02 13:33 -0500]:
> There is this absolutely fantastic option that is a reference for
> EVERYthing that exim can or cannot do. Its saved in a file 'spec.txt' in

Yup - it does exist ...

> bounce_return_message           Type: boolean                   Default: true
>     If this option is set false, the original message is not included in
>     bounce messages generated by Exim. See also "return_size_limit".

Does it really include the headers as well?  PH doesn't seem to think so.

	-srs

--

## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 0 comments |
headers
Vadim Vygonets | 1 Apr 2002 04:09

Re: [Exim] auditing bandwidth

Quoth Jake on Tue, Apr 09, 2002:
                   ^^^^^^^^^^^^
The future is here!

> [ Picked text/plain from multipart/alternative ]

Please don't post HTML and wrap your lines at <=72 characters.

> Hello-
> I would like to use exim in a virtual host/reseller environment.  I can not seem to find a way to log the amount
of traffic (in MBs) that a particular domain has over a given period of time.  It doesn't appear as if message
size is logged in the logs.  Has anyone solved this problem?  I need to keep records of traffic for billing purposes.

Others proposed solution for Exim, but you might also want to
charge for other kinds of traffic (WWW, FTP, raw connectivity,
etc.).  In this case, my advise to you is to use traffic shaping
and logging facilities present in some UNIX operating systems.

It will give you different numbers, of course (think about raw IP
packets), but this may be what you really want (but then, it may
be not).

Vadik.

--
The ill-formed Orange
Fails to satisfy the eye:
Segmentation fault.

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kaz Sasayama | 1 Apr 2002 04:34
Picon

[Exim] Format of a delivery error message?

Is there any description about the format of a delivery error message
created by each Exim version? I'd like to fix Ecartis mailing list
manager so that it can find failing addresses in the error message made
by any version of Exim, including any future version.

Thanks in advance.

--
"Free software is not for free."
Kaz Sasayama <Kaz.Sasayama <at> HyperLinuxJP.com>; Screen Name: kazssym
Hyper Linux Systems (Hypercore Software Design, Ltd.)
<URL:http://www.hypercore.co.jp/>

--

## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 4 comments |
headers
Phil Pennock | 1 Apr 2002 03:06

[Exim] NL FTP mirror

I'm delighted to be able to announce a new public FTP mirror for the
Exim FTP content.

rsync'd daily from Nigel's ftp.exim.org site, Demon Netherlands provides
for the public:

 <URL:ftp://ftp.demon.nl/pub/mirrors/exim/≥

Any problems experienced with this site may be addressed to
<ftpadmin <at> demon.net> or to me personally.

This site has a respectable Internet connection and in practice only
proves to be slow around the time of a new Half-Life release.  :^)
--
Systems Administrator, Network Operations Centre, Demon Internet Nederland
NL Sales: +31 20 422 20 00       Thus Plc       NL Support: 0800 33 6666 8

--

## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 5 comments |
headers
Matthew Grant | 1 Apr 2002 03:38
Picon

[Exim] [PATCH] ssmtp (old-style SSL) support for exim 3.3x via inetd for old style SSL MTAs ...

--
--
--
[ Picked text/plain from multipart/alternative ]
Hi THere!

I have been working on getting a site up to support SSL based email
clients for a 'VPN' distributed worker network I need to set up.  I
found that evolution and MS Outhouse 5.0, and Netscape 4.0x were not
supported by the STARTTLS mechanism in exim 3.35 under Debian
sid/woody.  After playing for hours with stunnel and sslwrap and seeing
all the problems that pertained to this (broken logging of source host,
some clients refusing to deliver through the SSL wrapping daemon),
changing exim turned out to be a good easy solution - all I needed was
SSL/TLS startup on connect added to 'exim -bs' so I could the legacy
support from inetd...

(I do greatly encourage peole to up grade their older MTA clients, but
their machines are/can be too under powered etc.  - the Evolution team
should have used STARTTLS, but I guess that it doesn't work well with
some legacy commercial mail servers from a certain big corporation...).

Due to the excellent code structure for TLS in exim, I found the code
changes to be really simple for the rudimentary support needed for these
older MTAs, and only three code insertions of a few lines each needed to
be made, and one simple change to a log message!  Since TLS support was
already in exim, getting the SSL on connect wired up to the new -bssmtp
and -bsmtps command line switches was very basic.  The execution of
these code segments is controlled via the new global tls_on_connect flag
that gets set by the command line switch.  Thus the new code does not
(Continue reading)

Permalink | Reply | 22 comments |
headers
Patrice Fournier | 1 Apr 2002 05:08

Re: [Exim] Format of a delivery error message?

Quoting Kaz Sasayama <Kaz.Sasayama <at> Hypercore.co.jp>:

> Is there any description about the format of a delivery error message
> created by each Exim version? I'd like to fix Ecartis mailing list
> manager so that it can find failing addresses in the error message
> made by any version of Exim, including any future version.

If all you want is the failing addresses, you could simply use the
X-Failed-Recipients: header.

--
Patrice Fournier
pfournier <at> loups.net

--

## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 1 comment |

Gmane