Koozali.org: home of the SME Server

Obsolete Releases => SME Server 9.x => Topic started by: William R H on June 20, 2018, 05:23:01 PM

Title: How to supplement email from a very primitive client?
Post by: William R H on June 20, 2018, 05:23:01 PM

We have a bought in, line of business, application that has a primitive email client built into it. It sends out PDFs it creates on the fly to suppliers, landlords and tenants. There is little to no possibility of it being changed.

Problem 1 - missing Message ID
It creates very simple message headers - and in particular does not create a Message ID header.  https://wiki.apache.org/spamassassin/Rules/MISSING_MID complains and assigns a spam score of 1.6 This is not good for us.

Problem 2 - no S/MIME support
Exactly that - emails are created and despatched with no possibility of encryption

Solutions for prob 1?
A. Send those emails to my own application that corrects them as needed then forwards them using SME Server qmail?
Or
B. I have had a look at the qmail docs and it seems that there is a utility qmail-qfilter which allows messages to be altered before they are passed to qmail-queue. I presume it would be fairly straightforward to add a message-ID header if it were missing.

Solutions for prob 2?
As above - but now, if we find that we have a key/cert or whatever it is called for the recipient we also S/MIME encrypt the body.

Has anyone any experience of doing either of these things? using qfilter? Is it already in SME Server?

Any thoughts, pointers or ideas very welcome.

Thanks

Title: Re: How to supplement email from a very primitive client?
Post by: William R H on June 20, 2018, 06:51:42 PM

Doing a bit of research I see that qmail-inject should be fixing the missing message-id header

"NAME
          qmail-inject - preprocess and send a mail message
     SYNOPSIS
          qmail-inject [ -nNaAhH ] [ -fsender ] [ recip ... ]
     DESCRIPTION
          qmail-inject reads a mail message from its standard input,
          adds appropriate information to the message header, and
          invokes qmail-queue to send the message to one or more
          recipients.
          See qmail-header(5) for information on how qmail-inject
          rewrites header fields."

Does that mean I can solve problem 1 easily?

Title: Re: How to supplement email from a very primitive client?
Post by: CharlieBrady on June 20, 2018, 11:47:05 PM

Quote from: William R H on June 20, 2018, 06:51:42 PM

Does that mean I can solve problem 1 easily?

Yes, if you have your application which is doing the S/MIME encoding run on SMEServer, and inject the resulting mail into qmail's queue via qmail-inject (or sendmail, which is a wrapper around qmail-inject) then the message-id will be added automatically.

Title: Re: How to supplement email from a very primitive client?
Post by: Jean-Philippe Pialasse on June 21, 2018, 05:55:49 AM

however if your application is running on another machine then you are not using qmail-inject but qpsmtpd which act in place of qmail-smtpd and put it to qmail-queue.

s o in this case you should check for qpsmtp plugin to do the job...

Title: Re: How to supplement email from a very primitive client?
Post by: William R H on June 28, 2018, 02:11:58 PM

I have sort of concluded that Ciphermail is the ready made answer to all of this and lots more too.
Thanks for your contributions and maybe help out there?
William

See

Quote from: brianr on June 28, 2018, 11:59:45 AM

I am looking at using the Ciphermail product to pre and post process email sent and received through SMEServer (acting as a gateway)