Re: [SOGo] Help needed, making a real admin tool for SOGO, needs commands.
Hello, I wrote this few months ago: https://inverse.ca/sogo/lists/arc/users/2012-10/msg00218.html Accounts management works fine. Other modules are not implemented for now. I'm interested to keep this project alive, but if nobody uses it it will surely die. It clearly lacks of documentation. If you want to test it, just tell me and I'll write it. Tell me if you're interested to test/contribute/... Source code is still here: https://github.com/rledisez/SOGoAccountsManager -- Romain LE DISEZ -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] DB Backend
To migrate a SOGo installation from PostgreSQL to MySQL (or the opposite), use sogo-tool backup / sogo-tool restore I did it last month, it works fine. Greetings. -- Romain LE DISEZ -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Change Logo
Better, in Apache config : RedirectPermanent /SOGo.woa/WebServerResources/sogo-logo.png http://webmail.example.com/my_logo.png -- Romain LE DISEZ -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGoAccountsManager - An accounts manager that integrates well with SOGo
Interesting suggestion. Can you point me in the right direction? An API documentation and a small code example would be great. Thanks. Le Lundi 15 Octobre 2012 19:48 CEST, Ludovic Marcotte lmarco...@inverse.ca a écrit: While it's quite small, you might want to consider switching to Python instead of PHP. This could give you: * direct access to SOGo objects using the Python bindings we ported a few months ago (PyObjC). Using this, you could reuse SOGo's business logic to: -- Romain LE DISEZ Support technique, Netensia Administratif Commercial : +33 811 555 005 (prix d'un appel local) Support Hébergement : +33 2 97 69 05 68 Télécopie : +33 2 97 68 14 01 -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] ANN: SOGoAccountsManager - An accounts manager that integrates well with SOGo
SOGo Users, I am pleased to announce SOGoAccountsManager, a new project that aim to provide a SOGo user interface to manage users accounts. Before going to the technical informations, let's see some screenshots and a short screencast: - http://web.ledisez.net/sogo-accounts-manager/screenshot1.png - http://web.ledisez.net/sogo-accounts-manager/screenshot2.png - http://web.ledisez.net/sogo-accounts-manager/screenshot3.png - http://web.ledisez.net/sogo-accounts-manager/screenshot4.png - http://web.ledisez.net/sogo-accounts-manager/screenshot5.png - http://web.ledisez.net/sogo-accounts-manager/screenshot6.png - http://web.ledisez.net/sogo-accounts-manager/screencast1.mp4 SOGoAccountsManager is composed by two (unamed) subprojects: the backend and the frontend. The backend is developed in PHP, using the Slim Framework[1]. It is modular so you can adapt it to your users database (LDAP, SQL, ...). It is a small piece of code, less than 600 lines of real code. The frontend is developed using SproutCore[2]. So it is fully Javascript and only runs in the browser. Frontend and backend communicate via a REST interface. SOGoAccountsManager reuses the cookie of SOGo, so there is no need to re-authenticate. SOGoAccountsManager is not features complete for now. It is stable enought to be tested for accounts management. Domains management, Mail groups management, etc... are not developed for now. As soon as accounts management will be rock solid, it will be easy to continue the development. It is like an alpha 1 release. There is no real documentation for now. Basically: 1/ Place backend/ on your SOGo server (eg: in /srv/www/webmail.example.com/SOGoAccountsManager/) 2/ Extract Slim Framework (tested with last stable, v2.1) and Zend Framework (tested with last stable, v2.0.2) in one of the PHP includes path: - /usr/share/php on RHEL6/CentOS6 - [...]/backend/library/ 3/ Edit [...]/backend/application/config.php 4/ Build the frontend with the SproutCore tools and upload it to your server (eg: /srv/www/webmail.example.com/SOGoAccountsManager/static/) 5/ Put this in your Apache config BEFORE the SOGo config: ProxyPass /SOGo/AccountsManager ! Alias /SOGo/AccountsManager/api/ /srv/www/webmail.ledisez.net/SOGoAccountsManager/backend/www/index.php/ Alias /SOGo/AccountsManager /srv/www/webmail.ledisez.net/SOGoAccountsManager/static/sogo_accounts_manager/en/b26d3251b668789fa394b64f087d2f238e73ed65 Alias /static /srv/www/webmail.ledisez.net/SOGoAccountsManager/static SOGoAccountsManager is an open source software released under the AGPLv3: https://github.com/rledisez/SOGoAccountsManager Any kinds of feedbacks/contributions will be greatly appreciated. Best regards. [1] http://www.slimframework.com/ [2] http://sproutcore.com/ -- Romain LE DISEZ -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Header reply-to is null
Hi all, i'm facing a strange bug, some emails sent with SOGo contains the header reply-to: null. When it happens, SOGo displays Reply-To: null@unspecified-domain. I'm unable to reproduce the bug. It seems to happen randomly. There is nothing interesting in the logs. My configuration (CentOS 5): - SOGo 1.3.17 - Sendmail 8.13 - Cyrus 2.3 I'm pretty sure Sendmail is not the problem because in the folder Sent of the sender, the mail has the reply-to: null header. Have you already seen this bug? Greetings. -- Romain LE DISEZ -- users@sogo.nu https://inverse.ca/sogo/lists
Re: Browser cache and upgrades (Was: Re: [SOGo] ANN: SOGo v1.3.15)
Hi all, Le Vendredi 18 Mai 2012 18:40 CEST, Jean Raby jr...@inverse.ca a écrit: However, if SOGo is _not_ restarted after the upgrade, the client will see a mostly empty page. sogod should be automatically restarted after an upgrade. That's how packages work in RHEL (eg: httpd, postgresql) and Debian. A small patch is attached for RHEL. It is not tested, but it should work. -- Romain LE DISEZ -- users@sogo.nu https://inverse.ca/sogo/lists patch-sogo_restart_after_upgrade.diff Description: Binary data
Re: [SOGo] Using SOGo behind a router
Hi Tim, a better description of the problem than it does not work could help. But, here is my idea. When configuring a SOGo server, you configure Apache to set some headers that indicate to SOGo the URL/port used for the connection. If it work internally, you probably set those headers: RequestHeader set x-webobjects-server-port 80 RequestHeader set x-webobjects-server-name 192.168.1.3 RequestHeader set x-webobjects-server-url http://192.168.1.3; But these values are incorrects when accessing from the outside. Try to change these values with the outside URL / port: RequestHeader set x-webobjects-server-port 665 RequestHeader set x-webobjects-server-name 140.134.120.134 RequestHeader set x-webobjects-server-url http://140.134.120.134:675; If it works, you found the problem. The fix is to create two vhosts in Apache. You can also use a generic configuration (but for the port forwarding, you must have inside port = outside port). See the diff attached for a generic Apache configuration (generated on a CentOS, can't guarantee it is applicable on a Debian). Greetings. Le Samedi 07 Avril 2012 13:54 CEST, Kniggedigge kniggedi...@freenet.de a écrit: Hi Marc, hi Christian, sry for not describing my setup in detail: Lets say the subnet behind the router is something like: 192.168.1.0/24 The WAN in which the router is placed is the 140.134.120.134 subnet. When I try to connect to SOGo via lightning or webinterface in the subnet (192.168...) everything works. But when I connect to the subnet via port forwarding through the router (port 675 is forwarded to the internal address of the SOGo server (say its 192.168.1.3) on port 80) it does not work. How should a setup look like to fully connect with the SOGo server from outside (140.134.12)? Thanks in advance and happy easter, Tim Am 05.04.2012 um 11:49 schrieb Christian Mack: Hello Tim Am Donnerstag, 05. April 2012 11h:10m CEST, Kniggedigge kniggedi...@freenet.de schrieb: I just tried to use SOGo behind a router in a subnet. When I'm accessing SOGo in the subnet, there's no problem. But when I try to access SOGo from the WAN, the address is always rewritten. Is there anybody who figured out how to configure apache, so that it is possible to access SOGo from the outside? Obviously your Router uses NAT. So it always rewrites the IP of the Sender to its own. And in order to reach your server behind it, you have to use the IP of your router instead of the IP of your SOGo server. That's how NAT works! You could use the same DNS name from inside and outside, if you use split DNS. This means, if you search with the DNS name of your SOGo server, you have to provide to the Internet the IP of your router and for your subnet you provide the IP of your real SOGo server. This only works with 2 DNS servers with different information, which must be kept synchronized. Kind regards, Christian Mack -- Christian Mack Rechenzentrum Universitauml;t Konstanz mailto:christian.m...@uni-konstanz.de http://www.rz.uni-konstanz.de/ -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists -- Romain LE DISEZ Support technique, Netensia Administratif Commercial : +33 811 555 005 (prix d'un appel local) Support Hébergement : +33 2 97 69 05 68 Télécopie : +33 2 97 68 14 01 -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] User-Prefs resetted after DB-Schema-Update and SOGo-Update to 12c?
Hi Francis, Le mercredi 15 février 2012 à 14:31 -0500, Francis Lachapelle a écrit : Which version of PostgreSQL do you use? CentOS 5 postgresql-server-8.1.23-1.el5_7.3 -- Romain LE DISEZ romain.ledi...@netensia.fr -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] User-Prefs resetted after DB-Schema-Update and SOGo-Update to 12c?
Le jeudi 16 février 2012 à 06:26 -0500, Ludovic Marcotte a écrit : On 16/02/12 04:17, Martin Rabl wrote: Does the error depends on the database and its version? It might be related to http://www.sogo.nu/bugs/view.php?id=1551 Try updating only sope-gdl1-postgresql to the upcoming nightly and report in the ticket your findings. I upgraded to postgresql 8.4. It seems it solved the problem. Need to be confirmed in the next hours. I can't test more on this server, it was almost a civil war at my customer's office ;-) -- Romain LE DISEZ Support technique, Netensia Administratif Commercial : +33 2 97 47 00 07 Support Hébergement : +33 2 97 69 05 68 Télécopie : +33 2 97 68 14 01 -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] User-Prefs resetted after DB-Schema-Update and SOGo-Update to 12c?
I'm on 1.3.12c with PgSQL database. Users are loosing their preferences without touching them. Since I restored the database : * I checked that the sogo_user_profile.c_defaults has changed * I'm pretty sure users didn't change preferences because there is no POST like this in the logs : POST /SOGo/so/$USER/preferences Le mercredi 15 février 2012 à 15:10 +0100, Romain LE DISEZ a écrit : I have the same bug. It is really problematic as all signatures are lost, SIEVE rules are lost and deleted from the server, etc... Is it related to this in changelog for 1.3.12b ? 2012-02-14 Wolfgang Sourdeau wsourd...@inverse.ca * SoObjects/SOGo/SOGoSQLUserProfile.m (_sqlJsonRepresentation:): removed obsolete method. (-storeJSONProfileInDB:): we now properly escape the stored value via the adaptor methods and by using a hacking EOAttribute instance (FIXME). I restaured table sogo_user_profile and asked users to not change their preferences until the server is updated. Le mercredi 15 février 2012 à 07:35 -0600, Donny Brooks a écrit : On 2/15/2012 5:03 AM, Martin Rabl wrote: Hi, I did a update to 1.3.12c (SOGo was before on 12a), and with 12a I did the suggested mysql-schema-update via bash-script. After update to 12c I logged into the calendar and found all my calendars colored in grey (instead of my wellsorted colors ;-) ), the subcribed calendar vanished into thin air ;-) and the user preferences reset to default. Maybe I did something wrong, but what was the mistake? Is it possible that the database schema update has some effects to the user prefs? I looked into the script and see no further cruelties ... I cannot imagine it, but is it possible that the update to 12c has some effects to the user prefs like resetting or something? We too saw this but it was said only the users that had saved their preferences back to the server would have experienced this bug. As of 5pm yesterday I still had no preferences yet my supervisor still had all hers. We both had been on all day. Now I am tasked with having to locate all the users that were affected and have them redo their preferences and see if they stick. That should be fun. Donny B. -- Romain LE DISEZ Support technique, Netensia Administratif Commercial : +33 2 97 47 00 07 Support Hébergement : +33 2 97 69 05 68 Télécopie : +33 2 97 68 14 01 -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] TR: SOGo internet access
An other option. Replace the proxy section with this one :
Proxy http://127.0.0.1:2/SOGo
RewriteEngine On
RewriteBase /
RewriteRule .* -
[E=SOGO_HTTP_SCHEME:http,E=SOGO_HTTP_HOST:%{HTTP_HOST},E=SOGO_SERVER_PORT:%{SERVER_PORT},NE]
RewriteCond %{HTTPS} =on
RewriteRule .* - [E=SOGO_HTTP_SCHEME:https,NE]
## adjust the following to your configuration
RequestHeader set x-webobjects-server-port %{SOGO_SERVER_PORT}e
RequestHeader set x-webobjects-server-name %{SOGO_HTTP_HOST}e
RequestHeader set x-webobjects-server-url
%{SOGO_HTTP_SCHEME}e://%{SOGO_HTTP_HOST}e
## When using proxy-side autentication, you need to uncomment and
## adjust the following line:
# RequestHeader set x-webobjects-remote-user %{REMOTE_USER}e
RequestHeader set x-webobjects-server-protocol HTTP/1.0
RequestHeader set x-webobjects-remote-host %{REMOTE_HOST}e env=REMOTE_HOST
AddDefaultCharset UTF-8
Order allow,deny
Allow from all
/Proxy
This configuration will work for every host and every port you use. I use it as
a standard configuration for small deployment or multi-domains deployment.
Le Mardi 20 Décembre 2011 21:11 CET, Paul van der Vlis p...@vandervlis.nl a
écrit:
Op 20-12-11 20:51, Daniel Müller schreef:
I myself tried the same wioth SOGo. And it did not work as it should.
The problem I think is that SOGo itself has a redirected rule in apaches
sogo.conf. And ist is difficult to redirect this rule again so it can fit
with the local network too.
I am using a setup what I've described here: http://wiki.debian.org/SOGo
I can switch between port 443 and port 80. I don't use sogo.conf, see my
apache setup at the end of the page.
With regards,
Paul van der Vlis.
--
Paul van der Vlis Linux systeembeheer Groningen
http://www.vandervlis.nl
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
Romain LE DISEZ
--
users@sogo.nu
https://inverse.ca/sogo/lists
[SOGo] Connect SOGo to memcached and pgsql with unix socket
Hello all, just a little tip, it could be useful to someone. Problem with memcached is that there is no access control. You can force memcached to bind to 127.0.0.1, but it's a poor option because every process can access it. With UNIX socket, you can strictly restrict access to memcached. Run memcached (use the configuration file of your distrib): memcached -d -u sogo -s /tmp/memcached.sock -a 0700 And update the configuration of SOGo: defaults -u sogo write sogod SOGoMemcachedHost /tmp/memcached.sock You can also use UNIX socket for PostgreSQL. On EL6, by default, the UNIX socket of PostgreSQL is in /tmp: /tmp/.s.PGSQL.5432 So, set your configuration as following: defaults -u sogo write sogod OCSFolderInfoURL postgresql://%2Ftmp/sogo/sogo_folder_info defaults -u sogo write sogod OCSSessionsFolderURL postgresql://%2Ftmp/sogo/sogo_sessions_folder defaults -u sogo write sogod SOGoProfileURL postgresql://%2Ftmp/sogo/sogo_user_profile /!\ WARNING /!\ You can't update the PostgreSQL URL without updating the content of the table sogo_folder_info. Please note that: - thanks to ident, you don't need to specify user and password if the database owner is sogo. - You must only specify the folder containing the socket file, replacing / with %2F Greetings. -- Romain LE DISEZ romain.ledi...@netensia.fr smime.p7s Description: S/MIME cryptographic signature
Re: [SOGo] NGImap4ParserException
Hi Wolfgang, Le jeudi 24 mars 2011 à 09:57 -0400, Wolfgang Sourdeau a écrit : I fixed the bug this morning. You will need to update sope49-mime from the next nigthly builds. can I help you, one way or another, to fix this bug ? Thanks for your attention, Greetings. -- Romain LE DISEZ smime.p7s Description: S/MIME cryptographic signature
Re: [SOGo] NGImap4ParserException
Le lundi 04 avril 2011 à 09:34 -0400, Wolfgang Sourdeau a écrit : I have fixed two problems related to this issue last week. Can you try again by updating the nightly sope-mime package? I did it one hour ago, just before sending the mail. No progress, still the same error message :-( catched IMAP4 parser exception NGImap4ParserException: unsupported fetch key: nil Greetings. -- Romain LE DISEZ smime.p7s Description: S/MIME cryptographic signature
Re: [SOGo] NGImap4ParserException
Hi Wolfgang, I'm facing the exact same problem on a Debian 6 : # dpkg -l | grep -E (sogo|sope|dbmail) ii dbmail 2.2.11-1+b1 ii dbmail-mysql2.2.11-1+b1 ii libsope-appserver4.94.9.r1664.20110127 ii libsope-core4.9 4.9.r1664.20110127 ii libsope-gdl1-4.94.9.r1664.20110127 ii libsope-ldap4.9 4.9.r1664.20110127 ii libsope-mime4.9 4.9.r1664.20110127 ii libsope-xml4.9 4.9.r1664.20110127 ii sogo1.3.5a ii sope4.9-gdl1-mysql 4.9.r1664.20110127 ii sope4.9-libxmlsaxdriver 4.9.r1664.20110127 I can provide you a PCAP file and a log file. Are you still working on this ? Greetings. Le mardi 30 novembre 2010 à 17:15 -0500, Wolfgang Sourdeau a écrit : I will need the full sniff log but redirected into a file. Send it to me privately and keep the email adresses there as they might be part of the problem. The log you sent is incomplete because it only contains responses to commands that are not even listed... -- Romain LE DISEZ smime.p7s Description: S/MIME cryptographic signature
Re: [SOGo] Nightly DEBS not working
Hi, same for the debian packages. There is no sogo directory : http://inverse.ca/debian-nightly/pool/lenny/s/ Greetings. Le mardi 28 septembre 2010 à 18:41 +0200, Martin Lehmann a écrit : Hi, the build process of the nightly RPMs works only partially. The SOGo-RPMs aren't created! Only RPMs for SOPE and libraries. See: http://inverse.ca/downloads/SOGo/CentOS5/nightly/x86_64/RPMS/ Thx, Martin -- Romain LE DISEZ / Netensia -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Order of SIEVE directives
Hello all,
it is currently impossible to disable the vacation message for one
specific sender because the vacation section is placed before the rules
section :
require [vacation,fileinto];
if allof ( ... ) {vacation :days 7 :addresses [lo...@example.com]
text:
Bla
.
;
}
if anyof (address :contains [to, cc] users@sogo.nu) {
fileinto Mailing lists.sogo;
}
elsif anyof (address :is from no_vacat...@example.com) {
stop;
}
By inverting the two sections, no_vacat...@example.com will not receive
vacation message :
require [vacation,fileinto];
if anyof (address :contains [to, cc] users@sogo.nu) {
fileinto Mailing lists.sogo;
}
elsif anyof (address :is from no_vacat...@example.com) {
stop;
}
if allof ( ... ) {vacation :days 7 :addresses [lo...@example.com]
text:
Bla
.
;
}
Is it possible that theses two sections be inverted ? Second option is
to create a field for exceptions.
Should I fill a ticket ?
We have this need because we have a ticketing system that sends
automaticaly mails, it could create a loop.
Greetings.
--
Romain LE DISEZ / Netensia
--
users@sogo.nu
https://inverse.ca/sogo/lists
Re: [SOGo] IMAP connections interface scalability
Hello, Le lundi 20 septembre 2010 à 19:03 +0300, Tomas Kuliavas a écrit : 1/ Can you confirm that SOGo keeps the IMAP connections open (opposed to PHP webmail which opens/closes a connection at each request) ? How long the connections are kept open ? Why do you ask? Check your IMAP logs. It is not clear how it works. On some servers, the connections stay open for 10 minutes (v1.3.0). On other servers, connections are closed immediatly (v1.3.1). That's the reason I ask this. Related question: is there a param to change the timeout I observed ? Greetings. -- Romain LE DISEZ / Netensia -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] IMAP connections interface scalability
Hi all, no answers ? :-( Greetings. Le jeudi 09 septembre 2010 à 16:16 +0200, Romain LE DISEZ a écrit : 1/ Can you confirm that SOGo keeps the IMAP connections open (opposed to PHP webmail which opens/closes a connection at each request) ? How long the connections are kept open ? 2/ When mailboxes are full (quota = 100%), users can not delete emails because SOGo tries to copy the email to the Trash. Is there a way to workaround that (eg: directly delete emails) ? 3/ If there are simultaneously 100 HTTP requests to SOGo, how many workers do you recommend ? Can a worker handle multiples requests at a time ? -- Romain LE DISEZ / Netensia -- users@sogo.nu https://inverse.ca/sogo/lists
