Hi all,
I just setup postfix on my server thats running Centos 5.x with webmin. Now I can send email out of the server but I cant receive email. Server side I can telnet into the 110 and 25 port but coming from the outside of the box I can only telnet into the 110 port but not port 25. The... (1 Reply)
Guys
i have 2 SUSE Linux Enterprise Server 10 SP1 (i586) boxes.if i take a look into /etc/security/access.conf ,i see following lines at the eof
# All other users should be denied to get access from all sources.
#- : ALL : ALL
- : myID : ALL
now earlier i had written scripts where files... (1 Reply)
hi all,
please help me in this regard. I am VFP 9 programmer. I want to send the mail from within VFP 9 application. I have used CDO of microsoft which is working fine. however to be able to send the mail i have to setup the router gateway on user machine which enable him to surf through the... (0 Replies)
hi all.
Am using smtpd_recipient_restrictions & check_recipient_access in postfix.
The hash file looks like this:
emailaddress1 HOLD
emailaddress2 HOLD
The aim is to place email from these recipients in the hold directory,check them then reinject them back in postfix on some... (0 Replies)
Hi All,
I have a root access for one of the server. But, when i try to cd one particular directory i will get the access denied message. Even though that particular directory is created under root. What would be the cause for this? I really wonder if any one have answer for my... (20 Replies)
im able to install postfix on my ubuntu server. no issues. but ican't send mail.
i dont know what to put for the "relayhost". i've googled this endlessly but i'm clueless. isn't there a general smart host i can use that'll allow me to send?
i dont care for receiving mail. i just want to be... (1 Reply)
I login to a server and get a Access Denied Prompt but I clearly lets me into the prompt with Putty.
I do a sudo -s enter my password tells me Access Denied but I am clearly now Root
Just wondering why this is so? what is misconfigured? I mean its not prohibiting me from anything, this is more... (3 Replies)
Whats the difference between mail and mailx?
I'm trying to troubleshoot a problem where I can send mail from server A with this `echo $MESSAGE | mail -s "$SUBJECT" -r $FROM $RECIPIENTS` command but executing the same command from server B throws me this error (Both servers are RHEL)
... (1 Reply)
Hello,
I am trying to setup a mail server (Postfix) on Ubuntu Server at my end but facing Relay access denied issue.
Mail Server DNS is mydomain.com and MX record is also added to the DNS server for the same. When i am sending out emails from outer domain to user1@mydomain.com, I configured... (2 Replies)
I'm unable to send email from my Linux server despite SMTP port 25 Active and Listening.
# hostname
TechX
I checked the mail log ( /var/log/maillog ) and found the below error.
I'm sharing all the ".cf" files seen in the error log.
1.
# more /etc/postfix/main.cf
# postfix... (0 Replies)
Discussion started by: mohtashims
0 Replies
LEARN ABOUT XFREE86
git-imap-send
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)