Mail Piling Up In Queue

Seem to be having a few problems and I'm not sure if they're separate issues or connected ones. Seems I need to get my "mail" house in order, but don't know where to start; I'm pretty new server admin. Had the mail server sending and receiving mail, but it just stopped one day. Not sure if it was an update I made, or something I didn't update and should be doing.
1. need to update ClamAV? currently running 0.88.5, recommended 0.88.7
2. amavisd problem?
Dec 26 19:08:09 my.server.com /usr/bin/amavisd[18292]: starting. /usr/bin/amavisd at my.server.com amavisd-new-2.2.0 (20041102), Unicode aware
Dec 26 19:08:09 my.server.com /usr/bin/amavisd[18292]: user=, EUID: 0 (0); group=, EGID: 0 0 (0 0)
Dec 26 19:08:09 my.server.com /usr/bin/amavisd[18292]: Perl version 5.008006
Dec 26 19:08:09 my.server.com /usr/bin/amavisd[18292]: Net::Server: 2006/12/26-19:08:09 Couldn't open pid file "/var/amavis/amavisd.pid" [No such file or directory].\n\n at line 268 in file /System/Library/Perl/Extras/5.8.6/Net/Server.pm
Dec 26 19:08:09 my.server.com /usr/bin/amavisd[18292]: Net::Server: 2006/12/26-19:08:09 Server closing!
3. postfix problem? SMTP log:
Dec 26 20:47:18 server postfix/qmgr[18228]: F07D886C68: to=<[email protected]>, relay=none, delay=334187, status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: Connection refused)
Dec 26 20:47:42 server postfix/smtp[19389]: connect to mx.futurequest.net[69.5.6.174]: Operation timed out (port 25)
Some not sure why the local host 127.0.0.1 rejects mail to a user I've set up in Workgroup Manager. (First log entry above)
I've got some dozens of messages that aren't getting through to me that I would like to read, but can't get delivered.
Don't get much spam yet, but the second log entry is a typical one. How do I prevent spam from building up in the queue, since most are sent to users/email accounts that aren't real? All I've done so far is in: Mail > Settings > Relay "Refuse all messages from these hosts and networks".
4. Have server set-up as an open directory master, but something must be funny, since I keep getting this message:
Dec 26 20:44:11 my.server.com kadmin.local[19356](info): No dictionary file specified, continuing without one.
For some reason, access for users I've defined in Workgroup Manager sequentially get dropped. It's easy to re-click "access account" for each user, but this isn't a solution!
Any help would be much appreciated, since I feel like I'm shooting in the dark on many of these issues. If nothing else, please point me in the right direction or post a link so I can study and learn.
Thank you =)

Hi Dale,
Thanks for the post. If I did delete or change something related to amavisd-new (since amavisd doesn't appear to be there), how would I get it back?
Might also be helpful for you all to know that I did install HenWen months ago, but didn't have much luck getting the software to work as desired. I haven't been using it, since it (esp. snort) did weird things to my system (using 100% processing power at times for no particular reason that I could identify). Perhaps the software tricked something out? Wish I knew. For more basic overview of HenWen see: http://seiryu.home.comcast.net/henwen.html
sigh
Here are the results of the unix commands listed:
One:
ls -lsa /private/var
total 0
0 drwxr-xr-x 30 root wheel 1020 Dec 24 23:05 .
0 drwxr-xr-x 6 root wheel 204 Dec 24 23:05 ..
0 drwxr-xr-x 5 daemon wheel 170 Oct 22 2005 at
0 drwxr-x--- 2 root admin 68 Oct 19 2005 audit
0 drwx------ 3 root wheel 102 Aug 10 03:15 backups
0 drwxr-xr-x 6 clamav clamav 204 Dec 28 19:23 clamav
0 drwxr-xr-x 3 root wheel 102 Aug 22 2005 cron
0 drwxr-xr-x 31 root wheel 1054 Dec 28 19:13 db
0 drwxr-xr-x 2 root sys 68 Aug 22 2005 empty
0 drwxr-xr-x 16 cyrusima mail 544 Dec 28 19:23 imap
0 drwxr-x--- 6 jabber jabber 204 Aug 22 2005 jabber
0 drwxr-xr-x 3 root wheel 102 Sep 29 14:22 launchd
0 drwxr-xr-x 101 root wheel 3434 Dec 28 03:15 log
0 drwxrwxr-x 2 root mail 68 Aug 22 2005 mail
0 drwxrwsr-x 9 root mailman 306 Aug 22 2005 mailman
0 drwxr-xr-x 2 root wheel 68 Aug 22 2005 msgs
0 drwxr-xr-x 9 root wheel 306 Dec 26 18:27 named
0 drwxr-xr-x 2 root wheel 68 Aug 22 2005 netboot
0 drwxr-x--- 7 root wheel 238 Dec 27 19:12 root
0 drwxrwxr-x 55 root daemon 1870 Dec 28 19:12 run
0 drwxr-xr-x 2 root wheel 68 Aug 22 2005 rwho
0 drwxr-xr-x 18 root wheel 612 Sep 19 20:44 samba
0 drwxr-xr-x 30 root wheel 1020 Aug 9 21:53 servermgrd
0 drwxr-xr-x 8 root wheel 272 Aug 5 19:31 spool
0 drwxr-xr-x 2 root wheel 68 Aug 24 2005 swupd
0 drwxrwxrwt 15 root wheel 510 Dec 24 23:05 tmp
0 drwxr-x--- 2 clamav clamav 68 Aug 22 2005 virusmails
0 drwxr-xr-x 4 root wheel 136 Dec 24 23:05 vm
0 drwxr-xr-x 4 root wheel 136 Oct 20 2005 xgrid
0 drwxr-xr-x 4 root wheel 136 Oct 19 2005 yp
Two:
ls -lsa /private/var/amavis
ls: /private/var/amavis: No such file or directory
(certainly could be the problem—above)
Three:
ls -lsa /private/var/clamav
total 16368
0 drwxr-xr-x 6 clamav clamav 204 Dec 28 19:23 .
0 drwxr-xr-x 30 root wheel 1020 Dec 24 23:05 ..
0 drwx------ 4 clamav clamav 136 Oct 2 01:00 .spamassassin
2832 -rw-r--r-- 1 clamav clamav 1447910 Dec 28 19:07 daily.cvd
8 -rw-rw---- 1 clamav clamav 4 Dec 28 19:23 freshclam.pid
13528 -rw-r--r-- 1 clamav clamav 6924820 Dec 26 19:07 main.cvd
Best wishes and thanks

Similar Messages

  • HELP! Mail stuck in the queue.

    Hey All,
    We just noticed that none of us here recieved any mail today and that all of our messages incoming/outgoing have been stuck in the queue all day.
    We seem to be able to view old messages with our mail clients as well as any folders. But any new messages that we send or recieve just go to the server and sit there.
    It's quite puzzeling because we haven't changed anything on it, the server has just been quietly humming along for a while now.
    However, this seems to have started happening after we restarted the box this morning because a web app we were building on it ended up in an infinite loop.
    I tried re-starting the box, restarting the mail service, resending the queue and nothing, messages hit the queue and fail to be delivered to mailboxes.
    Looking at my logs I saw this:
    Nov 9 16:56:28 resserver imap[4733]: DBERROR: critical database situation
    Nov 9 17:00:07 resserver imap[4833]: DBERROR: critical database situation
    Nov 9 17:15:56 resserver reconstruct[5700]: DBERROR: critical database situation
    Nov 9 17:16:02 resserver reconstruct[5726]: DBERROR: critical database situation
    In the queue some messages say this at the end:
    host 127.0.0.1[127.0.0.1] said: 421 4.3.2 Service shutting down, closing channel (in reply to end of DATA command
    Looking in my resources and in other places on the forums I've tried the following so far in hopes to narrow down and fix the problem:
    - rebuilt with mailbfr (as per petrobytes suggestion with someone else)
    - turned on and off content filtering
    - confirmed that the machine has the same IP
    - confirmed that it resolves forward and backward to it's hostname/IP
    I can post any conf files you need, I'm desperate to get this fixed! Any help or insight anyone could provide would be well appreciated!
    eMac, iBook, iMac, xServe, PowerBook   Mac OS X (10.4.3)  

    I'm noticing some interesting stuff happening in the logs can someone make sense of this?
    solutionim.com /usr/bin/amavisd[7872]: (07872-01) Requesting process rundown after fatal error
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7872]: (07872-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 2 results at (eval 41) line 150.
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T184715-07873
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) TIMING [total 350 ms] - SMTP EHLO: 23 (7%), SMTP pre-MAIL: 2 (1%), mkdir tempdir: 1 (0%), create email.txt: 2 (0%), SMTP pre-DATA-flush: 9 (3%), SMTP DATA: 9 (3%), body_hash: 3 (1%), mkdir parts: 3 (1%), mime_decode: 72 (21%), rundown: 226 (65%)
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 568.
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) Requesting process rundown after fatal error
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) ESMTP::10024 /var/amavis/amavis-20061109T184715-07876: <[email protected]> -> <[email protected]> Received: SIZE=50687 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07876-01 for <[email protected]>; Thu, 9 Nov 2006 18:47:15 -0500 (EST)
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) Checking: [216.46.146.115] <[email protected]> -> <[email protected]>
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p004 1 Content-Type: multipart/mixed
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p005 1/1 Content-Type: multipart/alternative
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p001 1/1/1 Content-Type: text/plain, size: 259 B, name:
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p002 1/1/2 Content-Type: text/html, size: 2227 B, name:
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p003 1/2 Content-Type: application/vnd.ms-excel, size: 33280 B, name: Emploment Application.xls
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7879]: (07876-01) run_command: child process [7879]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7879]: (07876-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T184715-07876
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 3 results at (eval 41) line 150.
    Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T184715-07876
    Nov 9 18:47:16 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) TIMING [total 366 ms] - SMTP EHLO: 24 (7%), SMTP pre-MAIL: 3 (1%), mkdir tempdir: 2 (0%), create email.txt: 2 (1%), SMTP pre-DATA-flush: 25 (7%), SMTP DATA: 31 (8%), body_hash: 3 (1%), mkdir parts: 3 (1%), mime_decode: 95 (26%), rundown: 178 (49%)
    Nov 9 18:47:16 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 771.
    Nov 9 18:47:16 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) Requesting process rundown after fatal error
    Nov 9 18:47:16 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
    Nov 9 18:48:33 resserver.resolutionim.com /usr/bin/amavisd[7759]: Net::Server: 2006/11/09-18:48:33 Server closing!
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: starting. /usr/bin/amavisd at resserver.resolutionim.com amavisd-new-2.2.0 (20041102), Unicode aware
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: user=, EUID: 0 (0); group=, EGID: 0 0 (0 0)
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Perl version 5.008006
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: 2006/11/09-18:48:36 Amavis (type Net::Server::PreForkSimple) starting! pid(7927)
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: Binding to UNIX socket file /var/amavis/amavisd.sock using SOCK_STREAM
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: Binding to TCP port 10024 on host 127.0.0.1
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: Setting gid to "82 82"
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: Setting uid to "82"
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Amavis::Conf 2.033
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Archive::Tar 1.22
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Archive::Zip 1.14
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Compress::Zlib 1.33
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Convert::TNEF 0.17
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Convert::UUlib 1.03
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module DB_File 1.810
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module MIME::Entity 5.416
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module MIME::Parser 5.416
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module MIME::Tools 5.416
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Mail::Header 1.65
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Mail::Internet 1.65
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Mail::SpamAssassin 3.001005
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Net::Cmd 2.26
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Net::DNS 0.58
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Net::SMTP 2.29
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Net::Server 0.94
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Time::HiRes 1.65
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Unix::Syslog 0.99
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Amavis::DB code NOT loaded
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Amavis::Cache code NOT loaded
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Lookup::SQL code NOT loaded
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Lookup::LDAP code NOT loaded
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: AMCL-in protocol code loaded
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: SMTP-in protocol code loaded
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: ANTI-VIRUS code loaded
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: ANTI-SPAM code loaded
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Unpackers code loaded
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $file at /usr/bin/file
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $arc, not using it
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $gzip at /usr/bin/gzip
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $bzip2 at /usr/bin/bzip2
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $lzop, not using it
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $lha, not using it
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $unarj, not using it
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $uncompress at /usr/bin/uncompress
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $unfreeze, not using it
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $unrar, not using it
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $zoo, not using it
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $cpio at /usr/bin/cpio
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $ar, not using it
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $rpm2cpio, not using it
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $cabextract, not using it
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $dspam, not using it
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found secondary av scanner Clam Antivirus - clamscan at /usr/bin/clamscan
    Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: SpamControl: initializing Mail::SpamAssassin
    Nov 9 18:48:44 resserver.resolutionim.com /usr/bin/amavisd[7927]: SpamControl: done
    SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 350.
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9584]: (09584-01) Requesting process rundown after fatal error
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9584]: (09584-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) ESMTP::10024 /var/amavis/amavis-20061109T194144-09586: <[email protected]> -> <[email protected]>,<[email protected]> Received: SIZE=236428 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09586-01; Thu, 9 Nov 2006 19:41:44 -0500 (EST)
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) Checking: [192.168.1.121] <[email protected]> -> <[email protected]>,<[email protected]>
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) ESMTP::10024 /var/amavis/amavis-20061109T194144-09587: <[email protected]> -> <[email protected]> Received: SIZE=2799147 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09587-01 for <[email protected]>; Thu, 9 Nov 2006 19:41:44 -0500 (EST)
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p008 1 Content-Type: multipart/alternative
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p001 1/1 Content-Type: text/plain, size: 1103 B, name:
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p009 1/2 Content-Type: multipart/mixed
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p002 1/2/1 Content-Type: text/html, size: 4971 B, name:
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p003 1/2/2 Content-Type: application/vnd.ms-excel, size: 16384 B, name: Feed Locations.xls
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p004 1/2/3 Content-Type: application/octet-stream, size: 15355 B, name: Example of Feed Locations.pdf
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p005 1/2/4 Content-Type: image/jpeg, size: 68882 B, name: zurlftoct06.JPG
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p006 1/2/5 Content-Type: image/jpeg, size: 65599 B, name: extrrtlondsoct06.JPG
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p007 1/2/6 Content-Type: text/html, size: 184 B, name:
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9588]: (09586-01) run_command: child process [9588]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9588]: (09586-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T194144-09586
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 7 results at (eval 41) line 150.
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T194144-09586
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) TIMING [total 435 ms] - SMTP EHLO: 22 (5%), SMTP pre-MAIL: 3 (1%), mkdir tempdir: 1 (0%), create email.txt: 2 (0%), SMTP pre-DATA-flush: 10 (2%), SMTP DATA: 45 (10%), body_hash: 6 (1%), mkdir parts: 3 (1%), mime_decode: 158 (36%), rundown: 185 (42%)
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 3144.
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) Requesting process rundown after fatal error
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) ESMTP::10024 /var/amavis/amavis-20061109T194144-09589: <[email protected]> -> <[email protected]> Received: SIZE=2244 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09589-01 for <[email protected]>; Thu, 9 Nov 2006 19:41:44 -0500 (EST)
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) Checking: [65.54.246.141] <[email protected]> -> <[email protected]>
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) p001 1 Content-Type: text/plain, size: 1084 B, name:
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9590]: (09589-01) run_command: child process [9590]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
    Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9590]: (09589-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T194144-09589
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 1 results at (eval 41) line 150.
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T194144-09589
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) TIMING [total 240 ms] - SMTP EHLO: 19 (8%), SMTP pre-MAIL: 2 (1%), mkdir tempdir: 1 (1%), create email.txt: 2 (1%), SMTP pre-DATA-flush: 8 (3%), SMTP DATA: 2 (1%), body_hash: 2 (1%), mkdir parts: 3 (1%), mime_decode: 36 (15%), rundown: 165 (69%)
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 67.
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) Requesting process rundown after fatal error
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9591]: (09591-01) ESMTP::10024 /var/amavis/amavis-20061109T194145-09591: <[email protected]> -> <[email protected]> Received: SIZE=2799145 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09591-01 for <[email protected]>; Thu, 9 Nov 2006 19:41:45 -0500 (EST)
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) Checking: [65.54.246.171] <[email protected]> -> <[email protected]>
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9591]: (09591-01) Checking: [65.54.246.173] <[email protected]> -> <[email protected]>
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) p003 1 Content-Type: multipart/mixed
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) p001 1/1 Content-Type: text/html, size: 6064 B, name:
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) p002 1/2 Content-Type: video/x-ms-wmv, size: 2025860 B, name: JBSklip.wmv
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9592]: (09587-01) run_command: child process [9592]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
    Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9592]: (09587-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T194144-09587
    Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 2 results at (eval 41) line 150.
    Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T194144-09587
    Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) TIMING [total 1950 ms] - SMTP EHLO: 22 (1%), SMTP pre-MAIL: 4 (0%), mkdir tempdir: 1 (0%), create email.txt: 2 (0%), SMTP pre-DATA-flush: 9 (0%), SMTP DATA: 868 (44%), body_hash: 34 (2%), mkdir parts: 3 (0%), mime_decode: 610 (31%), rundown: 397 (20%)
    Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) ESMTP::10024 /var/amavis/amavis-20061109T194146-09587: <[email protected]> -> <[email protected]> Received: SIZE=14124 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09587-02 for <[email protected]>; Thu, 9 Nov 2006 19:41:46 -0500 (EST)
    Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) Checking: [64.233.166.181] <[email protected]> -> <[email protected]>
    Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) p003 1 Content-Type: multipart/alternative
    Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) p001 1/1 Content-Type: text/plain, size: 2089 B, name:
    Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) p002 1/2 Content-Type: text/html, size: 9454 B, name:
    Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9593]: (09587-02) run_command: child process [9593]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
    Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9593]: (09587-02) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T194146-09587

  • Can I cancel mail job from SOST queue and make its status to be error or red

    Do you have any idea to cancel mail job from SOST queue and make its status to be error or red (msgno = 806) by using coding ??

    veekwall wrote:
    Hi,
    I recently (over this past summer) updated my phone and plan with Verizon.  I'm from Pittsburgh, Pennsylvania, and I got the phone in Pittsburgh.  It is a Droid Eris and very nice.  I got it and a month later I moved to Olympia, Washington for school.  Since moving there, I have hardly been able to use it.  The service is terrible and its been impossible to keep in touch with my family, I wasn't even able to call them over Thanksgiving.  I'm also having to pay extra money so I can use the internet on my phone, but I can't even access the internet let alone make phone calls.  It's really frustrating.  I can't use my phone to keep in touch with everyone in Pittsburgh-and if I am ever in trouble I wouldn't be able to call for help, which makes me really nervous.  Is there a way I can cancel my 2yr contract?  Yes.  Just visit a Verizon store, or dial *611 from your phone and let them know you would like to cancel your account.  Would I have to pay a fee-and how much would that cost? Yes, Verizon no longer waives ETFs due to moving to an area without service, so you will probably have to pay an Early Termination Fee.  Since you have a smartphone, it will probably be $350 less $10 for each month of service you have completed.  The Customer Service rep you contact about cancelling will be able to tell you the exact amount.  Would I have to go to the Verizon store I bought the phone from to do this or would I have to do this in Washington-where I am now living and having the problems? You can do it over the phone, or at a corporate Verizon store.  Help!
    -Victoria

  • PLEASE HELP!1000s of e-mails piling up.When trying to find out if previous question had been answered I clicked on notifications-took me to list of e-mail options.Clicked yes on 1

    PLEASE HELP!  1000s of e-mails piling up.When trying to check responses to previous question, clicked on something in notifications to get responses in e-mail.Since then I''m inundated.Tried Stop E-mail notifications, buut doesn't help.  Please tell me what to do.

    Did you turn off all email notifications as the second tutorial describes?
    If you turned them all off and are still getting notifications, what do you see when you try to turn them off again? Has your account been reset to continue recieving the notifications? Or is is still set to off?
    Let us know.

  • I did SMTP server configuration but the mails arestill queued.that means all the mails are going into queue folder.

    If you see the last command line that saying queued for delivery. what are the causes for this.
    Please tell me its urgent.
    -thanks
    Swapnil

    Hello Swapnil,
    Navigate to your queue folder and refresh it.
    If problem still persists, kindly restart your SMTP server.
    -Hatim

  • Incoming EVT mails are in the queued Siebel folder

    Hi anyone,
    Currently we have issue with 6000 files got strucked in evt format at email's Queued folder.
    Refered document:- https://support.oracle.com/epmos/faces/DocumentDisplay?id=946166.1
    Take the backup of all the unprocessed evt files, converted to .error and then copy the .error files back in to the same directory. All the .error files got re-processed.
    Thanks
    Ruban

    Hi,
    From your description, I recommend you use the Test-ServiceHealth cmdlet to check if all the Windows services that Exchange server requires have started. Especially Exchange Transport service and Mailbox transport service.
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Status=Deferred (temporary failure) with mail stuck in queue

    Adding the "domainname.com" (as in [email protected]) to local host aliases solved the "Mail loops back to myself" bounce message.
    At least mail is being received, but...
    now is piling up in queue.
    I've already tried restarting the queue, no change.
    [SMTP LOG]
    May 5 12:39:31 alpha postfix/pipe[22148]: 1F5A09C1B9: to=<[email protected]>, relay=cyrus, delay=2, status=deferred (temporary failure)
    [MAIL ACCESS LOG]
    May 5 13:06:00 alpha lmtpunix[22527]: AOD: user opts: looking up user record: rbird
    May 5 13:06:00 alpha lmtpunix[22527]: AOD: getting mail attribute for user: rbird
    May 5 13:06:00 alpha lmtpunix[22527]: AOD: mail enabled
    May 5 13:06:00 alpha lmtpunix[22527]: AOD: mbrcheck_servicemembership with accessallservices
    May 5 13:06:00 alpha lmtpunix[22527]: AOD: mail service ACL NOT enabled
    May 5 13:06:00 alpha lmtpunix[22527]: couldn't create stage directory: /var/spool/imap/stage./: File exists
    May 5 13:06:00 alpha lmtpunix[22527]: IOERROR: creating message file /var/spool/imap/stage./22527-1146848760-0: File exists

    Problem solved. It was the finder copy of the mailbfr files from the old server to the new server before I issued the mailbfr restore command.
    I restored an older backup of the database that was already on the SUPERDUPER image, and everything is working now.
    Today's lesson.. Do not use FINDER copy to move mailbfr backups from one machine to another.
    Mike

  • Any way to clear the Mail Queue Completely?

    So it seems my SMTP service was hacked over the weekend, with someone deciding to use my server to send a whole lot of mail. I've shut down the service and locked down the security hole, but now I have a lot of mail sitting in the queue and it is taking hours to clear it all out by using the Maintenance tab. Is there a quicker, easier way to clear the queue?

    Hi
    Rather than using Server Admin it's generally agree to use the command line instead.
    sudo mailq
    This command flushes the mail queue
    sudo postfix flush
    To re-queue the mail queue
    sudo postsuper -r ALL
    Command to see what's in the mail queue
    sudo postqueue -p
    Command to delete everything in the mail queue
    sudo postsuper -d ALL
    If you've got lots in there it will take some time. You might benefit by stopping the mail service first:
    sudo serveradmin stop mail
    Use this command to restart the service afterwards:
    sudo serveradmin start mail
    If you've got a lot of mail in there it will take the time it takes. You will need some patience. This link discusses how you can secure your mail server:
    http://osx.topicdesk.com/content/view/38/41/
    Some friendly advice. Secure your server further by placing it behind a firewall. Only open ports required by the Mail Service. If you have to open ssh secure it by using ssh-keygens and disable sshd passwords. Beef up all your passwords.
    My 2p.
    Tony

  • Lot of SPAM mails in queue - Warnings from ISP

    Hi Jay,Shane and ALL,
    We are running messaging on Solaris 10 with below version.
    Sun Java(tm) System Messaging Server 6.2-7.05 (built Sep 5 2006)
    libimta.so 6.2-7.05 (built 12:18:44, Sep 5 2006)
    Insured that no entries added to mappings (except localhost) and only "authenticated SMTP" allowed.
    We implemented Separate AV/anti-spam box with aliasdetour and conversion channel which is working fine.
    we could achieve >95% spam control but recently we started receiving warnings from ISP that SPAM being sent out from our mail server.
    ++++++++Part of mail sent by ISP+++++++++
    Data received in complaint:
    Return-Path: <x>
    Delivered-To: x
    Received: from webmail.<our-domain>.com (our_mail_server_IP) by mail.iecc.com with SMTP;
    7 Sep 2007 03:29:00 -0000
    Received: from User ([210.70.82.129]) by webmail.<our-domain>.com (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTPA id <x> for x; Thu,
    06 Sep 2007 20:45:43 -0400 (EDT)
    Date: Fri, 07 Sep 2007 08:47:54 +0800
    From: Bank of America <x>
    Subject: Account Information Update.
    To: Undisclosed recipients: ;
    Reply-to: x
    Message-id: <x>
    MIME-version: 1.0
    X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
    X-Mailer: Microsoft Outlook Express 6.00.2600.0000
    X-Priority: 1
    X-MSMail-priority: High
    X-DCC-IECC-Metrics: tom.iecc.com 1107;
    bulk Body=154 Fuz1=154 Fuz2#X-Tag: tagged by DCC
    Content-Type: text/plain
    Content-Transfer-Encoding: 8bit
    ++++++++++++end-of-part-mail-sent-by-ISP++++++++++++
    I noticed around 10K SPAM mails getting generated (added) daily in tcp_local channel queue.
    +++++++++a mail in queue++++++++++
    qm.maint> read 3000
    Message id: 3000
    Filename: /iplanet/SUNWmsgsr/data/queue/tcp_local/017/ZWf0I3dFTzue9.00
    Transport layer information:
    Envelope From: address: [email protected]
    Envelope To: addresses: [email protected]
    Message header:
    Received: from User ([203.144.16.210])
    by webmail.<our_domain>.com (Sun Java System Messaging Server 6.2-7.05 (built Sep
    5 2006)) with ESMTPA id <0JO300B5LSZDBK10@webmail.<our_domain>.com> for
    [email protected]; Sun, 09 Sep 2007 09:47:45 -0400 (EDT)
    Date: Sun, 09 Sep 2007 23:49:59 +1000
    From: Bank Of America <[email protected]>
    Subject: Account Information Update Urgently Needed
    To: Undisclosed recipients: ;
    Reply-to: [email protected]
    Message-id: <0JO300B5MSZFBK10@webmail.<our_domain>.com>
    MIME-version: 1.0
    X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
    X-Mailer: Microsoft Outlook Express 6.00.2600.0000
    Content-type: text/html; charset=Windows-1251
    Content-transfer-encoding: 7BIT
    X-Priority: 3
    X-MSMail-priority: Normal
    qm.maint>
    ++++++++++++++++++++end-of-mail-in-queue++++++++++++++++++++
    Wondering how these mails exist in tcp_local queue wherein none of IPs (or users) allowed to relay through our servers.
    Pl help me resolve this issue.
    TIA
    Prvn

    Thanks Shane.
    Pl find my below answers:
    Hi,
    You need to track down the source of the emails by
    locating the relevant mail.log lines that correspond
    to the email delivery attempt. This will at least
    tell you how they are getting in (whether the email
    is coming in via the
    tcp_local/tcp_auth/tcp_submit/tcp_intranet channel
    etc.).07-Sep-2007 19:13:44.02 tcp_auth tcp_local EA 3 [email protected] rfc822;[email protected] [email protected] User ([210.70.82.129])
    08-Sep-2007 16:21:44.38 tcp_auth tcp_local EA 1 [email protected] rfc822;[email protected] [email protected] User ([203.144.16.210])
    >
    From there you can determine (if you have enough
    logging enabled such as LOG_USERNAME=1,
    LOG_CONNECTION=1, LOG_MESSAGE_ID=1) why they emails
    are being allowed through... After enabling the three parameters (option.dat and did cnbuild/restart),
    i noticed lot of such entries in mail.log_current:
    10-Sep-2007 00:04:28.59 tcp_local Q 2 [email protected] rfc822;[email protected] [email protected] <0JO400CPG2A15F00@webmail.<our-domain>.com> *admin@<our-domain>.com mailin.binghamton.edu dns;mailin.binghamton.edu (TCP|192.168.1.41|34548|128.226.7.23|25) (mail2.binghamton.edu ESMTP [7e5e6797de0c707331914caad1b54f2f]) smtp;450 <[email protected]>: Sender address rejected: Domain not found [email protected]: smtp;450 <alert@bancamerica.
    I have seen cases of:
    -> Incorrect mapping rules (so tcp_local->tcp_local
    relaying was broken)
    -> Overly large 'internal' IP mappings (so
    tcp_intranet was the source channel)My Mappings file:
    +++++
    ! MTA mappings file
    ! for access control and other table lookups
    PORT_ACCESS
    *|*|*|*|* $C$|INTERNAL_IP;$3|$Y$E
    * $YEXTERNAL
    INTERNAL_IP
    $(192.168.1.41/32) $Y
    127.0.0.1 $Y
    * $N
    ORIG_SEND_ACCESS
    tcp_local|*|tcp_local|* $N$D30|Relaying$ not$ allowed
    tcp_*|*|native|* $N
    tcp_*|*|hold|* $N
    tcp_*|*|pipe|* $N
    tcp_*|*|ims-ms|* $N
    ! Block "external" submissions of explicitly source-routed "internal" addresses
    tcp_local|*|tcp_intranet|@*:*.* $N$D30|Explicit$ routing$ not$ allowed
    tcp_local|*|tcp_intranet|*$%*@* $N$D30|Explicit$ routing$ not$ allowed
    tcp_local|*|tcp_intranet|*.*!*@* $N$D30|Explicit$ routing$ not$ allowed
    tcp_local|*|tcp_intranet|"*@*"@* $N$D30|Explicit$ routing$ not$ allowed
    SEND_ACCESS
    tcp_*|*|*|*@[127.*] $X5.1.2|$NBad$ destination$ system
    tcp_*|*|*|*@localhost.* $X5.1.2|$NBad$ destination$ system
    tcp_*|*|*|*@example.com $X5.1.2|$NBad$ destination$ system
    tcp_*|*|*|*@example.net $X5.1.2|$NBad$ destination$ system
    tcp_*|*|*|*@example.org $X5.1.2|$NBad$ destination$ system
    tcp_*|*|*|*@*.test $X5.1.2|$NBad$ destination$ system
    tcp_*|*|*|*@*.example $X5.1.2|$NBad$ destination$ system
    tcp_*|*|*|*@*.invalid $X5.1.2|$NBad$ destination$ system
    tcp_*|*|*|*@*.localhost $X5.1.2|$NBad$ destination$ system
    <IMTA_TABLE:mappings.locale
    NOSCAN_IP
    $(192.168.1.49/32) $Y$E
    * $N
    CONVERSIONS
    IN-CHAN=tcp_noscan;OUT-CHAN=*;CONVERT No
    IN-CHAN=tcp_local;OUT-CHAN=tcp_intranet;CONVERT No
    IN-CHAN=tcp_*;OUT-CHAN=*;CONVERT Yes,Channel=tcp_scan
    ++++++++
    -> A users username/password being hacked so
    authenticated delivery was being used (tcp_auth was
    the source channel with the same username each time)i will see this option but if somebody gets authenticated, i should see in logs?
    Pls help me on this.....
    Thanks
    Prvn

  • Both Incoming and Outgoing Mail Stuck in Queue

    Hi, I have an issue with a new install of OS X 10.5.8 Mail Server. It queues everything and won't let anything in or out. I feel like I must have missed something setting it up, but I followed the PDF pretty much step by step.
    Does anyone have any tips or tricks to getting a new mail server running correctly?

    Does anyone have any tips or tricks to getting a new mail server running correctly?
    Yes. Read the logs.
    There are approximately 2 gazllion and seven reasons why mail might not pass through the server and get queued. The logs should shed some light on the problem and narrow down the focus.

  • Tiger Server Outgoing Mail Stuck In Queue

    We are running Tiger Server 10.4.7 at our small school. All our incoming mail is suspended in queue. Our outgoing mail is just fine.
    I looked in the mail log and it shows a zillion:
    postfix/local[3144]: fatal: main.cf configuration error: mailboxsizelimit is smaller than messagesizelimit
    We have no limit set on the size of messages that can be received...so what gives? In Workgroup manager we have 0 set in mail quota for everyone. From serveradmin/maintenance/mail queue I tried to resend..but to no avail. Anyone have an idea of how to get the incoming mail flowing?
    John
    MacBook Pro   Mac OS X (10.4.7)  

    Here it is
    alias_maps = hash:/etc/aliases
    always_bcc = [email protected]
    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
    inet_interfaces = all
    luser_relay = jpage
    mail_owner = postfix
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    mapsrbldomains = bl.spamcop.net,sbl.spamhaus.org,cbl.abuseat.org,relays.ordb.org,dun.dnsrbl.net, spam.dnsrbl.net,list.dsbl.org,dnsbl.njabl.org,pm.blitzed.org,xbl.spamhaus.org,wi ll-spam-for-food.eu.org,bl.spamcannibal.org,sbl-xbl.spamhaus.org
    messagesizelimit = 104857600
    mydestination = $myhostname,localhost.$mydomain
    mydomain_fallback = localhost
    myhostname = mehermontessori.org
    mynetworks = 127.0.0.1/32,24.205.128.85,63.193.132.13,63.193.132.9,63.193.132.10
    mynetworks_style = host
    newaliases_path = /usr/bin/newaliases
    ownerrequestspecial = no
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    recipient_delimiter = +
    relayhost =
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = postdrop
    smtpdclientrestrictions = permit_mynetworks rejectrblclient bl.spamcop.net rejectrblclient sbl.spamhaus.org rejectrblclient cbl.abuseat.org rejectrblclient relays.ordb.org rejectrblclient dun.dnsrbl.net rejectrblclient spam.dnsrbl.net rejectrblclient list.dsbl.org rejectrblclient dnsbl.njabl.org rejectrblclient pm.blitzed.org rejectrblclient xbl.spamhaus.org rejectrblclient will-spam-for-food.eu.org rejectrblclient bl.spamcannibal.org rejectrblclient sbl-xbl.spamhaus.org hash:/etc/postfix/smtpdreject permit
    smtpdenforcetls = no
    smtpdpw_server_securityoptions = cram-md5
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpdtls_certfile = /etc/postfix/server.pem
    smtpdtlsloglevel = 0
    smtpduse_pwserver = yes
    smtpdusetls = no
    unknownlocal_recipient_rejectcode = 550

  • Establish mail flow from Exchange 2007 to Exchange 2013

    I am currently using Exchange 2007 into three sites in three cities and two of the sites are connected to Internet sending and receiving emails via Edge transport servers.
    Now I am planning to upgrade to exchange 2013 CU1. I don't find any documentation on how to establish mail flow between Exchange 2007 and Exchange 2013. Will it be automatic or do i need to create specific connectors between them?

    Was this question answered.  We're in the same situation now as we're upgrading to Exchange 2013 from 2007. The latest CU certainly helped.   Initially the test mailboxes on Exchange 2013 couldn't email each other - This was resolved with CU7 and
    using "Custom Settings" - manually entered IPs for DNS in the Exchange  Admin Center "DNS Lookups".
    Issue at the moment Test mailboxes on Exchange 2013 cannot email mailboxes on 2007 or visa-versa and mail from external sources queues on the 2007 box.  
    Any assistance will be greatly appreciated.  

  • [Solved] postfix local mail delivery fails

    Hi Guys,
    on my home pc i use postfix (gmail as a smtp relay) and fetchmail for sending/receiving mails, this works very well, however sending a mail to a local user fails, I'm lost here and need your help guys.
    if i send a mail like :
    $>echo "Test" | mail -s "Test : local mail delivery" "andy"
    The mail stays in the queue for ever...
    $>mailq
    -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
    CC82513BCA* 455 Sun Aug 3 09:53:09 [email protected]
    [email protected]
    Sending to external addresses works without any problems.
    Here some important info/config files :
    $>whoami
    andy
    $>hostname
    box
    $>cat /etc/host.conf
    # /etc/hosts
    #<ip-address> <hostname.domain.org> <hostname>
    127.0.0.1 localhost.localdomain localhost box
    ::1 localhost.localdomain localhost
    192.168.1.3 lbox.localdomain lbox
    $>cat /etc/postfix/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 = /var/spool/postfix
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    command_directory = /usr/bin
    # 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/lib/postfix
    # The data_directory parameter specifies the location of Postfix-writable
    # data files (caches, random numbers). This directory must be owned
    # by the mail_owner account (see below).
    data_directory = /var/lib/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
    #myhostname = mail.example.com
    myhostname = localhost.localdomain
    # 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
    mydomain = localdomain
    # 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
    inet_interfaces = 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
    #mydestination = localhost, localhost.localdomain
    # 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 $pr/oxy_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]
    relayhost = [smtp.gmail.com]
    # 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
    alias_maps = hash:/etc/postfix/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
    alias_database = $alias_maps
    # 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"
    mailbox_command = /usr/bin/procmail
    # 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".
    # Cyrus IMAP over LMTP. Specify ``lmtpunix cmd="lmtpd"
    # listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
    #mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
    # Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
    # subsequent line in master.cf.
    #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
    ddd $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 = /etc/postfix/sample
    # readme_directory: The location of the Postfix README files.
    readme_directory = /usr/share/doc/postfix
    inet_protocols = ipv4
    # Enable smtp auth
    smtp_sasl_auth_enable = yes
    smtp_sasl_password_maps = hash:/etc/postfix/saslpass
    smtp_sasl_security_options = noanonymous
    # Enable tls
    smtp_use_tls = yes
    smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
    # Max message size limit
    message_size_limit = 0
    Please help
    Last edited by Rumcajs (2014-08-05 06:16:11)

    I have solved it, and this was the problem (main.cf) message_size_limit = 0 i have set this to unlimited "0" so bigger mails not get rejected by postfix, the defualt value was 10240000 (~10 Mb) after finally checking the postfix log with journalctl -u postfix (because /var/log/mail.log) is not used anymore i found this line : "fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit" after setting mailbox_size_limit to unlimited "0" postfix starts to delivery local mail.
    Last edited by Rumcajs (2014-08-05 06:17:23)

  • Redundent mail server setup (backup mail server)

    i have been reading all the post of setting up a mackup postfix server. i have looked at the configuration files and have a second machine ready to be implemented but have some questions on how exactly the backup works. my current setup is:
    - xserve1 with 10.4.3 OD master running mail, web, dns, ichat, ftp, host name is mail.mydomain.com
    - xserve2 with 10.4.3 (i will make this replica) running web and backup dns
    - G4 466MHz with 10.4.3 Server running mail and web, host name is mail2.mydomain.com (this is to bemy postfix backup server)
    all 3 are behind a firewall with NAT. they have local LAN IPs with NAT to 3 separate WAN IPs and open ports for the needed services.
    my first question is: do i need to run dns as well on mail2.mydomain.com?
    while i understand that mail stays in the queue on the postfix backup, does that mean that while mail.mydomain.com (primary mail server) is down users will not be getting any mail? can the users actually login to the mail2.mydomain.com and if yes how do they authorize?
    should i keep mail2.mydomain.com as a standalone or make it part of the directory?
    any info is appreciated.
    thanks
    martin
    xserve G5   Mac OS X (10.4.3)  

    don't mail servers hold mail for days anyway and keep
    retrying and when our mail comes back up will get all
    the mail?
    Yes, they typically do (unless some braindead administrator has configured his server to try only for a few hours or so).
    i assume there is no difference if my
    backup mail server runs on 10.3.9 then?
    None whatsoever.
    - is there a practical way to set up a mail that
    clinets can login to and check mail while the primary
    server is down?
    Practical? No.
    can the backup server forward as well
    while it holds to the queue?
    Why would you want that? Where should it forward to if the primary is down? As soon as the primary is up, the secondary will forward to i.
    the last time i had some
    coruption and problems with reconstruct (which you
    helped me with), we were down for 24 hours. i am
    trying to avoid this. i have an image and i run
    mailbfr to backup i assume i can use that in case of
    harware failure or massive os corruption that may
    take hours to fix.
    If push comes to shove this may help. Although images are never too brilliant for mail services recovery.
    my problem is that if this happens
    during the week, during daytime we cannot really
    afford to be down at that time.
    This is really your call. Only you can decide how much money you want/need to throw at resilience. But if you decide you cannot afford more than an hour of downtime, you will need far more than an onsite secondary mx
    Alex

  • How can I make mail retry sending messages in the Outbox?

    Howdy all,
    As the title says how can a force Mail to try to resend the messages in the outbox? I use my MacBook Pro in a number of different environments and when I am on one flakey access point in particular or when I have forgotten to open Safari to reauthorize recently on another network Mail will fail to contact the SMTP server. When this happens my message gets stuck in the outbox to be sent later. My problem is that I do not know how to get it out of there effectively.
    Once I have fixed the transitive error in the network (or or the problem fixes itself) how do I get the messages out of the inbox? At this point I can send more messages with no problem and they will happily go out but those in the queue just sit there.
    Now, I have tried a number of things like quitting and restarting Mail, bringing the various network interfaces back up and down, and other things to try to trick Mail into sending the queued messages but that has been haphazard at best. I can't help thinking that there is something obvious I am missing.
    Thanks for any help!

    Highlight the message in the inbox, double-click on it, and click on the "send" icon
    You may even consider BCCing yourself to see whether the message actually goes or not, and you just have an artifact copy stuck in your outbox that you could then just delete.
    Otherwise, copy&paste the stuck message body into a new message, and delete the stuck one out of the outbox before attempting to send the new one

Maybe you are looking for

  • Cf11 installation issue on windows 2003 R2 : installer crashes

    Below are the steps I went through : . download the installer exe (ColdFusion_11_WWEJ_win.exe) : 571 106 928 octets . launch it --> nothing happen (I can see in tasklanager some cpu activity during few seconds then nothing) . then I have tried to ope

  • Can I modify the column "Net Price" of purchase order to display 3 decimals

    Dear expert,      Can I modify the column "Net Price" of purchase order to display 3 decimals?      Looking forward to your reply.      Many thanks. Best Regards, Merry

  • Payment Method Printing

    Hi I have excuted the payment run with payment method C and T.  If I wanted to find the out put for my payment method out put print of my check plz let me know how i could find it. Regards, Raghu

  • WM QM Interface Clarification

    Good morning to all, Can any body explain to me that what are things we need to setup in Material Master Data (In WM point of view) if we have the  interface with WM-QM(Quality Management).

  • Smartforms symbol not found?

    Hi experts, I am facing a problem with smartforms, hopefully anyone of you got a solution on this. The call of my Smartforms FM results in a exception 1 --> formatting error. Smartforms_trace says:   MSGV1: GV_PRINT-AMOUNT        symbol GV_PRINT-AMOU