Paul Douglas Franklin | 1 Dec 01:48 2009

SA failed to parse

I found the following line when I ran /kolab/bin/spamassassin --lint:
warn: config: SpamAssassin failed to parse line, no value provided for 
"body", skipping: body.
1)  Has anyone information on how I could track down the reason for this 
new warning?
2)  Since it's only a warn error, will it be problematic to restart amavisd?
--Paul
--

-- 

Paul Douglas Franklin
Computer Manager
http://www.yugm.org/

/Husband of Danette/
/Father of Laurene, Miriam, Tycko, Timothy, Sarabeth, Marie, Dawnita, Anna Leah, Alexander, and Caleb/

Upgrade to the premier Office package today!

Free download here:
http://www.openoffice.org/
Paul Douglas Franklin | 1 Dec 19:18 2009

Re: SA failed to parse

Ok, I found the line with nothing but body on it.  I didn't even know I 
had edited in that part of the file.
--Paul

Paul Douglas Franklin wrote:
> I found the following line when I ran /kolab/bin/spamassassin --lint:
> warn: config: SpamAssassin failed to parse line, no value provided for 
> "body", skipping: body.
> 1)  Has anyone information on how I could track down the reason for 
> this new warning?
> 2)  Since it's only a warn error, will it be problematic to restart 
> amavisd?
> --Paul

--

-- 

Paul Douglas Franklin
Computer Manager
http://www.yugm.org/

/Husband of Danette/
/Father of Laurene, Miriam, Tycko, Timothy, Sarabeth, Marie, Dawnita, Anna Leah, Alexander, and Caleb/

Upgrade to the premier Office package today!

Free download here:
http://www.openoffice.org/
Albrecht Dreß | 2 Dec 11:37 2009

Q: automatically create a mail folder when a new user is created?

Hi all,

the subject says it all - is it possible (maybe through a hook?) to *automatically* create a folder when a
user is created?  E.g. it would be nice if automatically a "Junk" mail folder could be created.

Thanks, Albrecht.
Thorsten Schnebeck | 2 Dec 12:31 2009
Picon
Picon

forwarding should use a selected mailserver

Hi,

I would like to solve a very special problem. Some Kolab-user forward their mail to an external exchange
server. This external domain has 3 mails servers in its mx record with different metrics. Due to some very
strange relay rules the the first and second attempt to forward a mail does time-out. Only the last server
is the one that accepts incoming mails. There is no chance to change this messy setup. Its part of their
fail-back strategy.
I would like to reduce the time for forwarding to this mail domain and drop sending according to mx metrics
and want to send mails to anyuser <at> forwarddomain.net directly to the 3rd mailserver.

Question:
Is there  somewhere a magic postfix config where I can define the mailserver of a named mail domain?

Bye

  Thorsten
Alex Potter | 2 Dec 14:54 2009
Picon

Re: forwarding should use a selected mailserver

On Wednesday 02 December 2009 11:31:26 Thorsten Schnebeck wrote:
> Hi,
> 
> I would like to solve a very special problem. Some Kolab-user forward their
>  mail to an external exchange server. This external domain has 3 mails
>  servers in its mx record with different metrics. Due to some very strange
>  relay rules the the first and second attempt to forward a mail does
>  time-out. Only the last server is the one that accepts incoming mails.
>  There is no chance to change this messy setup. Its part of their fail-back
>  strategy. I would like to reduce the time for forwarding to this mail
>  domain and drop sending according to mx metrics and want to send mails to
>  anyuser <at> forwarddomain.net directly to the 3rd mailserver.
> 
> Question:
> Is there  somewhere a magic postfix config where I can define the
>  mailserver of a named mail domain?

If I have understood you correctly, you should add a line like

example.com        smtp:required_mx_.example.com

to /kolab/etc/kolab/templates/transport.template

and run kolabconf, that should do as you require.

HTH

Alex
			
(Continue reading)

Thorsten Schnebeck | 2 Dec 15:13 2009
Picon
Picon

Re: forwarding should use a selected mailserver

Am Mittwoch 02 Dezember 2009 14:54:01 schrieb Alex Potter:
> > Question:
> > Is there  somewhere a magic postfix config where I can define the
> >  mailserver of a named mail domain?
> 
> If I have understood you correctly, you should add a line like
> example.com        smtp:required_mx_.example.com
> to /kolab/etc/kolab/templates/transport.template
> and run kolabconf, that should do as you require.
> 
> HTH
> 
> Alex

works :-) Thanks a lot!

Bye

  Thorsten
Alex Potter | 2 Dec 15:35 2009
Picon

Using native apache with kolab

Currently, I have 2 instances of apache running on the machine that acts as my 
general-purpose server. (ubuntu-8.0.4). 

My kolab installation was build from the openpkg sources and the kolab 
instance of apache is configured to listen on a non-standard port for HTTP, but 
still uses 443 for HTTPS, so as not to interfere with pre-existing uses of 
apache. 

Is there something odd about kolab's default apache configuration, or would it 
be relatively easy to import the kolab-specific configuration into the other 
instance?

TIA

Alex
Richard Bos | 2 Dec 17:51 2009
Picon

Re: Using native apache with kolab

Hello Alex,

Op woensdag 02 december 2009 15:35:10 schreef Alex Potter:
> Currently, I have 2 instances of apache running on the machine that acts as
> my general-purpose server. (ubuntu-8.0.4).
>
> My kolab installation was build from the openpkg sources and the kolab
> instance of apache is configured to listen on a non-standard port for HTTP,
> but still uses 443 for HTTPS, so as not to interfere with pre-existing uses
> of apache.
>
> Is there something odd about kolab's default apache configuration, or would
> it be relatively easy to import the kolab-specific configuration into the
> other instance?

is this https://issues.kolab.org/issue3942 of any help?

--

-- 
Richard
Gunnar Wrobel | 3 Dec 09:13 2009
Picon

Re: Using native apache with kolab

Hi Alex,

Quoting Alex Potter <alex <at> ap-consulting.co.uk>:

> Currently, I have 2 instances of apache running on the machine that  
> acts as my
> general-purpose server. (ubuntu-8.0.4).
>
> My kolab installation was build from the openpkg sources and the kolab
> instance of apache is configured to listen on a non-standard port  
> for HTTP, but
> still uses 443 for HTTPS, so as not to interfere with pre-existing uses of
> apache.
>
> Is there something odd about kolab's default apache configuration,  
> or would it
> be relatively easy to import the kolab-specific configuration into the other
> instance?

The configuration should be no real problem. In former times we used a  
special LDAP authentication module but the newer apaches do not make  
this necessary anymore. So the configuration should have become more  
portable. Of course you need to extract the relevant bits for the  
different sites from the Kolab Apache configuration. This is a little  
bit of work as I don't consider our current configuration files to be  
very clean. The issue Richard mentioned relates to that.

There is one caveat though: PHP. You need to ensure that your original  
Apache provides a mod-PHP that is completely compatible with the one  
within the Kolab server. And that one has some Kolab specific patches!  
(Continue reading)

Gunnar Wrobel | 3 Dec 09:25 2009
Picon

Re: Q: automatically create a mail folder when a new user is created?

Quoting Albrecht Dreß <albrecht.dress <at> lios-tech.com>:

> Hi all,
>
> the subject says it all - is it possible (maybe through a hook?) to  
> *automatically* create a folder when a user is created?  E.g. it  
> would be nice if automatically a "Junk" mail folder could be created.

I see several options:

  - Try to use the cyrus autocreate patches. This probably means patching the
    cyrus though - I did not check if the OpenPKG package we use  
already has them
    or not.

  - Modify the kolabd daemon to create the folder once the user gets created.
    Takes a line or two of perl code - I did this for a customer recently, too.

  - Open a "wish" issue in the tracker. One could add code to kolabd  
to make such
    things configurable.

A general comment:

As far as I understood it the general rule of thumb with IMAP is: The  
clients create the folder. Automatically creating folders is probably  
not good practice. I did never really look into that issue so I'm just  
saying this was the impression I had. The user chooses his client and  
the client ensures that the IMAP storage fits the needs of the client.

(Continue reading)


Gmane