Re: SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Bowie Bailey]

On 2/13/2013 11:03 PM, Anirudha Patil wrote:
On Tue, Feb 12, 2013 at 6:16 PM, Mark Martinec 
mailto:mark.martinec...@ijs.si>> wrote:


Anirudha,

> I have a stable running setup of postfix after-queue using
amavis-new
> [currently using for content inspection and antivirus only] and
would like
> to use this for additional spam protection.
>
> As i understand from the above comments to my query, i dont need
to run the
> 'spamd' as separate process, but would invoke the spamprotection via
> amavis-new [via spamassasin perl moduled].

Exactly.

> I would continue to install the latest version of spamassasin
with existing
> amavis-new and check if the same error is encountered.

Right.


Thank you Mark and Bailey,
I have upgraded the spamassasin to 3.3.2, now i dont see the initial 
error message and can see that amavis is invoking the multiple 
rulesets of SA and also the corresponding scores are set for emails.


Does SA increases the load on the system ? Are they any tweaking 
guides to enable only specific rules in SA and not all?


The main thing to watch for with SA is memory usage.  Each Amavis 
process will load up all of the SA rules, so they can use a fair chunk 
of RAM.  Make sure to tweak the max number of processes in the Amavis 
config so that you don't go into swap when the system gets busy.


SA is already tuned as much as possible for general use.  Unless you 
have specific problems, it is not usually a good idea to disable any of 
the default rules.  Most of the "tweaks" you will find for SA involve 
loading extra rules.  This causes SA to use more resources, but it can 
increase the accuracy.


http://wiki.apache.org/spamassassin/ImproveAccuracy

--
Bowie

Re: SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Anirudha Patil]

On Tue, Feb 12, 2013 at 6:16 PM, Mark Martinec wrote:

> Anirudha,
>
> > I have a stable running setup of postfix after-queue using amavis-new
> > [currently using for content inspection and antivirus only] and would
> like
> > to use this for additional spam protection.
> >
> > As i understand from the above comments to my query, i dont need to run
> the
> > 'spamd' as separate process, but would invoke the spamprotection via
> > amavis-new [via spamassasin perl moduled].
>
> Exactly.
>
> > I would continue to install the latest version of spamassasin with
> existing
> > amavis-new and check if the same error is encountered.
>
> Right.
>
>
> Thank you Mark and Bailey,
I have upgraded the spamassasin to 3.3.2, now i dont see the initial error
message and can see that amavis is invoking the multiple rulesets of SA and
also the corresponding scores are set for emails.

Does SA increases the load on the system ? Are they any tweaking guides to
enable only specific rules in SA and not all?

Re: SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Mark Martinec]

Anirudha,

> I have a stable running setup of postfix after-queue using amavis-new
> [currently using for content inspection and antivirus only] and would like
> to use this for additional spam protection.
> 
> As i understand from the above comments to my query, i dont need to run the
> 'spamd' as separate process, but would invoke the spamprotection via
> amavis-new [via spamassasin perl moduled].

Exactly.

> I would continue to install the latest version of spamassasin with existing
> amavis-new and check if the same error is encountered.

Right.

  Mark

Re: SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Anirudha Patil]

On Tue, Feb 12, 2013 at 5:00 PM, Mark Martinec wrote:

> Anirudha,
>
> > So what should be the ideal setup of running binaries. I want Amavis
> > running both Spamprotection and ANtivirus protection, hence i have below
> > process running in current production
> > 1. Postfix MTA
> > 2. Amavisd
> > 3. Clamd
> > Should the spamd be running for spamprotection via amavis-new?
>
> To use Mail::SpamAssassin, you either use spamd as a front end,
> or amavisd as a front end, no need for both. The difference is
> in the protocol used between an MTA and a front end: in case
> of amavisd this is a standard SMTP (or LMTP) protocol;
> in case of spamd it is a dedicated spamc/spamd protocol, so
> typically you also need a spamc on the MTA side in this case.
>
> A content filter can be invoked by an MTA at the time of
> mail reception (before queue), or later after a message has
> already be accepted and queued (after queue). Each has its
> advantages and disadvantages. A before-queue setup is able
> to reject (not bounce) an undesired mail message, which is
> a very desired property, but is subject to much stricter
> timing constraints and resource usage proportional to peaks
> in mail traffic. An after-queue setup can process mail at
> leisure, but is unable to reject a mail - can only pass it
> or block it (or reroute it), or (heaven forbid) bounce it.
>
> See a Wikipedia article on Amavis:
>   http://en.wikipedia.org/wiki/Amavis
>
> To use a amavisd in a before-queue setup, a recent version
> of amavisd is needed (2.7.2 or 2.8.0), along with the
> latest version of Mail::SpamAssassin (3.3.2, or soon to
> come 3.4.0). Also a recent-ish version of Postfix is needed
> (2.7.0 or later) for its smtpd_proxy_options=speed_adjust
> option.
>
>
I have a stable running setup of postfix after-queue using amavis-new
[currently using for content inspection and antivirus only] and would like
to use this for additional spam protection.

As i understand from the above comments to my query, i dont need to run the
'spamd' as separate process, but would invoke the spamprotection via
amavis-new [via spamassasin perl moduled].
I would continue to install the latest version of spamassasin with existing
amavis-new and check if the same error is encountered.

Thank you Mark and Bailey

Re: SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Mark Martinec]

Anirudha,

> So what should be the ideal setup of running binaries. I want Amavis
> running both Spamprotection and ANtivirus protection, hence i have below
> process running in current production
> 1. Postfix MTA
> 2. Amavisd
> 3. Clamd
> Should the spamd be running for spamprotection via amavis-new?

To use Mail::SpamAssassin, you either use spamd as a front end,
or amavisd as a front end, no need for both. The difference is
in the protocol used between an MTA and a front end: in case
of amavisd this is a standard SMTP (or LMTP) protocol;
in case of spamd it is a dedicated spamc/spamd protocol, so
typically you also need a spamc on the MTA side in this case.

A content filter can be invoked by an MTA at the time of
mail reception (before queue), or later after a message has
already be accepted and queued (after queue). Each has its
advantages and disadvantages. A before-queue setup is able
to reject (not bounce) an undesired mail message, which is
a very desired property, but is subject to much stricter
timing constraints and resource usage proportional to peaks
in mail traffic. An after-queue setup can process mail at
leisure, but is unable to reject a mail - can only pass it
or block it (or reroute it), or (heaven forbid) bounce it.

See a Wikipedia article on Amavis:
  http://en.wikipedia.org/wiki/Amavis

To use a amavisd in a before-queue setup, a recent version
of amavisd is needed (2.7.2 or 2.8.0), along with the
latest version of Mail::SpamAssassin (3.3.2, or soon to
come 3.4.0). Also a recent-ish version of Postfix is needed
(2.7.0 or later) for its smtpd_proxy_options=speed_adjust
option.

  Mark

Re: SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Anirudha Patil]

On Mon, Feb 11, 2013 at 8:16 PM, Bowie Bailey  wrote:

> On 2/11/2013 3:23 AM, Anirudha Patil wrote:
>
>>
>> I have a MTA setup of [Postfix + Amavis-new + ClamAV + Spamassasin] of
>> which only the spamassasin part is disabled. Now i wish to enable the
>> Spamcontrol part.
>>
> 
>
>  [root@host spamassassin]# cat /etc/sysconfig/spamassassin
>> # Options to spamd
>> SPAMDOPTIONS="-d -c -m5 -H"
>>
>
> > This is irrelevant if you are using SpamAssassin via Amavisd-new.
>
>  [root@host spamassassin]# cat local.cf 
>> # These values can be overridden by editing ~/.spamassassin/user_prefs.cf<
>> http://user_prefs.cf>
>>
>> # (see spamassassin(1) for details)
>>
>> # These should be safe assumptions and allow for simple visual sifting
>> # without risking lost emails.
>>
>> required_hits 5
>> report_safe 0
>> rewrite_header Subject [SPAM]
>>
>
> > When you are calling SA via Amavis, the portions of SA's config related
> to required_hits and any header re- writing  are ignored in favor of the
> settings in the Amavis config.
>
>
>  [root@host spamassassin]# ps -elf | grep spam
>> 5 S root 29836 1 46  81   0 -  7184 pause  09:38 ?
>>  00:00:00 /usr/bin/spamd -d -c -m5 -H
>> 1 S root 29839 29836  0  78   0 -  7184 -  09:38 ?
>>  00:00:00 spamd child
>> 1 S root 29840 29836  0  78   0 -  7184 -  09:38 ?
>>  00:00:00 spamd child
>> 1 S root 29841 29836  0  81   0 -  7184 -  09:38 ?
>>  00:00:00 spamd child
>> 1 S root 29842 29836  0  81   0 -  7184 -  09:38 ?
>>  00:00:00 spamd child
>> 1 S root 29843 29836  0  81   0 -  7184 -  09:38 ?
>>  00:00:00 spamd child
>> 4 R root 29845 28512  0  78   0 -  1171 -  09:38 pts/2
>>  00:00:00 grep spam
>>
>
> > Amavisd-new runs the SA code internally.  You do not need to have spamd
> running.
>
>
So what should be the ideal setup of running binaries. I want Amavis
running both Spamprotection and ANtivirus protection, hence i have below
process running in current production

1. Postfix MTA
2. Amavisd
3. Clamd

Should the spamd be running for spamprotection via amavis-new?

Re: SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Bowie Bailey]

On 2/11/2013 3:23 AM, Anirudha Patil wrote:


I have a MTA setup of [Postfix + Amavis-new + ClamAV + Spamassasin] of 
which only the spamassasin part is disabled. Now i wish to enable the 
Spamcontrol part.



[root@host spamassassin]# cat /etc/sysconfig/spamassassin
# Options to spamd
SPAMDOPTIONS="-d -c -m5 -H"


This is irrelevant if you are using SpamAssassin via Amavisd-new.


[root@host spamassassin]# cat local.cf 
# These values can be overridden by editing 
~/.spamassassin/user_prefs.cf 

# (see spamassassin(1) for details)

# These should be safe assumptions and allow for simple visual sifting
# without risking lost emails.

required_hits 5
report_safe 0
rewrite_header Subject [SPAM]


When you are calling SA via Amavis, the portions of SA's config related 
to required_hits and any header re-writing are ignored in favor of the 
settings in the Amavis config.



[root@host spamassassin]# ps -elf | grep spam
5 S root 29836 1 46  81   0 -  7184 pause  09:38 ?   
 00:00:00 /usr/bin/spamd -d -c -m5 -H
1 S root 29839 29836  0  78   0 -  7184 -  09:38 ?   
 00:00:00 spamd child
1 S root 29840 29836  0  78   0 -  7184 -  09:38 ?   
 00:00:00 spamd child
1 S root 29841 29836  0  81   0 -  7184 -  09:38 ?   
 00:00:00 spamd child
1 S root 29842 29836  0  81   0 -  7184 -  09:38 ?   
 00:00:00 spamd child
1 S root 29843 29836  0  81   0 -  7184 -  09:38 ?   
 00:00:00 spamd child
4 R root 29845 28512  0  78   0 -  1171 -  09:38 pts/2   
 00:00:00 grep spam


Amavisd-new runs the SA code internally.  You do not need to have spamd 
running.


--
Bowie

Re: SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Mark Martinec]

Anirudha,

> Thank you Mark for the nice explanation. Just one question, can i upgrade
> my spamassasin to latest and still use it with amavis-new 2.6.4 version or
> does it also needs to be upgraded. Just that amavis required lots of
> depencies.

Yes, I believe amavis-new 2.6.4 should be able to use the recent versions
of SpamAssassin, including the coming 3.4.0 (currently in SVN trunk).

Some of the newer SpamAssassin features may not be available though
(like spam checking of large messages while still preserving a DKIM signature,
or timing constraints allowing amavisd to run in a pre-queue postfix
filtering setup).

  Mark

Re: SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Anirudha Patil]

On Mon, Feb 11, 2013 at 6:10 PM, Mark Martinec wrote:

> Anirudha,
>
> > > > My Setup details:
> > > > Postfix version: 2.7.3
> > > > Amavis-new version : 2.6.4-4
> > > > Spamassasin version : SpamAssassin version 3.0.1
> > > > running on Perl version 5.8.5
> > >
> > > The get_tag method was only made public with version of SpamAssassin
> > > 3.0.3, which was about 8 years ago! You need a newer version of
> > > SpamAssassin, like 3.3.2.  While at it, amavisd-new 2.6.4 is pretty old
> > > too (June 2009), consider using a more recent version.
> >
> > Thank you Mark, for the information, well i do understand that versions i
> > use are pretty old, but they are in production running smoothly and
> > currently we are not looking for any version upgrade if it can be
> avoided.
> >
> > Also does it mean the call for "get_tag" is not applicable for my
> > spamassasin version or does it has to do with any packages missing in my
> > setup
>
> > Right, the get_tag is not applicable to Spamassasin 3.0.1,
> > you need at least 3.0.3 - but both of these versions are long
> > time unsupported now.
>
> > When get_tag started to be used in amavisd-new-2.4.0 (2006-04),
> > SpamAssassin at that time was at version 3.1.8 or therabout.
> > There was no point in making amavisd backward-compatible with
> > SpamAssassin 3.0.2 (2004-12) or earlier.
>
> > but they are in production running smoothly and currently we
> > are not looking for any version upgrade if it can be avoided.
>
> > While amavisd-new 2.6.4 may possibly still do its job,
> > the spam warfare is evolving constantly. You can't expect
> > an eight years old spam filter to be able to cope with
> > current 'state of the art'. It may run, but its usefulness
> > will be next to none.
>
>
>
Thank you Mark for the nice explanation. Just one question, can i upgrade
my spamassasin to latest and still use it with amavis-new 2.6.4 version or
does it also needs to be upgraded. Just that amavis required lots of
depencies.

Re: SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Mark Martinec]

Anirudha,

> > > My Setup details:
> > > Postfix version: 2.7.3
> > > Amavis-new version : 2.6.4-4
> > > Spamassasin version : SpamAssassin version 3.0.1
> > > running on Perl version 5.8.5
> > 
> > The get_tag method was only made public with version of SpamAssassin
> > 3.0.3, which was about 8 years ago! You need a newer version of
> > SpamAssassin, like 3.3.2.  While at it, amavisd-new 2.6.4 is pretty old
> > too (June 2009), consider using a more recent version.
> 
> Thank you Mark, for the information, well i do understand that versions i
> use are pretty old, but they are in production running smoothly and
> currently we are not looking for any version upgrade if it can be avoided.
> 
> Also does it mean the call for "get_tag" is not applicable for my
> spamassasin version or does it has to do with any packages missing in my
> setup

Right, the get_tag is not applicable to Spamassasin 3.0.1,
you need at least 3.0.3 - but both of these versions are long
time unsupported now.

When get_tag started to be used in amavisd-new-2.4.0 (2006-04),
SpamAssassin at that time was at version 3.1.8 or therabout.
There was no point in making amavisd backward-compatible with
SpamAssassin 3.0.2 (2004-12) or earlier.

> but they are in production running smoothly and currently we
> are not looking for any version upgrade if it can be avoided.

While amavisd-new 2.6.4 may possibly still do its job,
the spam warfare is evolving constantly. You can't expect
an eight years old spam filter to be able to cope with
current 'state of the art'. It may run, but its usefulness
will be next to none.

  Mark

Re: SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Anirudha Patil]

On Mon, Feb 11, 2013 at 5:33 PM, Mark Martinec wrote:

> Anirudha Patil wrote:
>
> > I have a MTA setup of [Postfix + Amavis-new + ClamAV + Spamassasin] of
> > which only the spamassasin part is disabled. Now i wish to enable the
> > Spamcontrol part.
> >
> > But after enabling the spamassasin option in amavis-new, it shows the
> below
> > mentioned error.
> >
> > *(!!)SA failed: Can't locate object method "get_tag" via package
> > "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425,  line 29.
> > at (eval 86) line 467,  line 29*.
> >
> > Also the above line number, does is refer to "spamd" ?
>
> No, it refers to a file amavisd, relative to
> its module Amavis::SpamControl::SpamAssassin.
>
> > My Setup details:
> > Postfix version: 2.7.3
> > Amavis-new version : 2.6.4-4
> > Spamassasin version : SpamAssassin version 3.0.1
> > running on Perl version 5.8.5
>
> The get_tag method was only made public with version of SpamAssassin 3.0.3,
> which was about 8 years ago! You need a newer version of SpamAssassin,
> like 3.3.2.  While at it, amavisd-new 2.6.4 is pretty old too (June 2009),
> consider using a more recent version.
>
>
>
Thank you Mark, for the information, well i do understand that versions i
use are pretty old, but they are in production running smoothly and
currently we are not looking for any version upgrade if it can be avoided.

Also does it mean the call for "get_tag" is not applicable for my
spamassasin version or does it has to do with any packages missing in my
setup


Regards,
Anirudha

Re: SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Mark Martinec]

Anirudha Patil wrote:

> I have a MTA setup of [Postfix + Amavis-new + ClamAV + Spamassasin] of
> which only the spamassasin part is disabled. Now i wish to enable the
> Spamcontrol part.
> 
> But after enabling the spamassasin option in amavis-new, it shows the below
> mentioned error.
> 
> *(!!)SA failed: Can't locate object method "get_tag" via package
> "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425,  line 29.
> at (eval 86) line 467,  line 29*.
> 
> Also the above line number, does is refer to "spamd" ?

No, it refers to a file amavisd, relative to
its module Amavis::SpamControl::SpamAssassin.

> My Setup details:
> Postfix version: 2.7.3
> Amavis-new version : 2.6.4-4
> Spamassasin version : SpamAssassin version 3.0.1
> running on Perl version 5.8.5

The get_tag method was only made public with version of SpamAssassin 3.0.3,
which was about 8 years ago! You need a newer version of SpamAssassin,
like 3.3.2.  While at it, amavisd-new 2.6.4 is pretty old too (June 2009),
consider using a more recent version.

  Mark

SA failed: Can't locate object method "get_tag" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425

[Anirudha Patil]

Hello Folks,

I have a MTA setup of [Postfix + Amavis-new + ClamAV + Spamassasin] of
which only the spamassasin part is disabled. Now i wish to enable the
Spamcontrol part.

But after enabling the spamassasin option in amavis-new, it shows the below
mentioned error.

*(!!)SA failed: Can't locate object method "get_tag" via package
"Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425,  line 29.
at (eval 86) line 467,  line 29*.

Also the above line number, does is refer to "spamd" ?

I have already checked the mailing-list for such errors but none are
referring to my case here.

Any help is to direct me towards solving the case would be appreciated.

My Setup details:
Postfix version: 2.7.3
Amavis-new version : 2.6.4-4
Spamassasin version : SpamAssassin version 3.0.1  running on Perl version
5.8.5

[root@host spamassassin]# cat /etc/sysconfig/spamassassin
# Options to spamd
SPAMDOPTIONS="-d -c -m5 -H"

[root@host spamassassin]# cat local.cf
# These values can be overridden by editing ~/.spamassassin/user_prefs.cf
# (see spamassassin(1) for details)

# These should be safe assumptions and allow for simple visual sifting
# without risking lost emails.

required_hits 5
report_safe 0
rewrite_header Subject [SPAM]

[root@host spamassassin]# ps -elf | grep spam
5 S root 29836 1 46  81   0 -  7184 pause  09:38 ?00:00:00
/usr/bin/spamd -d -c -m5 -H
1 S root 29839 29836  0  78   0 -  7184 -  09:38 ?00:00:00
spamd child
1 S root 29840 29836  0  78   0 -  7184 -  09:38 ?00:00:00
spamd child
1 S root 29841 29836  0  81   0 -  7184 -  09:38 ?00:00:00
spamd child
1 S root 29842 29836  0  81   0 -  7184 -  09:38 ?00:00:00
spamd child
1 S root 29843 29836  0  81   0 -  7184 -  09:38 ?00:00:00
spamd child
4 R root 29845 28512  0  78   0 -  1171 -  09:38 pts/200:00:00
grep spam

Please find attached the debug info of a message trace for the error
mentioned.

Please let me know if any other additional detail is required

With Regards
Anirudha Patil
mobile no: 9221306620
email-id: anirudha.pa...@hotmail.com
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) SMTP> 220 [127.0.0.1] 
ESMTP amavisd-new service ready
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) SMTP< EHLO myhostname\r\n
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 250-[127.0.0.1]
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 250-VRFY
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 250-PIPELINING
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 250-SIZE
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 
250-ENHANCEDSTATUSCODES
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 250-8BITMIME
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 250-DSN
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 250 XFORWARD NAME 
ADDR PORT PROTO HELO SOURCE
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP< XFORWARD 
NAME=myhostname ADDR=127.0.0.1 PORT=32859\r\n
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 250 2.5.0 Ok 
XFORWARD
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP< XFORWARD 
PROTO=ESMTP HELO=mydomain SOURCE=LOCAL\r\n
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 250 2.5.0 Ok 
XFORWARD
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP< MAIL 
FROM: SIZE=445\r\n
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) check_mail_begin_task: 
task_count=1
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) TempDir::prepare: creating 
directory /var/amavis/tmp/amavis-20130211T090908-29615
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) TempDir::prepare_file: 
creating file /var/amavis/tmp/amavis-20130211T090908-29615/email.txt
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) lookup_ip_acl: 
key="127.0.0.1" matches "127.0.0.0/8", result=1
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) loaded policy bank "MYNETS"
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) lookup [debug_sender] => 
undef, "anirudha@myhostname" does not match
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 250 2.1.0 Sender 
 OK
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP< RCPT 
TO: ORCPT=rfc822;myuser@mydomain\r\n
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 250 2.1.5 Recipient 
 OK
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP< DATA\r\n
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP::10024 
/var/amavis/tmp/amavis-20130211T090908-29615:  -> 
 SIZE=445 Received: from myhostname ([127.0.0.1]) by localhost 
(myhostn...@apl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for 
; Mon, 11 Feb 2013 09:09:08 -0500 (EST)
Feb 11 09:09:08 myhostname amavis[29615]: (29615-01) ESMTP> 354 End data with 
.
Feb 11 09:09:0