Quanah Gibson-Mount:
> --On Monday, October 22, 2012 7:39 PM -0400 Wietse Venema
> <wie...@porcupine.org> wrote:
>
> > There is, however, no milter_default_action ON THE SMTP SERVER SIDE
> > that accepts mail and keeps it queued until the milter comes back.
> > That's what you objected to, and that's what will never exist.
>
> All I want is to be able to send an email, have it processed and signed by
> OpenDKIM, and then handed off to Amavis.
>
> It seems to me if this can work without Amavis in the picture, it should be
> possible to do it with Amavis in the picture too.
>
> I understand the milter has to be fronted as a filter. I understand I need
> the ability to route mail differently through amavis depending on whether
> or not it is originating or foreign email. What I'm missing is how to get
> all this to play together the way I want it to.
>
> I.e., it is fine with me if "milter" is not how the SMTP server "sees"
> things, just as it doesn't see it that way using the content filter.
>
> So, is setting it up this way truly impossible as well, or is there some
> way to stack filters (not milters), which was my original question.
Use a before-queue filter for mail from outside.
Internet -> smtpd -> Amavis ...
Use a Postfix queue BEFORE and AFTER the signing Milter for mail
from inside.
... -> queue -> smtp -> smtpd -> cleanup -> queue -> smtp -> Amavis ...
| |
signing
milter
The part with "smtp -> smtpd" is a "null filter" where the two
programs talk directly to each other.
Instead of the above you could simply use Amavis's DKIM support to
sign the messages.
No doubt there will be some other objection, and never a thankyou.
Wietse
