Courier-IMap


 
Thread Tools Search this Thread
Operating Systems Linux Ubuntu Courier-IMap
# 1  
Old 12-10-2009
Courier-IMap

I am running postfix, courier-imap and Atmail Webmail client. I can telnet to port 143 I can send mail from the command line using the mail command to the user. When I try to login through webmail using the atmail client nothing happens. I check the the maillog and it shows the localhost address and nothing else. I doesn't show the username that tried to login or anything. When I do netstat is shows tcp name of server:58700 pop3 close_wait
tcp name of server:34430 imap2 close_wait
tcp6 imap2 listen
I can login from the command line if I do telnet localhost 143
When I check the log files it shows
imapd: connection, ip=[::ffff:127.0.0.1]
Can someone please help me?????????????????????????
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

Courier (authlib) and vacation

Hello, I want to use vacation autoreply with courier userdb Users is in "/etc/courier/userdb" I search on forum but dont find anything about (only found for local and mysql user) How to configure an user to use vacation (or other stuff) to make autoreply with userdb ? Plateform :... (0 Replies)
Discussion started by: safsound
0 Replies

2. Ubuntu

Courier-IMAP

I am running Unbuntu Server. I have installed postfix and courie-imap. I cant seem to be able to login using imap. Login failed. I can telnet using imap. I have a valid user. Authdaemonrc is running using authpam which is the default. I am running atmail webclient. What else do I need to check? (0 Replies)
Discussion started by: rbizzell
0 Replies

3. UNIX for Advanced & Expert Users

Courier IMAP to Dovecot Migration

Hi, I have done a very stupid thing. I have migrated from Courier IMAP and POP to Dovecot without reading about the migration process. ( I resolve not to repeat it again). Now it has been 2 weeks. Webmail seems to work fine. I have problems with POP3. POP3 clients don't remove messages from the... (2 Replies)
Discussion started by: tmm
2 Replies

4. UNIX for Advanced & Expert Users

Courier-IMAP 4.1

I am running Freebsd 6.1, Postfix 2.2, and Courier-IMAP 4.1 I can telnet to port 143 I can't connect to IMAP server using microsoft outlook or any client. The authdaemon is running and working correctly I did netstat -an | grep -i list and it shows port 143 bound to the localhost 127.0.0.1. I can... (1 Reply)
Discussion started by: rbizzell
1 Replies

5. BSD

Courier-IMAP 4.1

I will be using postfix and courier-imap version 4.1. I never configured courier-imap. What configurations files do I have to configure and how do I start courier-imap. There isn't a authdaemonrc file in the courier-imap directorry. The files that are listed are imapd imap-ssl.dist... (0 Replies)
Discussion started by: rbizzell
0 Replies

6. HP-UX

courier-imap auth problem

Hi, My box is freeBSD6 and I've installed courier-imap and I want to authenticate the clients against /etc/passwd file. Inside the configuration file: /usr/local/etc/courier-imap/pop3d I've not these lines : Why? AUTHMODULES="authdaemon" AUTHMODULES_ORIG="authdaemon" Nevertheless I tried... (5 Replies)
Discussion started by: efrenba
5 Replies
Login or Register to Ask a Question
MAKESMTPACCESS, MAKE(8) 				      Double Precision, Inc.					   MAKESMTPACCESS, MAKE(8)

NAME
makesmtpaccess - Build ESMTP server access file SYNOPSIS
makesmtpaccess makesmtpaccess-msa DESCRIPTION
makesmtpaccess rebuilds the contents of the /etc/courier/smtpaccess.dat database from the contents of the files in the /etc/courier/smtpaccess directory. When the esmtpd script starts couriertcpd, the script specifies /etc/courier/smtpaccess.dat file to control access to the Courier mail server's ESMTP daemon. The makesmtpaccess script must be run before any changes in the /etc/courier/smtpaccess directory take effect. The couriertcpd(8)[1] manual page describes the general format of the access file. The default Courier mail server configuration uses the same access file, /etc/courier/smtpaccess.dat for both the regular ESMTP server, and the message submission server on port 587 (RFC 2476[2]). It is possible to use different access files. To do so, create a different access file, edit /etc/courier/esmtpd-msa, and set ACCESSFILE to the filename of the access file directory (the directory containing the plain text files, not the .dat file). Then, use makesmtpaccess-msa instead of makesmtpaccess to build the .dat file. The smtpaccess configuration file The couriertcpd(8)[1] manual page describes the generic format of the access file. The access file specifies what should be done with connections from defined IP address ranges. The basic choices are to accept or reject the connection. Also, the generic format of the access file allows arbitrary environment variables to be set based on the connection's remote IP address. The Courier mail server's ESMTPD server understands the following environment variables, which may be set in the access file: BLOCK If this variable is set to a non-empty value, all mail will be rejected for this connection. The contents of the environment variable will be used as the error message. This is not the same as the couriertcpd access file setting that immediately drops the connection. The incoming connection is accepted, but every message will be rejected. FAXRELAYCLIENT Allow the client to send faxes via the courierfax(8)[3] module. Note When ESMTP authentication is enabled, a successful authentication automatically sets FAXRELAYCLIENT. RELAYCLIENT Allow the client to relay mail. Note When ESMTP authentication is enabled, a successful authentication automatically sets RELAYCLIENT. The following options are typically set globally in the esmtpd configuration file, but may be overriden in the smtpaccess configuration file: BOFHCHECKDNS Do not check the return address's domain in DNS if this environment variable is set to 0. The default value of BOFHCHECKDNS is 1. Note Turning off the DNS check disables a number of options in the bofh configuration file. See courier(8)[4] for more information. BOFHCHECKHELO Set this variable to 1 to check the hostname argument to the ESMTP HELO/EHLO command, as follows: o A hostname that's actually an IP address, and is the same as the connecting ESMTP client's IP address, is valid. o Otherwise hostname should be a valid DNS name with MX and/or A records, with at least one record matching the connecting ESMTP client's IP address. o An ESMTP client with relaying privileges (either due to RELAYCLIENT explicitly set, or if it succesfully authenticates) may use anything for an EHLO/HELO. The EHLO/HELO argument coming from an authenticated/relaying client is not checked. BOFHNOEXPN Disable the EXPN command if this environment variable is set to 1. BOFHNOVRFY Disable the VRFY command if this environment variable is set to 1. Other useful environment variables are listed in the submit(8)[5] manual page. SEE ALSO
esmtpd(8)[6], couriertcpd(8)[1], submit(8)[5]. AUTHOR
Sam Varshavchik Author NOTES
1. couriertcpd(8) [set $man.base.url.for.relative.links]/couriertcpd.html 2. RFC 2476 http://www.rfc-editor.org/rfc/rfc2476.txt 3. courierfax(8) [set $man.base.url.for.relative.links]/courierfax.html 4. courier(8) [set $man.base.url.for.relative.links]/courier.html 5. submit(8) [set $man.base.url.for.relative.links]/submit.html 6. esmtpd(8) [set $man.base.url.for.relative.links]/esmtpd.html Courier Mail Server 08/30/2011 MAKESMTPACCESS, MAKE(8)