Solved

Sending email problems

Posted on 2008-06-24
33
1,014 Views
Last Modified: 2013-12-06
Currently I use a virtual dedicated server with Godaddy.  I'm running Red Hat Fedora Core 7.  We have emails set up with our hosted domains.  These email addresses all send fine, but don't recieve emails.  Can someone help me through this.  I tried to send a test message from yahoo and got the following message:

 Hi. This is the qmail-send program at yahoo.com.
I'm afraid I wasn't able to deliver your message to the following
 addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<anand.patel@innolox.com>:
208.109.221.17 does not like recipient.
Remote host said: 554 5.7.1 <anand.patel@innolox.com>: Recipient
 address rejected: Relay access denied
Giving up on 208.109.221.17.

--- Below this line is a copy of the message.

Return-Path: <andyjas7699@yahoo.com>
Received: (qmail 61023 invoked by uid 60001); 24 Jun 2008 18:44:05
 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;

  h=X-YMail-OSG:Received:Date:From:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;

  b=tSXncYLabx2CzMOzCOyxcQ4b6VLcJkD7T7ET/1ht1W/5G2j4U9afFUD+jRf6mLOlfyDOJquBnVzfnl9A0FGQFF+0Y7MoO0IBgzNkmq2hXW7B1ugRS91MlagqiVFsrGIvYZZjPZhArwL2jpKsS47hiUyom+l0djFtCn/UHYvsKSw=;
X-YMail-OSG:
 0GHFqDkVM1lu6xwNaLCNw9hUKF6zgg51oeriwVitPEGZoNRTs.6tM1Xug8eLdnfUqWTlAPlCPMe_V.d5xk.VIBqJczvXYBqjXzOM5Ev5rw--
Received: from [216.157.116.64] by web65413.mail.ac4.yahoo.com via
 HTTP; Tue, 24 Jun 2008 11:44:05 PDT
Date: Tue, 24 Jun 2008 11:44:05 -0700 (PDT)
From: Anand Patel <andyjas7699@yahoo.com>
To: anand.patel@innolox.com
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="0-410145136-1214333045=:60616"
Content-Transfer-Encoding: 8bit
Message-ID: <96264.60616.qm@web65413.mail.ac4.yahoo.com>

--0-410145136-1214333045=:60616
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

test
       
--0-410145136-1214333045=:60616
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

test<p>



     
--0-410145136-1214333045=:60616--

0
Comment
Question by:trifecta2k
  • 18
  • 15
33 Comments
 
LVL 14

Expert Comment

by:agriesser
ID: 21859454
As I saw in the SMTP greeting, you're using postfix.
Have you added innolox.com to /etc/postfix/local-host-names?
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21859558
Here's the problem.  I'm not a server guy, but I do know it worked previous so I would assume it was set up properly.  How can I add it.  Sorry but unfortunatly I'm just a beginner when it comes to this stuff.  
0
 
LVL 14

Expert Comment

by:agriesser
ID: 21859618
Open the file /etc/postfix/local-host-names with the UNIX editor of your choice (pick nano or pico if you're not familiar with unix editors as they're easy to use) and add "innolox.com" in a new line.

BTW: What does this file look like currently?
Are there any entries in this file by now?
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21865575
I am having trouble installing pico.  Like I said I'm new to this...
Here is what I did to try to install it.
1. Login to your server via SSH
2. Type: rpm -q pine
3. Type: wget ftp://rpmfind.net/linux/redhat/9/en/os/i386/RedHat/RPMS/pine-4.44-18.i386.rpm
4. Type: rpm -Uvh pine-4.44-18.i386.rpm

Here is the message I get
warning: pine-4.44-18.i386.rpm: Header V3 DSA signature:  NOKEY, key ID db42a60e
error:  Failed dependencies:
           libcom_err.so.3 is needed by pine-4.44-18.i386
           libcrypto.so.4 is needed by pine-4.44-18.i386
           liblber.so.2 is needed by pine-4.44-18.i386
           libldap.so.2 is needed by pine-4.44-18.i386
           libssl.so.4 is needed by pine-4.44-18.i386
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21865719
I do have VI installed, but I have no idea what I'm doing.  IF you can give me instructions for that I can do that as well.
0
 
LVL 14

Expert Comment

by:agriesser
ID: 21865775
OK, let's try :)


1. vim /etc/postfix/local-host-names
2. press 'G' (a capital g, the cursor should move to the last byte in the file
3. press 'A' (a capital a, the editor should change into insert mode
4. Type "innolox.com" (without the quotes, so that innolox.com is on a line on its own)
5. Press ESC ESC
6. Press ZZ (two capital z's, the file should now have been saved with the changes)

Check if the changes are really in the file using `less /etc/postfix/local-host-names` or `more /etc/postfix/local-host-names`.

Restart postfix (/etc/init.d/postfix restart) or `service postfix restart` (whatever is supported on your system).
0
 
LVL 14

Expert Comment

by:agriesser
ID: 21865783
Oh, if anything wents wrong during working at the file, press two times ESC and then enter :q! <Enter>
That will close the file without saving changes and you can start over.
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21866044
I'm sure this is a stupid question.  After I type vim /etc/postfix/local-host-names what do I hit?  Just enter.  When I hit enter it just goes to the next line and nothing happens.  Also there is an insert at the bottom left of my screen, is that ok?  
0
 
LVL 14

Expert Comment

by:agriesser
ID: 21866164
When vim starts, it is _NOT_ in insert mode (insert mode is what you would expect an editor to be in when you start it, e.g. you can start typing). vi is in command mode by default, that means you can enter commands into it.

So after you started vi, there should be no "Insert" displayed in the status bar, if there is "Insert" displayed, you're already in insert mode and can move down to the end of the file using your cursor keys as you would do with any other editor.

If it is in command mode, press G (shortcut for a command that brings you to the end of the file), then press A (command to bring you at the end of the current line (should be the last line after G) and start in insert mode).
Then you can type your text and when you're finished, press ESC to enter insert mode and return to command mode (in insert mode you can't save the file). On some vi configurations (depending on the vimrc file) it's necessary to enter ESC twice, so simply hit ESC as long as necessary to get out of input mode.

Back in command mode, type ZZ (shortcut for save and exit) and the editor should save the changes and close itself.
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21866331
Thanks.  I did it and added innolox.com.  I also did the less and saw innolox.  Then I restarted postfix.  What should I do next.  I tried to send an email and got the same error message.
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21866524
I don't know if this will help but this happened 1 time a while back and all I did was restart postfix and Cyrus POP3/IMAP Server.  
0
 
LVL 14

Expert Comment

by:agriesser
ID: 21866745
Well then have you tried to restart these services by now?

I assumed that you're running postfix on plain files but your mailserver could also be configured for virtual domains stored in a database etc. To be sure, I need to see your postfix configuration file (usually /etc/postfix/master.cf).
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21868849
I did restart those services.  Right now I'm working with GoDaddy to give me access to the master.cf file.  I keep getting permission denied.  They don't want to help me, but at the same time won'e let me help myself!  As soon as I can get it, I will post it.  Thanks so much for sticking it out with me, I truly appreciate it.  
0
 
LVL 14

Expert Comment

by:agriesser
ID: 21869012
Let's try this one:

http://www.jasin.biz/2006/02/24/smtp-email-out-on-godaddy-server/

It definetly seems to be a godaddy problem...
0
 
LVL 14

Expert Comment

by:agriesser
ID: 21869027
To quote the above mentioned URL (in case it's not reachable in some time in the future):

http://www.jasin.biz/2006/02/24/smtp-email-out-on-godaddy-server/

-----------------------------
The dedicated server on Go Daddy could not send email out. This was because Go Daddy block the port for smtp, a support from Go Daddy told us that we have to use k2smtpout.secureserver.net for sending out mails from our server.

So set this server name on my postfix configuration. Edit the file /etc/postfix/main.cf. edit the following:

relayhost = k2smtpout.secureserver.net

thats all and it works!... really funny must do this way in godaddy
-----------------------------
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21869497
I'm logged in as root, but when I do /etc/postfix/main.cf I keep getting:

bash: /etc/postfix/main.cf: Permission denied

I will try to contact them again, but they are not very good at getting back to me.  I'll keep you posted.  
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 
LVL 14

Expert Comment

by:agriesser
ID: 21869566
No, you can't start this file, you need to open it with an editor, f.ex.:

vi /etc/postfix/main.cf

0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21869598
I think the problem is that I am using SU to get root access.  I'm not logging in as root.  it won't let me.  
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21869628
Sorry, I told you I was new to this thing..haha.  Thanks for the patience

I got in and and the relayhost is already k2smtpout.secureserver.net
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21869661
Here is what my master.cf looks like
# ==========================================================================
# service type  private unpriv  chroot  wakeup  maxproc command + args
#               (yes)   (yes)   (yes)   (never) (100)
# ==========================================================================
smtp      inet  n       -       n       -       -       smtpd -o content_filter=spamassassin
pickup    fifo  n       -       n       60      1       pickup
cleanup   unix  n       -       n       -       0       cleanup
qmgr      fifo  n       -       n       300     1       nqmgr
rewrite   unix  -       -       n       -       -       trivial-rewrite
bounce    unix  -       -       n       -       0       bounce
defer     unix  -       -       n       -       0       bounce
flush     unix  n       -       n       1000?   0       flush
proxymap  unix  -       -       n       -       -       proxymap
smtp      unix  -       -       n       -       -       smtp
relay     unix  -       -       n       -       -       smtp
showq     unix  n       -       n       -       -       showq
error     unix  -       -       n       -       -       error
local     unix  -       n       n       -       -       local
virtual   unix  -       n       n       -       -       virtual
lmtp      unix  -       -       n       -       -       lmtp
maildrop  unix  -       n       n       -       -       pipe
  flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
old-cyrus unix  -       n       n       -       -       pipe
  flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
cyrus     unix  -       n       n       -       -       pipe
  user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
uucp      unix  -       n       n       -       -       pipe
  flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
ifmail    unix  -       n       n       -       -       pipe
  flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
bsmtp     unix  -       n       n       -       -       pipe
  flags=Fq. user=foo argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient
spamassassin
          unix  -       n       n       -       -       pipe
  user=nobody argv=/usr/bin/spamc -f
                   -e /usr/sbin/sendmail.postfix
                   -oi -f ${sender} ${recipient}
0
 
LVL 14

Expert Comment

by:agriesser
ID: 21872217
OK, master.cf looks fine. Let me please see your main.cf too.

BTW: The relayhost is reachable from your system, is it?
Try to ping k2smtpout.secureserver.net, is it reachable?

Time to check the logs. Could you please open a new terminal (PuTTY or whatever used to connect to this machine) and start the command `tail -f /var/log/maillog`.
This command will give you a realtime view of your maillog file. Leave this terminal alone for now and try to send mail. All new log entries regarding your mailing system should now pop up in the previous terminal. Post them in here, please.
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21875951
Here is what's happening.  It looks like the mail is getting there and then getting expunged.  

Jun 26 08:46:03 ip-208-109-221-17 lmtpunix[21849]: accepted connection
Jun 26 08:46:03 ip-208-109-221-17 lmtpunix[21849]: lmtp connection preauth'd as postman
Jun 26 08:46:03 ip-208-109-221-17 master[24348]: about to exec /usr/lib/cyrus-imapd/lmtpd
Jun 26 08:46:03 ip-208-109-221-17 lmtpunix[21849]: IOERROR: fstating sieve script /var/lib/imap/sieve/domain/i/independencegreenyachts.com/i/info/defaultbc: No such file or directory
Jun 26 08:46:03 ip-208-109-221-17 lmtpunix[21849]: duplicate_check: <752166.87593.qm@web65412.mail.ac4.yahoo.com> independencegreenyachts.com!user.info 0
Jun 26 08:46:03 ip-208-109-221-17 spamd[11998]: prefork: child states: II
Jun 26 08:46:03 ip-208-109-221-17 lmtpunix[21849]: duplicate_check: <752166.87593.qm@web65412.mail.ac4.yahoo.com> independencegreenyachts.com!user.info 0
Jun 26 08:46:03 ip-208-109-221-17 lmtpunix[21849]: mystore: starting txn 2147483834
Jun 26 08:46:03 ip-208-109-221-17 lmtpunix[21849]: mystore: committing txn 2147483834
Jun 26 08:46:03 ip-208-109-221-17 lmtpunix[21849]: duplicate_mark: <752166.87593.qm@web65412.mail.ac4.yahoo.com> independencegreenyachts.com!user.info 1214495163 0
Jun 26 08:46:03 ip-208-109-221-17 lmtpunix[24348]: executed
Jun 26 08:46:03 ip-208-109-221-17 lmtpunix[21849]: Delivered: <752166.87593.qm@web65412.mail.ac4.yahoo.com> to mailbox: independencegreenyachts.com!user.info
Jun 26 08:46:03 ip-208-109-221-17 postfix/lmtp[24347]: 866952B82F8: to=<info@independencegreenyachts.com>, relay=ip-208-109-221-17.ip.secureserver.net[/var/lib/imap/socket/lmtp], delay=0.03, delays=0.01/0.01/0/0.01, dsn=2.1.5, status=sent (250 2.1.5 Ok)
Jun 26 08:46:03 ip-208-109-221-17 postfix/qmgr[18295]: 866952B82F8: removed
Jun 26 08:46:03 ip-208-109-221-17 imap[19828]: accepted connection
Jun 26 08:46:03 ip-208-109-221-17 master[24350]: about to exec /usr/lib/cyrus-imapd/imapd
Jun 26 08:46:03 ip-208-109-221-17 imap[19828]: login: ip-208-109-221-17.ip.secureserver.net [127.0.0.1] info@independencegreenyachts.com plaintext User logged in
Jun 26 08:46:03 ip-208-109-221-17 imap[19828]: seen_db: user info@independencegreenyachts.com opened /var/lib/imap/domain/i/independencegreenyachts.com/user/i/info.seen
Jun 26 08:46:03 ip-208-109-221-17 imap[24350]: executed
Jun 26 08:46:03 ip-208-109-221-17 imap[19828]: open: user info@independencegreenyachts.com opened INBOX
Jun 26 08:46:03 ip-208-109-221-17 last message repeated 2 times
Jun 26 08:46:03 ip-208-109-221-17 imap[19828]: SQUAT failed to open index file
Jun 26 08:46:03 ip-208-109-221-17 imap[19828]: SQUAT failed
Jun 26 08:46:13 ip-208-109-221-17 imap[23776]: accepted connection
Jun 26 08:46:13 ip-208-109-221-17 imap[23776]: login: ip-208-109-221-17.ip.secureserver.net [127.0.0.1] info@independencegreenyachts.com plaintext User logged in
Jun 26 08:46:13 ip-208-109-221-17 imap[23776]: seen_db: user info@independencegreenyachts.com opened /var/lib/imap/domain/i/independencegreenyachts.com/user/i/info.seen
Jun 26 08:46:13 ip-208-109-221-17 imap[23776]: open: user info@independencegreenyachts.com opened INBOX
Jun 26 08:46:13 ip-208-109-221-17 last message repeated 2 times
Jun 26 08:46:13 ip-208-109-221-17 imap[23776]: SQUAT failed to open index file
Jun 26 08:46:13 ip-208-109-221-17 imap[23776]: SQUAT failed
Jun 26 08:46:20 ip-208-109-221-17 master[17817]: process 21511 exited, status 0
Jun 26 08:46:23 ip-208-109-221-17 pop3[22233]: accepted connection
Jun 26 08:46:23 ip-208-109-221-17 master[24548]: about to exec /usr/lib/cyrus-imapd/pop3d
Jun 26 08:46:23 ip-208-109-221-17 pop3[24548]: executed
Jun 26 08:46:25 ip-208-109-221-17 pop3[22233]: login: c-68-32-196-125.hsd1.pa.comcast.net [68.32.196.125] info@independencegreenyachts.com plaintext User logged in
Jun 26 08:46:25 ip-208-109-221-17 master[17817]: process 21713 exited, status 0
Jun 26 08:46:34 ip-208-109-221-17 pop3[22233]: Expunged 1 messages from independencegreenyachts.com!user.info
Jun 26 08:46:35 ip-208-109-221-17 pop3[21512]: accepted connection
Jun 26 08:46:35 ip-208-109-221-17 pop3[22234]: accepted connection
Jun 26 08:46:35 ip-208-109-221-17 master[25691]: about to exec /usr/lib/cyrus-imapd/pop3d
Jun 26 08:46:35 ip-208-109-221-17 pop3[25691]: executed
Jun 26 08:46:35 ip-208-109-221-17 pop3[21512]: login: pool-71-251-148-242.hrbgpa.fios.verizon.net [71.251.148.242] anand.patel@innolox.com APOP User logged in
Jun 26 08:46:35 ip-208-109-221-17 pop3[22234]: login: pool-71-251-148-242.hrbgpa.fios.verizon.net [71.251.148.242] info@independencegreenyachts.com APOP User logged in
0
 
LVL 14

Expert Comment

by:agriesser
ID: 21876255
OK, this is only the IMAP log.
Is there any designated postfix log on your system?
What's in /var/log? is there a postfix subfolder or something like this?
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21877508
This is all I have....no postfix subfolder.  
boot.log        cron.13.gz     maillog.2.gz    messages.7.gz  spooler.1.gz
boot.log.1.gz   cron.14.gz     maillog.3.gz    messages.8.gz  spooler.10.gz
boot.log.10.gz  cron.2.gz      maillog.4.gz    messages.9.gz  spooler.11.gz
boot.log.11.gz  cron.3.gz      maillog.5.gz    mysqld.log     spooler.12.gz
boot.log.12.gz  cron.4.gz      maillog.6.gz    samba          spooler.13.gz
boot.log.13.gz  cron.5.gz      maillog.7.gz    secure         spooler.14.gz
boot.log.14.gz  cron.6.gz      maillog.8.gz    secure.1.gz    spooler.2.gz
boot.log.2.gz   cron.7.gz      maillog.9.gz    secure.10.gz   spooler.3.gz
boot.log.3.gz   cron.8.gz      mailman         secure.11.gz   spooler.4.gz
boot.log.4.gz   cron.9.gz      messages        secure.12.gz   spooler.5.gz
boot.log.5.gz   dmesg          messages.1.gz   secure.13.gz   spooler.6.gz
boot.log.6.gz   faillog        messages.10.gz  secure.14.gz   spooler.7.gz
boot.log.7.gz   httpd          messages.11.gz  secure.2.gz    spooler.8.gz
boot.log.8.gz   lastlog        messages.12.gz  secure.3.gz    spooler.9.gz
boot.log.9.gz   maillog        messages.13.gz  secure.4.gz    tallylog
btmp            maillog.1.gz   messages.14.gz  secure.5.gz    turbopanel
cron            maillog.10.gz  messages.2.gz   secure.6.gz    wtmp
cron.1.gz       maillog.11.gz  messages.3.gz   secure.7.gz    wtmp.1.gz
cron.10.gz      maillog.12.gz  messages.4.gz   secure.8.gz    yum.log
cron.11.gz      maillog.13.gz  messages.5.gz   secure.9.gz
cron.12.gz      maillog.14.gz  messages.6.gz   spooler
0
 
LVL 14

Expert Comment

by:agriesser
ID: 21878379
OK then please let me see your main.cf.

Debugging such issues without getting my fingers on this machine is always a bit complicated.
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21878555
I understand and I'm glad you continue to work with me. Here is the main.cf.  it's pretty large.  I think you only need the bottom portion but I will post the whole thing just in case.
[root@ip-208-109-221-17 ~]# vi /etc/postfix/main.cf
sendmail_path = /usr/sbin/sendmail.postfix

# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
#
newaliases_path = /usr/bin/newaliases.postfix

# mailq_path: The full pathname of the Postfix mailq command.  This
# is the Sendmail-compatible mail queue listing command.
#
mailq_path = /usr/bin/mailq.postfix

# setgid_group: The group for mail submission and queue management
# commands.  This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
#
setgid_group = postdrop

# html_directory: The location of the Postfix HTML documentation.
#
html_directory = no

# manpage_directory: The location of the Postfix on-line manual pages.
#
manpage_directory = /usr/share/man

# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
#
sample_directory = /usr/share/doc/postfix-2.4.5/samples

# readme_directory: The location of the Postfix README files.
#
readme_directory = /usr/share/doc/postfix-2.4.5/README_FILES
virtual_mailbox_domains = hash:${config_directory}/virtual_domains,hash:${config_directory}/turbopanel/virtual_domains
virtual_alias_maps = hash:${config_directory}/virtual_alias,hash:/etc/mailman/virtual-mailman,hash:${config_directory}/turbopanel/virtual_alias
virtual_mailbox_maps = ${virtual_alias_maps}
sender_canonical_maps = hash:${config_directory}/sender_canonical,hash:${config_directory}/turbopanel/sender_canonical
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination
smtpd_use_tls = yes
smtpd_tls_auth_only = no
smtpd_tls_key_file = ${config_directory}/ssl/post.pem
smtpd_tls_cert_file = ${config_directory}/ssl/post.pem
smtpd_tls_CAfile = ${config_directory}/ssl/post.pem
smtpd_tls_loglevel = 3
smtpd_tls_received_header = yes
smtpd_tls_session_cache_timeout = 3600s
tls_random_source = dev:/dev/urandom
tls_random_exchange_name = /var/run/prng_exch
mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
virtual_transport = lmtp:unix:/var/lib/imap/socket/lmtp
recipient_delimiter = +
owner_request_special = no
relayhost = k2smtpout.secureserver.net
myhostname = ip-208-109-221-17.ip.secureserver.net
message_size_limit = 10485760
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21878637
Actually that wasn't the whole thing...here is the extended version.  
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
#
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
#
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.

# SOFT BOUNCE
#
# The soft_bounce parameter provides a limited safety net for
# testing.  When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#
#soft_bounce = no

# LOCAL PATHNAME INFORMATION
#
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
#
queue_directory = /var/spool/postfix

# The command_directory parameter specifies the location of all
# postXXX commands.
#
command_directory = /usr/sbin

# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
#
daemon_directory = /usr/libexec/postfix

# QUEUE AND PROCESS OWNERSHIP
#
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes.  Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
#
mail_owner = postfix

# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#
#default_privs = nobody

# INTERNET HOST AND DOMAIN NAMES
#
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld

# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#
#mydomain = domain.tld

# SENDING MAIL
#
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites.  If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# user@that.users.mailhost.
#
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#
#myorigin = $myhostname
#myorigin = $mydomain

# RECEIVING MAIL

# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on.  By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
#
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
#
# Note: you need to stop/start Postfix when this parameter changes.
#
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
inet_interfaces = all

# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
#
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4

# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
#
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
#
# The default is $myhostname + localhost.$mydomain.  On a mail domain
# gateway, you should also include $mydomain.
#
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
#
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
#
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
#
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
#
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#
mydestination = $myhostname,localhost.$mydomain,localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
#       mail.$mydomain, www.$mydomain, ftp.$mydomain

# REJECTING MAIL FOR UNKNOWN LOCAL USERS
#
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
#
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
#
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
#
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
#
# - You define $mydestination domain recipients in files other than
#   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
#   For example, you define $mydestination domain recipients in
#   the $virtual_mailbox_maps files.
#
# - You redefine the local delivery agent in master.cf.
#
# - You redefine the "local_transport" setting in main.cf.
#
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
#   feature of the Postfix local delivery agent (see local(8)).
#
# Details are described in the LOCAL_RECIPIENT_README file.
#
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
#
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a user@domain.tld address.
#
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =

# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
#
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
#
unknown_local_recipient_reject_code = 550

# TRUST AND RELAY CONTROL

# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
#
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix.  See the smtpd_recipient_restrictions parameter
# in postconf(5).
#
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
#
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
#
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network.  Instead, specify an explicit
# mynetworks list by hand, as described below.
#
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host

# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
#
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
#
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table

# The relay_domains parameter restricts what destinations this system will
# relay mail to.  See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
#
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
#   subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
#
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
#
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace.  Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
#
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#
#relay_domains = $mydestination

# INTERNET OR INTRANET

# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
#
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
#
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
#
# If you're connected via UUCP, see also the default_transport parameter.
#
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]

# REJECTING UNKNOWN RELAY USERS
#
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
#
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
#
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a user@domain.tld address.
#
#relay_recipient_maps = hash:/etc/postfix/relay_recipients

# INPUT RATE CONTROL
#
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
#
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
#
# Specify 0 to disable the feature. Valid delays are 0..10.
#
#in_flow_delay = 1s

# ADDRESS REWRITING
#
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.

# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
#
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.

# "USER HAS MOVED" BOUNCE MESSAGES
#
# See the discussion in the ADDRESS_REWRITING_README document.

# TRANSPORT MAP
#
# See the discussion in the ADDRESS_REWRITING_README document.

# ALIAS DATABASE
#
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
#
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
#
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
#
# It will take a minute or so before changes become visible.  Use
# "postfix reload" to eliminate the delay.
#
#alias_maps = dbm:/etc/aliases
alias_maps = hash:${config_directory}/aliases,hash:/etc/mailman/aliases,hash:${config_directory}/turbopanel/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases

# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi".  This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
alias_database = hash:/etc/postfix/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases

# ADDRESS EXTENSIONS (e.g., user+foo)
#
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#
#recipient_delimiter = +

# DELIVERY TO MAILBOX
#
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user.  Specify
# "Maildir/" for qmail-style delivery (the / is required).
#
#home_mailbox = Mailbox
#home_mailbox = Maildir/

# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail

# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception:  delivery for root is done as $default_user.
#
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
#
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
#
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
#
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"

# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
#
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf.  The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#
#mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp

# If using the cyrus-imapd IMAP server deliver local mail to the IMAP
# server using LMTP (Local Mail Transport Protocol), this is prefered
# over the older cyrus deliver program by setting the
# mailbox_transport as below:
#
# mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
#
# The efficiency of LMTP delivery for cyrus-imapd can be enhanced via
# these settings.
#
# local_destination_recipient_limit = 300
# local_destination_concurrency_limit = 5
#
# Of course you should adjust these settings as appropriate for the
# capacity of the hardware you are using. The recipient limit setting
# can be used to take advantage of the single instance message store
# capability of Cyrus. The concurrency limit can be used to control
# how many simultaneous LMTP sessions will be permitted to the Cyrus
# message store.
#
# To use the old cyrus deliver program you have to set:
#mailbox_transport = cyrus

# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
#
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf.  The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#
#fallback_transport = lmtp:unix:/var/lib/imap/socket/lmtp
#fallback_transport =

# The luser_relay parameter specifies an optional destination address
# for unknown recipients.  By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
#
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
#
# luser_relay works only for the default Postfix local delivery agent.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#
#luser_relay = $user@other.host
#luser_relay = $local@other.host
#luser_relay = admin+$local

# JUNK MAIL CONTROLS
#
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.

# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
#
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
#
# For details, see "man header_checks".
#
#header_checks = regexp:/etc/postfix/header_checks

# FAST ETRN SERVICE
#
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
#
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#
#fast_flush_domains = $relay_domains

# SHOW SOFTWARE VERSION OR NOT
#
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
#
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)

# PARALLEL DELIVERY TO THE SAME DESTINATION
#
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
#
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter.  The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.

#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20

# DEBUGGING CONTROL
#
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
#
debug_peer_level = 2

# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain

# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
#
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
#
debugger_command =
         PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
         xxgdb $daemon_directory/$process_name $process_id & sleep 5

# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
#
# debugger_command =
#       PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
#       echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
#       >$config_directory/$process_name.$process_id.log & sleep 5
#
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
#
# debugger_command =
#       PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
#       -dmS $process_name gdb $daemon_directory/$process_name
#       $process_id & sleep 1

# INSTALL-TIME CONFIGURATION INFORMATION
#
# The following parameters are used when installing a new Postfix version.
#
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
#
sendmail_path = /usr/sbin/sendmail.postfix

# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
#
newaliases_path = /usr/bin/newaliases.postfix

# mailq_path: The full pathname of the Postfix mailq command.  This
# is the Sendmail-compatible mail queue listing command.
#
mailq_path = /usr/bin/mailq.postfix

# setgid_group: The group for mail submission and queue management
# commands.  This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
#
setgid_group = postdrop

# html_directory: The location of the Postfix HTML documentation.
#
html_directory = no

# manpage_directory: The location of the Postfix on-line manual pages.
#
manpage_directory = /usr/share/man

# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
#
sample_directory = /usr/share/doc/postfix-2.4.5/samples

# readme_directory: The location of the Postfix README files.
#
readme_directory = /usr/share/doc/postfix-2.4.5/README_FILES
virtual_mailbox_domains = hash:${config_directory}/virtual_domains,hash:${config_directory}/turbopanel/virtual_domains
virtual_alias_maps = hash:${config_directory}/virtual_alias,hash:/etc/mailman/virtual-mailman,hash:${config_directory}/turbopanel/virtual_alias
virtual_mailbox_maps = ${virtual_alias_maps}
sender_canonical_maps = hash:${config_directory}/sender_canonical,hash:${config_directory}/turbopanel/sender_canonical
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination
smtpd_use_tls = yes
smtpd_tls_auth_only = no
smtpd_tls_key_file = ${config_directory}/ssl/post.pem
smtpd_tls_cert_file = ${config_directory}/ssl/post.pem
smtpd_tls_CAfile = ${config_directory}/ssl/post.pem
smtpd_tls_loglevel = 3
smtpd_tls_received_header = yes
smtpd_tls_session_cache_timeout = 3600s
tls_random_source = dev:/dev/urandom
tls_random_exchange_name = /var/run/prng_exch
mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
virtual_transport = lmtp:unix:/var/lib/imap/socket/lmtp
recipient_delimiter = +
owner_request_special = no
relayhost = k2smtpout.secureserver.net
myhostname = ip-208-109-221-17.ip.secureserver.net
message_size_limit = 10485760
0
 
LVL 14

Expert Comment

by:agriesser
ID: 21878667
Please check for the existance of your domain name in the files /etc/postfix/virtual_domains and /etc/postfix/turbopanel/virtual_domains.

It should be listed in either one of these two files.

Additionally, all your e-mail addresses for the hosted domains should be listed in /etc/postfix/virtual_alias as well as /etc/postfix/turbopanel/virtual_alias.

Regarding the turbopanel directory: I guess it's the graphical user interface to configure your webserver, is it?
Before making changes to these files manually, I'd check if it's possible to make the changes in the GUI (you never know how a GUI will react if changes have been made manually to GUI controlled configuration files).

Besides that, you should definetly make sure to create a reverse lookup entry for your IP address to your MX record, that means that your IP address (208.109.221.17) does not reversely resolve to mail.innolox.com. Some mailserver (e.g. GMX) will refuse mails from you because your IP address does not resolve to your MX record.
0
 
LVL 14

Accepted Solution

by:
agriesser earned 500 total points
ID: 21878743
After seeing the second part of your main.cf, please change/add the following configuration options (some of them are already present, like myhostname f.ex., so you need to change it instead of just adding a new line with the same configuration option):
myhostname = mail.innolox.com

mydomain = innolox.com

myorigin = $mydomain

mynetworks_style = host

Open in new window

0
 
LVL 5

Author Comment

by:trifecta2k
ID: 21878772
When I looked at the 2 files.  The first one /etc/postfix/virtual_alias had nothing in it.  The 2nd one /etc/postfix/turbopanel/virtual_alias had all of my email addresses
0
 
LVL 5

Author Comment

by:trifecta2k
ID: 22119930
Agriesser, I just wanted to you know that your solution worked.  Thank you for all of your help and sorry about the extremely late response.
0
 
LVL 5

Author Closing Comment

by:trifecta2k
ID: 31470319
Thanks a lot for working through this problem with me step by step.  I really appreciate all of the help.  Also, I am really sorry about accepting your answer so late.  
0
 
LVL 14

Expert Comment

by:agriesser
ID: 22119969
Don't worry, I'm glad that I could help you.
Thanks for the question and for the points!
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Problem "Can you help me recover my changes?  I double-clicked the attachment, made changes, and then hit Save before closing it.  But when I try to re-open it, my changes are missing!"    Solution This solution opens the Outlook Secure Temp Fold…
Email attacks are the most efficient and effective way for cyber criminals and hackers to compromise a computer or network. We often find our-self second guessing the authenticity of an email message, for such instances we can follow practical princ…
Excel styles will make formatting consistent and let you apply and change formatting faster. In this tutorial, you'll learn how to use Excel's built-in styles, how to modify styles, and how to create your own. You'll also learn how to use your custo…
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now