10 More Discussions You Might Find Interesting
1. AIX
Hi there,
I have configured sendmail in AIX 6.1 and able to send emails to most of the domains like yahoo and gmail. But certain domains are denying to verify my domain probably due to the masquarding not happening correctly. Following are some logs of sendmail command.... (9 Replies)
Discussion started by: sraj142
9 Replies
2. Solaris
Hi,
when i am trying to send more than 50000 emails by using solaris sendmail utility, server is getting hanged up, needs to restart it once again. but it is sending nearly 20000 emails with out any issues. So what the configuration changes i need to make for the solaris sendmail utility to... (0 Replies)
Discussion started by: anilmanepu
0 Replies
3. Linux
I am trying to send mail from my CentOS server.
I have made nacessory changes required from sendmail.
But it is not working.
I am getting following messages in maillog-
Dec 17 09:25:12 localhost sendmail: mBH3tCTi016891: fps.company.com did not issue MAIL/EXPN/VRFY/ETRN during... (1 Reply)
Discussion started by: kailas.awchar
1 Replies
4. AIX
I get the following error while trying to send mail from my AIX box. I have cross checked the sendmail.cf file of this system with a working system (similar h/w and o/s) and found no difference. can somebody sugget??
/etc/sendmail.cf: line 98: readcf: map arith: class arith is not available... (1 Reply)
Discussion started by: gsabarinath
1 Replies
5. UNIX for Dummies Questions & Answers
I have a user who's email comes out looking like this:
From name@domain.com Wed Aug 6 15:36:39 2008
Return-Path: <name@domain.com>
X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on it2
X-Spam-Level: *
X-Spam-Status: No, score=1.5 required=5.0 tests=AWL,BAYES_20,MISSING_SUBJECT,... (1 Reply)
Discussion started by: photon
1 Replies
6. Red Hat
Hi everyone...
i'm trying to send mail with attachment using /usr/sbin/sendmail
and from some reason it's not working for me only from one computer.
the command i'm using is:
cat /etc/fstab | /usr/sbin/sendmail -t RECIPIENT@MAIL.COM
am i doing something wrong?
p.s. the OS is RedHat. (6 Replies)
Discussion started by: eliraza6
6 Replies
7. UNIX for Dummies Questions & Answers
I replaced sendmail.cf (made a abckup first) with main.cf and stopped and then stopped and started sendmail. I am still getting the following:
ibasdb02:/ # May 21 14:06:23 ibasdb02 sendmail: l4L
I6Np3001094: Losing ./qfl4LI6Np3001094: savemail panic
and this message in my log:
May 21... (3 Replies)
Discussion started by: hshapiro
3 Replies
8. UNIX for Dummies Questions & Answers
Hi all,
I am new to this forums, so please be kind to me :)
Anyways, I have this problem when I am trying to send out email using sendmail.
I can send an email to gmail.com or other email host, but when I am trying to send an email to email address removed by moderator or anything to the... (2 Replies)
Discussion started by: iluvhk
2 Replies
9. UNIX for Advanced & Expert Users
Hi,
I have some problem with sendmail daemon.
Earlier it was working fine as I used to get alert mail through crontab jobs.
Two days back it stopped sending alert messages.
When I executed mail command from shell prompt, I could read all the pending messages, generated through crontab... (1 Reply)
Discussion started by: amit_sapre
1 Replies
10. UNIX for Dummies Questions & Answers
I run UNIX and PHP
I use a forum (ibf)
and the mail() function from PHP only allows emails to be sent to an email account that is on my server, so IT doesn't send any emails for example to eden@hotmail.com
How can I fix this?
I have to edit php.ini???'
Please help me
Thanks. (3 Replies)
Discussion started by: eden2
3 Replies
addresses(5) File Formats Manual addresses(5)
NAME
addresses - formats for Internet mail addresses
INTRODUCTION
A mail address is a string of characters containing @.
Every mail address has a local part and a domain part. The domain part is everything after the final @. The local part is everything
before.
For example, the mail addresses
God@heaven.af.mil
@heaven.af.mil
@at@@heaven.af.mil
all have domain part heaven.af.mil. The local parts are God, empty, and @at@.
Some domains have owners. It is up to the owner of heaven.af.mil to say how mail messages will be delivered to addresses with domain part
heaven.af.mil.
The domain part of an address is interpreted without regard to case, so
God@heaven.af.mil
God@HEAVEN.AF.MIL
God@Heaven.AF.Mil
all refer to the same domain.
There is one exceptional address that does not contain an @: namely, the empty string. The empty string cannot be used as a recipient
address. It can be used as a sender address so that the real sender doesn't receive bounces.
QMAIL EXTENSIONS
The qmail system allows several further types of addresses in mail envelopes.
First, an envelope recipient address without an @ is interpreted as being at envnoathost. For example, if envnoathost is heaven.af.mil,
the address God will be rewritten as God@heaven.af.mil.
Second, the address #@[] is used as an envelope sender address for double bounces.
Third, envelope sender addresses of the form pre@host-@[] are used to support variable envelope return paths (VERPs). qmail-send will re-
write pre@host-@[] as prerecip=domain@host for deliveries to recip@domain. Bounces directly from qmail-send will come back to pre@host.
CHOOSING MAIL ADDRESSES
Here are some suggestions on choosing mail addresses for the Internet.
Do not use non-ASCII characters. Under RFC 822 and RFC 821, these characters cannot be used in mail headers or in SMTP commands. In prac-
tice, they are regularly corrupted.
Do not use ASCII control characters. NUL is regularly corrupted. CR and LF cannot be used in some combinations and are corrupted in all.
None of these characters are usable on business cards.
Avoid spaces and the characters
"<>()[],;:
These all require quoting in mail headers and in SMTP. Many existing mail programs do not handle quoting properly.
Do not use @ in a local part. @ requires quoting in mail headers and in SMTP. Many programs incorrectly look for the first @, rather than
the last @, to find the domain part of an address.
In a local part, do not use two consecutive dots, a dot at the beginning, or a dot at the end. Any of these would require quoting in mail
headers.
Do not use an empty local part; it cannot appear in SMTP commands.
Avoid local parts longer than 64 characters.
Be wary of uppercase letters in local parts. Some mail programs (and users!) will incorrectly convert God@heaven.af.mil to
god@heaven.af.mil.
Be wary of the following characters:
$&!#~`'^*|{}
Some users will not know how to feed these characters safely to their mail programs.
In domain names, stick to letters, digits, dash, and dot. One popular DNS resolver has, under the banner of security, recently begun
destroying domain names that contain certain other characters, including underscore. Exception: A dotted-decimal IP address in brackets,
such as [127.0.0.1], identifies a domain owned by whoever owns the host at that IP address, and can be used safely.
In a domain name, do not use two consecutive dots, a dot at the beginning, or a dot at the end. This means that, when a domain name is
broken down into components separated by dots, there are no empty components.
Always use at least one dot in a domain name. If you own the mil domain, don't bother using the address root@mil; most users will be
unable to send messages to that address. Same for the root domain.
Avoid domain names longer than 64 characters.
ENCODED ADDRESSES IN SMTP COMMANDS
RFC 821 defines an encoding of mail addresses in SMTP. For example, the addresses
God@heaven.af.mil
a"quote@heaven.af.mil
The Almighty.One@heaven.af.mil
could be encoded in RCPT commands as
RCPT TO:<God@heaven.af.mil>
RCPT TO:<a"quote@heaven.af.mil>
RCPT TO:<The Almighty.One@heaven.af.mil>
There are several restrictions in RFC 821 on the mail addresses that can be used over SMTP. Non-ASCII characters are prohibited. The
local part must not be empty. The domain part must be a sequence of elements separated by dots, where each element is either a component,
a sequence of digits preceded by #, or a dotted-decimal IP address surrounded by brackets. The only allowable characters in components are
letters, digits, and dashes. Every component must (believe it or not) have at least three characters; the first character must be a let-
ter; the last character must not be a hyphen.
ENCODED ADDRESSES IN MAIL HEADERS
RFC 822 defines an encoding of mail addresses in certain header fields in a mail message. For example, the addresses
God@heaven.af.mil
a"quote@heaven.af.mil
The Almighty.One@heaven.af.mil
could be encoded in a To field as
To: God@heaven.af.mil,
<@brl.mil:"a"quote"@heaven.af.mil>,
"The Almighty".One@heaven.af.mil
or perhaps
To: < "God"@heaven .af.mil>,
"a"quote" (Who?) @ heaven . af. mil
, God<"The Almighty.One"@heaven.af.mil>
There are several restrictions on the mail addresses that can be used in these header fields. Non-ASCII characters are prohibited. The
domain part must be a sequence of elements separated by dots, where each element either (1) begins with [ and ends with ] or (2) is a
nonempty string of printable ASCII characters not including any of
".<>()[],;:
and not including space.
SEE ALSO
envelopes(5), qmail-header(5), qmail-inject(8), qmail-remote(8), qmail-smtpd(8)
addresses(5)