[Dovecot] sieve

[Christian Rößner]

Hi,

>> but I am looking for a mechanism that can reject Mail. Postfix can
>> use reject_unverified_recipient to connect to LMTP and ask if a mail
>> would successfully be enqueued and will return the status gotten from
>> the LMTP server if not. Chances are high that the mechanism would
>> work, too, if Dovecot would know about the sieve rule, while getting
>> a connection on LMTP. Does Dovecot know all rules at this point or is
>> sieve handled after the mail has already been accepted?
>> 
> 
> I have no idea if your above idea would actually work, but having
> followed your questions on the postfix ml and your interests in using
> reject_unverified_recipient and its cache with lmtp, it would be very
> unwise to cache deliverability on the postfix side based on sieve
> results, since sieve is able to reject/bounce on any part of the message
> including message body contents and such.

yes I know what you mean. The problem is that a user can decide to "reject" not based on "from" leading in rejects to other mails coming in to the same user. Probably a problem.

The idea came up, as I work for a little ISP/ESP here. Sometimes I get calls, where I get asked if I could reject mails from "xyz". And with a robut good working mechanism, where people could reject on their on decisions would make things easier. So I thought about sieve as being a workable solution.

Another solution would be to write some kind of milter/policy-service with a web-interface, where people can reject mails directly on the postfix side. But this is a lot of work.

Kind regards

-Christian Rößner

--
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Joerg Heidrich