On Aug 23, 2006, at 8:50 PM, Nicholas Ink wrote:
The first problem I experienced was that there a host name lookup
failure for "gmail.com," which I have subsequently corrected by adding
This is wrong; you should be using an IP address inside the domain-
literal form (square brackets).
You should try to fix whatever the problem with your DNS is, instead.
"dig -t mx gmail.com" should return valid results....
However, there is still a problem, when I
try to send an e-mail, /var/log/maillog says:
Aug 23 23:18:08 arches sm-mta: k7O3I7K2001049:
from=<[EMAIL PROTECTED]>, size=397, class=0, nrcpts=1,
msgid=<[EMAIL PROTECTED]>, proto=ESMTP, daemon=IPv6,
Aug 23 23:18:16 arches sm-mta: STARTTLS=client,
relay=gmail-smtp.l.google.com., version=TLSv1/SSLv3, verify=FAIL,
Aug 23 23:18:16 arches sm-mta: k7O3I7K2001049:
to=<[EMAIL PROTECTED]>, ctladdr=<[EMAIL PROTECTED]> (1007/0),
delay=00:00:08, xdelay=00:00:08, mailer=smtp, pri=30397,
relay=gmail-smtp.l.google.com. [22.214.171.124], dsn=5.0.0,
Aug 23 23:18:16 arches sm-mta: k7O3I7K2001049: k7O3IGK2001051:
DSN: Service unavailable
where arches is my host name. I can't understand why it continues to
say "Service unavailable" when I know Gmail is not experiencing any
downtime or anything else. Is this some sort of spam filter?
Yes, on their side. gmail.com isn't going to relay random email
without you authenticating first, probably; look into configuring
SMTP AUTH on your side, or talk with <[EMAIL PROTECTED]> about
what their requirements are to permit you to relay via their mail
However, normally people configure their machines to relay email via
the SMTP server(s) which your ISP provides, as they are generally
configured to trust their client networks without requiring SMTP AUTH
and thus are easier to use...
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"