Andrew Richey | 2 Jul 14:22 2007
Picon

ingo - vacation question

Hey guys,

I posted this to the horde mailing list.  Should have realized there was one specific to ingo, so I'm
reposting here.

Just a quick rundown of what I'm using:

Horde: 3.1.4
Imp: H3 (4.1.4)
Ingo: H3 (1.1.3)

On FreeBSD 6.2, presumably using the built in vacation program.

Doesn't seem like I can find the vacation options in filters.  Just whitelist and blacklist.  When I attempt
to go directly to horde/ingo/vacation.php I get this error:    "Vacation is not supported in the current
filtering driver"

Is there a way to update this driver?  If so, does it matter if my webmail server and mail servers are separate? 
Any help on this would be greatly appreciated!

-Andrew

--

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Eric Jon Rostetter | 3 Jul 07:06 2007
Picon

Re: ingo - vacation question

Quoting Andrew Richey <richey@...>:

> Doesn't seem like I can find the vacation options in filters.  Just   
> whitelist and blacklist.  When I attempt to go directly to   
> horde/ingo/vacation.php I get this error:    "Vacation is not   
> supported in the current filtering driver"

Sounds like you didn't select a backend driver that supports vacation
messages.

> Is there a way to update this driver?

Either you picked the wrong driver, or the drive you picked doesn't support
vacation, IMHO.

> If so, does it matter if my  webmail server and mail servers are  
> separate?  Any help on this  would be greatly appreciated!

Depends on the backend.

> -Andrew
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
(Continue reading)

Eric Jon Rostetter | 3 Jul 17:49 2007
Picon

Re: ingo - vacation question

Quoting Andrew Richey <richey@...>:

>    Figured I'd just reply to you as you're the only one who has
> responded.  Appreciate it, by the way. :-)

Yeah, but keep it on the list.  Others will reply eventually, or if needed.
Sometimes we're all just busy...

>    Forgive my ignorance on this, but I've no idea how to select a
> backend driver or even what backend driver it's referring to.  Is this
> something I can change in the backend.php file?

Yes, in ingo/config/backends.php, you select a driver (e.g. timsieved,
vfs, etc) and a script (e.g. imap, maildrop, procmail, sieve, etc).

The combination of these determines what functions are available to you.

> I haven't been able to
> find directions on this anywhere.  Believe me, I looked for a while
> before posting to the mailing list.  -  I've scoured the Horde page for
> detailed directions on configuring Ingo, but haven't found anything.
> Know if anything exists out there?

No, I don't know if anything exists other than the mailing list for help.

>    This is a default installation of Horde Groupware Webmail, by the
> way.  Running on FreeBSD 6.2.  And FreeBSD does support .forward
> vacation messages (at the moment we create them manually for people who
> request them).  I assume that our webmail, running on a different
> server, should be able to access and create .forward/.vacation.msg
(Continue reading)

Andrew Richey | 3 Jul 20:16 2007
Picon

Re: ingo - vacation question

    Thanks Eric, appreciate the help.  I've been playing around with 
sork this afternoon, and that seems to work well.  I've one issue, but 
will direct it to the sork mailing list.

Eric Jon Rostetter wrote:
> Ingo doesn't, AFAIK, support using .forward files.  For that, you should
> look at sork/forwards instead.  However, Ingo does support procmail (I
> myself migrated from sork with .forward files to ingo with procmail,
> even though I "created" the sork modules).  So if you can use procmail,
> that is a viable option.
>
> Otherwise, if you must use .forward files, you might have to use sork
> (forwards and vacations) instead.  Sork isn't as flexible as 
> ingo+procmail
> though.
>
> I'n not sure why there isn't a "ftp" method for ingo to support the
> normal unix file vacation and sendmail forwarding... (probably just no
> one has written one yet?)  There are some difficulties with doing this
> process, but it should probably still be done someday.
>
> If you can, I'd suggest using the procmail driver.  If you can't (your
> system doesn't support procmail), then I'd suggest either you switch to
> the sork modules, or you sponsor a bounty to have ingo handle this type
> of setup.

--

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
(Continue reading)

patrick | 25 Jul 21:23 2007
Picon

Huge Horde/IMP/Ingo size rule bug

I'm not finding exactly where this is happening, but somewhere there
is an option to set a rule for any header matching something. I
suspect it happens when you click on the blacklist option, but what's
happening is a rule for every header is created including one that
looks like:

Size is greater than "some text search string"

When this is processed, it evaluates to true, as the value is simply
cast to a float which becomes 0. The size of a message will always be
greater than zero, so this always returns true. The default action for
blacklisted messages is to delete it, so all messages are getting
deleted.

Has anyone else come across this bug?
Jan Schneider | 26 Jul 10:44 2007

Re: Huge Horde/IMP/Ingo size rule bug

Zitat von patrick <gibblertron@...>:

> I'm not finding exactly where this is happening, but somewhere there
> is an option to set a rule for any header matching something. I
> suspect it happens when you click on the blacklist option, but what's
> happening is a rule for every header is created including one that
> looks like:
>
> Size is greater than "some text search string"
>
> When this is processed, it evaluates to true, as the value is simply
> cast to a float which becomes 0. The size of a message will always be
> greater than zero, so this always returns true. The default action for
> blacklisted messages is to delete it, so all messages are getting
> deleted.
>
> Has anyone else come across this bug?
> --
> Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: ingo-unsubscribe@...
>

Please create a ticket on http://bugs.horde.org/.

Jan.

--

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
(Continue reading)

Chr. v. Stuckrad | 29 Jul 14:26 2007
Picon
Picon

URGENT Compatibility Problem between Cyrus and Ingo (Whitelist sieve)

Hi!

I'm new to the list, because I'm postmaster of {math/inf/mi}.fu-berlin.de
and we recently installed a cyrus mailstore and then ingo to generate
sieve filter rules in/on that cyrus.

Way to late I realized a semantic incompatibility between the two
following installed methods (1,2) of delivering our mail:

What happens is:

1) the MTA puts Spam (tagged by spamassassin) into <USER+spam <at> mailstore>
which cyurus interprets as
- "if not filtered elsewhere, put into Box named 'spam' foer USER"

2) INGO creates a 'whitelist' using  sieve clause which does (something like)
- "if ...adress... is ...in.... then ***keep***"

3) This 'keep' is interpreted by cyrus/sieve as
- "do the default action, as if there was no sieve script"

The result is - *NO* WHITELIST - any more, because "keep" results in
accepting the MTA's default "+spam".  Of course Uers complain ;-)

Now I seem to have two ways out
A) eighter revoking the whole concept of letting the MTA decide on '+spam',
   THEN I'd need a default ingo script/database-entry per User
   *pre*installed to have the spamfilter on-by-default, or
B) I somehow patch the 'whitelist-Sieve-Script' to
   use 'fileinto INBOX' instead of 'keep' to safely avoid false-positives.
(Continue reading)

Jan Schneider | 31 Jul 14:17 2007

Re: URGENT Compatibility Problem between Cyrus and Ingo (Whitelist sieve)

Zitat von "Chr. v. Stuckrad" <stucki@...>:

> Hi!
>
> I'm new to the list, because I'm postmaster of {math/inf/mi}.fu-berlin.de
> and we recently installed a cyrus mailstore and then ingo to generate
> sieve filter rules in/on that cyrus.
>
> Way to late I realized a semantic incompatibility between the two
> following installed methods (1,2) of delivering our mail:
>
> What happens is:
>
> 1) the MTA puts Spam (tagged by spamassassin) into <USER+spam <at> mailstore>
> which cyurus interprets as
> - "if not filtered elsewhere, put into Box named 'spam' foer USER"
>
> 2) INGO creates a 'whitelist' using  sieve clause which does (something like)
> - "if ...adress... is ...in.... then ***keep***"
>
> 3) This 'keep' is interpreted by cyrus/sieve as
> - "do the default action, as if there was no sieve script"
>
> The result is - *NO* WHITELIST - any more, because "keep" results in
> accepting the MTA's default "+spam".  Of course Uers complain ;-)

I'm not sure I was able to follow you completely, but from what you  
write the result should be "no spam filtering anymore", and only  
whitelisted addresses should be affected, which is the expected  
behaviour.
(Continue reading)


Gmane