Question regarding SMTP on my own mail server

This might be a dumb question. I understand if I want to use os x server to run my mail server, I need to update the MX records for my domain so that all email sent to my companies domain goes to the static IP of my server. Where I'm confused is with smtp, how does that work? If I create a new message and send it to someone on the internet, how does my leopard server know how to deliver it? I haven't changed any MX settings yet, just confused how SMTP works?

Thanks for your help, still having issues. My MX records for invution.com are not set up yet as I'm waiting for my static IP to be installed. I can send mail of course to local users, but I'm just testing sending externally. Does my MX records need to be set up for that? If so then this question is answered.
I'm trying to email myself at gmail.com but it never sends. Here's SMTP log:
Feb 7 08:23:29 darwin postfix/postfix-script[59769]: refreshing the Postfix mail system
Feb 7 08:23:29 darwin postfix/master[59668]: reload configuration /etc/postfix
Feb 7 08:23:29 darwin postfix/qmgr[59774]: 002D187E09: from=<[email protected]>, size=966, nrcpt=1 (queue active)
Feb 7 08:23:29 darwin postfix/qmgr[59774]: 2A5EC87F6B: from=<[email protected]>, size=925, nrcpt=1 (queue active)
Feb 7 08:23:29 darwin postfix/qmgr[59774]: 3D57287E5E: from=<[email protected]>, size=966, nrcpt=1 (queue active)
Feb 7 08:23:29 darwin postfix/qmgr[59774]: 62E7F8686B: from=<[email protected]>, size=970, nrcpt=1 (queue active)
Feb 7 08:23:29 darwin postfix/qmgr[59774]: 7172587EAF: from=<[email protected]>, size=927, nrcpt=1 (queue active)
Feb 7 08:23:29 darwin postfix/qmgr[59774]: D11CB87FAA: skipped, still being delivered
Feb 7 08:23:29 darwin postfix/smtp[59724]: connect to alt1.gmail-smtp-in.l.google.com[74.125.79.27]: Operation timed out (port 25)
Feb 7 08:23:59 darwin postfix/smtp[59724]: connect to alt2.gmail-smtp-in.l.google.com[209.85.129.27]: Operation timed out (port 25)
Feb 7 08:23:59 darwin postfix/smtp[59724]: D11CB87FAA: to=<[email protected]>, relay=none, delay=150, delays=0.06/0.04/150/0, dsn=4.4.1, status=deferred (connect to alt2.gmail-smtp-in.l.google.com[209.85.129.27]: Operation timed out)
Feb 7 08:23:59 darwin postfix/smtp[59776]: connect to gmail-smtp-in.l.google.com[72.14.205.27]: Operation timed out (port 25)
Feb 7 08:23:59 darwin postfix/smtp[59778]: connect to gmail-smtp-in.l.google.com[72.14.205.27]: Operation timed out (port 25)
Feb 7 08:23:59 darwin postfix/smtp[59777]: connect to gmail-smtp-in.l.google.com[209.85.133.114]: Operation timed out (port 25)
Feb 7 08:23:59 darwin postfix/smtp[59779]: connect to gmail-smtp-in.l.google.com[209.85.133.114]: Operation timed out (port 25)
Feb 7 08:23:59 darwin postfix/smtp[59780]: connect to gmail-smtp-in.l.google.com[209.85.133.114]: Operation timed out (port 25)
Feb 7 08:24:29 darwin postfix/postfix-script[59788]: refreshing the Postfix mail system
Feb 7 08:24:29 darwin postfix/master[59668]: reload configuration /etc/postfix
Feb 7 08:24:29 darwin postfix/qmgr[59793]: 002D187E09: skipped, still being delivered
Feb 7 08:24:29 darwin postfix/qmgr[59793]: 2A5EC87F6B: skipped, still being delivered
Feb 7 08:24:29 darwin postfix/qmgr[59793]: 3D57287E5E: skipped, still being delivered
Feb 7 08:24:29 darwin postfix/qmgr[59793]: 62E7F8686B: skipped, still being delivered
Feb 7 08:24:29 darwin postfix/qmgr[59793]: 7172587EAF: skipped, still being delivered
Feb 7 08:24:29 darwin postfix/qmgr[59793]: D11CB87FAA: from=<[email protected]>, size=925, nrcpt=1 (queue active)
Feb 7 08:24:29 darwin postfix/smtp[59776]: connect to alt1.gmail-smtp-in.l.google.com[74.125.79.27]: Operation timed out (port 25)
Feb 7 08:24:29 darwin postfix/smtp[59778]: connect to alt1.gmail-smtp-in.l.google.com[74.125.79.27]: Operation timed out (port 25)
Feb 7 08:24:29 darwin postfix/smtp[59777]: connect to alt2.gmail-smtp-in.l.google.com[209.85.129.27]: Operation timed out (port 25)
Feb 7 08:24:29 darwin postfix/smtp[59779]: connect to alt1.gmail-smtp-in.l.google.com[74.125.79.27]: Operation timed out (port 25)
Feb 7 08:24:29 darwin postfix/smtp[59780]: connect to alt1.gmail-smtp-in.l.google.com[66.249.93.27]: Operation timed out (port 25)
And then postconf -n shows:
darwin:~ admin$ postconf -n
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
html_directory = no
inet_interfaces = all
localrecipientmaps =
luser_relay = admin
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
messagesizelimit = 0
mydestination = $myhostname,localhost.$mydomain,localhost,invution.com
mydomain = invution.com
mydomain_fallback = localhost
myhostname = invution.com
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
relayhost =
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpsasl_passwordmaps =
smtpdenforcetls = no
smtpdpw_server_securityoptions = gssapi,cram-md5,login,plain
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdtls_certfile = /etc/certificates/Default.crt
smtpdtls_keyfile = /etc/certificates/Default.key
smtpdtlsloglevel = 0
smtpduse_pwserver = yes
smtpdusetls = no
unknownlocal_recipient_rejectcode = 550
Is something set up wrong or do I need MX working first? Thanks!

Similar Messages

SMTP error from remote mail server 522 IP REPUTATI...

I have a hosting business, and one of my clients on BTinternet, using BT Mail is now having mail bounce back to sender when forwarded from her domain mailbox.
Here is an example of the bounced errors -
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[email protected]
(ultimately generated from [email protected])
host mx.bt.lon5.cpcloud.co.uk [65.20.0.49]
SMTP error from remote mail server after MAIL FROM:<[email protected]> SIZE=3749:
522 IP REPUTATION BAD (please check for IP address listing on reputation services)
I've changed the actual addresses above. The server the mail is being forwarded from has an IP address 138.128.161.22
It seems that BT believes that the server the mail is forwarded from is blacklisted. However, I am unable to discover any blacklist issue for this server. As you can see from the MXToolbox enquiry, there are no blacklists reported -
http://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a138.128.161.22&run=toolpage
Can anybody from BT tell me who I need to contact to find out why they are not accepting mail from my server? I'm not having a problem with mail forwarded to any other ISP, and it seems to be just BT that is rejecting the mail.
I hope someone can advise.
Myles

Hi @magicalwonders
Have a look at http://bt.custhelp.com/app/answers/detail/a_id/47055/kw/postmaster/c/346,6592/session/L3RpbWUvMTQyOD...
Also have a look at this post: https://community.bt.com/t5/Email/BT-Email-bounce-backs/m-p/1477146/highlight/true#M34004
Openwave messaging (was Critical Path) is the company who designed and implemented the BT consumer email system and platform may require you to correctly set up a SPF record.
Also have a look at:
https://community.bt.com/t5/Email/BTinternet-rejecting-all-our-emails/m-p/1480775/highlight/true#M34...
jac_95 | BT.com Help Site | BT Service Status
Someone Solved Your Question?
Please let other members know by clicking on ’Mark as Accepted Solution’
Try a Search
See if someone in the community had the same problem and how they got it resolved.

SMTP error from remote mail server after initial connection:

Hello folks. I having some serious issues sending email to clients with .mac accounts. I keep on getting the following error. Can someone help? I have replaced email address names with "Blank@...) for obvious reasons.
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[email protected]
SMTP error from remote mail server after initial connection:
host smtp-mx1.mac.com [17.148.20.64]: 452 try later:
retry timeout exceeded
------ This is a copy of the message, including all the headers. ------
Return-path: <[email protected]>
Received: from ip72-207-229-240.br.br.cox.net ([72.207.229.240] helo=[192.168.0.102])
by srv3.purenrg.com with esmtp (Exim 4.68)
(envelope-from <[email protected]>)
id 1JFeOb-0001FZ-5F
for [email protected]; Thu, 17 Jan 2008 18:43:41 -0500
Message-Id: <[email protected]>
From: "[email protected]" <[email protected]>
To: Cindy Barnes <[email protected]>
Content-Type: multipart/alternative; boundary=Apple-Mail-3--1032078955
Mime-Version: 1.0 (Apple Message framework v915)
Subject: invoice 520 is overdue
Date: Thu, 17 Jan 2008 17:43:40 -0600
X-Mailer: Apple Mail (2.915)
X-PopBeforeSMTPSenders: [email protected]{
--Apple-Mail-3--1032078955
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit

I'm sure someone will give more detail, but it looks like the server blocked your address because it thinks it's a spam source. If you're not spamming, then it might be someone on the same network spamming, or malware on your computer doing it. Or it could just be a mistake. try calling whoever runs your mail server and see if they can give you more information.

Creating a mail server from an SMTP feed

Currently, we are unsatisfied with our mail provider - mostly due to delayed mail receipt. After speaking to our ISP they advised us that we could set up our own mail server and they could stream SMTP to us, avoiding POP3.
Although I administer the server and the network I have no experience of mail servers and have a few questions. I would have searched the forum but I don't really know which terms to search.
I would very much appreciate a fairly full explanation and nothing too vague please.
1. Is this easy to set up without additional hardware/software - is it built-in to OSX Server? What is it called and is it only accessed through CLI? Is there a good GUI alternative?
2. What hardware/software would you recommend for a facility handling about 200-300 emails per day, most with attachments of around 1Mb? It is not unusual to exceed 1Gb of email bandwidth in a working day.
3. What problems/shortfalls do I need to be aware of? Fequent crashes, database rebuilding, common address books, support, missing/undelivered/undeliverable mail, client set-up, etc
4. How will our email change, both sending and receiving? Will we or our recipients notice any sort of change?
Thank you in advance. Please feel free to ask any questions.
Steve

Currently, we are unsatisfied with our mail provider
- mostly due to delayed mail receipt. After speaking
to our ISP they advised us that we could set up our
own mail server and they could stream SMTP to us,
avoiding POP3.
Although I administer the server and the network I
have no experience of mail servers and have a few
questions. I would have searched the forum but I
don't really know which terms to search.
I would very much appreciate a fairly full
explanation and nothing too vague please.
1. Is this easy to set up without additional
hardware/software - is it built-in to OSX Server?
What is it called and is it only accessed through
CLI? Is there a good GUI alternative?
Sorry for the 'vague' answer but it's called "Mail" in Server Admin app - presumably the application you are using to administer your server? You can find documentation on it in the Mail Service section here...
http://www.apple.com/support/macosxserver/index.html
Apple docs are not everyones cup of tea but they are the starting point.
There are also other 3rd party mail server apps you can run in place of the built-in one.
2. What hardware/software would you recommend for a
facility handling about 200-300 emails per day, most
with attachments of around 1Mb? It is not unusual to
exceed 1Gb of email bandwidth in a working day.
A G4 could do that easily - depending (of course) on what else it is doing.
3. What problems/shortfalls do I need to be aware of?
Fequent crashes, database rebuilding, common address
books, support, missing/undelivered/undeliverable
mail, client set-up, etc
It just runs fine. Any time I have had problems it is because I have 'fiddled', but it is still a bit of software and you therefore become responsible for it (rather than your ISP/mail provider). "Common address books" is not a function of the OS X mail server. The mail logs are there for tracking whether "missing" mail was actually sent/delivered. Client set up is just as per usual requirements except you point clients to your server rather than ISP's.
4. How will our email change, both sending and
receiving? Will we or our recipients notice any sort
of change?
Sending from within the same LAN as your server appears a lot faster to people on the LAN since the transfer to the server is within LAN rather than out to internet. The server then sends out to internet.
Apologies again for the possibly not "full" answers but if I did that I would end up writing a manual
-david

Mail server stops IMAP and POP services, SMTP won't work

Hello fellow Lion Server users,
I am trying hard to get my mail server productive. I want to fetch mails from my ISP's IMAP mail server and distribute it to all my devices via my own mail server. Also the mails shall be sent via ISPs SMTP.
After managing it being able to send and receive email in the way I want I realized that web server was down. Because I want to use the integrated web mail and Wiki server I had to fix that. After restoring to default values in httpd.conf and others I got that problem solved just to realize that I am not able any more to send and receive email. I would be grateful if you could help me out.
The current status is that Server admin app claims the mail server still running, but POP, IMAP stopped whilst SMTP is running. In my mail.app I can send Emails successfully but they never reach the addressee. Receiving is just not possible at all. The connection doctor in integrated in Mail.app won't find a problem. It claims SMTP and IMAP connections I used before are working.
I use a dyndns forwarding to my server at home. Lion server is up to date. Port forwarding in the router is enabled (for each port Apple suggests).
Even in local network (with this very machine) it is not possible to successfully send or receive emails using localhost. My guess is that something went wrong in the configuration files but I don't know where I have to look and for what exactly.
I also tried a program called MailServe after running into the first problems with the mail server which did so far a good job in configuring of Postfix, Dovecot and Fetchmail but now I am stuck.
Do you have any hints for me, your help would be highly appreciated. Thank you.

I think I may have just figured out a part of this puzzle. I have more than just my att account set up in Mail. Even though all of my accounts are setup to use the ATT SMTP server only (with the appropriate ATT login info) I am getting the same rejection notices as everyone else.
I noticed that in the rejection notice though, that it was saying I was sending mail from my other main account, not my sbcglobal (ATT) account. I thought that was strange since I set up all my accounts to use the SBC (ATT) login info for ATT's SMTP Server. So obviously it is a problem in Mail. Mail is somehow confused and sending some wrong piece of info to the SMTP server. When I changed the sender from my other account to my SBCGLOBAL account, the mail went right out with no other problems.
So this isn't a solution for those of you who are struggling with only an ATT account, but I think it points to a possible problem within Mail. The answer might be to delete the accounts in Mail and set them back up again. It's looking like Apple might need to make a tweak to Mail to fix this if indeed this is the correct cause. Hope this helps someone.

A very simple question: how to obtain the mail server name?

In our JSP application, at one point an email will be sent to notify one event. Currently, that is done by using the html tag: mailto. To have more control on the email in tems of context format (a bad layout right now) and others. I would like to have it processed at servlet by using the JavaMail API, so that it have a nice format and have the sender's email address right in case email client is not installed in the machine where the browser in. The JavaMail API is straight forward. The question is how to obtain the mail server name, and the sender's email address if there is one?
Thanks.
v.

How to obtain the mail server's name? It's your server, you should know its name. Or if it isn't your server, you should ask the administrator for its name. Point is, you need to decide in advance what server you are going to use and hard-code its name into the program or into a properties file.
And how to obtain the client's e-mail address? You have to ask the client, probably by putting a box in the HTML and asking them to type it.

Configure BIP Delivery- Email. Do I have to install ArGo mail server

I am coinfiguring BI Publisher Delivery following the OBE at the URLhttp://www.oracle.com/technology/obe/obe_bi/bipub/advance/advance.htm#t1
Pre-request step 5It requeire install a 3 party mail server from ArGo Software. Since our company has our own mail server, can it be used instread of install another 3rd party mail server?

Delivery Manager can deliver to any SMTP Email Server. Just put your mail server name and port.
Regards,
Gareth

Need to have mail1 play nice with upstream mail server....

Switched to new mail server and hitting a problem. We have a debian linux box doing SPAM filtering further upstream from the mail server and then sending down to the new leopard mail1 box.
On the debian box we're seeing:
2009-04-03 09:14:08 H=216-174-222-148.atgi.net (email.wdcsc.org) [216.174.222.148] F=<[email protected]> temporarily rejected RCPT <[email protected]>: remote host address is the local host
2009-04-03 09:14:08 1Lpfar-0004fh-Ku ** [email protected] R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<[email protected]>: host nescosrv.nesco.ee [194.204.28.195]: 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in local recipient table
And mail isn't piping thru to the mail1 box. Here's the main.cf
sh-3.2# cat main.cf
# 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 = /private/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
# [email protected].
# 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
# 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,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
# 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 [email protected] 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 [email protected] 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:/etc/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/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:/file/name
#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:/file/name
#fallback_transport = cyrus
#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 = [email protected]
#luser_relay = [email protected]
#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
# 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
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# 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/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
mydomain_fallback = localhost
message_size_limit = 52428800
myhostname = mail1.stanwood.wednet.edu
mailbox_transport = cyrus
mydomain = stanwood.wednet.edu
mailbox_size_limit = 0
enable_server_options = yes
inet_interfaces = all
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
smtpd_use_tls = yes
smtpd_enforce_tls = no
smtpd_tls_cert_file = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpd_tls_key_file = /etc/certificates/mail1.stanwood.wednet.edu.key
smtpd_sasl_auth_enable = yes
smtpd_use_pw_server = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_pw_server_security_options = gssapi,cram-md5,login,plain
content_filter = smtp-amavis:[127.0.0.1]:10024
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
owner_request_special = no
recipient_delimiter = +
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
# 02/02/09 Server Checkup by Alex
bounce_queue_lifetime = 6h
delay_warning_time = 6h
maximal_queue_lifetime = 2d
# Topicdesk Frontline Defense
disable_vrfy_command = yes
smtpd_client_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_rbl_client zen.spamhaus.org, permit
smtpd_helo_required = yes
smtpd_helo_restrictions = permit_sasl_authenticated, permit_mynetworks, check_helo_access hash:/etc/postfix/helo_access, reject_non_fqdn_hostname,reject_invalid_hostname, permit
smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_sender, permit
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_data_restrictions = permit_mynetworks, reject_unauth_pipelining, permit
virtual_transport = virtual
virtual_mailbox_domains =
sh-3.2#

Right, what was happening is that it was a big loop. We had to modify our DNS and some other settings on the spam bucket... but... wondering if there's another solution...
mail1:~ admin$ postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
bouncequeuelifetime = 6h
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
delaywarningtime = 6h
disablevrfycommand = yes
enableserveroptions = yes
html_directory = no
inet_interfaces = all
localrecipientmaps = proxy:unix:passwd.byname $alias_maps
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
maximalqueuelifetime = 2d
messagesizelimit = 52428800
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
mydomain = stanwood.wednet.edu
mydomain_fallback = localhost
myhostname = mail1.stanwood.wednet.edu
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdclientrestrictions = permitsaslauthenticated, permit_mynetworks, rejectrblclient zen.spamhaus.org, permit
smtpddatarestrictions = permit_mynetworks, rejectunauthpipelining, permit
smtpdenforcetls = no
smtpdhelorequired = yes
smtpdhelorestrictions = permitsaslauthenticated, permit_mynetworks, checkheloaccess hash:/etc/postfix/helo_access, rejectnon_fqdn_hostname,reject_invalidhostname, permit
smtpdpw_server_securityoptions = gssapi,cram-md5,login,plain
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdsenderrestrictions = permitsaslauthenticated, permit_mynetworks, rejectnon_fqdnsender, permit
smtpdtls_certfile = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpdtls_keyfile = /etc/certificates/mail1.stanwood.wednet.edu.key
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550
virtualmailboxdomains =
virtual_transport = virtual
mail1:~ admin$

Mail Server for ABAP Trial Version

Hi,
Is it possible to configure external smtp service as a mail server for the sneak preview trial edition.
For ex: gmail allows to use it smtp service for free (smtp.gmail.com and Port: 465 or 587).
How can I use this service as a mail server for the sneak preview.
Thanks,
sam

Hello Sam,
Yes it is. Check the documentation at
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/cc/bae93a2876a81ae10000000a11402f/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/cc/bae93a2876a81ae10000000a11402f/frameset.htm</a>
for further details.
Regards,
Klaus

Create Connection to other Mail server ( Mdaemon )

hi all,
i would like implement collaboration SAP Portal Between Mail Server Mdaemon,
my question how create System landscape to Mail server Mdaemon. because i would like implement collaboration between Calendar on our Mail server.
thanks for your help
rgds
echo

Hi Echo,
You will have to create your own groupware transport for connecting to your mail server.
Out of the box we have connector for MS Exchange and Lotus Domino. Use this as a starting point for creating your own groupware connector
https://media.sdn.sap.com/html/submitted_docs/nw_kmc/howto/coll/How%20To%20Build%20a%20Groupware%20Connector.html
Hope this helps.
Akhilesh

Which mail server is used in a webapp?

Hi all,
I have a Webapp where the users can send an email
to me including the parameters of a form
( <form action="mailto:[email protected])....>
<input type="hidden" name="param1" value="xx"/>
Now depending on which mail client the user has on his machine the resulting email differs, sometimes the parameters as 1 attachment, sometimes xx attachments.
So I want to implement it with javamail-api.
MY question: I have to tell the API the name of the mailserver. How can I know what mail-server the user uses? Or are all these emails processed through my own mail-server?
Please help me to understand it. Thanks a lot in advance,
Peter

Hey ho.
You have to hardconde the mail servers in your code to point to the mail server you use (= your ISP's server) or host (= Your own mailserver). All the mails are then processed through that specified server.

Mail server: TCP connection failed

Hi,
I'm hosting my own mail server on my SnowLeopard server. I've got an Internet Domain Name (cinema-voiron.fr) and a fix IP address. The router which manages my internet connection redirects incoming smtp request to my server using NAT (port 25 opened on my server and on my public IP)
I successfully receive mails from most of people excepts for those with an mail address which is [email protected] Looking in the mail log file, I did not find any mail sent from these addresses. Using tcpdump on my server, I discovered that it seems that the TCP connection between my mail server (passrlminisrv) and the remote smtp server fails.
22:16:25.978773 IP smtp10.smtpout.orange.fr.41183 > passrlminisrv.cinema-voiron.fr.smtp: Flags [S], seq 105066692, win 5840, options [mss 1380,sackOK,TS val 2993558281 ecr 0,nop,wscale 8], length 0
22:16:28.978262 IP smtp10.smtpout.orange.fr.41183 > passrlminisrv.cinema-voiron.fr.smtp: Flags [S], seq 105066692, win 5840, options [mss 1380,sackOK,TS val 2993561281 ecr 0,nop,wscale 8], length 0
22:16:34.977258 IP smtp10.smtpout.orange.fr.41183 > passrlminisrv.cinema-voiron.fr.smtp: Flags [S], seq 105066692, win 5840, options [mss 1380,sackOK,TS val 2993567281 ecr 0,nop,wscale 8], length 0
22:16:41.011109 IP passrlminisrv.cinema-voiron.fr.smtp > smtp10.smtpout.orange.fr.41183: Flags [S.], seq 1934215990, ack 105066693, win 65535, options [mss 1460,nop,wscale 1,nop,nop,TS val 537443811 ecr 2993567281,sackOK,eol], length 0
22:16:41.051125 IP smtp10.smtpout.orange.fr.41183 > passrlminisrv.cinema-voiron.fr.smtp: Flags [R], seq 105066693, win 0, length 0
Any idea of the root cause? Could it be an issue with my DNS configuration or is it related with my own smtp server?
Thank you in advance for your help
Xavier

Fixed it. The root cause is the router layer of my internet modem which is not managing properly TCP windows scaling. I created a new virtual interface on my server on the same subnet of my modem to bypass the routing layer and it works.
xavier

Mail server crashed and burned. Can't get it restored

I setup a DynDns server 2 years ago and then setup postfix to have my own mail server. I will admit that all this took me over a month as I'm not an IT guru. Many kind people helped through some forums.
Recently I had a complete server melt down. Server and both raid drives gone!
I'm replaced all the hardware and I'm tring to start again. I took what I thought were good notes just in case I ever had to start again but I can't get this working.
i have reestablished my DnyDns account and can get my web page to show from out side my network.
I'm using a road runner cable modem, with a linksys router. I have postfix enabler but I don't think it's working correctly.
I have tried telnet commands through terminal but the results are not consistent.
The end result is that I can't receive any mail. I can send mail.
Can anybody help me find a good web page with strong istructions or can anybody offer an help?
As I said, this isn't my strongest talent. I would appreciate any help.
Thank you,

Never answered or replied to . Figured it out on my own

Mail Server Not Responding

I have my own mail server. When my iPhone is on the local WiFi, it can log in and read mail. When it is on the 3G connection, it gets the message 'The mail server "intellexcorp.com" is not responding. Verify that you have entered the correct account info in the Mail settings.' The setttings are unchanged. There is no firewall on the server computer. I can't see why the same settings would have a problem connecting. No other services, including mail and remote access have a problem accessing this computer by name or by IP.
Please, do _NOT_ suggest that I check my settings. As I have said the same settings work fine on Wifi.
Randy Kaempen

Reception is fine. Already tried a reboot. This is an ongoing problem over a period of months. I can't undestand why the 'outside of network' connection can't get to the server while the 'inside the network' can, since there is no firewall and the exact same settings. The mail server is not showing that it is blocking anything. Puzzling.
Randy Kaempen

SMTP error from remote mail service

I am receiving a error that states"SMTP error from remote mail service" This is my work e-mail that is a out look e-mail service--but was put on my laptop in mozilla. If I test send e-mails to my gmail, aol and the work e-mail the work e-mail goes through (on the mozilla) but I get the error report for the gmail and aol test.

''Matt [[#answer-672468|said]]''
<blockquote>
what is the complete error message please.
</blockquote>
Hi Matt--thank you for reaching out to assist--here is the full error message I receive when I attempt to send emails--
SMTP error from remote mail server after end of data:
host p3nlsmtpcp-v01.prod.phx3.gdg [72.167.191.78]:
552 5.2.0 bT641p03m3RZ6FL01 :: CPANEL :: Message rejected for spam or virus content ::
Please include this entire message when contacting support ::
v=2.1 cv=Yecz5mhf c=1 sm=1 tr=0 p=dXr4a0FlAAAA:8 a=9P+wmFvZGoNcfX5LD2dIAQ==:117 a=9P+wmFvZGoNcfX5LD2dIAQ==:17 a=TZb1taSUAAAA:8 a=xSRs65CQCjkA:10 a=IkcTkHD0fZMA:10 a=o1OHuDzbAAAA:8 a=YNv0rlydsVwA:10 a=AK46IGkTethYI5b8t1AA:9 a=QEXdDO2ut3YA:10 a=RBqHpAr1aNgA:10 a=SZlYXZE0WA8A:10 a=POQKUN4lQn8A:10 a=5LQJebhDX5EA:10 a=lWHhIcKi20EA:10 a=AP_QpuyW5RgA:10 a=_ZmE1jEfA50A:10 a=fVc70mvjwYYA:10 a=BfRt8DTvoOQA:10 ::
100.00

Question regarding SMTP on my own mail server

Similar Messages

Maybe you are looking for