Great! [:)]

I am using policy tasks to analyse incoming email through a perlscript (I have written an own spam filtering mechanism which connects to an own database on a different machine)

I want to react on the email different it it is received with SMTP AUTH. How can I check this, because there is no corresponding line in the Email-Header ?

As I can see from the logfile, spamhalter realises incoming emails being SMTP authenticated, so there must be some way to get this information ?

Best regards

 Heiko

I asked almost the same question in this thread.

http://community.pmail.com/forums/thread/4071.aspx

[quote user="Marschall"]

I am using policy tasks to analyse incoming email through a perlscript (I have written an own spam filtering mechanism which connects to an own database on a different machine)

I want to react on the email different it it is received with SMTP AUTH. How can I check this, because there is no corresponding line in the Email-Header ?

As I can see from the logfile, spamhalter realises incoming emails being SMTP authenticated, so there must be some way to get this information ?

Best regards

 Heiko

[/quote]

If Spamhalter can do this, and I'm not sure that it does,  then it's being done via the  daemon interface.  Spamhalter gets all the mail files, both the QCF and QDF, after it's been received via MercuryS and/or MercuryD so I'm not all that sure how it knows that the message has gone through the MercuryS ESMTP authentication process.

[quote user="Thomas R. Stephenson"]

If Spamhalter can do this, and I'm not sure that it does,  then it's being done via the  daemon interface.  Spamhalter gets all the mail files, both the QCF and QDF, after it's been received via MercuryS and/or MercuryD so I'm not all that sure how it knows that the message has gone through the MercuryS ESMTP authentication process.

[/quote]

It is one of my tricks. [:D] Deamon interface not provide this kind of information, but I can made deduction by other informations instead:

• message not goes by mercuryD
• Server is not configured as openrelay
  
• message going from known local address
• message is for non-local user

At this case, message is very probably autorized by SMTP AUTH. Yes, hole os here, when message is for local user. But Spamhalter need this test for detect inbound/outgoing message, and for this purpose is this test enough.

By new API (SMTP server hooks) is possible to know if message is authorized, just here is problem how to get this information to queue procesing daemon. Maybe will be easy to write small daemon what can add some header with information about authorization. When i got a small free time, then I see what I can do with this. [;)]

Don't worry Lukas - it's pretty trivial to add this in MercuryS itself; I'll do it for v4.53.

Cheers!

-- David --