RE: [SOGo] Maximal value length for user-preferences set defaults?
Hi Christian, I knew this issue, but I did not connect it with sogo-tool. I thought this only describes that a sieve script can only have a maximal length. Thanks for this information. Regards, Malte -Original Message- From: Christian Mack [mailto:christian.m...@uni-konstanz.de] Sent: Donnerstag, 5. April 2012 09:41 To: m_bru...@cs.uni-kl.de Cc: users@sogo.nu Subject: Re: [SOGo] Maximal value length for user-preferences set defaults? On 2012-04-04 23:09, Malte Brunnlieb wrote: Hi, i am currently working on a perl script which reads existing roundcube sieve scripts and provides the rules to sogo by calling sogo-tool user-preferences set defaults... Unfortunaltely some sieve scripts are very large and everytime I want to insert the converted rules to sogo, I got a JSON parse exception. So I validated my inputs but nothing is wrong with it. I tried some rules which could be problematic, but all of them work. I recognized that at some point, where the parameter to be set for SOGoSieveFilters gets very large, the JSON parse exception occurs. It seems like the input gets cut at some number of literals, isn't it? Is this a bug as I could not insert more than some number of literals as sieve scripts using sogo-tool? Not just with sogo-tool. It also doesn't work when using the SOGo Webfrontend see Bug #1569 http://www.sogo.nu/bugs/view.php?id=1569 Should be fixed in the next GNUStep version. Kind regards, Christian Mack -- Christian Mack Gruppe Informationsdienste Rechenzentrum Universität Konstanz -- users@sogo.nu https://inverse.ca/sogo/lists
AW: [SOGo] Sort messages by threads
Hi, I posted a bug report as I think this is an unintended behavior which should be fixed. http://www.sogo.nu/bugs/view.php?id=1683 Greetings, Malte -Ursprüngliche Nachricht- Von: Pablo Barrachina [mailto:pa...@digitalvalue.es] Gesendet: Montag, 26. März 2012 11:35 An: users@sogo.nu Betreff: [SOGo] Sort messages by threads Hi, When using down Sort messages by threads new message dont float, and then new entries for a topic go down the list of messages beneath the original message. And this is a problems when receiving many mails. In iphone for instante, new messages float topics and threads get ordered by last update time. I belive this update time order is preferable when sorting by thread. Is that possible in Sogo? Many thanks in advance for your help = Pablo Barrachina pa...@digitalvalue.es www.digitalvalue.es Tel: +34 963 162 089 Fax: +34 963 738 507 -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
AW: [SOGo] Problems while importing sieve rules
Hi,
I moved some steps forward. I eliminated the proxy problem when saving my
web preferences by resetting the sieve rules directly in the database.
Now I got another exception when calling something like this:
sudo -u $sogoUser sogo-tool user-preferences set defaults $userToModify
$sogoUser:$pw SOGoSieveFilters '{SOGoSieveFilters: [{actions:
[{method: fileinto, argument: INBOX\/Test}], active: true,
rules: [{operator: contains, field: from, value:
us...@web.de}], match: any, name: UserFilter}]}'
Error:
2012-03-25 14:52:18.189 sogo-tool[29277] failure. Attempting with a renewed
password (no authname supported)
2012-03-25 14:52:18.189 sogo-tool[29277] Could not login '$USER' on Sieve
server: 0x0xa37d10[NGSieveClient]: socket=NGActiveSocket[0x0xa40ca0]:
mode=rw address=0x0xa43bf0[NGInternetSocketAddress]:
host=localhost.localdomain port=37434
connectedTo=0x0xa3c150[NGInternetSocketAddress]: host=localhost
port=2000: (nil)
I do not know why, but sogo-tool cannot login to the sieve server although
there is no problem when using or adding sieve rules via the web
preferences.
Any suggestions? Hope for help.
Best regards,
Malte
Von: Malte Brunnlieb [mailto:ma...@brunnlieb.net] Im Auftrag von
m_bru...@cs.uni-kl.de
Gesendet: Freitag, 23. März 2012 16:04
An: users@sogo.nu
Betreff: AW: [SOGo] Problems while importing sieve rules
Hi,
I have done a second try enabling each debug setting which is possible.
(http://www.sogo.nu/english/nc/support/faq/article/how-to-enable-more-verbos
e-logging-in-sogo.html)
After calling the sogo-tool command mentioned in the previous mail, I got
this:
Mar 23 14:54:47 sogo-tool [18630]: 0x0x1057ca0[SOGoCache] Cache cleanup
interval set every 300.00 seconds
Mar 23 14:54:47 sogo-tool [18630]: 0x0x1057ca0[SOGoCache] Using host(s)
'localhost' as server(s)
2012-03-23 14:54:47.211 sogo-tool[18630] -[NGLdapConnection
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base à_;²
filter Àx;² for attrs :²
2012-03-23 14:54:47.211 sogo-tool[18630] -[NGLdapConnection
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base filter
Àx;² for attrs :²
2012-03-23 14:54:47.215 sogo-tool[18630] -[NGLdapConnection
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base Àx;²
filter Àx;² for attrs :²
2012-03-23 14:54:47.222 sogo-tool[18630] MySQL4 connection established
0x0xed9ff0
2012-03-23 14:54:47.222 sogo-tool[18630] MySQL4 channel 0x0xfef9e0 opened
(connection=0x0xed9ff0,sogo)
2012-03-23 14:54:47.222 sogo-tool[18630] MySQL4Channel[0x0xfef9e0]
connection=0x0xed9ff0 SQL: SELECT c_defaults FROM sogo_user_profile WHERE
c_uid = 'malte';
2012-03-23 14:54:47.222 sogo-tool[18630] MySQL4Channel[0x0xfef9e0]
connection=0x0xed9ff0 query has results, entering fetch-mode.
Aborted
So why do sogo-tool abort this operation? I cannot see any problem message
or hint according to the abortion. The only interesting thing is, that I am
using a MySQL 5 database, so why is the MySQL4 debugger integrated in this
command call?
Is there anybody having an idea what is going wrong here?
Best regards,
Malte
Von: Malte Brunnlieb [mailto:ma...@brunnlieb.net] Im Auftrag von
m_bru...@cs.uni-kl.de
Gesendet: Freitag, 16. März 2012 13:16
An: users@sogo.nu
Betreff: [SOGo] JSON problems while importing sieve rules
Hi folks,
I am currently importing sieve rules into sogo using the sogo-tool.
Therefore I execute the following: ($...: variables that I have
instantiated)
sudo -u $sogoUser sogo-tool user-preferences set defaults $userToModify
$sogoUser:$pw SOGoSieveFilters '{SOGoSieveFilters: [{actions:
[{method: fileinto, argument: INBOX\/Test}], active: true,
rules: [{operator: contains, field: from, value:
us...@web.de}], match: any, name: UserFilter}]}'
All I get is:
0x0x1c8f710[SOGoCache] Cache cleanup interval set every 300.00 seconds
0x0x1c8f710[SOGoCache] Using host(s) 'localhost' as server(s)
Aborted
I cannot see any problem with the example sieve rule and nothing is said
about an error.
Any suggestions?
Best regards,
Malte
--
users@sogo.nu
https://inverse.ca/sogo/lists
AW: [SOGo] Problems while importing sieve rules
Hi,
I have done a second try enabling each debug setting which is possible.
(http://www.sogo.nu/english/nc/support/faq/article/how-to-enable-more-verbos
e-logging-in-sogo.html)
After calling the sogo-tool command mentioned in the previous mail, I got
this:
Mar 23 14:54:47 sogo-tool [18630]: 0x0x1057ca0[SOGoCache] Cache cleanup
interval set every 300.00 seconds
Mar 23 14:54:47 sogo-tool [18630]: 0x0x1057ca0[SOGoCache] Using host(s)
'localhost' as server(s)
2012-03-23 14:54:47.211 sogo-tool[18630] -[NGLdapConnection
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base à_;²
filter Àx;² for attrs :²
2012-03-23 14:54:47.211 sogo-tool[18630] -[NGLdapConnection
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base filter
Àx;² for attrs :²
2012-03-23 14:54:47.215 sogo-tool[18630] -[NGLdapConnection
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base Àx;²
filter Àx;² for attrs :²
2012-03-23 14:54:47.222 sogo-tool[18630] MySQL4 connection established
0x0xed9ff0
2012-03-23 14:54:47.222 sogo-tool[18630] MySQL4 channel 0x0xfef9e0 opened
(connection=0x0xed9ff0,sogo)
2012-03-23 14:54:47.222 sogo-tool[18630] MySQL4Channel[0x0xfef9e0]
connection=0x0xed9ff0 SQL: SELECT c_defaults FROM sogo_user_profile WHERE
c_uid = 'malte';
2012-03-23 14:54:47.222 sogo-tool[18630] MySQL4Channel[0x0xfef9e0]
connection=0x0xed9ff0 query has results, entering fetch-mode.
Aborted
So why do sogo-tool abort this operation? I cannot see any problem message
or hint according to the abortion. The only interesting thing is, that I am
using a MySQL 5 database, so why is the MySQL4 debugger integrated in this
command call?
Is there anybody having an idea what is going wrong here?
Best regards,
Malte
Von: Malte Brunnlieb [mailto:ma...@brunnlieb.net] Im Auftrag von
m_bru...@cs.uni-kl.de
Gesendet: Freitag, 16. März 2012 13:16
An: users@sogo.nu
Betreff: [SOGo] JSON problems while importing sieve rules
Hi folks,
I am currently importing sieve rules into sogo using the sogo-tool.
Therefore I execute the following: ($...: variables that I have
instantiated)
sudo -u $sogoUser sogo-tool user-preferences set defaults $userToModify
$sogoUser:$pw SOGoSieveFilters '{SOGoSieveFilters: [{actions:
[{method: fileinto, argument: INBOX\/Test}], active: true,
rules: [{operator: contains, field: from, value:
us...@web.de}], match: any, name: UserFilter}]}'
All I get is:
0x0x1c8f710[SOGoCache] Cache cleanup interval set every 300.00 seconds
0x0x1c8f710[SOGoCache] Using host(s) 'localhost' as server(s)
Aborted
I cannot see any problem with the example sieve rule and nothing is said
about an error.
Any suggestions?
Best regards,
Malte
--
users@sogo.nu
https://inverse.ca/sogo/lists
[SOGo] JSON problems while importing sieve rules
Hi folks,
I am currently importing sieve rules into sogo using the sogo-tool.
Therefore I execute the following: ($...: variables that I have
instantiated)
sudo -u $sogoUser sogo-tool user-preferences set defaults $userToModify
$sogoUser:$pw SOGoSieveFilters '{SOGoSieveFilters: [{actions:
[{method: fileinto, argument: INBOX\/Test}], active: true,
rules: [{operator: contains, field: from, value:
us...@web.de}], match: any, name: UserFilter}]}'
All I get is:
0x0x1c8f710[SOGoCache] Cache cleanup interval set every 300.00 seconds
0x0x1c8f710[SOGoCache] Using host(s) 'localhost' as server(s)
Aborted
I cannot see any problem with the example sieve rule and nothing is said
about an error.
Any suggestions?
Best regards,
Malte
--
users@sogo.nu
https://inverse.ca/sogo/lists
AW: [SOGo] Proxy Error while saving preferences
Hi André, thanks for your quick reply. 1. There is my user name at $USER ;) 2. Hopefully this is related to my problem, but there are two mysterious messages in the log: a. Mar 14 08:11:58 sogod [25740]: 0x0x260e340[WOPasswordField] -[WOInput takeValuesFromRequest:inContext:]: form value is not settable: 0x0x260e5a0[WOValueAssociation]: value= Mar 14 08:11:58 sogod [25740]: 0x0x260eeb0[WOPasswordField] -[WOInput takeValuesFromRequest:inContext:]: form value is not settable: 0x0x260f110[WOValueAssociation]: value= b. 2012-03-14 08:11:58.028 sogod[25740] ERROR(-[NGBundleManager bundleWithPath:]): could not create bundle for path: '/usr/share/GNUstep/Libraries/gnustep-base/Versions/1.19/Resources/SSL.bundl e' Von: André Schild [mailto:an...@schild.ws] Gesendet: Dienstag, 13. März 2012 19:16 An: users@sogo.nu Betreff: Re: [SOGo] Proxy Error while saving preferences 1. Is the message realy incldung $USER, or does it show the correct user name there ? 2. What does sogo.log tell you ? Am 13.03.2012 19:00, schrieb m_bru...@cs.uni-kl.de: Hi folks, I am currently migrating from a simple mail web frontend to SOGo. Until now everything worked fine for me, but now I got a proxy error every time I try to save my preferences in the SOGo web frontend: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST /SOGo/so/$USER/preferences. Reason: Error reading from remote server Unfortunately I have not worked with sogo for some month as I had no time. So I cannot identify any specific cause for this problem. I have found some update/upgrade issues related to this error but all of them are related to postgreSQL. I am using MySQL (5.1.61) running on Ubuntu 10.04.2 and the latest sogo packages (release). Nothing about POST calls in the logs. Only GET operations are called successfully: [13/Mar/2012:18:37:24 GMT] GET /SOGo/so/$USER/preferences HTTP/1.1 200 15649/0 0.096 70790 77% 172K Any suggestions how to get rid of this problem? Regards, Malte -- users@sogo.nu https://inverse.ca/sogo/lists
AW: [SOGo] Proxy Error while saving preferences
I have checked some other user accounts for this proxy error. So it seems to be an individual problem for my account. This leads to the conclusion that the cause could be the manually migration of sieve rules from roundcube to sogo. As sogo saves its sieve rules in a huge array in the database as part of the user profile, I converted existing rules to the database representation. I inserted the new rules and as intended they are correctly loaded into sogo webinterface. After that I had a look at the generated sogo.sieve file on which managesieve determines its rule application. As this file seems to be left in old state, I wanted to force sogo to generate a new sogo.sieve file from database using the save preferences mechanism. Unfortunately while saving I got the proxy error the first time. So I restored the old database entries for my profile in order to get rid of this problem, but nothing new... the proxy error occurs whenever I want to save my settings although I restored the original settings. Any new ideas how to get rid of the proxy error? -Ursprüngliche Nachricht- Von: Martin Rabl [mailto:martin.r...@rablnet.de] Gesendet: Mittwoch, 14. März 2012 08:44 An: users@sogo.nu Betreff: Re: [SOGo] Proxy Error while saving preferences Am 14.03.12 08:20, schrieb m_bru...@cs.uni-kl.de: b.2012-03-14 08:11:58.028 sogod[25740] ERROR(-[NGBundleManager bundleWithPath:]): could not create bundle for path: '/usr/share/GNUstep/Libraries/gnustep-base/Versions/1.19/Resources/SSL.bundl e' This can be ignored. http://www.sogo.nu/bugs/view.php?id=287 Greetings, Martin -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Proxy Error while saving preferences
Hi folks, I am currently migrating from a simple mail web frontend to SOGo. Until now everything worked fine for me, but now I got a proxy error every time I try to save my preferences in the SOGo web frontend: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST /SOGo/so/$USER/preferences. Reason: Error reading from remote server Unfortunately I have not worked with sogo for some month as I had no time. So I cannot identify any specific cause for this problem. I have found some update/upgrade issues related to this error but all of them are related to postgreSQL. I am using MySQL (5.1.61) running on Ubuntu 10.04.2 and the latest sogo packages (release). Nothing about POST calls in the logs. Only GET operations are called successfully: [13/Mar/2012:18:37:24 GMT] GET /SOGo/so/$USER/preferences HTTP/1.1 200 15649/0 0.096 70790 77% 172K Any suggestions how to get rid of this problem? Regards, Malte -- users@sogo.nu https://inverse.ca/sogo/lists
AW: AW: [SOGo] Error with recipient
But I think there is no other way to do the filtering of mails, isn’t it? When I add a filter in the SOGo webfrontent, the rule will be processed by sieve. So I think it is a little bit ironic, that SOGo provides such filter functionality but then does not check subfolders for new mails or is there another way to provide this update functionality for subfolders, e.g. by connecting a different filter technique? I only heard of managesieve for dovecot. Malte -Ursprüngliche Nachricht- Von: Patrick Ben Koetter [mailto:p...@state-of-mind.de] Gesendet: Freitag, 19. August 2011 22:52 An: users@sogo.nu Betreff: Re: AW: [SOGo] Error with recipient * m_bru...@cs.uni-kl.de users@sogo.nu: One example I think of is: http://www.sogo.nu/bugs/view.php?id=1289 And unfortunately I have found this too late and added a new one containing the same problem. To me this isn't a sieve error. The problem seems to be that the SOGo client does not check subfolders. Of course this becomes a problem the moment you start using sieve filters with its :fileinto capability, because then you start noticing the client doesn't notice ... I was oriented towards http://wiki.dovecot.org/LDA and other HowTo's. Anything I have forgotten? Dovecot and so managesieve is running with the dovecot user. Unless you don't see any errors in the mail.log you should be fine. p@rick -- state of mind () http://www.state-of-mind.de Franziskanerstraße 15 Telefon +49 89 3090 4664 81669 München Telefax +49 89 3090 4666 Amtsgericht MünchenPartnerschaftsregister PR 563 -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
AW: [SOGo] Error with recipient
Ah k, nice technical information. Does anybody also know where exactly this map is managed? Perhaps I can patch this for my needs as I have several folders where mails can be sorted in. There are too much to click through each of the folders in order to look for new mails. I think it is an issue some other users will be happy of having that. Malte -Ursprüngliche Nachricht- Von: Ludovic Marcotte [mailto:lmarco...@inverse.ca] Gesendet: Samstag, 20. August 2011 14:04 An: users@sogo.nu Betreff: Re: [SOGo] Error with recipient On 20/08/11 07:55, Martin Rabl wrote: - Checking subfolders for new Mails is an IMAP thing an a client thing. The client can check for Mails in subfolders by sending an command to the IMAP server. But IMHO only the root folder state is sent to the client. Adding a slight precision here. When you login in SOGo, go in the mail interface and open mailboxes other than the INBOX, SOGo will build a list of them. They will be also updated for new messages just like the INBOX is by default. When you logout or change module, that list is wiped. This is pretty much how Thunderbird 3.1 does it too, beside the change module thing. Regards, -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
AW: AW: [SOGo] Error with recipient
Thanks a lot for your time, I will spend some time on this problem this weekend.
And by the way, I am using Ubuntu ;)
Greetings,
Malte
-Ursprüngliche Nachricht-
Von: Patrick Ben Koetter [mailto:p...@state-of-mind.de]
Gesendet: Donnerstag, 18. August 2011 22:10
An: users@sogo.nu
Betreff: Re: AW: [SOGo] Error with recipient
* m_bru...@cs.uni-kl.de users@sogo.nu:
here are my postconf -n data, I removed some sensitive data, but I
think this should be enough for debugging:
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
Debian, eh?
biff = no
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
home_mailbox = .mailbox/
inet_protocols = ipv4
That's default. You don't need to set $inet_protocols.
mailbox_command = /usr/lib64/dovecot/deliver mydestination = all
domains, localhost myhostname = main domain
myhostname = $mydomain
mynetworks = localhost IP and domain
Do not add a host or domainname to $mynetworks. It will work ONLY if your DNS
works and Postfix is able to resolve the domain or hostname. Rather go this
way:
mynetworks = 127.0.0.0/8, IP/range
myorigin = /etc/mailname
This setting is often broken on Debian systems. I recommend using the hosts
real name as $myorigin applies to system accounts:
myorigin = $myhostname
If you do this don't forget to add $myhostname to the list of domains in
$mydestinations.
readme_directory = no
recipient_delimiter = +
relayhost =
smtp_sasl_auth_enable = no
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
smtpd_client_restrictions = smtpd_data_restrictions =
reject_unauth_pipelining smtpd_helo_required = yes
smtpd_helo_restrictions = reject_invalid_hostname
You have this:
smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination,
reject_invalid_hostname,
reject_unknown_sender_domain,
check_policy_service inet:127.0.0.1:10023
I recommend rearranging and adding some options at the beginning. They assure
you only send mail that actually can be transported to other hosts:
smtpd_recipient_restrictions =
reject_non_fqdn_sender,
reject_non_fqdn_recipient,,
reject_unknown_sender_domain,
reject_unknown_recipient_domain,
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination,
reject_invalid_hostname,
check_policy_service inet:127.0.0.1:10023
smtpd_sasl_auth_enable = yes
smtpd_sasl_local_domain =
smtpd_sasl_path = smtpd
smtpd_sasl_security_options = noanonymous smtpd_sasl_type = cyrus
$smtpd_sasl_type defaults to cyrus. You don't need to set it.
smtpd_sender_restrictions = reject_non_fqdn_sender,
reject_unknown_sender_domain
Drop smtpd_sender_restrictions if you follow my recommendation from above on
smtpd_recipient_restrictions.
smtpd_tls_auth_only = yes
smtpd_tls_cert_file = ssl pem
smtpd_tls_key_file = ssl key
smtpd_tls_security_level = may
smtpd_tls_session_cache_database =
btree:${data_directory}/smtpd_scache
So far so good. You might want to spend more time adding more anti-spam stuff.
Your sending problem could/should be gone once you localhost in $mynetworks
with 127.0.0.0/8.
If not run the Postfix smtpd daemon verbose by adding '-v' at the end of the
line that invokes smtpd in master.cf. You should probably send the output to
the Postfix mailing list. If you want help in German subscribe
postfix-us...@de.postfix.org. I will be there ... ;)
p@rick
--
state of mind ()
http://www.state-of-mind.de
Franziskanerstraße 15 Telefon +49 89 3090 4664
81669 München Telefax +49 89 3090 4666
Amtsgericht MünchenPartnerschaftsregister PR 563
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
AW: AW: [SOGo] Error with recipient
Jey, nice one! It works. Thanks a lot!
Now I hope that all imap folders get updated for new mails sorted by a filter
beforehand, not only the incoming folder.
But unfortunately this does not work yet in SOGo as I have seen some tracker
issues for that :(
Greetings,
Malte
-Ursprüngliche Nachricht-
Von: Patrick Ben Koetter [mailto:p...@state-of-mind.de]
Gesendet: Donnerstag, 18. August 2011 22:10
An: users@sogo.nu
Betreff: Re: AW: [SOGo] Error with recipient
* m_bru...@cs.uni-kl.de users@sogo.nu:
here are my postconf -n data, I removed some sensitive data, but I
think this should be enough for debugging:
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
Debian, eh?
biff = no
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
home_mailbox = .mailbox/
inet_protocols = ipv4
That's default. You don't need to set $inet_protocols.
mailbox_command = /usr/lib64/dovecot/deliver mydestination = all
domains, localhost myhostname = main domain
myhostname = $mydomain
mynetworks = localhost IP and domain
Do not add a host or domainname to $mynetworks. It will work ONLY if your DNS
works and Postfix is able to resolve the domain or hostname. Rather go this
way:
mynetworks = 127.0.0.0/8, IP/range
myorigin = /etc/mailname
This setting is often broken on Debian systems. I recommend using the hosts
real name as $myorigin applies to system accounts:
myorigin = $myhostname
If you do this don't forget to add $myhostname to the list of domains in
$mydestinations.
readme_directory = no
recipient_delimiter = +
relayhost =
smtp_sasl_auth_enable = no
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
smtpd_client_restrictions = smtpd_data_restrictions =
reject_unauth_pipelining smtpd_helo_required = yes
smtpd_helo_restrictions = reject_invalid_hostname
You have this:
smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination,
reject_invalid_hostname,
reject_unknown_sender_domain,
check_policy_service inet:127.0.0.1:10023
I recommend rearranging and adding some options at the beginning. They assure
you only send mail that actually can be transported to other hosts:
smtpd_recipient_restrictions =
reject_non_fqdn_sender,
reject_non_fqdn_recipient,,
reject_unknown_sender_domain,
reject_unknown_recipient_domain,
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination,
reject_invalid_hostname,
check_policy_service inet:127.0.0.1:10023
smtpd_sasl_auth_enable = yes
smtpd_sasl_local_domain =
smtpd_sasl_path = smtpd
smtpd_sasl_security_options = noanonymous smtpd_sasl_type = cyrus
$smtpd_sasl_type defaults to cyrus. You don't need to set it.
smtpd_sender_restrictions = reject_non_fqdn_sender,
reject_unknown_sender_domain
Drop smtpd_sender_restrictions if you follow my recommendation from above on
smtpd_recipient_restrictions.
smtpd_tls_auth_only = yes
smtpd_tls_cert_file = ssl pem
smtpd_tls_key_file = ssl key
smtpd_tls_security_level = may
smtpd_tls_session_cache_database =
btree:${data_directory}/smtpd_scache
So far so good. You might want to spend more time adding more anti-spam stuff.
Your sending problem could/should be gone once you localhost in $mynetworks
with 127.0.0.0/8.
If not run the Postfix smtpd daemon verbose by adding '-v' at the end of the
line that invokes smtpd in master.cf. You should probably send the output to
the Postfix mailing list. If you want help in German subscribe
postfix-us...@de.postfix.org. I will be there ... ;)
p@rick
--
state of mind ()
http://www.state-of-mind.de
Franziskanerstraße 15 Telefon +49 89 3090 4664
81669 München Telefax +49 89 3090 4666
Amtsgericht MünchenPartnerschaftsregister PR 563
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
AW: AW: [SOGo] Error with recipient
One example I think of is: http://www.sogo.nu/bugs/view.php?id=1289
And unfortunately I have found this too late and added a new one containing the
same problem.
But perhaps I have also a configuration error in my Dovecot LDA? Here are my
related relevant configurations:
Sogo config:
keySOGoIMAPServer/key
stringimaps://localhost:993/string
keySOGoSieveScriptsEnabled/key
stringYES/string
keySOGoSieveServer/key
stringsieve://localhost:2000/string
Dovecot config:
protocol lda {
mail_plugins = sieve
sendmail_path = /usr/lib/sendmail
}
auth default {
..
socket listen {
master {
path = /var/run/dovecot/auth-master
mode = 0600
user = root
}
...
}
..
}
Postfix config:
mailbox_command = /usr/lib64/dovecot/deliver
I was oriented towards http://wiki.dovecot.org/LDA and other HowTo's. Anything
I have forgotten? Dovecot and so managesieve is running with the dovecot user.
Hopefully you can help me also with this problem ;) Thanks a lot for your help
right now!
Cheers,
Malte
-Ursprüngliche Nachricht-
Von: Patrick Ben Koetter [mailto:p...@state-of-mind.de]
Gesendet: Freitag, 19. August 2011 20:56
An: users@sogo.nu
Betreff: Re: AW: [SOGo] Error with recipient
* m_bru...@cs.uni-kl.de users@sogo.nu:
Jey, nice one! It works. Thanks a lot!
Now I hope that all imap folders get updated for new mails sorted by a
filter beforehand, not only the incoming folder.
If you use Dovecots LDA deliver it will update the mailbox index anytime it
changes (add/modify/delete) mails in the mailbox.
Whenever a client connects to Dovecots imapd daemon and requests to access e.g.
SELECT a folder, imapd accesses a fresh index.
But unfortunately this does not work yet in SOGo as I have seen some
tracker issues for that :(
I don't get it. Mind to show some URLs to refer to the bugs you're talking
about?
p@rick
--
state of mind ()
http://www.state-of-mind.de
Franziskanerstraße 15 Telefon +49 89 3090 4664
81669 München Telefax +49 89 3090 4666
Amtsgericht MünchenPartnerschaftsregister PR 563
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
AW: AW: [SOGo] Error with recipient
Hi,
here are my postconf -n data, I removed some sensitive data, but I think this
should be enough for debugging:
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
home_mailbox = .mailbox/
inet_protocols = ipv4
mailbox_command = /usr/lib64/dovecot/deliver
mydestination = all domains, localhost
myhostname = main domain
mynetworks = localhost IP and domain
myorigin = /etc/mailname
readme_directory = no
recipient_delimiter = +
relayhost =
smtp_sasl_auth_enable = no
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
smtpd_client_restrictions =
smtpd_data_restrictions = reject_unauth_pipelining
smtpd_helo_required = yes
smtpd_helo_restrictions = reject_invalid_hostname
smtpd_recipient_restrictions = permit_mynetworks,
permit_sasl_authenticated, reject_unauth_destination,
reject_invalid_hostname, reject_unknown_sender_domain,
check_policy_service inet:127.0.0.1:10023
smtpd_sasl_auth_enable = yes
smtpd_sasl_local_domain =
smtpd_sasl_path = smtpd
smtpd_sasl_security_options = noanonymous
smtpd_sasl_type = cyrus
smtpd_sender_restrictions = reject_non_fqdn_sender,
reject_unknown_sender_domain
smtpd_tls_auth_only = yes
smtpd_tls_cert_file = ssl pem
smtpd_tls_key_file = ssl key
smtpd_tls_security_level = may
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
Greetings,
Malte
-Ursprüngliche Nachricht-
Von: Patrick Ben Koetter [mailto:p...@state-of-mind.de]
Gesendet: Mittwoch, 17. August 2011 22:43
An: users@sogo.nu
Betreff: Re: AW: [SOGo] Error with recipient
Malte,
* Francis Lachapelle users@sogo.nu:
Hi Malte
On 2011-08-17, at 2:49 PM, m_bru...@cs.uni-kl.de m_bru...@cs.uni-kl.de
wrote:
here the relevant lines of the postfix log:
Aug 17 18:39:49 v220101057154023 postfix/smtpd[7069]: connect from
localhost.localdomain[127.0.0.1] Aug 17 18:39:49 v220101057154023
postfix/smtpd[7069]: NOQUEUE: reject: RCPT from
localhost.localdomain[127.0.0.1]: 554 5.7.1 testt...@web.de: Relay
access denied; from=* to=testt...@web.de proto=ESMTP
helo=localhost.localdomain Aug 17 18:39:49 v220101057154023
postfix/smtpd[7069]: disconnect from
localhost.localdomain[127.0.0.1]
My configuration of the postfix parameters mydestination and mynetworks
is the following:
mydestination: my domains, localhost
mynetworks: localhost, my IP, my domain What should be changed
in order to send email via SOGo. Everything works fine using
Roundcube or directly connecting to SMTP server via other clients.
Maybe you should explicitly use 127.0.0.1 in mynetworks.
Otherwise, is permit_mynetworks appears in smtpd_client_restrictions?
Sorry, if I interrupt. You won't get the picture if you ask for
permit_mynetworks or anything alike if you don't know about other options that
control how restrictions are evaluated.
postconf smtpd_client_restrictions
Please send postconf -n to debug this.
p@rick
--
state of mind ()
http://www.state-of-mind.de
Franziskanerstraße 15 Telefon +49 89 3090 4664
81669 München Telefax +49 89 3090 4666
Amtsgericht MünchenPartnerschaftsregister PR 563
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
[SOGo] Error with recipient
Hi all, I have more or less successfully established sogo in my currently working infrastructure of postfix and dovecot. Now I have a problem while sending a mail via sogo. Every time I want to do so I get the error message, that the recipient is not ok. So here are the relevant lines of the sogo.log Perhaps this is helpful: C: connect to 0x0xee99a0[NGInternetSocketAddress]: host=localhost not-filled S: SMTP-Reply: code=220 line=' ESMTP Postfix (Ubuntu)' C: EHLO localhost.localdomain S: SMTP-Reply: code=250 line='DSN' S: pipelining extension supported. S: size extension supported. C: MAIL FROM:* C: RCPT TO:testt...@web.de Aug 14 21:57:36 sogod [23905]: 0x0x2d303c0[SOGoMailer] error with recipient ' testt...@web.de' C: QUIT S: SMTP-Reply: code=221 line='2.0.0 Bye' My postfix server works fine with Roundcube/Outlook/Thunderbird. Hopefully this is the last problem I have to work on. Any Ideas? Greetings -- users@sogo.nu https://inverse.ca/sogo/lists
AW: [SOGo] Proxy error after Logging in
Hi,
Check whether the configuration value SOGoForceIMAPLoginWithEmail is not set
to YES. By default this value should be set on NO according to the
documentation.
-Ursprüngliche Nachricht-
Von: Florian Unger [mailto:florian.un...@intego.de]
Gesendet: Dienstag, 2. August 2011 09:45
An: users@sogo.nu
Betreff: Re: [SOGo] Proxy error after Logging in
Hi,
I have got the same error. The problem probably is that I did not configure
the IMAP settings in GNUstepDefaults and did not set up an IMAP server
because we don't need it.
Log file says:
192.168.124.51 - - [02/Aug/2011:08:54:21 GMT] GET /SOGo/ HTTP/1.1 302 0/0
0.043 - - 676K
192.168.124.51 - - [02/Aug/2011:08:54:21 GMT] GET /SOGo/tom HTTP/1.1 302
0/0 0.003 - - 0
192.168.124.51 - - [02/Aug/2011:08:54:21 GMT] GET /SOGo/tom/view HTTP/1.1
302 0/0 0.003
- - 4K
192.168.124.51 - - [02/Aug/2011:08:54:21 GMT] GET /SOGo/so/tom/Mail
HTTP/1.1 302 0/0
0.002 - - 12K
2011-08-02 08:54:21.245 sogod[20613] WARNING: IMAP4 connection pooling is
disabled!
Aug 02 08:54:21 sogod [20613]: [ERROR]
0x0x8c8c5c8[NGImap4ConnectionManager] IMAP4 login
failed:
host=localhost, user=tom, pwd=yes
url=imap://tom@localhost/INBOX/
base=(nil)
base-class=(nil))
= 0x0x8c8e678[NGImap4Client]: login=tom(pwd)
address=0x0x8c9eec0[NGInternetSocketAddress]: host=localhost port=143
2011-08-02 08:54:21.247 sogod[20613] Note(NGImap4Connection): using '/' as
the IMAP4 folder separator.
Aug 02 08:54:21 sogod [20613]: 0x08C91A50[SOGoMailFolder]:folderINBOX
renewing imap4 password Aug 02 08:54:21 sogod [20613]: [ERROR]
0x0x8c8c5c8[NGImap4ConnectionManager] IMAP4 login
failed:
host=localhost, user=tom, pwd=yes
url=imap://tom@localhost/INBOX/
base=(nil)
base-class=(nil))
= 0x0x8c859b8[NGImap4Client]: login=tom(pwd)
address=0x0x8c86d28[NGInternetSocketAddress]: host=localhost port=143 Aug
02 08:54:21 sogod [20613]: [ERROR] 0x08C91A50[SOGoMailFolder]:folderINBOX
Could not connect IMAP4
EXCEPTION: NSException: 0x8c973c0 NAME:NSInvalidArgumentException
REASON:Tried to add nil value for key 'uids' to dictionary INFO:{headers =
((To, Attachment, Flagged, Subject, From, Unread, Priority, Date, Size,
rowClasses, labels, rowID, uid)); } Aug 02 08:54:21 sogod [3877]:
0x0x8993678[WOWatchDogChild] child 20613 exited Aug 02 08:54:21 sogod
[3877]: 0x0x8993678[WOWatchDogChild] (terminated due to signal 6) Aug 02
08:54:21 sogod [3877]: 0x0x8a0a548[WOWatchDog] child spawned with pid
21228
Regards
Florian
On 16.07.2011 12:58, Ludovic Marcotte wrote:
On 16/07/11 05:48, dirk.b...@directbox.com wrote:
I've just installed SOGo. With the first try to log in I get the
following proxy error:
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET
/SOGo/so/admin/Mail/view.
Can anyone help me to solve this problem?
Have a look at your sogo.log file in /var/log/sogo when that happens. What
does it log?
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
[SOGo] ldap address book as default
I all, I am new in the fields of SOGo groupware. At the moment I want to get started with SOGo, so I installed SOGo and also applied a LDAP authentication. So far everything works fine. But now I am wondering, why SOGo creates new address books or entries of the personal address book in the database. I cannot find any documentation considering this issue so far, or is there no way to manage the whole contacts using LDAP? Any ideas? Links for further reading except the general SOGo documentation, where only authentication against LDAP is documented? Greetings -- users@sogo.nu https://inverse.ca/sogo/lists
