similar to: Discard mail with from date older than xxxx

On 1/24/19 12:15 AM, Per Jessen wrote: > Trever L. Adams wrote: > >> I know that sieve doesn't do math. The file would be created >> externally. >> >> Based on examples in section 4.4 of >> https://tools.ietf.org/html/rfc5260#section-4 >> >> I figured something like this would work. >> >> if date :value "le" :originalzone

Trever L. Adams wrote: > On 1/24/19 12:15 AM, Per Jessen wrote: >> Trever L. Adams wrote: >> >>> I know that sieve doesn't do math. The file would be created >>> externally. >>> >>> Based on examples in section 4.4 of >>> https://tools.ietf.org/html/rfc5260#section-4 >>> >>> I figured something like this would work.

Trever L. Adams wrote: > I know that sieve doesn't do math. The file would be created > externally. > > Based on examples in section 4.4 of > https://tools.ietf.org/html/rfc5260#section-4 > > I figured something like this would work. > > if date :value "le" :originalzone "date" "date" "2018-10-25" { > fileinto

I have deploy an environment with pigeon sieve, managesieve, dovecot, squirrelmail and avelsieve plugin. The vacation messages are working fine. I am looking for a method to discard vacation messages in some date, when the user returns. Has somebody looked in this feature? Thanks a lot, -- Andr?s Fernando Yacopino Infraestructura - Dpto Sistemas AcaSalud Cooperativa de Prestaciones M?dico

On 1/24/19 10:07 AM, Per Jessen wrote: > > Sorry, I misunderstood. > > I rely on spamassasssin to deal with spam. > > > /Per > > You still led me to the correct solution. I use dspam. Occassionally some odd spams get through. Usually they are using this date trick (not that it fools dspam). The problem is the content is novel. So, I am using this to catch what cannot be

Hello, still trying to move from procmail to sieve, but there are new problems. Currently we use procmail for autoresponder and let user choose timerange, in which responder should work. May be you set up today your responder for 2 weeks in future where responder start and stop automatically without further manuell intervention. In procmail this is done by simple scripting and comparison of

I am able to get sieve issuing an "out of office"message correctly. However, I want to configure it to send an "OOO" message only during certain dates, say on weekends, or only between certain hours. I can do that manually; however, was wondering if there is any automatic method available that could handle this chore. Thanks! -- Jerry

Hello, I have a complete Postfix + Dovecot + openLDAP setup almost working, the only issue I have is the vacation script auto-reply that doesn't work properly. If I send an email to a user with the vacation filter enabled, the auto-reply is send to a local recipient with the same account name. So for example if I send a mail from test at xyz.com to test at example.com, the auto-reply is

Op 23-6-2017 om 16:15 schreef Larry Rosenman: > On 6/23/17, 9:13 AM, "dovecot on behalf of Jerry" <dovecot-bounces at dovecot.org on behalf of jerry at seibercom.net> wrote: > > On Fri, 23 Jun 2017 14:46:21 +0200, Stephan Bosch stated: > > >Op 21-6-2017 om 19:16 schreef lejeczek: > >> hi fellas > >> > >>

On Fri, 23 Jun 2017 14:46:21 +0200, Stephan Bosch stated: >Op 21-6-2017 om 19:16 schreef lejeczek: >> hi fellas >> >> generic construct for(if possible): reply vacation message if >> address is not from add1 at com1 add2 at com2 >> >> would you share? > >require "vacation"; > >if not address "from" ["add1 at com1",

Hello, there is a way with a sieve rule to add a Date: header when it is missing? Adding one with the time of reception of the message or using the date from the the first Received: header would be good options. Unfortunately I'm receiving some useful automated messages that lack a Date header and this screws up the sorting in my imap clients. I have a script to fix those acting on the

I am struggling with how to use the date extension for Dovecot/Pigenhole implementation of Sieve email filtering language. I have read RFC 5260 several times and tried different things with no luck. I would like to place all messages this year up till the end of March into the specified mail folder. What the snippet below actually seems to do is take any messages this year (whether before or after

http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz.sig Some small fixes and changes to v2.2.14. This release is mainly in the hope that it could still make it into the next Debian stable instead of v2.2.14 - mainly because of a couple of new assert crashes that started happening in v2.2.14 and should be fixed now. * Plugins can now print

http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz.sig Some small fixes and changes to v2.2.14. This release is mainly in the hope that it could still make it into the next Debian stable instead of v2.2.14 - mainly because of a couple of new assert crashes that started happening in v2.2.14 and should be fixed now. * Plugins can now print

Hi, i am playing about mail archive this is what allready works for me require ["variables","date","fileinto","mailbox","envelope","subaddress","regex"]; # Extract date info if currentdate :matches "year" "*" { set "year" "${1}"; } if currentdate :matches "month" "*"

Hello, Sometimes, when a call comes in from the PSTN through our VoIP gateway, the information that is sent to our web page that logs calls includes the original CID name instead of the one that is we expect to be rewritten on the fly using Asterisk's LookupCIDName: ================= ;extensions.conf [internal] exten => group,1,LookupCIDName exten =>

Hi there, I am trying to move from lmtpd (lmtpd.sf.net) to dovecot sieve. One thing used by some of powerusers are archiving mail automatically with autocreated folders based on year + month. Is there any good way to make that with sieve... One example require "fileinto"; if address :is ["From", "To"] "dovecot at dovecot.org" { fileinto

Hello Dovecot users, In the last week two nasty bugs were found in the new Sieve implementation. Primarily, the include extension did not work when a compiled binary was loaded from disk. This is something that is still not tested by the test suite, giving this bug the opportunity to slip through. Also, the value matching implementation would sometimes cause a assertion failure. Other than

Hello Dovecot users, In the last week two nasty bugs were found in the new Sieve implementation. Primarily, the include extension did not work when a compiled binary was loaded from disk. This is something that is still not tested by the test suite, giving this bug the opportunity to slip through. Also, the value matching implementation would sometimes cause a assertion failure. Other than

Hello. I'm trying to set up a vacation autoresponder but up to now, no success. I'm using dovecot managedsieve to set up the new filter and to my understanding it works correctly and it creates in the user's home the link .dovecot.sieve that points to sieve/managesieve.sieve ~$ cat .dovecot.sieve require ["date","relational","vacation"]; #