Sponsored Content
Full Discussion: UW imap and MacOSXS 1.2
Top Forums UNIX for Dummies Questions & Answers UW imap and MacOSXS 1.2 Post 6826 by Jude on Thursday 13th of September 2001 05:12:29 AM
Old 09-13-2001
UW imap and MacOSXS 1.2

Hi all,

I'm a totally newbie in this Unix-wonderland and I'm lost every now-and-then. Now I'm really confused with building UW imap in MacOSXS 1.2. I try to follow the instructions, but when I hit "make osx" I'll get the following answer:

"make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox' EXTRAAUTHENTICATORS='' PASSWDTYPE=std SSLTYPE=none EXTRASPECIALS='' BUILDTYPE=osx
Rebuilding c-client for osx...
touch c-client/SPECIALS
cd c-client;make all CC=`cat CCTYPE` \
CFLAGS="`cat CFLAGS`" `cat SPECIALS`
make[2]: Makefile: No such file or directory
make[2]: *** No rule to make target `all'. Stop.
make[1]: *** [rebuild] Error 2
make: *** [osx] Error 2"

Does anybody have a clue what I should do now?

TIA

Jude
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

IMAP on Redhat?

Does Redhat 9 come with an IMAP server? If so, how do I set it up? (1 Reply)
Discussion started by: Spetnik
1 Replies

2. Linux

pop3 and imap problem

Hi all I have a Redhat 8 box running sendmail-8.12.8-9.80. I use both imap and pop3 for clients to donwlaod mails. imap is used by some application related stuff. The users use opp3 to download their mails. The problem started a yesterday when 1 user complained that he was not able to... (2 Replies)
Discussion started by: skotapal
2 Replies

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

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

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

7. Linux

uw-imap

Hi guys. Is uw-imap maintained? according to their ftp site last version is imap-2007e. is it good to use uw-imap instead of dovecot or other imap daemons? which one do you suggest? I really have problem with dovecot. it's configuration is complex(at least for me). I don't prefer much... (3 Replies)
Discussion started by: majid.merkava
3 Replies
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)
All times are GMT -4. The time now is 04:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy