SMTP delay in Postfix

Due to the issue with sending emails to Verizon, it seems that verizon does a lookup back to the mail server to see if the user is listed. (as discussed here - http://blog.kloppmagic.ca/archives/2005/02/24/verizon-450-requested-mail-action- not-taken-try-later-error/ - Thanks Joel!!
The discussion says the issue is that Verizon has about a 2 second window to look for the user, then it times out. The discussion talks about setting the SMTP delay to something very short and I cant figure out how to accomplish that on OS X Server (10.4.8). it's part of postfix but when looking at all the configs for postfix, there are several SMTP delays listed
Here is the link for Postfix.
http://www.postfix.org/postconf.5.html
Could someone point me in the right direction on what i should change? Or if there may be other things I need to change to get this working. Tired of all these emails sitting in my mail queue.
Thanks all!!!

There is no reason you should change any of postfix' delay timings to get around the "verizon problem" (unless of course you already have tampered with your settings). If the sender verfication fails because of timing issues, then it most likely has nothing to do with your delay settings, but rather with more generic connection timeouts. Verizon's "moronic" anti-spam measure, doubles (if not more) the load on their mail servers. Add your server being busy, plus busy bandwidth and verification will fail. Sometimes it can take many retries for a message to go through.
Before changing anything check your log. Send an e-mail from your server to an existing verizon user and then follow the trace in your log.
You should see an incoming connection from a verizon host called "**pub.verizon.net" trying to send to the sending user at your domain from "[email protected]".
(You should see tons of those for unknown users on your system as well. That's normal and the reason why verizon uses this system in the first place.)
See what happens and post if you have any questions. If it actually is your server having timing issues, then this needs to be investigated. Still no reason to change default delays.
If you need more help post log extract and unmodified output of postconf -n

Similar Messages

Clear the smtp queue in postfix

I've been trying to find a way to clear the smtp queue from postfix in Lion Mail Server. Got hit by a bad account penetration sending spam and want to clear it to see what is new. TIA

Sorry for the delay in getting back. Thanks. That's exactly what I was looking for. Another one of those tidbits to tuck away.

Delayed Email Reports

Hi,
I today expirancing delayed email delivery from the form:
Received: from SMTP01.XXX.local (172.29.211.11) by
EXHUB02.xxxx.local (172.29.211.42) with Microsoft SMTP Server (TLS) id
14.0.702.0; Tue, 28 Sep 2010 16:25:10 -0400
Received: from mx0.gmx.net (213.165.64.100) by smtp01.xxxx.com
(172.29.211.11) with Microsoft SMTP Server id 14.0.702.0; Tue, 28 Sep 2010
16:24:42 -0400
Received: (qmail 17391 invoked by alias); 28 Sep 2010 20:25:08 -0000
Delivered-To: GMX delivery to [email protected]
Received: (qmail invoked by alias); 28 Sep 2010 20:25:08 -0000
Received: from smtp.lithium.com (EHLO smtp.lithium.com) [208.74.204.5] by
mx0.gmx.net (mx002) with SMTP; 28 Sep 2010 22:25:08 +0200
Received: from app-c2-22.sj.lithium.com (app-c2-22.sj.lithium.com
[10.20.110.222]) by smtp.lithium.com (Postfix) with ESMTP id 34FBBF0108 for
<[email protected]>; Tue, 28 Sep 2010 04:22:41 -0700 (PDT)
X-DomainKeys: Sendmail DomainKeys Filter v1.0.2 smtp.lithium.com 34FBBF0108
From: Lenovo Community Mailer <[email protected]>
To: johnripper <[email protected]>
Message-ID: <[email protected]om>
Subject: Lenovo Community Subscription: 1 Update: Re: Access Connection SMS
Menu disappeared!!!!
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_184_10340163.1285672961216"
Date: Tue, 28 Sep 2010 04:22:41 -0700
X-GMX-Antispam: -2 (not scanned, spam filter disabled);
Detail=5D7Q89H36p4L00VTXC6D4q0N+AH0PUCnKGJbGgJLbSXk30NezpdxUg==V1;
X-Resent-By: Forwarder <[email protected]>
X-Resent-For: [email protected]
X-Resent-To: [email protected]
Return-Path: [email protected]
X-MS-Exchange-Organization-PRD: lenovosocial.com
Received-SPF: None (SMTP01.xxx.local: [email protected] does not
designate permitted sender hosts)
X-MS-Exchange-Organization-Antispam-Report: XXX
X-MS-Exchange-Organization-SCL: 0
X-MS-Exchange-Organization-SenderIdResult: NONE
X-MS-Exchange-Organization-AuthSource: SMTP01.xxx.local
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AVStamp-Mailbox: MSFTFF;1;0;0 0 0
X-Auto-Response-Suppress: DR, OOF, AutoReply
s Is this fixed?
Thanks
JR
I

Yes. I created 8 separate 255.255.255.0 exceptions. In viewing the packet
trace data for the last couple of days it appears this resoloved the
problem.
Thanks
Brad Johnson
"Craig Johnson" <[email protected]> wrote in message
news:[email protected]..
> In article <XCo8l.13813$[email protected]>, Brad Johnson
> wrote:
>> Both servers are running NW 6.5 sp 6. After this problem started I
>> applied
>> BM38sp5_IR1, TCP681K, and wsock6o. This had no affect on the issue.
>>
>> If I create individual exceptions for the IP addresses I am currently
>> receiving mail from, rather than using the range of potential addresses,
>> the
>> problem goes away.
>>
> Well, it sounds definitive enough, but I think if it were a generic issue
> to
> the patch level I would have heard about it from my clients who use
> Postini
> mail filtering service. All of the Postini-related servers have a network
> address as a source in the filter exceptions for smtp.
>
> Instead of using a 255.255.248.0 mask, does it work if you set up 8
> different
> 255.255.255.0 exceptions?
>
>
> Craig Johnson
> Novell Support Connection SysOp
> *** For a current patch list, tips, handy files and books on
> BorderManager, go to http://www.craigjconsulting.com ***
>
>

Reverse DNS does not match SMTP Banner

Hello,
We have a client with an SLS who is configured to send mail using the ISP as relay. With this situation, the server-side mail rules (vacation notices) are not working.
So, I need to configure the server to use DNS to send mail. The client has one public static IP, in the form of client.static.isp.gr. ISP refuses to change the PTR for a single IP, so when I check the server using mxtoolbox.com, I get +Reverse DNS does not match SMTP Banner+.
In MS Exchange, you can set the "Internet e-mail name" and change the default SMTP banner.
How can I change the SMTP banner in Postfix? (in order to put the ISPs PTR for the static IP).
Regards
Kostas

Kostas B. has been tussling with other issues ("ISP refuses to change the PTR for a single IP") and this is unrelated to the configuration of Mail itself, from what I can tell of it. He's really trying to do something that the ISP involved isn't supporting, and that's more of an administrative or ISP issue and less of a technical issue.
As for your question (and presuming your public-facing DNS forward and reverse translations are correct and your MX record is correct, details which are not yet in evidence), launch Server Admin and set your mail server host name in the mail configuration. Server Admin > select server > Mail > general > fill in your internet-facing host name. This name should matche your public DNS MX record, and your public forward and reverse DNS translations should (also) match.
And as a general rule, please don't thread-jack. That largely serves to confound and confuse the discussions.

OS X Server 10.5.8 - SMTP not sending emails

Hi,
Clean install 10.5.8 Server. DNS and receiving emails works fine, but when i try sending emails with webmail or any mail client it doesn't work.
smtp log :
"Serveur postfix/postfix-script[14806]: fatal: the Postfix mail system is not running"
With 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 = 20971520
mydestination = $myhostname,localhost.$mydomain,localhost,Serveur.local,kctus.net
mydomain = kctus.net
mydomain_fallback = localhost
myhostname = kctus.net
mynetworks = 127.0.0.0/8,192.168.1.0/24
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
relayhost = smtp.orange.fr
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdenforcetls = no
smtpdpw_server_securityoptions = plain,login,cram-md5
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
Any help plz ?

Please increase logging level for SMTP to "Information". Next try to send mail and post the relevant log entries.

[new] postfix-tls+sasl

As subject, fresh postfix esperimental release with TLS and SASL support. I just modified the original script:
# Contributor: Federico Quagliata (quaqo) <[email protected]>
# Based on the official postfix Arch Linux package in current
pkgname=postfix-tls+sasl
pkgver=2.2
pkgrel=20041219
pkgdesc="Postfix experimental release with TLS and SASL support"
depends=('glibc' 'db' 'pcre' 'cyrus-sasl')
makedepends=('openssl')
# leave etc/mail/aliases in backup() for a few versions until
# people have migrated or made other provisions
backup=(etc/mail/aliases etc/postfix/aliases etc/postfix/virtual etc/postfix/relocated
etc/postfix/access etc/postfix/header_checks etc/postfix/transport
etc/postfix/main.cf etc/postfix/master.cf)
install="postfix.install"
url="http://www.postfix.org/"
source=(postfix.patch.bz2
postfix
postfix.install
http://postfix.portal-to-web.de/dist/experimental/postfix-$pkgver-$pkgrel+tls-nonprod.tar.gz)
md5sums=('a3c45ff23ef036143711793fcf2478c3' 'eb5f290655559bbdfbf7b9791aeb4a64'
'469ce1ce887bafb2afd243c4c64c843a')
provides=('smtp-server')
conflicts=('postfix')
build() {
cd $startdir/src/postfix-$pkgver-$pkgrel+tls-nonprod
make makefiles CCARGS="-DUSE_TLS -I/usr/include/openssl -DUSE_SASL_AUTH -I/usr/include/sasl" AUXLIBS="-lssl -lcrypto -lsasl2" || return 1
make OPT="${CFLAGS}" || return 1
sh postfix-install -non-interactive
install_root="$startdir/pkg"
daemon_directory="/usr/lib/postfix"
sample_directory="/etc/postfix/sample"
manpage_directory="/usr/man"
cd $startdir/pkg
cat $startdir/src/postfix.patch |patch -Np0 || return 1
rm etc/postfix/main.cf~
cd $startdir/pkg
mkdir etc/rc.d
install -m 0755 $startdir/src/postfix etc/rc.d/postfix
As usual, you can mail me at [email protected] for corrections, yadda yadda yadda... :-)

i am trying compile the package but i had a error :
ib -lsasl2 -lssl -lcrypto -L/usr/lib -lpcre -ldb -lnsl -lresolv
gcc: unrecognized option `-R/usr/lib'
/usr/lib/libdb.so: undefined reference to `pthread_condattr_setpshared'
/usr/lib/libdb.so: undefined reference to `pthread_mutexattr_destroy'
/usr/lib/libdb.so: undefined reference to `pthread_mutexattr_setpshared'
/usr/lib/libdb.so: undefined reference to `pthread_mutexattr_init'
/usr/lib/libdb.so: undefined reference to `pthread_mutex_trylock'
collect2: ld returned 1 exit status
make: *** [master] Error 1
make: *** [update] Error 1
make: *** [update] Error 2
==> ERROR: Build Failed. Aborting...
Error: Failed to build "postfix"
root@Celerondomain celeron #
i have db 4.2.52-1 :S
PD: i used srcpac

Sent mail occasionally not stored in sent folder

Hi,
we encountered weird problem with OS X server behaviour where user sent email via smtp server and it is not stored in his/her mailbox.
This issue is happening time to time I would say almost randomly.
Do you have any idea why this is happening and where is the sent mail?
I picked a case and gathered relevant logs:
Thank you in advance
Server OS 10.10.1 server 4.0.3
Amavis.log
Apr 1 17:10:28 smtp.server.tld /Applications/Server.app/Contents/ServerRoot/usr/bin/amavisd[99344]: (99344-14) ESMTP:[127.0.0.1]:10024 /Library/Server/Mail/Data/scanner/amavis/tmp/amavis-20150401T162847-99344-AfuMa tsy: <[email protected]> -> <[email protected]>,<[email protected]> SIZE=42753 Received: from smtp.server.tld ([127.0.0.1]) by localhost (smtp.server.tld [127.0.0.1]) (amavisd-new, port 10024) with ESMTP; Wed, 1 Apr 2015 17:10:28 +0200 (CEST)
Apr 1 17:10:28 smtp.server.tld /Applications/Server.app/Contents/ServerRoot/usr/bin/amavisd[99344]: (99344-14) Checking: JjUbZ6HVURz7 [31.7.245.146] <[email protected]> -> <[email protected]>,<[email protected]>
Apr 1 17:10:28 smtp.server.tld /Applications/Server.app/Contents/ServerRoot/usr/bin/amavisd[99344]: (99344-14) Open relay? Nonlocal recips but not originating: [email protected]
Apr 1 17:10:28 smtp.server.tld /Applications/Server.app/Contents/ServerRoot/usr/bin/amavisd[99344]: (99344-14) FWD from <[email protected]> -> <[email protected]>,<[email protected]>,BODY=7BIT 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 920CA6DC5A3
Apr 1 17:10:28 smtp.server.tld /Applications/Server.app/Contents/ServerRoot/usr/bin/amavisd[99344]: (99344-14) Passed CLEAN {RelayedInbound,RelayedOpenRelay}, [31.7.245.146]:47116 [31.7.245.146] <[email protected]> -> <[email protected]>,<[email protected]>, Queue-ID: 1D4EE6DC589, Message-ID: <[email protected]>, mail_id: JjUbZ6HVURz7, Hits: 0.732, size: 42753, queued_as: 920CA6DC5A3, 493 ms
mail.log
Apr 1 17:10:28 smtp.server.tld postfix/smtp[1487]: 1D4EE6DC589: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.55, delays=0.03/0.02/0/0.49, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 920CA6DC5A3)
Apr 1 17:10:36 smtp.server.tld postfix/smtp[1493]: 920CA6DC5A3: to=<[email protected]>, relay=mail.receiverserver.com[11.22.33.44]:25, delay=7.4, delays=0.06/0.03/0.37/7, dsn=2.0.0, status=sent (250 OK id=1YdKHr-0006of-5z)
filter na 920CA6DC5A3
Apr 1 17:10:28 smtp.server.tld postfix/smtpd[1491]: 920CA6DC5A3: client=localhost[127.0.0.1]
Apr 1 17:10:28 smtp.server.tld postfix/cleanup[1486]: 920CA6DC5A3: message-id=<[email protected]>
Apr 1 17:10:28 smtp.server.tld postfix/qmgr[215]: 920CA6DC5A3: from=<[email protected]>, size=43163, nrcpt=2 (queue active)
Apr 1 17:10:28 smtp.server.tld postfix/smtp[1487]: 1D4EE6DC589: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.55, delays=0.03/0.02/0/0.49, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 920CA6DC5A3)
Apr 1 17:10:28 smtp.server.tld postfix/smtp[1487]: 1D4EE6DC589: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.55, delays=0.03/0.02/0/0.49, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 920CA6DC5A3)
Apr 1 17:10:28 smtp.server.tld postfix/pipe[1495]: 920CA6DC5A3: to=<[email protected]>, orig_to=<[email protected]>, relay=dovecot, delay=0.16, delays=0.06/0.01/0/0.1, dsn=2.0.0, status=sent (delivered via dovecot service)
Apr 1 17:10:36 smtp.server.tld postfix/smtp[1493]: 920CA6DC5A3: to=<[email protected]>, relay=mail.receiverserver.com[11.22.33.44]:25, delay=7.4, delays=0.06/0.03/0.37/7, dsn=2.0.0, status=sent (250 OK id=1YdKHr-0006of-5z)
Apr 1 17:10:36 smtp.server.tld postfix/qmgr[215]: 920CA6DC5A3: removed

I have a few users reporting the same problem. It is inconsistent and I have not found a way to reproduce it at will.
Our users have been BCC them selves so they have a copy to move to sent it if is not there.
They have also reported mail being copied to the Send and Drafts folders when they send it.
When they login from a different mail client the folders are the same. So I am assuming the problem is server side? Or at least the result is.
Is it the clients job to ask the server to move the mail from outbox to the sent folder?
I think this is where the problem is occurring.
We were looking at it this morning and moving mail around from Drafts to Trash and Sent. Mostly it moved around fine but there was one instance where we moved mail from Drafts to Trash.
We then quit and opened mail again (we waited until the activity window was empty)
The mail we moved to Trash was gone. But a new mail was in Drafts that had been sent earlier that morning. A copy was still in the Sent folder.
We could not reproduce this.
We also have roundcube but it is the mail.app clients that notice the problems. They are the majority so it is to be expected.
Clients OS X 10.10.2, mail.app 8.2
Server 4.0.3, OS X 10.10.2, Roundcube 1.0.3 (Topicdesk Roundcube Installer 1.0.3a)

How: poll POP3 from ISP and feed into OSX mail server (Dovecot)

Hi all,
My desire: use IMAP for all my iOS and OSX devices to forget about the synchronization nightmare when using POP.
My ISP only provides POP3, and I can fetch emails from his POP3 server so they end up in my mail client on any OSX workstation.
But I want to use IMAP via the Dovecot email server on OSX server mountain lion.
How do I implement that missing link?
Can this be done by a cron script, mimicking a MTA?
Somehow the OSX mailserver cannot be convinced to fetch the emails from the POP3 server at the Internet Server Provider (ISP).
All the OSX or iOS device connects to my OSX Mountain Lion server running the mailserver (i.e. Dovecot).
In my private network sending emails and fetching them using IMAP already works fine.
I am lost on this one. Any help would be appreciated.
Thanks already.
best regards,
Bolko

One solution is to use a server based software (i.e. that runs on OS X server) which polls a remote POP3 server and delivers mail to an SMTP server — the Postfix SMTP server on your OS X server (NOT Dovecot, Postfix is the SMTP server which then hands off mail to Dovecot the IMAP on your OS X server)
This software would have to be installed 'by hand' meaning you have to download the source and compile it as is standard with Linux type utilities.
Here is link to the utility 'fetchmail'.
http://fetchmail.berlios.de/index.html
You may want to confirm with the package maintainers that this would work on OS X. If you are not comfortable working at the level of installing Linux packages then I would advise not to proceed.
UPDATE: I found this page on the Apple developers website:
http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/ man1/fetchmail.1.html
it refers to the fetchmail program above so it looks like it runs OK on OS X, but you still have to manually set it up.
Another option is this software
http://www.sspi-software.com/mailfwd_macx.html
I don't have any experience with it personally and I don't know if it can run as a service (that is with no-one logged into the machine).

A question about sendmail on solaris(10 and 11)

I have a private network for working,all machines are linux or unix.
I have one smtp server running postfix,wich force all connection
to make tls(escuse my english relly bad).
On hpux 11.31 i use this .mc
divert(0)dnl
VERSIONID(`$Id: generic-hpux10.mc,v 8.13 2001/05/29 17:29:52 ca Exp $')
OSTYPE(hpux11)dnl
DOMAIN(generic)dnl
define(`_X400_UUCP_')dnl
define(`_MASQUERADE_ENVELOPE_')dnl
define(`MASQUERADE_NAME')dnl
define(`confTRY_NULL_MX_LIST',`T')dnl
define(`LUSER_RELAY',`name_of_luser_relay')dnl
define(`DATABASE_MAP_TYPE',`dbm')dnl
define(`_CLASS_U_')dnl
define(`LOCAL_RELAY')dnl
define(`MAIL_HUB')dnl
TRUST_AUTH_MECH(`GSSAPI DIGEST-MD5')dnl
FEATURE(always_add_domain)dnl
MAILER(local)dnl
MAILER(smtp)dnl
MAILER(openmail)dnl
MAILER(uucp)dnl
define(`SMART_HOST', `posta.domain.com')
define(`confCACERT_PATH', `/etc/mail/certs')dnl
define(`confCACERT', `/etc/mail/certs/domain.com.crt')dnl
define(`confSERVER_CERT', `/etc/mail/certs/hpux2.domain.com.crt')dnl
define(`confSERVER_KEY', `/etc/mail/certs/hpux2.domain.com.key')dnl
define(`confCLIENT_CERT', `/etc/mail/certs/hpux2.domain.com.crt')dnl
define(`confCLIENT_KEY', `/etc/mail/certs/hpux2.domain.com.key')dnl
define(`confRAND_FILE',`egd:/dev/urandom')dnl
D{tls_version}TLSv1
O UseTLS=True
On Solaris this
divert(0)dnl
VERSIONID(`sendmail.mc (Sun)')
OSTYPE(`solaris11')dnl
DOMAIN(`solaris-generic')dnl
define(`confFALLBACK_SMARTHOST', `mailhost$?m.$m$.')dnl
FEATURE(genericstable)dnl
FEATURE(mailertable)dnl
FEATURE(domaintable)dnl
FEATURE(allmasquerade)dnl
FEATURE(promiscuous_relay)dnl
FEATURE(accept_unresolvable_domains)dnl
FEATURE(accept_unqualified_senders)dnl
FEATURE(no_default_msa)
DOMAIN(`posta.domain.local')dnl
MAILER(`local')dnl
MAILER(`smtp')dnl
define(`confSMTP_LOGIN_MSG', `$j Sendmail $b')
define(`SMART_HOST', `posta.domain.com')
define(`confCACERT_PATH', `/etc/mail/certs')dnl
define(`confCACERT', `/etc/mail/certs/domain.local.crt')dnl
define(`confSERVER_CERT', `/etc/mail/certs/solaris.domaincrt')dnl
define(`confSERVER_KEY', `/etc/mail/certs/solaris.domain.coml.key')dnl
define(`confCLIENT_CERT', `/etc/mail/certs/solaris.domain.com.crt')dnl
define(`confCLIENT_KEY', `/etc/mail/certs/solaris.domain.com.key')dnl
define(`confRAND_FILE',`egd:/dev/urandom')dnl
D{tls_version}TLSv1
On hpux all works fine,send mail,on solaris give me those errors
[192.168.3.252], dsn=5.0.0, stat=Service unavailable
Diagnostic-Code: SMTP; 530 5.7.0 Must issue a STARTTLS command first
I try to set UseTLS=True even on solaris but give me error and sendmail don't start
How to set sendmail to use tls?
thank to who help me

Solution found using this mc
divert(0)dnl
VERSIONID(`sendmail.mc (Sun)')
OSTYPE(`solaris11')dnl
DOMAIN(`solaris-generic')dnl
define(`confCACERT_PATH', `/etc/mail/certs')dnl
define(`confCACERT', `/etc/mail/certs/domain.com.crt')dnl
define(`confSERVER_CERT', `/etc/mail/certs/solaris11.domain.com.crt')dnl
define(`confSERVER_KEY', `/etc/mail/certs/solaris11.domain.com.key')dnl
define(`confCLIENT_CERT', `/etc/mail/certs/solaris11.domain.com.crt')dnl
define(`confCLIENT_KEY', `/etc/mail/certs/solaris11.domain.com.key')dnl
define(`confRAND_FILE',`egd:/dev/urandom')dnl
define(`_X400_UUCP_')dnl
define(`_MASQUERADE_ENVELOPE_')dnl
define(`MASQUERADE_NAME')dnl
define(`confTRY_NULL_MX_LIST',`T')dnl
define(`LUSER_RELAY',`name_of_luser_relay')dnl
define(`DATABASE_MAP_TYPE',`dbm')dnl
define(`_CLASS_U_')dnl
define(`LOCAL_RELAY')dnl
define(`MAIL_HUB')dnl
TRUST_AUTH_MECH(`GSSAPI DIGEST-MD5')dnl
FEATURE(always_add_domain)dnl
FEATURE(access_db)dnl
MAILER(local)dnl
MAILER(smtp)dnl
MAILER(uucp)dnl
define(`SMART_HOST', `posta.domain.com')
define(`confCACERT_PATH', `/etc/mail/certs')dnl
define(`confCACERT', `/etc/mail/certs/domain.com.crt')dnl
define(`confSERVER_CERT', `/etc/mail/certs/solaris11.domain.com.crt')dnl
define(`confSERVER_KEY', `/etc/mail/certs/solaris11.domain.com.key')dnl
define(`confCLIENT_CERT', `/etc/mail/certs/solaris11.domain.com.crt')dnl
define(`confCLIENT_KEY', `/etc/mail/certs/solaris11.domain.com.key')dnl
define(`confRAND_FILE',`file:/dev/random')dnl
D{tls_version}TLSv1
and makemap dbm access file
Last question: how to disable ssl3 and enable tls1 only?

Connect(/var/imap/socket/lmtp) failed: No such file or directory' + DBERROR

Mail server won't work: Dual 2 GHz PowerPC G5 running Mac OS X Server 10.5.8
Cleared /var/imap/db
Rebuilt the database using 'sudo mailbfr -f'
Logs say:
master: process started
deliver[nnn]: connect(/var/imap/socket/lmtp) failed: No such file or directory
ctl_cyrusdb[nnn]: DBERROR db4: unable to join the environment
ctl_cyrusdb[nnn]: verifying cyrus databases
ctl_cyrusdb[nnn]: skiplist: recovered/var/imap/mailboxes.db (xxx records, yyyyy bytes) in 0 seconds
ctl_cyrusdb[nnn]: skiplist: recovered/var/imap/annotations.db (0 records, zzz bytes) in 0 seconds
Help!

Update(s):
(1) problem went away on a reboot
(2) problem re-appeared at 02:00 this morning, following a attempted mailbfr backup
(3) new problem on reboot:
- IMAP now working
- Overview shows SMTP status as 'Running'
- SMTP log says: postfix/postfix-script[nnnn]: fatal: the Postfix mail system is not running
(4) so, try to shut down mail gracefully with 'serveradmin stop mail'
'mail: state = "STOPPING"'
'mail: status = 0'
BUT!
(5) 'Overview' shows IMAP and so on 'Stopped' and for SMTP 'Shutting down'
(6) 'Overview' now shows Outgoing SMTP and Incoming SMTP 'Running'
(7) Try again, says 'Shutting down' for a while, then 'Running' again

[Bug] Sent by collage... empty ?

Send via collage doesn't seem to work here, no real time to make new test, but emails appeared empty.
Franck
Return-Path: [email protected]
Received: from zimbra.xxx.net (LHLO
zimbra.xxx.net) (172.20.243.215) by
zimbra.xxx.net with LMTP; Mon, 30 Jan 2012 20:33:07 +0100
(CET)
Received: from smtp.xxx.fr (mx24.xxx.net [xx.xx.xx.xx])
          by zimbra.xxx.net (Postfix) with ESMTP id CDBB9748D80
          for <[email protected]>; Mon, 30 Jan 2012 20:33:06 +0100 (CET)
Received: from smtp.xxx.fr ([xx.xx.xx.xx])
          by mx1.xxx.fr (MXproxy) for [email protected];
          Mon, 30 Jan 2012 20:33:07 +0100 (CET)
X-xxx-SC: state=HAM score=15
Received: from 192.168.0.6 (did75-8-82-226-27-183.fbx.proxad.net [xx.xx.xx.xx])
          by smtp.xxx.fr (Postfix) with ESMTP id CEF75D482BC
          for <[email protected]>; Mon, 30 Jan 2012 20:33:03 +0100 (CET)
Date: Sat, 28 Jan 2012 22:01:18 +0100
Subject: Sent via Adobe Collage
Message-ID: <[email protected]>
From: Franck Payen <[email protected]>
To: fr <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
VGhpcyBpbWFnZSBpcyBjcmVhdGVkIHZpYSBBZG9iZSBDb2xsYWdlLg==

Hey Franck,
I sent myself jpegs of my project via email (Gmail in my case) using the Share via link and the images came through okay for me. I'm pretty sure the Share via options in Collage just hook into supported Share options through the Android device itself and the app doesn't natively include these services. You might test using a different email service or option if possible, the one here might be blocking or stripping attachments for some reason.
-Dave

Mavericks Server keeps editing master.cf

In order to enable SMTP clients to connect via port 587 (the "submission" port), you must manually edit /Library/Server/Mail/Config/postfix/master.cf and uncomment the appropriate "submission" lines. Did that, ran "postfix reload," everything's great. But after a restart, the lines are commented out. After a re-edit, and verifying that postfix is working properly, I try "serveradmin stop mail" and then "serveradmin start mail," which results in the lines in master.cf being commented out once again. So, I move the "submission" lines past the "auto-generated section" to get them out of Server Admin's grasp. Nope, it moves them back, comments them out, and duplicates them.
I'm obviously missing the magic incantation to make Mavericks Server retain my submission settings. It's like a raging feminist or something.

#
# Postfix master process configuration file. For details on the format
# of the file, see the master(5) manual page (command: "man 5 master").
# Do not forget to execute "postfix reload" after editing this file.
# ==========================================================================
# service type private unpriv chroot wakeup maxproc command + args
#               (yes)   (yes)   (yes)   (never) (100)
# ==========================================================================
# ==== Begin auto-generated section ========================================
# This section of the master.cf file is auto-generated by the Server Admin
# Mail backend plugin whenever mails settings are modified.
smtp      inet n       -       n       -       1       postscreen
smtpd     pass -       -       n       -       -       smtpd
dnsblog   unix -       -       n       -       0       dnsblog
tlsproxy unix -       -       n       -       0       tlsproxy
submission inet n       -       n       -       -       smtpd
-o smtpd_tls_security_level=may
-o smtpd_sasl_auth_enable=yes
-o smtpd_client_restrictions=permit_sasl_authenticated,reject
-o content_filter=dksign:[127.0.0.1]:10027
smtp      unix -       -       n       -       -       smtp
# === End auto-generated section ===========================================
proxywrite unix -       -       n       -       1       proxymap
# Modern SMTP clients communicate securely over port 25 using the STARTTLS command.
# Some older clients, such as Outlook 2000 and its predecessors, do not properly
# support this command and instead assume a preconfigured secure connection
# on port 465. This was sometimes called "smtps", but such usage was never
# approved by the IANA and therefore conflicts with another, legitimate assignment.
# For more details about managing secure SMTP connections with postfix, please see:
#   http://www.postfix.org/TLS_README.html
# To read more about configuring secure connections with Outlook 2000, please read:
#   http://support.microsoft.com/default.aspx?scid=kb;en-us;Q307772
# Apple does not support the use of port 465 for this purpose.
# After determining that connecting clients do require this behavior, you may choose
# to manually enable support for these older clients by uncommenting the following
# four lines.
465      inet n       -       n       -       -       smtpd
-o smtpd_tls_wrappermode=yes
-o smtpd_sasl_auth_enable=yes
-o smtpd_client_restrictions=permit_sasl_authenticated,reject
-o content_filter=dksign:[127.0.0.1]:10027
-o milter_macro_daemon_name=ORIGINATING
#628       inet n       -       n       -       -       qmqpd
pickup    fifo n       -       n       60      1       pickup
-o content_filter=smtp-amavis:[127.0.0.1]:10024
cleanup   unix n       -       n       -       0       cleanup
qmgr      fifo n       -       n       300     1       qmgr
#qmgr     fifo n       -       n       300     1       oqmgr
tlsmgr    unix -       -       n       1000?   1       tlsmgr
rewrite   unix -       -       n       -       -       trivial-rewrite
bounce    unix -       -       n       -       0       bounce
defer     unix -       -       n       -       0       bounce
trace     unix -       -       n       -       0       bounce
verify    unix -       -       n       -       1       verify
sacl-cache unix -       -       n       -       1       sacl-cache
flush     unix n       -       n       1000?   0       flush
proxymap unix -       -       n       -       -       proxymap
# When relaying mail as backup MX, disable fallback_relay to avoid MX loops
relay     unix -       -       n       -       -       smtp
     -o smtp_fallback_relay=
#       -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
showq     unix n       -       n       -       -       showq
error     unix -       -       n       -       -       error
retry     unix -       -       n       -       -       error
discard   unix -       -       n       -       -       discard
local     unix -       n       n       -       -       local
virtual   unix -       n       n       -       -       virtual
lmtp      unix -       -       n       -       -       lmtp
anvil     unix -       -       n       -       1       anvil
scache    unix -       -       n       -       1       scache
# ====================================================================
# Interfaces to non-Postfix software. Be sure to examine the manual
# pages of the non-Postfix software to find out what options it wants.
# Many of the following services use the Postfix pipe(8) delivery
# agent. See the pipe(8) man page for information about ${recipient}
# and other message envelope options.
# ====================================================================
# maildrop. See the Postfix MAILDROP_README file for details.
# Also specify in main.cf: maildrop_destination_recipient_limit=1
#maildrop unix -       n       n       -       -       pipe
# flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
# ====================================================================
# Recent Cyrus versions can use the existing "lmtp" master.cf entry.
# Specify in cyrus.conf:
#   lmtp    cmd="lmtpd -a" listen="localhost:lmtp" proto=tcp4
# Specify in main.cf one or more of the following:
# mailbox_transport = lmtp:inet:localhost
# virtual_transport = lmtp:inet:localhost
# ====================================================================
# Cyrus 2.1.5 (Amos Gouaux)
# Also specify in main.cf: cyrus_destination_recipient_limit=1
#cyrus     unix -       n       n       -       -       pipe
# user=_cyrus argv=/usr/bin/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
# ====================================================================
# Old example of delivery via Cyrus.
#old-cyrus unix -       n       n       -       -       pipe
# flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
# ====================================================================
# Dovecot
dovecot   unix -       n       n       -       25      pipe
flags=DRhu user=_dovecot:mail argv=/Applications/Server.app/Contents/ServerRoot/usr/libexec/dovecot/dovecot-lda -d ${user}
# Use these settings to enable +addressing ([email protected])
# flags=DRhu user=_dovecot:mail argv=/Applications/Server.app/Contents/ServerRoot/usr/libexec/dovecot/dovecot-lda -d ${user} -a ${recipient} -m ${extension}
# ====================================================================
# Greylist policy server
policy    unix -       n       n       -       -       spawn
user=nobody:mail argv=/usr/bin/perl /usr/libexec/postfix/greylist.pl
# ====================================================================
# See the Postfix UUCP_README file for configuration details.
#uucp      unix -       n       n       -       -       pipe
# flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
# ====================================================================
# Other external delivery methods.
#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=bsmtp argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient
#scalemail-backend unix -       n       n       -       2       pipe
# flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store
# ${nexthop} ${user} ${extension}
#mailman   unix -       n       n       -       -       pipe
# flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
# ${nexthop} ${user}
smtp-amavis unix -      -       y       -       2       smtp
   -o smtp_data_done_timeout=1200
   -o smtp_send_xforward_command=yes
   -o disable_dns_lookups=yes
   -o smtp_tls_security_level=none
   -o smtpd_tls_security_level=none
127.0.0.1:10025 inet n -       y       -       -       smtpd
   -o content_filter=
   -o local_recipient_maps=
   -o relay_recipient_maps=
   -o smtpd_restriction_classes=
   -o smtpd_client_restrictions=
   -o smtpd_helo_restrictions=
   -o smtpd_sender_restrictions=
   -o smtpd_recipient_restrictions=permit_mynetworks,reject
   -o mynetworks=127.0.0.0/8
   -o smtp_tls_security_level=none
   -o smtpd_tls_security_level=none
   -o strict_rfc821_envelopes=yes
   -o smtpd_error_sleep_time=0
   -o smtpd_soft_error_limit=1001
   -o smtpd_hard_error_limit=1000
   -o receive_override_options=no_header_body_checks
# DKIM signing proxy
dksign    unix -       -       n       -       10      smtp
        -o smtp_send_xforward_command=yes
        -o smtp_tls_security_level=none
        -o smtpd_tls_security_level=none
127.0.0.1:10028 inet n -      n       -       10      smtpd
        -o content_filter=
        -o receive_override_options=no_unknown_recipient_checks,no_header_body_checks
        -o smtp_tls_security_level=none
        -o smtpd_tls_security_level=none
        -o smtpd_helo_restrictions=
        -o smtpd_client_restrictions=
        -o smtpd_sender_restrictions=
        -o smtpd_recipient_restrictions=permit_mynetworks,reject
        -o mynetworks=127.0.0.0/8
        -o smtpd_authorized_xforward_hosts=127.0.0.0/8

Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - 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,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - 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, $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 [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

Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint.

Postfix/smtp[8437] Operation timed out can't send mail to 1 address

server 10.4.5 running mail, filesharing and website.
The mail server has been up for months working fawlessly. We have one address (domain) where we can't send mail, and users at that address can't send us mail.
All other mail functions on both ends seem to be functioning fine.
They seem to be running exchange as a mail server, but i don't have other details from their side. DNS/MX records all look like you would expect.
This has me stumped.
i turned debug level loging on and got the following smtp message written to the log when i tried to mail to an address at that domain.
Feb 23 20:45:10 fileserver postfix/smtp[8437]: 775401AFD61: to=<[email protected]>, relay=none, delay=31, status=deferred (connect to anhc-mail.anhc.org[24.237.2.213]: Operation timed out)

Yes, good luck to them.
relay=none
doesn't look so good.
Of course, a successful outgoing message should look something more like:
Apr 8 11:41:05 server postfix/smtp[2300]: F1D4D3B8A27: to=<[email protected]>, relay=mail.someobfuscatedserver.com[6x.20x.148.1x6], delay=5, status=sent (250 2.0.0 k38FYfDS023848 Message accepted for delivery)
I take it you can send to any/all other mail addresses (servers) ?
Here's a thought:
Some time ago, I had to edit the helo_checks config of postfix, for a windows mailserver because their AntiVirus was horribly mangling their outgoing mail, helo-ing as <fix-your-dns>.local
Point being that .local anything is not a viable tld for anything in the public realm, and certainly won't work with the rest of the world in terms of DNS.
That might be the work of Norton's break-it-for-you addon for Windows Exchange mailservers, not sure.
Please post the output of:
postconf -n
on your server,
and the mail.log file content when they try to send you an email (confirm via telephone and watch for it).

Smtp postfix logs after upgrade

I successfully upgraded server 3.2 to 4 and now in SMTP Logs appears only postfix/smtpd 'warning' level - like this
postfix/smtpd[41555]: warning: hostname keryf.hsopt.ru does not resolve to address 62.109.21.8: nodename nor servname provided, or not known
and nothing else.
How to fix this?

If you change both of those logging levels to debug, you get verbose logs like this:
Nov 1 10:46:20 mail.100greenwood.net postfix/postscreen[99398]: CONNECT from [10.0.1.2]:61560 to [10.0.1.240]:25
Nov 1 10:46:20 mail.100greenwood.net postfix/dnsblog[99400]: warning: dnsblog_query: lookup error for DNS query 2.1.0.10.zen.spamhaus.org: Host or domain name not found. Name service error for name=2.1.0.10.zen.spamhaus.org type=A: Host not found, try again
Nov 1 10:46:26 mail.100greenwood.net postfix/postscreen[99398]: PASS OLD [10.0.1.2]:61560
Nov 1 10:46:26 mail.100greenwood.net postfix/smtpd[99409]: connect from tim.100greenwood.net[10.0.1.2]
Nov 1 10:46:26 mail.100greenwood.net postfix/smtpd[99409]: DDEC11C2202: client=tim.100greenwood.net[10.0.1.2], sasl_method=DIGEST-MD5, sasl_username=timmcmanus
Nov 1 10:46:26 mail.100greenwood.net postfix/cleanup[99414]: DDEC11C2202: message-id=<[email protected]>
Nov 1 10:46:26 mail.100greenwood.net postfix/qmgr[4953]: DDEC11C2202: from=<[email protected]>, size=604, nrcpt=1 (queue active)
Nov 1 10:46:27 mail.100greenwood.net postfix/smtpd[99418]: connect from localhost[127.0.0.1]
Nov 1 10:46:27 mail.100greenwood.net postfix/smtpd[99418]: 1E39E1C2210: client=localhost[127.0.0.1]
Nov 1 10:46:27 mail.100greenwood.net postfix/cleanup[99414]: 1E39E1C2210: message-id=<[email protected]>
Nov 1 10:46:27 mail.100greenwood.net postfix/smtpd[99418]: disconnect from localhost[127.0.0.1]
Nov 1 10:46:27 mail.100greenwood.net postfix/qmgr[4953]: 1E39E1C2210: from=<[email protected]>, size=1059, nrcpt=1 (queue active)
Nov 1 10:46:27 mail.100greenwood.net postfix/smtp[99415]: DDEC11C2202: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.25, delays=0.03/0.04/0.01/0.17, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 1E39E1C2210)
Nov 1 10:46:27 mail.100greenwood.net postfix/qmgr[4953]: DDEC11C2202: removed
Nov 1 10:46:28 mail.100greenwood.net postfix/smtp[99419]: Untrusted TLS connection established to mx2.mail.icloud.com[17.172.34.12]:25: TLSv1 with cipher AES256-SHA (256/256 bits)
Nov 1 10:46:29 mail.100greenwood.net postfix/smtp[99419]: 1E39E1C2210: to=<[email protected]>, relay=mx2.mail.icloud.com[17.172.34.12]:25, delay=2.5, delays=0/0.02/0.89/1.6, dsn=2.5.0, status=sent (250 2.5.0 Ok, envelope id [email protected])
Nov 1 10:46:29 mail.100greenwood.net postfix/qmgr[4953]: 1E39E1C2210: removed
Nov 1 10:47:26 mail.100greenwood.net postfix/smtpd[99409]: disconnect from tim.100greenwood.net[10.0.1.2]
Nov 1 10:48:05 mail.100greenwood.net postfix/postscreen[99398]: CONNECT from [17.158.232.237]:36395 to [10.0.1.240]:25
Nov 1 10:48:11 mail.100greenwood.net postfix/postscreen[99398]: PASS NEW [17.158.232.237]:36395
Nov 1 10:48:12 mail.100greenwood.net postfix/smtpd[99409]: connect from nk11p03mm-asmtp002.mac.com[17.158.232.237]
Nov 1 10:48:12 mail.100greenwood.net postfix/smtpd[99409]: B49961C2275: client=nk11p03mm-asmtp002.mac.com[17.158.232.237]
Nov 1 10:48:12 mail.100greenwood.net postfix/cleanup[99514]: B49961C2275: message-id=<[email protected]>
Nov 1 10:48:12 mail.100greenwood.net postfix/qmgr[4953]: B49961C2275: from=<[email protected]>, size=1621, nrcpt=1 (queue active)
Nov 1 10:48:13 mail.100greenwood.net postfix/smtpd[99409]: disconnect from nk11p03mm-asmtp002.mac.com[17.158.232.237]
Nov 1 10:48:13 mail.100greenwood.net postfix/smtpd[99519]: connect from localhost[127.0.0.1]
Nov 1 10:48:13 mail.100greenwood.net postfix/smtpd[99519]: 690921C227F: client=localhost[127.0.0.1]
Nov 1 10:48:13 mail.100greenwood.net postfix/cleanup[99514]: 690921C227F: message-id=<[email protected]>
Nov 1 10:48:13 mail.100greenwood.net postfix/smtpd[99519]: disconnect from localhost[127.0.0.1]
Nov 1 10:48:13 mail.100greenwood.net postfix/qmgr[4953]: 690921C227F: from=<[email protected]>, size=2092, nrcpt=1 (queue active)
Nov 1 10:48:13 mail.100greenwood.net postfix/smtp[99515]: B49961C2275: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.84, delays=0.23/0.03/0.01/0.58, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 690921C227F)
Nov 1 10:48:13 mail.100greenwood.net postfix/qmgr[4953]: B49961C2275: removed
Nov 1 10:48:13 mail.100greenwood.net postfix/pipe[99521]: 690921C227F: to=<[email protected]>, orig_to=<[email protected]>, relay=dovecot, delay=0.13, delays=0/0.02/0/0.11, dsn=2.0.0, status=sent (delivered via dovecot service)
Nov 1 10:48:13 mail.100greenwood.net postfix/qmgr[4953]: 690921C227F: removed
Nov 1 10:48:38 mail.100greenwood.net postfix/postscreen[99398]: CONNECT from [10.0.1.2]:61574 to [10.0.1.240]:25
Nov 1 10:48:38 mail.100greenwood.net postfix/postscreen[99398]: PASS OLD [10.0.1.2]:61574
Nov 1 10:48:38 mail.100greenwood.net postfix/smtpd[99409]: connect from tim.100greenwood.net[10.0.1.2]
Nov 1 10:48:38 mail.100greenwood.net postfix/smtpd[99409]: A78C41C22A9: client=tim.100greenwood.net[10.0.1.2], sasl_method=DIGEST-MD5, sasl_username=timmcmanus
Nov 1 10:48:38 mail.100greenwood.net postfix/cleanup[99514]: A78C41C22A9: message-id=<[email protected]>
Nov 1 10:48:38 mail.100greenwood.net postfix/qmgr[4953]: A78C41C22A9: from=<[email protected]>, size=1053, nrcpt=1 (queue active)
Nov 1 10:48:38 mail.100greenwood.net postfix/smtpd[99519]: connect from localhost[127.0.0.1]
Nov 1 10:48:38 mail.100greenwood.net postfix/smtpd[99519]: D898A1C22BC: client=localhost[127.0.0.1]
Nov 1 10:48:38 mail.100greenwood.net postfix/cleanup[99514]: D898A1C22BC: message-id=<[email protected]>
Nov 1 10:48:38 mail.100greenwood.net postfix/smtpd[99519]: disconnect from localhost[127.0.0.1]
Nov 1 10:48:38 mail.100greenwood.net postfix/qmgr[4953]: D898A1C22BC: from=<[email protected]>, size=1508, nrcpt=1 (queue active)
Nov 1 10:48:38 mail.100greenwood.net postfix/smtp[99515]: A78C41C22A9: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.21, delays=0.01/0/0/0.2, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as D898A1C22BC)
Nov 1 10:48:38 mail.100greenwood.net postfix/qmgr[4953]: A78C41C22A9: removed
Nov 1 10:48:39 mail.100greenwood.net postfix/smtp[99560]: Untrusted TLS connection established to mx5.mail.icloud.com[17.172.34.68]:25: TLSv1 with cipher AES256-SHA (256/256 bits)
Nov 1 10:48:40 mail.100greenwood.net postfix/smtp[99560]: D898A1C22BC: to=<[email protected]>, relay=mx5.mail.icloud.com[17.172.34.68]:25, delay=1.1, delays=0/0.03/0.24/0.87, dsn=2.5.0, status=sent (250 2.5.0 Ok, envelope id [email protected])
Nov 1 10:48:40 mail.100greenwood.net postfix/qmgr[4953]: D898A1C22BC: removed
This is an exchange between my Server 4.0 mail server and Apple's iCloud mail servers.
Logs can be found in the Server 4.0 app in the following screen shot:

SMTP delay in Postfix

Similar Messages

Maybe you are looking for