Thomas Baumann | 25 Nov 11:05 2014
Picon

forward-only e-Mail Address (with regex?)

Hello all,

how can a forward only e-Mail Address being created in Kolab 3?

(1) All Mails to


should get delivered to

support <at> otherdomain.com (on another server).

(2) Is this possible with regex?

E.g. support.(.*) <at> mydomain.com

should be delivered to

support <at> \1-otherdomain.com

(where \1 contains the match of the .*)

Best regards,
Thomas.
_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Edison Jackson | 24 Nov 19:50 2014
Picon

How set something

How set something:

1. I want to add new domains
    E.g. root domain: xxx <at> domain1.com | new domain: xxx <at> new.com


2. How to setup SMTP, POP, IMAP servers?
    E.g. root domain: smtp/pop/imap.domain1.com | new domain: smtp/pop/imap.new.com
_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Friedemann Schorer | 24 Nov 19:03 2014

Kolab <-> UCS 4.0

Hi!

As I didn't find anything while searching - can anyone point me to a resource that might tell when Kolab will be available for Univention Corporate Server v4.0?

 

Thanks in advance,

 

 

Friedemann 

 

--
I respect your position, Professor - I just don't share it.
_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
hiddenBit | 24 Nov 11:09 2014

kolab_smtp_access_policy exit status 1

Hi list users,

the last days I struggled with a clean kolab installation at a wheezy debian. After "setup-kolab" I just added my external domains as additional domains to the default domain.

Unfortunately I am unable to send and receive e-mails due to the follow mail.log messages.

(sending mail to external)
Nov 23 18:12:03 postfix/submission/smtpd[8377]: connect from localhost[127.0.0.1]
Nov 23 18:12:04 postfix/spawn[8380]: warning: command /usr/lib/postfix/kolab_smtp_access_policy exit status 1
Nov 23 18:12:04 postfix/submission/smtpd[8377]: warning: premature end-of-input on private/submission_policy while reading input attribute name
Nov 23 18:12:05 postfix/spawn[8380]: warning: command /usr/lib/postfix/kolab_smtp_access_policy exit status 1
Nov 23 18:12:05 postfix/submission/smtpd[8377]: warning: premature end-of-input on private/submission_policy while reading input attribute name
Nov 23 18:12:05 postfix/submission/smtpd[8377]: warning: problem talking to server private/submission_policy: Connection reset by peer
Nov 23 18:12:05 postfix/submission/smtpd[8377]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 451 4.3.5 Server configuration problem; from=<mail <at> additional-domain.tld> to=<external-test <at> gmail.com> proto=ESMTP helo=<5.45.99.123>
Nov 23 18:12:05 postfix/submission/smtpd[8377]: disconnect from localhost[127.0.0.1]

I just removed the policy checks from the main.cf and got the mails flowing, but that couldn't be the way to go. :-\

Can you give me any hints, how to debug the "kolab_smtp_access_policy"?

I got a message on the kolab log, but not sure, if this belongs to my issue.

2014-11-23 21:23:48,227 pykolab.imap ERROR Could not rename user/mail.biz/Archive <at> localdomain.tld to reside on partition archive

Regards,
Mathias


_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Matt . | 24 Nov 13:21 2014
Picon

IPA Mailalias

Hi,

My setup, with IPA does recognize the mailaddress of the user, which
is nice and should be working as well.

My next target is adding more mailaddresses to a user and have them
recognized by my setup and delivered to that user as well in his
existing mailbox.

As the mailaddress of a user using IPA/Kolab is bound to his username
for IPA, I get some not so nice emailaddresses, there for the aliases
I want to have working.

Any people know where to start or have some ideas ?

Thanks!

Matt
Henning | 24 Nov 08:37 2014
Picon

Roundcubemail and kolab dynamic distribution lists

Hi,

does anyone work yet with dynamic distribution lists? I cannot get them
to work with roundcubemail. The group ist displayed, but seems to be empty.

LDAP:
# Service Users, Groups, domain.com
dn: cn=Service-Users,ou=Groups,dc=domain,dc=com
cn: Service-Users
memberURL:
ldap://localhost/ou=People,dc=domain,dc=com??sub?(authorizedservice=service)
mail: service-users <at> domain.com
objectClass: top
objectClass: groupofurls
objectClass: kolabgroupofuniquenames

Roundcubemail says on loading the dynamic list:
C: Read cn=Service-Users,ou=Groups,dc=domain,dc=com [(objectClass=*)]
S: OK
C: Close

Sending messages to service-users <at> domain.com works though (locally
delivered).

Any thoughts here? I copied the config from my old roundcubemail setup,
so maybe there is some missing value here somewhere?

Best
Henning
Henning | 24 Nov 08:24 2014
Picon

Re: Kolab 3.1: LDAP-Verzeichnis im Thunderbird-Adressbuch

Hallo,

ein paar mehr Informationen wären nett.

Was sind denn deine "alten Einstellungen"? Versuche von deinem
Thunderbird-Rechner eine einfache ldapsuche ohne Thunderbird. Kannst du
deinen Server überhaupt auf Port 389 oder 636 erreichen (telnet)?

Viele Grüße
Henning

Am 21.11.2014 um 14:41 schrieb Wolfgang Rothermich:
> Hallo zusammen,
> 
> wir haben die Migration von Kolab 2.2 auf 3.1 nahezu abgeschlossen. Ich
> wollte jetzt in Thunderbird-Adressbuch das LDAP-Verzeichnis vom alten
> Kolab-Server auf den neuen umstellen. Die Einstellungen habe ich analog
> zum alten Kolab2-Server gewählt. Ich bekomme zwar keine Fehlermeldungen,
> aber auch keine Treffer.
> 
> Gibt es hierzu eine Dokumentation? Im Netz bin ich leider nicht fündig
> geworden.
Mark Berndt | 21 Nov 11:52 2014
Picon

bulk update of secondary email address

Hello,  I have hundreds of email aliases to migrate from kolab 2 to kolab 3 

secondary email addresses. This kolab instance has only a few users, but many aliases per user.

 

In kolab 2 web admin the email alias was a list box that allowed block cut and paste.  Kolab 3 is not so easy.

 

What is the best way to import these aliases?

 

Thanks

Mark Berndt

_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Tom Reijnders | 23 Nov 16:57 2014
Picon

Process .forward on Kolab 3.3

L.S.,

I need to be able to process .forward files for a specific kolab user 
(the mail needs to be sent to a command).

I created a local user on the linux box, created a kolab user, and 
created a .forward file in the home folder of the user.

This used to work in Kolab 2, but now the .forward file is NOT 
processed. How can I enable .forward processing?

Tom

--

-- 
--

Tom Reijnders
TOR Informatica
Chopinlaan 27
5242HM Rosmalen
Tel: 073 5226191
Fax: 073 5226196
Matt . | 23 Nov 16:20 2014
Picon

Mailbox does not exists after login

It seems that the mailbox for a user is not created after login.

I get this in a debug log:

[LIST] No results
2014-11-23 15:57:31,815 pykolab.imap DEBUG [29883]: Looking for folder
'user/uid <at> domain.tld', we found folders: []
2014-11-23 15:57:31,815 pykolab.imap INFO Waiting for the Cyrus IMAP
Murder to settle...
  57:32.31 > GKOP11 LIST "" "user/uid <at> domain.tld"
  57:32.31 < GKOP11 OK Completed (0.000 secs)
  57:32.31      matched r'(?P<tag>GKOP\d+) (?P<type>[A-Z]+)
(?P<data>.*)' => ('GKOP11', 'OK', 'Completed (0.000 secs)')
[LIST] No results
2014-11-23 15:57:32,319 pykolab.imap DEBUG [29883]: Looking for folder
'user/uid <at> domain.tld', we found folders: []
2014-11-23 15:57:32,319 pykolab.imap INFO Waiting for the Cyrus IMAP
Murder to settle...
^C

I have read that cyrus should not be able to login when it doesn't
have the default domain from the ldap server.

My setup is:

ldap: dc=sub,dc=comp,dc=local

and my users have uid <at> domain.tld as their domainname.

in my ldap (ipa I have)

# kolab, config
dn: cn=kolab,cn=config
objectClass: top
objectClass: extensibleobject
cn: kolab

# example.org, kolab, config
dn: associateddomain=example.org,cn=kolab,cn=config
objectClass: top
objectClass: domainrelatedobject
objectClass: inetdomain
associatedDomain: dc=sub,dc=comp,dc=local
associatedDomain: example.org
inetDomainBaseDN: dc=sub,dc=comp,dc=local

Any idea on this ?
Matt . | 22 Nov 17:03 2014
Picon

SMTP-failure: [554] 5.7.1 <DATA>: Data command rejected: Unverifiable sender.

Hi guys,

What can cause this issue when sending an email from Roundcube when I
use an associated domain ?

I used the Multidomain howto but I still get this on sending an email.

SMTP-failure: [554] 5.7.1 <DATA>: Data command rejected: Unverifiable sender.

Any idea on this ?

Cheers,

Matt

Gmane