On Mon, Mar 08, 2010 at 02:33:37PM +0100,
postfix-us...@tja-server.de wrote:
> /dev/rob0 wrote:
> >>But as far as i can tell, this is already quite late in
> >>processing the mails!
> >
> >Why do you think so?
>
> I seem to remember, that the recipient code technically is
> called later - after
postfix-us...@tja-server.de schrieb:
/dev/rob0 wrote:
But as far as i can tell, this is already quite late in
processing the mails!
Why do you think so?
I seem to remember, that the recipient code technically is called later
- after all headers and maybe even data has been read by the serve
/dev/rob0 wrote:
But as far as i can tell, this is already quite late in
processing the mails!
Why do you think so?
I seem to remember, that the recipient code technically is called later
- after all headers and maybe even data has been read by the server.
I would like to reject those mail
On Mon, Mar 08, 2010 at 12:12:39PM +0100,
postfix-us...@tja-server.de wrote:
> I would like to reject any mail to "user@..." as early as
> possible while still allowing mail to any other "user.s...@..."
> or "u...@...".
>
> So far, i could only find "check_recipient_access" that points
> to
Hello,
i used to create on-the-fly mail-addresses with "recipient_delimiter"
set to "."
Now, one of those mail-addresses is heavily receiving spam.
As this mail-address is of the form "user@...", cannot just remove
the user "user.sub" from my list of users.
I would like to reject any ma
