Sponsored Content
Full Discussion: Courier-IMAP 4.1
Top Forums UNIX for Advanced & Expert Users Courier-IMAP 4.1 Post 302093018 by blowtorch on Monday 16th of October 2006 09:55:43 PM
Old 10-16-2006
Can you telnet to port 143 from any system on the network? Your process shouldn't be listening on 127.0.0.1:143. This means that it is listening on the loop-back address. The process should listen on <server_ip>:143.

Check the config files and change the IP to your server's network IP.
 

6 More Discussions You Might Find Interesting

1. 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

2. 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

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. 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

5. 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

6. Ubuntu

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... (0 Replies)
Discussion started by: rbizzell
0 Replies
IMAP(3pm)						User Contributed Perl Documentation						 IMAP(3pm)

NAME
Cyrus::IMAP - Interface to Cyrus imclient library SYNOPSIS
use Cyrus::IMAP; my $client = Cyrus::IMAP->new('mailhost'[, $flags]); $flags = Cyrus::IMAP::CONN_NONSYNCLITERAL; ($server, $mailbox) = Cyrus::IMAP->fromURL($url); $url = Cyrus::IMAP->toURL($server, $mailbox); $client->setflags($flags); $client->clearflags(Cyrus::IMAP::CONN_INITIALRESPONSE); $flags = $client->flags; $server = $client->servername; $client->authenticate; $flags = Cyrus::IMAP::CALLBACK_NUMBERED || Cyrus::IMAP::CALLBACK_NOLITERAL; $client->addcallback({-trigger => $str, -flags => $flags, -callback => &cb, -rock => $var}, ...); $client->send(&callback, &cbdata, $format, ...); $client->processoneevent; ($result, $text) = $client->send(undef, undef, $format, ...); ($fd, $writepending) = $client->getselectinfo; DESCRIPTION
The Cyrus::IMAP module provides an interface to the Cyrus imclient library. These are primarily useful for implementing cyradm operations within a Perl script; there are easier ways to implement general client operations, although they may be more limited in terms of authentication options when talking to a Cyrus imapd. In the normal case, one will attach to a Cyrus server and authenticate using the best available method: my $client = Cyrus::IMAP::new('imap'); $client->authenticate; if (!$client->send('', '', 'CREATE %s', 'user.' . $username)) { warn "createmailbox user.$username: $@"; } In simple mode as used above, "send()" is invoked with "undef", 0, or '' for the callback and rock (callback data) arguments; it returns a list of "($result, $text)" from the command. If invoked in scalar context, it returns $result and places $text in $@. In this mode, there is no need to use "processoneevent()". If more control is desired, use the callback and rock arguments and invoke "processoneevent()" regularly to receive results from the IMAP server. If still more control is needed, the "getselectinfo()" method returns a list containing a file descriptor (not Perl filehandle) which can be passed to select(); if the second element of the list is true, you should include it in the write mask as well as the read mask because the imclient library needs to perform queued output. For more information, consult the Cyrus documentation. NOTES
"send()" behaves as if the "Cyrus::IMAP::CONN_NONSYNCLITERAL" flag is always set. This is because it is a wrapper for the C version, which cannot be made directly available from Perl, and synchronous literals require interaction with the IMAP server while parsing the format string. This is planned to be fixed in the future. The 'LOGIN' mechanism can be used to authenticate with a plaintext username and password. This is intended as a workaround for a bug in early SASL implementations; use of Cyrus::IMAP with non-Cyrus servers is not recommended, primarily because there are easier ways to implement IMAP client functionality in Perl. (However, if you need SASL support, "Cyrus::IMAP" is currently the only way to get it.) The file descriptor returned by "getselectinfo()" should not be used for anything other than "select()". In particular, I/O on the file descriptor will almost certainly cause more problems than whatever problem you think you are trying to solve. The toURL and fromURL routines are to ease conversion between URLs and IMAP mailbox and server combinations, and are a simple frontend for the libcyrus functions of the same name. The imparse library routines are not implemented, because they are little more than a (failed) attempt to make parsing as simple in C as it is in Perl. This module exists primarily so we can integrate Cyrus administration into our Perl-based account management system, and secondarily so that we can rewrite cyradm in a sensible language instead of Tcl. Usability for other purposes is not guaranteed. AUTHORs Brandon S. Allbery <allbery@ece.cmu.edu>, Rob Siemborski <rjs3+@andrew.cmu.edu> SEE ALSO
Cyrus::IMAP::Admin perl(1), cyradm(1), imclient(3), imapd(8). perl v5.14.2 2012-04-19 IMAP(3pm)
All times are GMT -4. The time now is 04:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy