Pegasus Mail & Mercury

oaneadp: I’ve been doing some testing, when “Authenticated SMTP connections may relay mail” is checked, the setting of “Do not permit SMTP relaying of non-local mail” seems to become irrelevant; because regardless of its state - as long as I authenticate whilst sending a mail, I can send make the “FROM:” header anything, for example ...

There is absolutely no necessity to get complicated. The more complicated the solution, the more difficult it is to implement. And few of the ''anti-spam technologies'' tackle the problem where it occurs, which is actually where it must be tackled. Once it gets past the SMTP layer, i.e. at the mail clients, all the ''anti-spam technologies'' are ...

It should be solved by small daemon by SMTP server hooking. I know if connection is authjorized here, and i am using this information in GrayWall. (Authorized connections are not delayed anymore...) So, most easy way is small daemon what can detect this state and add requested header to message. I must think about it too. 

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 ...

In the auth file you put username [one space] password. Each line makes a pair. So you can duplicate the authentication so that the information is the same as the pop3 acct/passwords your user knows about. We too would like a simple check-box instead or as add-on for this feature - since that is the most common way email clients set this ...