12-05-2008
Ahem. Welcome to the club.
There are a couple of blacklisting sites. Scan them regularly to see if your host is blacklisted. If it is, appeal immediately.
As far as your legal question... there are some laws that say that, but who's going to enforce indonesian hackers spamming Canadian businesses using a German domain?
10 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
I have been a member for almost a year now. I have always recieved email notifications when I select "subcribe to this thread" at the bottom of posts that I reply to.
However, over the last month or so, I have not been recieving email notification of replys to posts I respond to.
I have... (6 Replies)
Discussion started by: Kelam_Magnus
6 Replies
2. Shell Programming and Scripting
hello! this is my first post in this forum :)
when sending mail from unix, using the mailx facility, does it save a copy of the sent mail anywhere on the server? Or if the mail is not delivered to the recipient, does it write a notification to the user about the status of the mail?
thanks! (0 Replies)
Discussion started by: starla0316
0 Replies
3. What is on Your Mind?
No, i do NOT mean spam itself, but the word "spam". Here is my shot, which implies a historical dimension of the word, most people might not be aware of:
Sine Prudentia Agitare et Molestare.
What does that tell us about the spamming habits of the ancient Romans?
bakunin (1 Reply)
Discussion started by: bakunin
1 Replies
4. Linux
The mails are reaching from all my domains (hosted in same server) to yahoo properly when tested. But all the mails from a particular domain out of many domains hosted in the server sent to yahoo reaches yahoo's spam box. The host says that this problem is nothing to do with them since it works... (0 Replies)
Discussion started by: lampscholar
0 Replies
5. Programming
I have to run a script provided by a vendor. Its an executable so I can't change it.
basically after I call it it prompts me for a password. The script does not provide a way for me to pass a password with the command that calls the script.
I would like to automate running this script from... (5 Replies)
Discussion started by: guessingo
5 Replies
6. Linux
I am using Linux box. i am able to send mails through sendmail to local and other domains.
i am not receving any incoming mails.
dovecot service is running. (4 Replies)
Discussion started by: harishindn
4 Replies
7. Shell Programming and Scripting
I am using mutt on ksh Unix to send emails to addresses plucked from the database. If the "To:" email address is not longer valid and so the email is not sent to the "To:" recipient, but is sent to the valid cc address, I need to be able to get an error code returned to the shell script so that... (3 Replies)
Discussion started by: jzuber
3 Replies
8. UNIX for Advanced & Expert Users
Hello there,
First of all I tell you that this is my first postfix installation so please be patient...
I have following scenario:
fetchmail --> postfix --> amavis-new --> postfix --> exchange 2010.
Everything -except exchange ;-)- runs on an opensuse 12.1 box.
Now, I have a list of... (0 Replies)
Discussion started by: lpacor
0 Replies
9. UNIX and Linux Applications
Hello there,
First of all I tell you that this is my first postfix installation so please be patient...
I have following scenario:
fetchmail --> postfix --> amavis-new --> postfix --> exchange 2010.
Everything -except exchange ;-)- runs on an opensuse 12.1 box.
Now, I have a list of... (0 Replies)
Discussion started by: lpacor
0 Replies
10. UNIX for Dummies Questions & Answers
Hello there,
First of all I tell you that this is my first postfix installation so please be patient...
I have following scenario:
fetchmail --> postfix --> amavis-new --> postfix --> exchange 2010.
Everything -except exchange ;-)- runs on an opensuse 12.1 box.
Now, I have a list of... (2 Replies)
Discussion started by: lpacor
2 Replies
LEARN ABOUT FREEBSD
mailaddr
MAILADDR(7) BSD Miscellaneous Information Manual MAILADDR(7)
NAME
mailaddr -- mail addressing description
DESCRIPTION
Mail addresses are based on the Internet protocol listed at the end of this manual page. These addresses are in the general format
user@domain
where a domain is a hierarchical dot separated list of subdomains. For example, a valid address is:
eric@CS.Berkeley.EDU
Unlike some other forms of addressing, domains do not imply any routing. Thus, although this address is specified as an Internet address, it
might travel by an alternate route if that were more convenient or efficient. For example, at Berkeley, the associated message would proba-
bly go directly to CS over the Ethernet rather than going via the Berkeley Internet gateway.
Abbreviation.
Under certain circumstances it may not be necessary to type the entire domain name. In general, anything following the first dot may be
omitted if it is the same as the domain from which you are sending the message. For example, a user on ``calder.berkeley.edu'' could send to
``eric@CS'' without adding the ``berkeley.edu'' since it is the same on both sending and receiving hosts.
Compatibility.
Certain old address formats are converted to the new format to provide compatibility with the previous mail system. In particular,
user@host
and
user@host.domain
are allowed;
host.domain!user
is converted to
user@host.domain
and
host!user
is converted to
user@host.UUCP
This is normally converted back to the ``host!user'' form before being sent on for compatibility with older UUCP hosts.
Case Distinctions.
Domain names (i.e., anything after the ``@'' sign) may be given in any mixture of upper and lower case with the exception of UUCP hostnames.
Most hosts accept any combination of case in user names, with the notable exception of MULTICS sites.
Route-addrs.
Under some circumstances it may be necessary to route a message through several hosts to get it to the final destination. Normally this
routing is done automatically, but sometimes it is desirable to route the message manually. Addresses which show these relays are termed
``route-addrs.'' These use the syntax:
<@hosta,@hostb:user@hostc>
This specifies that the message should be sent to hosta, from there to hostb, and finally to hostc. This path is forced even if there is a
more efficient path to hostc.
Route-addrs occur frequently on return addresses, since these are generally augmented by the software at each host. It is generally possible
to ignore all but the ``user@hostc'' part of the address to determine the actual sender.
[Note: the route-addr syntax is officially deprecated in RFC 1123 and should not be used.]
Many sites also support the ``percent hack'' for simplistic routing:
user%hostc%hostb@hosta
is routed as indicated in the previous example.
Postmaster.
Every site is required to have a user or user alias designated ``postmaster'' to which problems with the mail system may be addressed.
Other Networks.
Some other networks can be reached by giving the name of the network as the last component of the domain. This is not a standard feature and
may not be supported at all sites. For example, messages to CSNET or BITNET sites can often be sent to ``user@host.CSNET'' or
``user@host.BITNET'' respectively.
SEE ALSO
mail(1), sendmail(8)
Crocker, D. H., Standard for the Format of Arpa Internet Text Messages, RFC822.
HISTORY
Mailaddr appeared in 4.2BSD.
BUGS
The RFC822 group syntax (``group:user1,user2,user3;'') is not supported except in the special case of ``group:;'' because of a conflict with
old berknet-style addresses.
Route-Address syntax is grotty.
UUCP- and Internet-style addresses do not coexist politely.
BSD
June 16, 1993 BSD