07-15-2009
Mail Problem. Maybe, it is a DNS Problem!
Hi,
i've a redhat linux 9 upadated by redhat from 7 version to 9 version. A couple of days ago i was a problem with my mail, in other words i'm not able to get any email nor to send any email. I've a proxy configuration and i tried to set iptables in order to verify the port. The 110,255 and 995 ports are opened but the mails on the client stations doesn't work. The mails works only on the server station in eth1 but it doesn't work in eth0. Therefore,i tried to verify name sever and it is incomplete, probably the automatic update raised the problem. Furthermore, i tried to pinging the host name (e.g. pop.gmail.com, domainame, ecc...) but it failed,the same thinks with the telnet command, the message was impossible to connect to the hostname or domainame.
I believe that it could be a band problem because it could not be able to link the IP with the hosts. Someone could ask to me why the http links work, so i believe that the optenet service is able to fix this problem,but only against http links.
Any idea? what do you think?
pintalgi
Last edited by pintalgi; 07-15-2009 at 07:19 AM..
10 More Discussions You Might Find Interesting
1. IP Networking
helo all
i got problem in my network
i got sun 206 and i work with sendmail
when i had the praimery dns of my isp i can send mail from the server but
i cant send from the clinet (outlook in the network) and if i chnage it to secundery dns off my isp i can send frome the server and frome the... (2 Replies)
Discussion started by: nis
2 Replies
2. IP Networking
Hello!
I´ve got a problem with the dns on one of our servers.
When i try to look someting up with either nslookup or ping i get the folowing error message.
--------------------------------------------------------------------------------
# nslookup sun.com
*** Can't find server name for... (4 Replies)
Discussion started by: dozy
4 Replies
3. IP Networking
Hello Everyone,
I am working on a HP-Unix machine and I am trying to get it to use the University's DNS servers. Long story short... the resolv.conf file is ok :
nameserver 149.150.51.1
nameserver 149.150.51.2
search shu.edu
The hosts file is ok.
And when I make the nsswitch.conf file... (1 Reply)
Discussion started by: loslappy
1 Replies
4. Solaris
hello !!!
I have some problem for Sun Solaris DNS i already configured named.boot , named.rev, named.hosts but when i start the DNS service there is an error " error cannot find named.conf " in my manual there is no named.conf configuration it said that if you configure named.boot... (3 Replies)
Discussion started by: giancarlodjabon
3 Replies
5. UNIX for Advanced & Expert Users
It seems that mail from our servers are going through a third party security mail scanner (offsite),
due the the mx records specified on our internal and external DNS servers.
However, our internal user to user email does not go through the third party security mail scanner.
I discovered... (2 Replies)
Discussion started by: xnightcrawl
2 Replies
6. Shell Programming and Scripting
sorry guys,
I had big problem solving this simple problem..:D hope expertise here can solve this problem.
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 1361
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;. IN... (0 Replies)
Discussion started by: unknown2205
0 Replies
7. UNIX for Advanced & Expert Users
Hello again I having a wired problem if use nslookup to check some changes that I made to the blackhole list.First I'll check a site that I know has access throught our sever and it would time out. Then If I'll try it 10 seconds later it would work. Isn't that wierd. But my blackhole list site... (0 Replies)
Discussion started by: aojmoj
0 Replies
8. Ubuntu
hello. i'm running ubuntu desktop 8.04 and i use it ot host some sites (actually i'm trying )
well i'm running to websites (with the same dns,ip) site1.com work fine but site2.com give me this
Hmm, site2.com isn't loading right now.
The computers that run site2.com are having some trouble.... (2 Replies)
Discussion started by: mazi
2 Replies
9. IP Networking
I uploaded a new domain and I am having problems with the paths...
Works..shop.mydomain.com/index.php?main_page=contact.
Does Not Work..shop.mydomain.com/contact/.
copied the entire directory from a working directory and changed the appropriate paths where necessary (as usual) so ...?
... (3 Replies)
Discussion started by: tifischer
3 Replies
10. Debian
I have a standalone PC running Debian 6. DNS stopped working suddenly. I haven't changed anything. Email works because it has the ip address of the mail server. Firefox can apparently fend for itself. nslookup some_url or nslookup some_ip_address returns: nslookup: parse of /etc/resolv.conf... (4 Replies)
Discussion started by: snorkack59
4 Replies
LEARN ABOUT OSX
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)