saslauthd

2004-11-05 Thread W . Andrew Loe III
I am trying to get PLAIN authentication over TLS to work with postfix. 
I am having a problem with getting saslauthd (checking against system 
users) to run. /etc/init.d/saslauthd exists, but it doesn't do anything 
- if I want saslauthd to run I have to manually run /usr/sbin/saslauthd 
- clearly not the way to do this. The init script is completely dead no 
mater what I send to it I get nothing back - is it known to be broken? 
Also I have postfix-tls installed (testing distribution), this should 
properly use sasl2 not sasl, but it seems that it never finds my 
smtpd.conf, so it doesn't know to use saslauthd to check if the user 
authenticates - leaving me out in the cold :(

Suggestions on getting saslauthd running correctly and then getting 
this whole system working? I know I'm close but the errors/warning in 
/var/log/mail.log suck - they just tell me it doesn't work - which I 
already know. Thanks!

-- Andrew
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


New SSL Certificates for Postfix & Courier-imap

2004-12-13 Thread W . Andrew Loe III
I am trying to figure out how to re-build my SSL certificates for 
postfix and courier-imap. Right now my certificate for postfix has some 
errors on it (wrong CN), but I am able to download it and set it to be 
accepted by OS X (ends pop-ups in Mail.app). My courier-imap 
certificate does not work in OS X, I've tried using mkimapdcert in 
/usr/sbin/ but it is not generating certificates that are compatible 
with OS X. Suggestions on how I can use OpenSSL to generate 
certificates for both?

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Mailman Broken

2004-12-28 Thread W . Andrew Loe III
I'm asking this question here as more people on this list probably have 
experience with with mailman. I had mailman installed on my system, but 
stupidly apt-get --purge'd it. Now I cannot get it to re-install 
correctly:

Selecting previously deselected package mailman.
(Reading database ... 35297 files and directories currently installed.)
Unpacking mailman (from .../mailman_2.1.5-4_i386.deb) ...
Setting up mailman (2.1.5-4) ...
Looking for enabled languages (this may take some time) ... done.
Installing site language en 
 done.
Configuring mailman for domain mydomain1.com
mydomain2com
mydomain3.com ...
sed: -e expression #1, char 43: unterminated `s' command
dpkg: error processing mailman (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 mailman
E: Sub-process /usr/bin/dpkg returned an error code (1)
[EMAIL PROTECTED]>>

I've tried apt-get --fix-broken, but haven't had any luck there. I've 
tried removing it and then searching my entire system for any remnants 
to remove, to no avail. I'm pretty sure this is probably my ignorance 
of how to properly use apt-get, but the documentation is not helping me 
at all. Thank you for your time.

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Mailman Broken

2004-12-28 Thread W . Andrew Loe III
I'm asking this question here as more people on this list probably have 
experience with with mailman. I had mailman installed on my system, but 
stupidly apt-get --purge'd it. Now I cannot get it to re-install 
correctly:

Selecting previously deselected package mailman.
(Reading database ... 35297 files and directories currently installed.)
Unpacking mailman (from .../mailman_2.1.5-4_i386.deb) ...
Setting up mailman (2.1.5-4) ...
Looking for enabled languages (this may take some time) ... done.
Installing site language en 
 done.
Configuring mailman for domain mydomain1.com
mydomain2com
mydomain3.com ...
sed: -e expression #1, char 43: unterminated `s' command
dpkg: error processing mailman (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 mailman
E: Sub-process /usr/bin/dpkg returned an error code (1)
[EMAIL PROTECTED]>>

I've tried apt-get --fix-broken, but haven't had any luck there. I've 
tried removing it and then searching my entire system for any remnants 
to remove, to no avail. I'm pretty sure this is probably my ignorance 
of how to properly use apt-get, but the documentation is not helping me 
at all. Thank you for your time.

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


IMAP Servers

2005-01-12 Thread W. Andrew Loe III
I'm currently using Courier-IMAP as my IMAP mail server, but the way it 
handles folders is a bit annoying (.FolderName/cur/ .FolderName/new/). 
Is this standard IMAP protocol, or do different servers handle this 
differently? Which other servers should I check out?




Re: IMAP Servers

2005-01-12 Thread W. Andrew Loe III
Michael F. Sprague wrote:
W. Andrew Loe III <[EMAIL PROTECTED]> wrote:
 

I'm currently using Courier-IMAP as my IMAP mail server, but the way it 
handles folders is a bit annoying (.FolderName/cur/ .FolderName/new/). 
Is this standard IMAP protocol, or do different servers handle this 
differently? Which other servers should I check out?
   

The format you're describing is maildir which Courier happens to implement.
Other apps use maildir too.  If you're looking for something that does IMAP,
you may want to check out Cyrus.  I've used it successfully but it has its
own mailstore.  It's similar to maildir in that each message is stored in its
own file, but it doesn't have the 'new' and 'cur' subdirectories, etc.
thanks,
mikeS
 

I'm sorry, I meant to refer to its implementation of Maildir. Is this 
the standard format? I had a lot of trouble getting this format to work 
well with Apple Mail. I'm pretty sure its Mail's issue as thunderbird 
works perfectly.