Daniel Zwick writes:
I am not familiar with how zdkimfilter works, so I can't say for certain. With this kind of a configuration the E-mail (from the mail server's standpoint) originates locally, and perhaps zdkimfilter is configured to sign only mail that's received via SMTP (from a client).Yes, according to zdkimfilter's documentation, "The signing domain can be inferred in two ways, either by SMTP authentication or by setting RELAYCLIENT."Do I have a way of setting RELAYCLIENT for messages that originate locally?
No, this is a remote-only setting.
As far as the bcc header goes, this should be suppressed in build 20201028, at http://www.courier-mta.org/download.html#coneThanks, but does this mean, that the message is transmitted twice now (on version for sending and another for the Sent folder)?
No, the bcc header is removed in this case.The SMAP server does not parse headers, so it can't modify the message. Courier removes the Bcc header only if it's told to read the headers for the list of recipients. In this sequence of events the list of recipients gets specified explicitly, so they don't get removed.
The other alternative is to have Courier always removes Bcc headers from local mail. That would work too, however this would make cone rely on the mail server for that functionality, and I haven't decided if that's a reasonable assumption to make.
pgpatlMkqIlVE.pgp
Description: PGP signature
_______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
