Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I used this guide: http://jonsview.com/how-to-setup-email-services-on-ubuntu-using-postfix-tlssasl-and-dovecot

telnet localhost 25 says

220 episodecalendar.com ESMTP Postfix (Ubuntu)
ehlo localhost
250-episodecalendar.com
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN

Installation seems fine?

/var/log/mail.log says

Nov 26 14:04:06 ubuntu postfix/pickup[12107]: A742E2B9E1: uid=0 from=<root>
Nov 26 14:04:06 ubuntu postfix/cleanup[12114]: A742E2B9E1: message-id=<20111126130406.A742E2B9E1@episodecalendar.com>
Nov 26 14:04:06 ubuntu postfix/qmgr[12108]: A742E2B9E1: from=<root@episodecalendar.com>, size=300, nrcpt=1 (queue active)
Nov 26 14:04:06 ubuntu postfix/local[12115]: A742E2B9E1: to=<support@episodecalendar.com>, relay=local, delay=3.3, delays=3.3/0/0/$
Nov 26 14:04:06 ubuntu postfix/cleanup[12114]: AD2662B9E0: message-id=<20111126130406.AD2662B9E0@episodecalendar.com>
Nov 26 14:04:06 ubuntu postfix/qmgr[12108]: AD2662B9E0: from=<>, size=2087, nrcpt=1 (queue active)
Nov 26 14:04:06 ubuntu postfix/bounce[12117]: A742E2B9E1: sender non-delivery notification: AD2662B9E0
Nov 26 14:04:06 ubuntu postfix/local[12115]: AD2662B9E0: to=<root@episodecalendar.com>, relay=local, delay=0.02, delays=0.01/0/0/0$
Nov 26 14:04:06 ubuntu postfix/qmgr[12108]: AD2662B9E0: removed
Nov 26 14:04:06 ubuntu postfix/qmgr[12108]: A742E2B9E1: removed

I'm not really understanding the log file, and obviously I'm not getting any emails.

Right now I'm running Ubuntu on a Virtualbox (development box). Is that a problem? The internet connection works fine on it. What about domains etc..?

edit: /etc/postfix/main.cf

# See /usr/share/postfix/main.cf.dist for a commented, more complete version


# Debian specific:  Specifying a file name will cause the first
# line of that file to be used as the name.  The Debian default
# is /etc/mailname.
#myorigin = /etc/mailname

smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

readme_directory = no

# TLS parameters
smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt
smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key
smtpd_use_tls = yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.

# See /usr/share/postfix/main.cf.dist for a commented, more complete version


# Debian specific:  Specifying a file name will cause the first
# line of that file to be used as the name.  The Debian default
# is /etc/mailname.
#myorigin = /etc/mailname

smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

readme_directory = no

# TLS parameters
smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt
smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key
smtpd_use_tls = yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.
share|improve this question
    
Now you see why you can't set up a mailserver in 15 minutes! Follow the official documentation and try again: help.ubuntu.com/10.04/serverguide/C/postfix.html –  mailq Nov 26 '11 at 20:13
add comment

1 Answer 1

The log entry "sender non-delivery notification", tells that the emails are not being processed by postfix properly, whose reason is that postfix is not properly configured.

If you can share your configuration files, then troubleshooting the issue can be lot easire, otherwise, it will be like Hit and Trial method.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.