headers
murthy | 1 Oct 2009 13:55
Picon
Favicon

auth_authen macro not visible in mimedefang

Hello all,
   I am trying to capture the auth_authen macro in mimedefang. The
%SendmailMacros has values for things like daemon_name, if_addr,
mail_addr etc but not for auth_authen.

My sendmail configuration for Milter is as below

O Milter.macros.connect=j, _, {daemon_name}, {if_name}, {if_addr}
O Milter.macros.helo={tls_version}, {cipher}, {cipher_bits},
{cert_subject}, {cert_issuer}
O Milter.macros.envfrom=i, {auth_type},
{auth_authen},{auth_ssf},{auth_author},{mail_mailer},{mail_host},{mail_addr}
O Milter.macros.envrcpt={rcpt_mailer}, {rcpt_host}, {rcpt_addr}
O Milter.macros.eom={msg_id}

And I am running mimedefang with option '-a auth_authen'.

Still the macro value does not appear. I have tested that my sendmail
daemon asks user authentication properly. Please help me.

regards
murthy
Permalink | Reply | 1 comment |
headers
David F. Skoll | 1 Oct 2009 16:35
Favicon

Re: auth_authen macro not visible in mimedefang

murthy wrote:

> O Milter.macros.envfrom=i, {auth_type},
> {auth_authen},{auth_ssf},{auth_author},{mail_mailer},{mail_host},{mail_addr}

> And I am running mimedefang with option '-a auth_authen'.

> Still the macro value does not appear.

The macros are normally only available from filter_begin or later.  If
you want them available at filter_sender time, call:

    read_commands_file();

to populate  <at> SendmailMacros

Regards,

David.
Permalink | Reply | 0 comments |
headers
Cliff Hayes | 7 Oct 2009 05:21

scanning outgoing mail

Hello,

Mimedefang and Spamassassin are doing a fine job of scanning incoming mail
on incoming MX servers.
I have the MX servers feeding a POP3 server.  How would I scan outgoing mail
to stop infected senders?  Do I use mimedefang for that or just
spamassassin?

Thanks in advance,

Cliff
Permalink | Reply | 4 comments |
headers
Steffen Kaiser | 7 Oct 2009 08:46
Picon

Re: scanning outgoing mail


On Tue, 6 Oct 2009, Cliff Hayes wrote:

> How would I scan outgoing mail
> to stop infected senders?  Do I use mimedefang for that or just
> spamassassin?

It depends on how the scans of incoming and outgoing 
messages differ :)

I use MIMEDefang for both.

Bye,

--

-- 
Steffen Kaiser
Permalink | Reply | 0 comments |
headers
Joseph Brennan | 7 Oct 2009 14:58
Favicon

Re: scanning outgoing mail


--On Tuesday, October 6, 2009 22:21 -0500 Cliff Hayes <chayes <at> afo.net> 
wrote:

> Hello,
>
> Mimedefang and Spamassassin are doing a fine job of scanning incoming mail
> on incoming MX servers.
> I have the MX servers feeding a POP3 server.  How would I scan outgoing
> mail to stop infected senders?  Do I use mimedefang for that or just
> spamassassin?

We use Mimedefang for both.  The key advantage is being able to apply
rules conditionally.  For example the Spamhaus PBL should be used only
on incoming.  And you might have identifiable internally-generated mail
that should always be accepted (announcements from the boss, etc).

Joseph Brennan
Columbia University Information Technology
Permalink | Reply | 2 comments |
headers
Cliff Hayes | 8 Oct 2009 02:54

Re: scanning outgoing mail

Thanks,

May I trouble you for some hints on a direction to take.  Perhaps a link to
a walk-through?  I have searched the web and found nothing.  I have both
spamassassin books and not a word.  I couldn't find a mimedefang book.

-----Original Message-----
From: mimedefang-bounces <at> lists.roaringpenguin.com
[mailto:mimedefang-bounces <at> lists.roaringpenguin.com]On Behalf Of Joseph
Brennan
Sent: Wednesday, October 07, 2009 7:59 AM
To: mimedefang <at> lists.roaringpenguin.com
Subject: Re: [Mimedefang] scanning outgoing mail

--On Tuesday, October 6, 2009 22:21 -0500 Cliff Hayes <chayes <at> afo.net>
wrote:

> Hello,
>
> Mimedefang and Spamassassin are doing a fine job of scanning incoming mail
> on incoming MX servers.
> I have the MX servers feeding a POP3 server.  How would I scan outgoing
> mail to stop infected senders?  Do I use mimedefang for that or just
> spamassassin?

We use Mimedefang for both.  The key advantage is being able to apply
rules conditionally.  For example the Spamhaus PBL should be used only
on incoming.  And you might have identifiable internally-generated mail
that should always be accepted (announcements from the boss, etc).
(Continue reading)

Permalink | Reply | 1 comment |
headers
NFN Smith | 10 Oct 2009 00:29
Picon

Header extraction question

Is there a way of extracting headers of a message in mimedefang?

What's up is that for messages submitted by my local users 
(authenticated connections), I'd like to get to the contents of 
User-Agent and X-Mailer headers.

Initially I want to just do logging for some statistical analysis, but 
in the longer run, if it's possible, I'd like to be able to force 
rejections of exchanges coming from users that have unapproved mailers 
(e.g., old versions that are no longer supported by the developer).

Is there a way of doing this?

Smith
Permalink | Reply | 1 comment |
headers
Joseph Brennan | 11 Oct 2009 04:07
Favicon

Re: Header extraction question


--On Friday, October 9, 2009 3:29 PM -0700 NFN Smith 
<worldoff9908 <at> mail.com> wrote:

> Is there a way of extracting headers of a message in mimedefang?
>
> What's up is that for messages submitted by my local users (authenticated
> connections), I'd like to get to the contents of User-Agent and X-Mailer
> headers.
>
> Initially I want to just do logging for some statistical analysis, but in
> the longer run, if it's possible, I'd like to be able to force rejections
> of exchanges coming from users that have unapproved mailers (e.g., old
> versions that are no longer supported by the developer).
>
> Is there a way of doing this?
>

We do this to get stats on what clients people are using.  And as long
as you're capturing header data at all, it's not too expensive to check
other interesting patterns in headers.

Joseph Brennan
Columbia University Information Technology

    %Header = '';

    # In the HEADERS file, any multiline headers have been rewritten to
    # be one line.  Received: is a typical example.  So here we do not
    # need to worry about continuation lines.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Philip A. Prindeville | 13 Oct 2009 20:35

Error messages about "require Mail::SpamAssassin:"

Can someone remind me what causes (and what fixes) the message:

Oct 13 12:16:14 mail mimedefang-multiplexor[2297]: Slave 2 stderr: plugin: failed to parse plugin (from
 <at> INC): syntax error at (eval 113) line 1, near "require Mail::SpamAssassin:

this is on an FC11 system that was recently updated via "preupgrade".

Thanks,

-Philip
Permalink | Reply | 1 comment |
headers
Steffen Kaiser | 14 Oct 2009 09:35
Picon

Re: Error messages about "require Mail::SpamAssassin:"


On Tue, 13 Oct 2009, Philip A. Prindeville wrote:

> Can someone remind me what causes (and what fixes) the message:

> Oct 13 12:16:14 mail mimedefang-multiplexor[2297]: Slave 2 stderr: 
> plugin: failed to parse plugin (from  <at> INC): syntax error at (eval 113) 
> line 1, near "require Mail::SpamAssassin:

Hmm, I would start checking MIMEDefang and the filter on command line, in 
order to get the complete error message:

# mimedefang.pl -features

# mimedefang.pl -test

see man mimedefang.pl

Bye,

--

-- 
Steffen Kaiser
Permalink | Reply | 0 comments |

Gmane