Courier-IMAP


 
Thread Tools Search this Thread
Operating Systems Linux Ubuntu Courier-IMAP
# 1  
Old 08-25-2009
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?
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

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

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

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
GIT-IMAP-SEND(1)						    Git Manual							  GIT-IMAP-SEND(1)

NAME
git-imap-send - Send a collection of patches from stdin to an IMAP folder SYNOPSIS
git imap-send [-v] [-q] [--[no-]curl] DESCRIPTION
This command uploads a mailbox generated with git format-patch into an IMAP drafts folder. This allows patches to be sent as other email is when using mail clients that cannot read mailbox files directly. The command also works with any general mailbox in which emails have the fields "From", "Date", and "Subject" in that order. Typical usage is something like: git format-patch --signoff --stdout --attach origin | git imap-send OPTIONS
-v, --verbose Be verbose. -q, --quiet Be quiet. --curl Use libcurl to communicate with the IMAP server, unless tunneling into it. Ignored if Git was built without the USE_CURL_FOR_IMAP_SEND option set. --no-curl Talk to the IMAP server using git's own IMAP routines instead of using libcurl. Ignored if Git was built with the NO_OPENSSL option set. CONFIGURATION
To use the tool, imap.folder and either imap.tunnel or imap.host must be set to appropriate values. Variables imap.folder The folder to drop the mails into, which is typically the Drafts folder. For example: "INBOX.Drafts", "INBOX/Drafts" or "[Gmail]/Drafts". Required. imap.tunnel Command used to setup a tunnel to the IMAP server through which commands will be piped instead of using a direct network connection to the server. Required when imap.host is not set. imap.host A URL identifying the server. Use a imap:// prefix for non-secure connections and a imaps:// prefix for secure connections. Ignored when imap.tunnel is set, but required otherwise. imap.user The username to use when logging in to the server. imap.pass The password to use when logging in to the server. imap.port An integer port number to connect to on the server. Defaults to 143 for imap:// hosts and 993 for imaps:// hosts. Ignored when imap.tunnel is set. imap.sslverify A boolean to enable/disable verification of the server certificate used by the SSL/TLS connection. Default is true. Ignored when imap.tunnel is set. imap.preformattedHTML A boolean to enable/disable the use of html encoding when sending a patch. An html encoded patch will be bracketed with <pre> and have a content type of text/html. Ironically, enabling this option causes Thunderbird to send the patch as a plain/text, format=fixed email. Default is false. imap.authMethod Specify authenticate method for authentication with IMAP server. If Git was built with the NO_CURL option, or if your curl version is older than 7.34.0, or if you're running git-imap-send with the --no-curl option, the only supported method is CRAM-MD5. If this is not set then git imap-send uses the basic IMAP plaintext LOGIN command. Examples Using tunnel mode: [imap] folder = "INBOX.Drafts" tunnel = "ssh -q -C user@example.com /usr/bin/imapd ./Maildir 2> /dev/null" Using direct mode: [imap] folder = "INBOX.Drafts" host = imap://imap.example.com user = bob pass = p4ssw0rd Using direct mode with SSL: [imap] folder = "INBOX.Drafts" host = imaps://imap.example.com user = bob pass = p4ssw0rd port = 123 sslverify = false EXAMPLE
To submit patches using GMail's IMAP interface, first, edit your ~/.gitconfig to specify your account settings: [imap] folder = "[Gmail]/Drafts" host = imaps://imap.gmail.com user = user@gmail.com port = 993 sslverify = false You might need to instead use: folder = "[Google Mail]/Drafts" if you get an error that the "Folder doesn't exist". Once the commits are ready to be sent, run the following command: $ git format-patch --cover-letter -M --stdout origin/master | git imap-send Just make sure to disable line wrapping in the email client (GMail's web interface will wrap lines no matter what, so you need to use a real IMAP client). CAUTION
It is still your responsibility to make sure that the email message sent by your email program meets the standards of your project. Many projects do not like patches to be attached. Some mail agents will transform patches (e.g. wrap lines, send them as format=flowed) in ways that make them fail. You will get angry flames ridiculing you if you don't check this. Thunderbird in particular is known to be problematic. Thunderbird users may wish to visit this web page for more information: http://kb.mozillazine.org/Plain_text_e-mail_-_Thunderbird#Completely_plain_email SEE ALSO
git-format-patch(1), git-send-email(1), mbox(5) GIT
Part of the git(1) suite Git 2.17.1 10/05/2018 GIT-IMAP-SEND(1)