Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Mail server in home network and without domain name Post 302105365 by BOFH on Thursday 1st of February 2007 08:49:02 AM
Old 02-01-2007
I don't know your configuration so it's hard to troubleshoot the problem. What sorts of errors are you receiving when you can't log in to your imap server and what errors are you receiving when you are not able to send mail. Your server logs should have details on what the problem is.

For sendmail and other MTA's, there may be a few issues to consider.

1. Your ISP may be blocking port 25 for all but their own mail servers. It doesn't sound like that's your problem since it seems to be working some of the time.

2. Due to spam, other MTA's will check to see if you have a valid domain and will automatically reject your mail if your IP is not matched to a host name.

3. Again, due to spam, other MTA's automatically block e-mail from general user space such as the Comcast range. Per Comcast (and this is an example; your ISP may have different policies), you're not allowed to run servers on your home cable connection. Since Comcast doesn't block server ports at their firewall, you can get away with it but your mail may be generally blocked.

Why can't you get a domain though? There are lots available at pretty cheap prices. You can hit http://www.dyndns.com to register and manage a DHCP IP address. Their DNS servers accept input from your server as to its true IP and will reconfigure the IP for your domain to point to your server again. It's pretty quick. I used it until I started using a colocated server.

As to your request for howto's, a very fast google search turned up:

Linux Home Server HOWTO

You might want to consider searching for the information next time. Try searching on "howto +sendmail". In this case, that was one of the first items that popped up. It doesn't have imap info but I'm sure another seach would turn up an informative howto.

Carl
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

home network - can you have a primary name server, or only a caching-only name server

i'm setting up a solaris 9 box to be my home network's DNS server. actually it's up and running, but it's set as a caching-only name server. can i set it up to be the primary name server? what are the advantages if i can set it up to be a primary name server vs. a caching only name server? (3 Replies)
Discussion started by: xyyz
3 Replies

2. AIX

Problem sending mail to an external domain

On one of our AIX servers, I'm having problems sending email to an external domain. I'm not a SYSADM and not sure how to troubleshoot this issue. Any help will be greatly appreciated. The following mail components are installed on the server $ lslpp -l bos.mh Fileset ... (2 Replies)
Discussion started by: voorkey
2 Replies

3. UNIX for Dummies Questions & Answers

block certain domain from sending mail to server

hi currently i have a server that is able to send out and receive mail. is there a way to configure the server such that mails can be sent to a certain domail like abc@yahoo.com but block mails from this domain abc@yahoo.com. the server is running on solaris 10. thanks in advance :) (2 Replies)
Discussion started by: legato
2 Replies

4. UNIX for Dummies Questions & Answers

displaying network domain name in tru64

Hello: does anyone of you know how can I get the network domain name that my tru64 server belongs to??? Thanks alot (5 Replies)
Discussion started by: aladdin
5 Replies

5. Shell Programming and Scripting

Sendmail: Remove domain name from From mail id

While sending mails using sendmail, the domain name is getting appended to the from id. My requirement is not to have that domain name in the From mail id. Could anyone help me on this? I am using the below command: cat t|/usr/lib/sendmail -f"Admin" user1@domain1.com (0 Replies)
Discussion started by: skar_a
0 Replies

6. AIX

I Need to send mail to 2 domain

Hi, I need to send alert mail from AIX to mail server. My mail server IP is 192.168.0.10 so I've add /etc/hosts as below 192.168.0.10 mydomain1.com the I try to send mail to myname@mydomain1.com it's OK Then I need to send mail to myname@mydomain2.com too. so I've... (1 Reply)
Discussion started by: oakmojo
1 Replies

7. HP-UX

[Solved] How do I configure Unix Mail Server to use another Mail Exchange Server

We have configured our mail unix server and can send out emails automatically from applications running on unix to different people in our company as well as outside our company. However there is an outside client who is not receiving these emails because the settings on their mail server cannot... (4 Replies)
Discussion started by: Tenyhwa
4 Replies

8. UNIX for Advanced & Expert Users

need to configure mail setting to send mail to outlook mail server

i have sun machines having solaris 9 & 10 OS . Now i need to send mail from the machines to my outlook account . I have the ip adress of OUTLOOK mail server. Now what are the setting i need to do in solaris machines so that i can use mailx or sendmail. actually i am trying to automate the high... (2 Replies)
Discussion started by: amitranjansahu
2 Replies

9. UNIX and Linux Applications

Copy mail traffic to several server for a domain

Hello, everybody! I have a MX server (sendmail) and old pop3 server, I installed a zimbra server and I want to receive mail traffic to several mail server (old and Zimbra). How I do it on Postfix(Zimbra if will be a MX for my domain) or Sendmail? (0 Replies)
Discussion started by: Rezonans
0 Replies

10. UNIX for Dummies Questions & Answers

Configure sendmail to Only send mail to one domain

On both Solaris 10 and RHEL, we would like to configure sendmail in such a way that the email sent from the server should only go to a particular domain. For eg. We want our server to ONLY send the mail to <user_name>@abc.com. All other domains should be blocked/restricted. The server should not... (0 Replies)
Discussion started by: sk2code
0 Replies
MAKEHOSTEDDOMAINS(8)					      Double Precision, Inc.					      MAKEHOSTEDDOMAINS(8)

NAME
makehosteddomains - Build a database of hosted domains SYNOPSIS
makehosteddomains DESCRIPTION
makehosteddomains rebuilds the contents of the /etc/courier/hosteddomains.dat database from the contents of /etc/courier/hosteddomains. This can be either a file or a directory. If it's a directory, the contents of all the files in this directory are simply concatenated. The makehosteddomains script must be run in order for any changes to /etc/courier/hosteddomains to take effect. The function of /etc/courier/hosteddomains is very similar to the one of /etc/courier/locals. Both configuration files specify a list of domains that are considered to be local domains - domains whose mailboxes are stored locally. The difference is that domains listed in /etc/courier/locals are removed from addresses before their mailbox is looked up. For example, if the domain "example.com" is listed in /etc/courier/locals, then the address <user@example.com> is delivered to a local mailbox named "user". If this domain is listed, instead, in /etc/courier/hosteddomains, then the address <user@example.com> is delivered to a local mailbox named "user@example.com". Usually you would use /etc/courier/locals to specify domains that correspond to your local system accounts, that are looked up in your system's password database. The /etc/courier/hosteddomains file is usually used when you have database-based virtual domains, that are maintained via an LDAP or a MySQL server. The Courier mail server's LDAP and MySQL authentication modules will use the full E-mail address to query the LDAP or MySQL server for the location of the local mailbox that correspond to the E-mail address. The Courier mail server's authuserdb authentication module can also use full E-mail addresses. Contents of hosteddomains The file /etc/courier/hosteddomains simply contains a list of domains, one per line, for example: domain.com example.org Each domain can optionally be followed by a single tab character, in order to specify an alias for a domain, for example: domain.com mail.domain.com<TAB>domain.com example.com<TAB>domain.com First, we list the domain "domain.com" as a hosted domain. Then, we also list the domain "mail.domain.com", which is an alias for domain.com. The Courier mail server will take any address of the form <address@mail.domain.com>, rewrite it as <address@domain.com>, and attempt to deliver the mail to a local mailbox for that name. The third entry does the same for "example.com"; mail addressed to <address@example.com> is delivered to the local mailbox <address@domain.com>. alias@hosteddomain This is a special local mail delivery rule for hosteddomain-listed domains. This rule allows the Courier mail server accept mail to any address@hosteddomain, where "hosteddomain" is a domain listed in the hosteddomains file, but there is no corresponding account for address@hosteddomain. To provide delivery instructions for any non-existing address in a hosteddomain-listed domain: 1) Create the local address alias@hosteddomain. For example, if the hosteddomains file contains "example.com", create the local account alias@example.com. This should be a normal account, with its own home directory, userid and groupid. 2) Create $HOME/.courier-default file in this account, containing the delivery instructions. See the dot-courier(5)[1] manual page for available delivery instructions. NOTE that alias@example.com must be a real account, not a mail alias. If you want to forward alias@example.com to another address, put forwarding instructions in the .courier-default file. However, alias@example.com can be a clone of another account (with the same home directory, userid, and groupid). "WILDCARD DNS" Wildcard DNS is supported for hosteddomains by placing a single period character before the domain name. For example, the hosted domain entry ".domain.com" will cause the Courier mail server to accept mail for "anything.domain.com". The Courier mail server will accept mail for <address@any.thing.domain.com> and attempt to deliver it to the local mailbox <address@any.thing.domain.com>, and if that fails then attempt to deliver the mail to the local mailbox <address@.thing.domain.com>, then finally <address@.domain.com> Note There is a period after the '@' character. If you want all mail for "any.thing.domain.com" to be delivered as though it were sent to "domain.com", you should define an alias for the domain, for example: domain.com .domain.com<TAB>domain.com SEE ALSO
esmtpd(8)[2]. AUTHOR
Sam Varshavchik Author NOTES
1. dot-courier(5) [set $man.base.url.for.relative.links]/dot-courier.html 2. esmtpd(8) [set $man.base.url.for.relative.links]/esmtpd.html Courier Mail Server 08/30/2011 MAKEHOSTEDDOMAINS(8)
All times are GMT -4. The time now is 12:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy