On Wed, 2012-08-15 at 10:06 -0400, Wietse Venema wrote:
> What tag? What originates it? What brings the tag through the filter?
>
> Did you read and understand Victor's mail? Tags should be unnecessary.
> SRS munging is an output function. It does not depend on client
> identity.
The tag would be
Hi Wietse
On Tue, 2012-08-14 at 17:02 -0400, Wietse Venema wrote:
> Many sites have external content filters as described above.
>
> 1 - Postfix receives mail from the network with the Postfix SMTP
> server. This may be an original submission or not. Or, Postfix
> receives mail with the
On Tue, 2012-08-14 at 15:36 -0400, Wietse Venema wrote:
> How is this supposed to work with external content filters, such
> as before-queue filters (smtpd_proxy) or post-queue filters
> (amavisd-new over SMTP, and pipe(8)->filter->sendmail(1) over UNIX
> pipes)?
The tag would always be added by t
On Tue, 2012-08-14 at 14:11 -0400, Wietse Venema wrote:
> That would be a mistake.
Understood. You are correct, of course.
Would you consider then the possibility of adding a tag to the message
metadata in the queue?
The idea is that different smtpd instances could tag the messages they
add to
On Tue, 2012-08-14 at 11:53 -0400, Wietse Venema wrote:
> The scheduler API (actually a protocol) would then receive requests
> containing (sender, recipients) and it would reply with one or more
> (sender, transport, nexthop, recipients) responses. The scheduler
> would append these to its per-tra
Hi Wietse
On Mon, 2012-08-13 at 17:35 -0400, Wietse Venema wrote:
> In your case the scheduler could compare the orig_rcpt and rcpt and
> if they differ, switch to single-recipient mode. However, I don't
> want to maintain hard-coded versions of DKIM or SRS etcetera inside
> Postfix. That is why
On Mon, 2012-08-13 at 10:49 -0400, Wietse Venema wrote:
> You could dumb down Postfix and reduce the default_recipient_limit.
> I don't know if is a good idea to make the queue scheduler dependent
> on both the final and the initial recipient address.
Is there anything a milter application could d
Hi Michael
On Mon, 2012-08-13 at 17:47 +0400, Michael Tokarev wrote:
> Do you have a patch or an implementation comments about some feature
> you want to implement?
>
I am implementing an SRS-enabled SPF milter to work with postfix and was
wondering how to deal with this case.
Thanks,
Andre
Hello
Imagine the following situation:
a...@example.com sends an email to x...@local1.com and y...@local2.com. Both
@local*.com accounts, via virtual_alias_maps, redirect to x...@external.com
and y...@external.com.
Am I right to assume that Postfix will create a single SMTP session with
the SMTP
Hi Wietse
On Fri, 2012-08-03 at 09:35 -0400, Wietse Venema wrote:
> Why not query the same database?
>
> Postfix's database proxy service is not designed for use by non-Postfix
> programs. Programs that use this are unsupported, meaning they will
> whenever this internal protocol is changed.
Po
Hello
I'm writing an SPF milter application with SRS support, making use of
milter's CHGFROM to rewrite the MAIL FROM address.
The application has to handle SRS in outgoing messages in 3 situations:
1) An MTA user sends a message (no redirect);
2) The MTA receives a message whose destination is
On Mon, 2010-11-22 at 13:45 -0500, Wietse Venema wrote:
> I have yet to overcome my my aversion against monstrosities such
> as Libtool and Autobloat. Until then, use the source, or use the
> DEBIAN port.
But I'd still need to rebuild the main postfix package because
mail_dict.c is part of it, rig
Hello
I've implemented a simple dict to allow postfix to talk to an Erlang
(http://www.erlang.org/) node. The idea is to allow access to Erlang's
Mnesia distributed database
(http://www.erlang.org/doc/apps/mnesia/users_guide.html).
To do so, besides writing dict_erlang.c, I also had to patch mail
13 matches
Mail list logo
