Re: [SOGo] Probably another lame question but here goes....

2011-12-19 Thread Christian Mack
On 2011-12-16 17:14, Paul Mecham wrote:
 I can send mail with sogo and I receive the mail but only in the file
 system directory.  It does not show up in the sogo in mail box.  Can
 someone give me a hint about what ldap property or what
 .GNUstepDefaults entry controls how the imap mailbox folders are seen
 by SOGO?
 
 I can see the files with the incoming mail, they are in my 
 /home/pmehcam/Maildir/new/ Folder in filenames that look like: 
 1324050827.V2aIe20b1M282935.pahsogo1.pah.local
 
 I'm wondering if it has something to do with the pahsogo1.pah.local
 not matching my domain name of mail.rvscapes.com?
 

We are using cyrus as email server, so I'm not shure about this.
But I think this file names are created from the message ID. They are
created by the sender and therefore ony match your domain, if the sender
belongs to your domain too.

Can you connect with the parameters given in your SOGo configuration per
IMAP client?

How did you change your configuration?

Did you restart SOGo after changing your configuration?


Kind regards,
Christian Mack

-- 
Christian Mack
Gruppe Informationsdienste
Rechenzentrum Universität Konstanz
-- 
users@sogo.nu
https://inverse.ca/sogo/lists


RE: [SOGo] Probably another lame question but here goes....

2011-12-19 Thread Paul Mecham
 dynamic backend modules:
# modulepath/usr/lib/openldap

# Modules available in openldap-servers-overlays RPM package
# Module syncprov.la is now statically linked with slapd and there
# is no need to load it here
# moduleload accesslog.la
# moduleload auditlog.la
# moduleload denyop.la
# moduleload dyngroup.la
# moduleload dynlist.la
# moduleload lastmod.la
# moduleload pcache.la
# moduleload ppolicy.la
# moduleload refint.la
# moduleload retcode.la
# moduleload rwm.la
# moduleload smbk5pwd.la
# moduleload translucent.la
# moduleload unique.la
# moduleload valsort.la

# modules available in openldap-servers-sql RPM package:
# moduleload back_sql.la

# The next three lines allow use of TLS for encrypting connections using a
# dummy test certificate which you can generate by changing to
# /etc/pki/tls/certs, running make slapd.pem, and fixing permissions on
# slapd.pem so that the ldap user or group can read it.  Your client software
# may balk at self-signed certificates, however.
# TLSCACertificateFile /etc/pki/tls/certs/ca-bundle.crt
# TLSCertificateFile /etc/pki/tls/certs/slapd.pem
# TLSCertificateKeyFile /etc/pki/tls/certs/slapd.pem

# Sample security restrictions
#   Require integrity protection (prevent hijacking)
#   Require 112-bit (3DES or better) encryption for updates
#   Require 63-bit encryption for simple bind
# security ssf=1 update_ssf=112 simple_bind=64

# Sample access control policy:
#   Root DSE: allow anyone to read it
#   Subschema (sub)entry DSE: allow anyone to read it
#   Other DSEs:
#   Allow self write access
#   Allow authenticated users read access
#   Allow anonymous users to authenticate
#   Directives needed to implement policy:
# access to dn.base= by * read
# access to dn.base=cn=Subschema by * read
# access to *
#   by self write
#   by users read
#   by anonymous auth
#
# if no access controls are present, the default policy
# allows anyone and everyone to read anything but restricts
# updates to rootdn.  (e.g., access to * by * read)
#
# rootdn can always read and write EVERYTHING!

###
# ldbm and/or bdb database definitions
###

databasebdb
suffix  dc=rvscapes,dc=com
rootdn  dc=rvscapes,dc=com
# Cleartext passwords, especially for the rootdn, should
# be avoided.  See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
# rootpwsecret
# rootpw{crypt}ijFYNcSNctBYg
rootpw  {SSHA}exwFTOMNbBRH3ykaGDfrNk1dd3CAa5zr  

# The database directory MUST exist prior to running slapd AND 
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory   /var/lib/ldap

# Indices to maintain for this database
index objectClass   eq,pres
index ou,cn,mail,surname,givenname  eq,pres,sub
index uidNumber,gidNumber,loginShelleq,pres
index uid,memberUid eq,pres,sub
index nisMapName,nisMapEntryeq,pres,sub

# Replicas of this database
#replogfile /var/lib/ldap/openldap-master-replog
#replica host=ldap-1.example.com:389 starttls=critical
# bindmethod=sasl saslmech=GSSAPI
# authcId=host/ldap-master.example@example.com

Q. Are you restarting the services?
A.  All the time :).  Here is my restart shell script.
#~/bin/bash
/sbin/service saslauthd stop
/sbin/service memcached stop
/sbin/service postfix stop
/sbin/service postgresql stop
/sbin/service cyrus-imapd stop
/sbin/service ldap stop
/sbin/service sogod stop
/sbin/service httpd stop

/sbin/service saslauthd start
/sbin/service memcached start
/sbin/service postfix start
/sbin/service postgresql start
/sbin/service cyrus-imapd start
/sbin/service ldap start
/sbin/service sogod start
/sbin/service httpd start

Thank you for any guidance you can provide.

Paul



-Original Message-
From: Christian Mack [mailto:christian.m...@uni-konstanz.de] 
Sent: Monday, December 19, 2011 1:57 AM
To: users@sogo.nu
Cc: Paul Mecham
Subject: Re: [SOGo] Probably another lame question but here goes

On 2011-12-16 17:14, Paul Mecham wrote:
 I can send mail with sogo and I receive the mail but only in the file 
 system directory.  It does not show up in the sogo in mail box.  Can 
 someone give me a hint about what ldap property or what 
 .GNUstepDefaults entry controls how the imap mailbox folders are seen 
 by SOGO?
 
 I can see the files with the incoming mail, they are in my 
 /home/pmehcam/Maildir/new/ Folder in filenames that look like:
 1324050827.V2aIe20b1M282935.pahsogo1.pah.local
 
 I'm wondering if it has something to do with the pahsogo1.pah.local
 not matching my domain name of mail.rvscapes.com?
 

We are using cyrus as email server, so I'm not shure about this.
But I think this file names are created from the message ID. They are created

RE: [SOGo] Probably another lame question but here goes....

2011-12-19 Thread Paul Mecham
I'm starting to think I can't get email because of a mis-configuration on the 
IMAP side...

I see directories in the /var/lib/imap/user/someletter directory that seem to 
be setting up directory structures that look like they could potentially hold 
incoming mail.

My etc/imapd.conf file looks like this:
configdirectory: /var/lib/imap
partition-default: /var/spool/imap
admins: cyrus
sievedir: /var/lib/imap/sieve
sendmail: /usr/sbin/sendmail
hashimapspool: true
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN
tls_cert_file: /etc/pki/cyrus-imapd/cyrus-imapd.pem
tls_key_file: /etc/pki/cyrus-imapd/cyrus-imapd.pem
tls_ca_file: /etc/pki/tls/certs/ca-bundle.crt
allowplaintext: yes
altnamespace: yes

I'm going to find out what's up, it's just a matter of time :)


-Original Message-
From: Paul Mecham [mailto:pmec...@proapphosting.com] 
Sent: Monday, December 19, 2011 11:10 AM
To: Christian Mack; users@sogo.nu
Subject: RE: [SOGo] Probably another lame question but here goes

Thank you for your reply, I really, really appreciate it.  I'm sorry I don't 
believe I understand your questions 100% but I think I might be getting the 
gist of it. 

As mentioned earlier we're using Cyrus, PostFix and Postgresql per the SOGO 
install recommendations.  To send and retrieve mail we're using SMTP and 
IMAPI/CYRUS.  

Through the SOGO Web interface we can login and send mail and that mail get to 
it's destination; we have yet to see mail come to the inbox.  


We've got a server whose CentOS host name is:
pahsogo1.pah.local

The name that's recognized from an IP name resolution perspective is 
mail.rvscapes.com

The mail server name from an MX mail record perspective is:
rvscapes.com


As a quick aside, we had an initial problem that was resolved with your teams 
help where we were getting the return email address of 
pmec...@mail.rvscapes.com but now, with your help, we got the reply email 
address coming back as pmec...@rvscapes.com.  Thank you for helping get over 
that bump even though it was not in you software where we had to configure the 
repair.

When we respond to an email sent from SOGO, the response email appears to get 
sent to our server because we can see the contents of the reply stored in files 
in the /home/pmecham/Maildir/new/ Folder in filenames that are named:
1324050827.V2aIe20b1M282935.pahsogo1.pah.local

What I'm not getting is how to tell SOGO or Thunderbird for that matter to look 
in this areas for these return emails.  I'm not even sure if it (postfix or 
cyrus?  I'm thinking postfix is making these files) works off of directories or 
some sort of LDAP property it's expecting?

From what I believe I hear you saying is that if we had our server name named 
mail.rvscapes.com then it would be likely, that the default setup would have 
worked out of the box, but because we've got different names we need to set 
some sort of configuration option somewhere to map pahsogo1.pah.local to 
mail.rvscapes.com?

As for answers to your questions (and thanks again for taking the time to 
respond):
Q. Can you connect with the parameters given in your SOGo configuration per 
IMAP client?

A.
I'm using the cyradm, client, and can see mailboxes and  ACL information, but 
I don't think you're asking about this client, am I correct? 

We also used thunderbird to hook up to our mail server, but it's the same as 
SOGO in that it can't see any of the incoming mail.  We can copy messages to 
the inbox and then we can see them in both SOGO WEB interface and Thuderbird so 
they appear to both be looking at the same INBOX, but oddly enough we can't 
create sub folders off of the inbox and we never see any of our response emails 
in either the Thunderbird or through the SOGO web interface.  So I'm thinking 
that the INBOX is somehow not connected to where our incoming mail is going.

I'm pretty sure this is not a SOGO issue.  It's that I'm retarded and don't 
know how to map or set the ACL for the INBOX correctly .  In my defense the 
INBOX seems like it's a special folder that is represented by the LDAP 
directory user.pmecham, but I'm not really clear if that statement is accurate. 
 I've tried adding user.pmecham.INBOX but that just made a new folder called 
inbox.

I believe it's the Postfix process that is creating the files that contain the 
reply's to our emails begin sent into the server but I'm not sure how configure 
Postfix or LDAP/SOSO/Thunderbird to hook the INBOX to the correct 
directories/service/etc.

Q. How did you change your configuration?
Here's my GNUSETUP
?xml version=1.0 encoding=UTF-8?
!DOCTYPE plist PUBLIC -//GNUstep//DTD plist 0.9//EN 
http://www.gnustep.org/plist-0_9.xml;
plist version=0.9
dict
keyNSGlobalDomain/key
dict
/dict
keysogod/key
dict
keySOGoMailShowSubscribedFoldersOnly/key
stringNO/string
keyGCSFolderDebugEnabled/key
stringYES/string
keyGCSFolderStoreDebugEnabled/key
stringYES/string

[SOGo] Probably another lame question but here goes....

2011-12-16 Thread Paul Mecham
I can send mail with sogo and I receive the mail but only in the file system 
directory.  It does not show up in the sogo in mail box.  Can someone give me a 
hint about what ldap property or what .GNUstepDefaults entry controls how the 
imap mailbox folders are seen by SOGO?

I can see the files with the incoming mail, they are in my
/home/pmehcam/Maildir/new/
Folder in filenames that look like:
1324050827.V2aIe20b1M282935.pahsogo1.pah.local

I'm wondering if it has something to do with the pahsogo1.pah.local not 
matching my domain name of mail.rvscapes.com?

I'm so sorry I'm slow catching on.  Thanks for any help you can provde.

Paul

-Original Message-
From: Emmanuel Dreyfus [mailto:m...@netbsd.org] 
Sent: Friday, December 16, 2011 7:29 AM
To: users@sogo.nu
Subject: Re: [SOGo] LDAP search broken

Hello

No reply on this one? This is an annoying problem...

On Wed, Dec 14, 2011 at 11:25:53AM +, Emmanuel Dreyfus wrote:
 Hello
 
 It seems I cannot get LDAP authentication working, while it works for 
 the address book. When credentials should be validated by LDAP, it 
 always fail, and I have this in the logs:
 2011-12-14 12:10:39.717 sogod[12062] -[NGLdapConnection 
 _searchAtBaseDN:qualifier:attributes:scope:]: search with at base 
 àL»˜Kpº filter àL»HD–ºK for attrs  RK»€UcºI
 
 It seems the LDAP parameters did not made their way to the function 
 that uses them. This is SOGO 2.0.0b3.

--
Emmanuel Dreyfus
m...@netbsd.org
--
users@sogo.nu
https://inverse.ca/sogo/lists
-- 
users@sogo.nu
https://inverse.ca/sogo/lists