Mail Server Transfer!
I have Xserve running Mail Server, OD and Web which includes Mailman and webmail.
I have the boot drive and another partition which has the Mail Data on it..
what is the best way to transfer the files from this machine to another Xserve running 10.6.. i mean i know how to export mail settings under Server Admin, but how can i get the database and all that transfered.. i'm afraid i will lose something .. and never done this before!
I do my Cyrus backups to one of the internal drives on my Xserve via mailbfr (1 for backup 2 drives for mirrored OS, and an external array for mail data). When I want to migrate a user to my new Xserve running 10.6, I eject the backup disk and put it in one of the drive bays on the new Xserve. On the new Xserve, I have two 2TB drives mirrored for the mail, an internal SSD drive for the OS and a cheapo third drive I backup the OS to via Carbon Copy Cloner. I can just pop the third drive out and put in the backup disk from the other Xserve.
Note: I assume you are running Leopard Server on the old Xserve. Before you move any mail data over, you must stop the mail service. Cyrus is prone to corruption of the mail database unless you stop the mail service. Not so much with Dovecot, which is a big reason I am migrating...
Other was to do it are to copy your mail database to a Firewire of USB drive, then on to the new server, or over the network. Just remember to stop the mail service first.
On my new server, I am creating my OD users from scratch. I had some corruption on my other server, and wanted to start clean. For the mail settings, I'm duplicating them by hand via the ServerManager Mail plugin, or manually editing the files (/etc/postfix/main.cf and etc/dovecot/dovecot.conf). Also, I'm not doing all the mail accounts at once, but in groups. all-at-once is too risky for me. See:
http://discussions.apple.com/thread.jspa?threadID=2383747&tstart=0
for some specifics on my mail migration.
Message was edited by: flatrack
Similar Messages
-
XServe Mail Server not receiving emails from our phone system
Hi everyone,
Since late last year, staff haven't been receiving email notificiations to their work email (hosted by a 10.5.8 Xserve) of voice mail received by our 3COM NBX Phone System. However, if they provide any other email account, such as a Gmail account, they receive the email fine.
Our firewall providers have confirmed that there is nothing stopping the emails going in and out on their end. I've checked the server mail logs and can't find anything of value.
According to a forum thread, this is how our mail system sends an off-site notification via email:
1 - NCP performs an MX record lookup using DNS server IP information to return a valid TCP/IP address for each message being sent
2 - NCP acts as an MTA (Message Transfer Agent) - will directly contact each destination mail server for local delivery
3 - NCP establishes a TCP socket to the resolved TCP/IP address on SMTP port 25
4 - NCP must be able to open a TCP session to the resolved IP address of each destination email server
5 - Each destination server the NBX is sending email to may be configured for a rule base and based on certain criteria my reject an email or attachment that other email servers accept.
I'd appreciate any help you can provide.
Thankyou,
RhysI have no way of issuing that command from the "netSet".
Below is the link I found of the self service article on troubleshooting offsite notifications:
http://knowledge.3com.com/service/main.jsp;jsessionid=5CC7B2440667382AC7190A9665 9AC61D.selfservice1?t=solutionTab&ft=searchTab&ps=solutionPanels&locale=enUS&_dyncharset=UTF-8&curResURL=%2Fservice%2Fmain.jsp%3Bjsessionid%3D5CC7B2440667 382AC7190A96659AC61D.selfservice1%3FSearchButton%3DFind%26_dyncharset%3DUTF-8%26 locale%3DenUS%26t%3DsearchTab%26useFocusTopic%3Dtrue%26focusTopic%3D9029739%26searchstring% 3DNBX%252520-%252520Is%252520NAT%252520Supported%253f%26sfield%3D%26dosearch%3Dt rue%26pn%3D4&solutionId=1802&isSrch=Yes
I've tested the internal settings, the dig as we've established, and I've checked the server logs - they don't seem to show anything relating to the nbx.
The firewall has port 25 open to our mail server and phone system only.
-Rhys -
Hi,
I have problem with receiving msgs on our mail server. But just only mssgs with attachements. (tested on PDF file)
Looks like server get connected then transfer data but after few minutes timeout and lost connection.
from log:
Jul 18 09:57:32 odm postfix/smtpd[7299]: connect from mail-gx0-f176.google.com[209.85.161.176]
Jul 18 09:57:33 odm postfix/smtpd[7299]: AA5FB28DA47: client=mail-gx0-f176.google.com[209.85.161.176]
Jul 18 10:01:23 odm postfix/smtpd[5995]: lost connection after DATA (245975 bytes) from mail-gx0-f176.google.com[209.85.161.176]
Jul 18 10:01:23 odm postfix/smtpd[5995]: disconnect from mail-gx0-f176.google.com[209.85.161.176]
Jul 18 10:07:32 odm postfix/anvil[7304]: statistics: max connection rate 1/60s for (smtp:209.85.161.176) at Jul 18 09:57:32
Jul 18 10:07:32 odm postfix/anvil[7304]: statistics: max connection count 1 for (smtp:209.85.161.176) at Jul 18 09:57:32
What I Try:
I try to turn off graylisting and double check router settings ports 25, 465 correctly forwarded also i try to put our domain on whitelist on router then try turn off spam check on router. Nothing works.
Thanks for any clueGreylisting and ports and routing are not likely the trigger for the reported behavior. Those settings tend to be all-or-nothing; either the connection works, or it does not. And port 465 is a submission port, and not a port that receives messages from remote servers; only port 25 is relevant to inbound mail.
Errors such as described here can point to lower-level software or hardware errors, whether with the server itself or (more likely) with a network-level error.
The other typical trigger here can be the message size limit setting. Server Admin > select server > Mail > Settings > Quotas > Refuse Messages Larger Than...
Per-user limits and available disk storage can block larger messages.
If none of the above resolves this, try increasing the SMTP log level; move up to "Debug" for this testing. Server Admin > select server > Mail > Settings > Logging > SMTP Log Level. I'd probably also increase the Junk Mail logging level, too. -
Creating a mail server from an SMTP feed
Currently, we are unsatisfied with our mail provider - mostly due to delayed mail receipt. After speaking to our ISP they advised us that we could set up our own mail server and they could stream SMTP to us, avoiding POP3.
Although I administer the server and the network I have no experience of mail servers and have a few questions. I would have searched the forum but I don't really know which terms to search.
I would very much appreciate a fairly full explanation and nothing too vague please.
1. Is this easy to set up without additional hardware/software - is it built-in to OSX Server? What is it called and is it only accessed through CLI? Is there a good GUI alternative?
2. What hardware/software would you recommend for a facility handling about 200-300 emails per day, most with attachments of around 1Mb? It is not unusual to exceed 1Gb of email bandwidth in a working day.
3. What problems/shortfalls do I need to be aware of? Fequent crashes, database rebuilding, common address books, support, missing/undelivered/undeliverable mail, client set-up, etc
4. How will our email change, both sending and receiving? Will we or our recipients notice any sort of change?
Thank you in advance. Please feel free to ask any questions.
SteveCurrently, we are unsatisfied with our mail provider
- mostly due to delayed mail receipt. After speaking
to our ISP they advised us that we could set up our
own mail server and they could stream SMTP to us,
avoiding POP3.
Although I administer the server and the network I
have no experience of mail servers and have a few
questions. I would have searched the forum but I
don't really know which terms to search.
I would very much appreciate a fairly full
explanation and nothing too vague please.
1. Is this easy to set up without additional
hardware/software - is it built-in to OSX Server?
What is it called and is it only accessed through
CLI? Is there a good GUI alternative?
Sorry for the 'vague' answer but it's called "Mail" in Server Admin app - presumably the application you are using to administer your server? You can find documentation on it in the Mail Service section here...
http://www.apple.com/support/macosxserver/index.html
Apple docs are not everyones cup of tea but they are the starting point.
There are also other 3rd party mail server apps you can run in place of the built-in one.
2. What hardware/software would you recommend for a
facility handling about 200-300 emails per day, most
with attachments of around 1Mb? It is not unusual to
exceed 1Gb of email bandwidth in a working day.
A G4 could do that easily - depending (of course) on what else it is doing.
3. What problems/shortfalls do I need to be aware of?
Fequent crashes, database rebuilding, common address
books, support, missing/undelivered/undeliverable
mail, client set-up, etc
It just runs fine. Any time I have had problems it is because I have 'fiddled', but it is still a bit of software and you therefore become responsible for it (rather than your ISP/mail provider). "Common address books" is not a function of the OS X mail server. The mail logs are there for tracking whether "missing" mail was actually sent/delivered. Client set up is just as per usual requirements except you point clients to your server rather than ISP's.
4. How will our email change, both sending and
receiving? Will we or our recipients notice any sort
of change?
Sending from within the same LAN as your server appears a lot faster to people on the LAN since the transfer to the server is within LAN rather than out to internet. The server then sends out to internet.
Apologies again for the possibly not "full" answers but if I did that I would end up writing a manual
-david -
SMTP error from remote mail server after initial connection:
Hello folks. I having some serious issues sending email to clients with .mac accounts. I keep on getting the following error. Can someone help? I have replaced email address names with "Blank@...) for obvious reasons.
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[email protected]
SMTP error from remote mail server after initial connection:
host smtp-mx1.mac.com [17.148.20.64]: 452 try later:
retry timeout exceeded
------ This is a copy of the message, including all the headers. ------
Return-path: <[email protected]>
Received: from ip72-207-229-240.br.br.cox.net ([72.207.229.240] helo=[192.168.0.102])
by srv3.purenrg.com with esmtp (Exim 4.68)
(envelope-from <[email protected]>)
id 1JFeOb-0001FZ-5F
for [email protected]; Thu, 17 Jan 2008 18:43:41 -0500
Message-Id: <[email protected]>
From: "[email protected]" <[email protected]>
To: Cindy Barnes <[email protected]>
Content-Type: multipart/alternative; boundary=Apple-Mail-3--1032078955
Mime-Version: 1.0 (Apple Message framework v915)
Subject: invoice 520 is overdue
Date: Thu, 17 Jan 2008 17:43:40 -0600
X-Mailer: Apple Mail (2.915)
X-PopBeforeSMTPSenders: [email protected]{
--Apple-Mail-3--1032078955
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bitI'm sure someone will give more detail, but it looks like the server blocked your address because it thinks it's a spam source. If you're not spamming, then it might be someone on the same network spamming, or malware on your computer doing it. Or it could just be a mistake. try calling whoever runs your mail server and see if they can give you more information.
-
Outgoing mail server failed to deliver this message
This message appeared. I have not sent 400 messages. What's the deal??
""The outgoing mail server “smto,mac.com:jones” failed to deliver this message. 4.0.0 You have exceeded 400 recipients in the last 24 hours. Try again later.""
iMac G4 Mac OS X (10.2.8)You're welcome.
If you're a .Mac member using Mac OS X version 10.2.1 or later, you can synchronize the contact information between the Address Book application on your computer and your .Mac Address Book on the web. You can also synchronize your contact information between multiple Mac OS computers.
If you're using a version of Mac OS X earlier than version 10.4, you must have iSync installed on your computer to synchronize the information. To download iSync, go to
www.apple.com/support/downloads/isync.html
You can't synchronize the information in your .Mac Address Book if you have an email-only account.
To sync your .Mac Address Book:
Do one of the following:
If you're using a version of Mac OS X earlier than version 10.4, open iSync and click the .Mac button. Register your .Mac account, turn on .Mac synchronization, and then click the Sync Now button.
(Note: If you are syncing contact information between multiple Mac OS computers, use iSync to register all the computers you want to keep synchronized. For more information, choose Help > iSync Help when iSync is open.)
After the sync has completed, go to www.mac.com and click Address Book on the .Mac tab.
Click Preferences, and then select the "Turn on .Mac Address Book
Synchronization" checkbox.
Click Save.
With Address Book synchronization turned on, the contact information in your .Mac Address Book on the web and the Address Book application on your computer will be updated with any changes each time you sync.
You can turn off synchronization between the Address Book application on your computer and your .Mac Address Book on the web by deselecting the "Turn on .Mac Address Book Synchronization" checkbox. While this checkbox is deselected, changes you make to either address book are saved until the next time you select this checkbox and click the Sync Now button on the .Mac pane or in iSync. (For example, if you delete an address from your .Mac Address Book with this checkbox deselected, this address will be deleted from the Address Book on your computer's hard disk the next time you sync with synchronization turned on.)
If your kid has his/her own computer login account, one way to transfer selected contacts from your Address Book to your kid's address book is to create a folder on the Desktop named Contacts or whatever you prefer. Launch Address Book and one at a time, select a contact's name to highlight it and then single click and drag the contact to the created Contacts folder on the Desktop. This will create a vCard copy of the contact.
Using the Finder, go to Home > Shared. Place the Contacts folder on the Desktop in the Shared folder.
When your kid logs in to his/her account, the Contacts folder will be available in his/her Shared folder at Home > Shared.
Launch Address Book and at the menu bar, go to File > Import and select vCards. Navigate to/within the Contacts folder in the Shared folder and the vCards in the Contacts folder will be imported to your kid's Address Book. -
Help Setting Up 2nd Mail Server
I am running Mac OS 10.4 server. I have several web sites running on this server but only one of the domains currently has a mail server. I use Server Admin & Workgroup Manager to administor as I am not very unix savvy.
Here is what I have done so far.
Created the domain: m2venturepartners.com in the web:sites section
Created the Web Server Alias mail.m2venturepartners.com under the Web:Site:Aliases section
Since the DNS and website is hosted elsewhere I had them create the MX record that points to mail.m2venturepartners.com and a DNS record that points mail.m2venturepartners.com to 209.233.105.38 the ip address for my server.
I created mail users with the workgroup manager enabling mail and adding the mail server: mail.m2venturepartners.com
At this point I set up a user client and successfully logged into both the imap & smtp servers. But when I send an email to a [email protected] it comes back with the following failure notice:
Hi. This is the qmail-send program at yahoo.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<[email protected]>:
209.233.105.38 does not like recipient.
Remote host said: 554 <[email protected]>: Relay access denied
Giving up on 209.233.105.38.
--- Below this line is a copy of the message.
Return-Path: <[email protected]>
Received: (qmail 45053 invoked from network); 24 Aug 2007 22:48:56 -0000
Received: from unknown (HELO ?192.168.0.6?) ([email protected]@71.222.44.164 with plain)
by smtp120.sbc.mail.sp1.yahoo.com with SMTP; 24 Aug 2007 22:48:55 -0000
X-YMail-OSG: yQiheJEVM1l8vJBxkIys4PycpRxUDgIoO14X4_4y.8pYEICipPMkhjKPq8QO2Wcc139G.QMQaA--
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <[email protected]>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: Michael Teel <[email protected]>
From: Michael Teel <[email protected]>
Subject: Test7
Date: Fri, 24 Aug 2007 15:48:48 -0700
X-Mailer: Apple Mail (2.752.3)
I'm lost as to what to do under the Mail section of Server Admin. Because this section was filled in when I set up my original domain (theteelfamily.com) and I can't figure out how to add additional domains.
Can someone help me get this 2nd mail server up receiving mail?
ThanksI am having the same sort of problems as you - and I have not been able to resolve my problems as yet. The document which was referred to earlier might be helpful, but I have not been able to get this to work, and Apple don't seem to offer any real Postfix support. I can get outgoing mail to work but incoming mail is always rejected for one reason or another (550 nu such mailbox is the usual problem).
-
Hi.
I am in trouble setting up a basic mail server. I just spent the last 10 or so hours, in one more try to set it, and yet no results.
Please, give some help as i am becoming sort of desperated with it
This time, i followed this guide since the beginning.
What I've done:
- Created a user vmail, with home directory set on /var/mail/vmail/
- Had a LAMP server already working.
- Created two databases: postfix_db and roundcube_db, owned by postfix_user and roundcube_user respectively.
- Since it is for personal use and i don't use "old/odd clients like Outlook" i skipped smtps. And made the following files:
My postfix main.cf(every commented line removed):
queue_directory = /var/spool/postfix
command_directory = /usr/bin
daemon_directory = /usr/lib/postfix
data_directory = /var/lib/postfix
mail_owner = postfix
mydomain = mydomainname.tld
unknown_local_recipient_reject_code = 550
alias_maps = hash:/etc/postfix/aliases
alias_database = $alias_maps
debug_peer_level = 2
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
ddd $daemon_directory/$process_name $process_id & sleep 5
sendmail_path = /usr/bin/sendmail
newaliases_path = /usr/bin/newaliases
mailq_path = /usr/bin/mailq
setgid_group = postdrop
html_directory = no
manpage_directory = /usr/share/man
sample_directory = /etc/postfix/sample
readme_directory = /usr/share/doc/postfix
inet_protocols = ipv4
relay_domains = *
virtual_alias_maps = proxy:mysql:/etc/postfix/virtual_alias_maps.cf
virtual_mailbox_domains = proxy:mysql:/etc/postfix/virtual_domains_maps.cf
virtual_mailbox_maps = proxy:mysql:/etc/postfix/virtual_mailbox_maps.cf
virtual_mailbox_base = /var/mail/vmail
virtual_mailbox_limit = 512000000
virtual_minimum_uid = 5000
virtual_transport = virtual
virtual_uid_maps = static:5000
virtual_gid_maps = static:5000
local_transport = virtual
local_recipient_maps = $virtual_mailbox_maps
transport_maps = hash:/etc/postfix/transport
smtpd_sasl_auth_enable = yes
smtpd_sasl_type = dovecot
smtpd_sasl_path = /var/run/dovecot/auth-client
smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
smtpd_sasl_security_options = noanonymous
smtpd_sasl_tls_security_options = $smtpd_sasl_security_options
smtpd_tls_auth_only = yes
smtpd_tls_cert_file = /etc/ssl/private/server.crt
smtpd_tls_key_file = /etc/ssl/private/server.key
smtpd_sasl_local_domain = $mydomain
broken_sasl_auth_clients = yes
smtpd_tls_loglevel = 1
Postfix master.cf
smtp inet n - n - - smtpd
submission inet n - n - - smtpd
-o smtpd_tls_security_level=encrypt
-o smtpd_sasl_auth_enable=yes
pickup unix n - n 60 1 pickup
cleanup unix n - n - 0 cleanup
qmgr unix n - n 300 1 qmgr
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
flush unix n - n 1000? 0 flush
proxymap unix - - n - - proxymap
proxywrite unix - - n - 1 proxymap
smtp unix - - n - - smtp
relay unix - - n - - smtp
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
/etc/postfix/virtual_alias_maps.cf (sample password)
user = postfix_user
password = m/<~VN4XQ!G=jE[A/-
hosts = localhost
dbname = postfix_db
query = SELECT goto FROM alias WHERE address='%s' AND active = true
/etc/postfix/virtual_domains_maps.cf
user = postfix_user
password = m/<~VN4XQ!G=jE[A/-
hosts = localhost
dbname = postfix_db
query = SELECT domain FROM domain WHERE domain='%s' AND backupmx = false AND active = true
/etc/postfix/virtual_mailbox_limits.cf
user = postfix_user
password = m/<~VN4XQ!G=jE[A/-
hosts = localhost
dbname = postfix_db
query = SELECT quota FROM mailbox WHERE username='%s'
/etc/postfix/virtual_mailbox_maps.cf
user = postfix_user
password = m/<~VN4XQ!G=jE[A/-
hosts = localhost
dbname = postfix_db
query = SELECT maildir FROM mailbox WHERE username='%s' AND active = true
- Created the SSL key with no problem, and put it in place.
Edited dovecot.conf:
protocols = imap pop3
auth_mechanisms = plain
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql.conf
userdb sql {
driver = sql
args = /etc/dovecot/dovecot-sql.conf
service auth {
unix_listener auth-client {
group = postfix
mode = 0660
user = postfix
user = root
mail_home = /var/mail/vmail/%d/%u
mail_location = maildir:~
ssl_cert = </etc/ssl/private/server.crt
ssl_key = </etc/ssl/private/server.key
dict {
#quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
#expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext
!include conf.d/*.conf
!include_try local.conf
/etc/dovecot/dovecot-sql.conf
driver = mysql
connect = host=localhost dbname=postfix_db user=postfix_user password=m/<~VN4XQ!G=jE[A/-
default_pass_scheme = MD5-CRYPT
user_query = SELECT '/var/mail/vmail/%d/%u' as home, 'maildir:/var/mail/vmail/%d/%u' as mail, 5000 AS uid, 5000 AS gid, concat('dirsize:storage=', quota) AS quota FROM mailbox WHERE username = '%u' AND active = '1'
password_query = SELECT username as user, password, '/var/mail/vmail/%d/%u' as userdb_home, 'maildir:/var/mail/vmail/%d/%u' as userdb_mail, 5000 as userdb_uid, 5000 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1'
- Installed postfixadmin and roundcube and made their apache alias.
- Made directories writable for them.
/etc/webapps/postfixadmin/config.inc.php (note that there is no "?>" to end the script, it came just like that, and since it had no error there ill assume its normal)
<?php
$CONF['configured'] = true;
$CONF['setup_password'] = '562bc24a874b0c2a7340e3da04b3fdf6:d60282f5cbc19340c73cafbb6526379be696a7c7';
$CONF['postfix_admin_url'] = '[url]http://mydomain.com/postfixadmin[/url]';
$CONF['postfix_admin_path'] = dirname(__FILE__);
$CONF['default_language'] = 'en';
$CONF['database_prefix'] = '';
$CONF['database_tables'] = array (
'admin' => 'admin',
'alias' => 'alias',
'alias_domain' => 'alias_domain',
'config' => 'config',
'domain' => 'domain',
'domain_admins' => 'domain_admins',
'fetchmail' => 'fetchmail',
'log' => 'log',
'mailbox' => 'mailbox',
'vacation' => 'vacation',
'vacation_notification' => 'vacation_notification',
'quota' => 'quota',
'quota2' => 'quota2',
$CONF['admin_email'] = '[email protected]';
$CONF['smtp_server'] = 'localhost';
$CONF['smtp_port'] = '25';
$CONF['encrypt'] = 'md5crypt';
$CONF['authlib_default_flavor'] = 'md5raw';
$CONF['dovecotpw'] = "/usr/sbin/dovecotpw";
$CONF['min_password_length'] = 5;
$CONF['generate_password'] = 'NO';
$CONF['show_password'] = 'NO';
$CONF['page_size'] = '10';
$CONF['default_aliases'] = array (
'abuse' => '[email protected]',
'hostmaster' => '[email protected]',
'postmaster' => '[email protected]',
'webmaster' => '[email protected]'
$CONF['domain_path'] = 'NO';
$CONF['domain_in_mailbox'] = 'YES';
$CONF['maildir_name_hook'] = 'NO';
$CONF['aliases'] = '10';
$CONF['mailboxes'] = '10';
$CONF['maxquota'] = '10';
$CONF['quota'] = 'NO';
$CONF['quota_multiplier'] = '1024000';
$CONF['transport'] = 'NO';
$CONF['transport_options'] = array (
'virtual', // for virtual accounts
'local', // for system accounts
'relay' // for backup mx
$CONF['transport_default'] = 'virtual';
$CONF['vacation'] = 'NO';
$CONF['vacation_domain'] = 'autoreply.change-this-to-your.domain.tld';
$CONF['vacation_control'] ='YES';
$CONF['vacation_control_admin'] = 'YES';
$CONF['alias_control'] = 'NO';
$CONF['alias_control_admin'] = 'NO';
$CONF['special_alias_control'] = 'NO';
$CONF['alias_goto_limit'] = '0';
$CONF['alias_domain'] = 'YES';
$CONF['backup'] = 'YES';
$CONF['sendmail'] = 'YES';
$CONF['logging'] = 'YES';
$CONF['fetchmail'] = 'YES';
$CONF['fetchmail_extra_options'] = 'NO';
$CONF['show_header_text'] = 'NO';
$CONF['header_text'] = ':: Postfix Admin ::';
$CONF['user_footer_link'] = "[url]http://mydomain.com[/url]";
$CONF['show_footer_text'] = 'YES';
$CONF['footer_text'] = 'Return to mydomain.com';
$CONF['footer_link'] = '[url]http://mydomain.com[/url]';
$CONF['welcome_text'] = <<<EOM
Welcome to your new account.
EOM;
$CONF['emailcheck_resolve_domain']='YES';
$CONF['show_status']='NO';
$CONF['show_status_key']='NO';
$CONF['show_status_text']=' ';
$CONF['show_undeliverable']='NO';
$CONF['show_undeliverable_color']='tomato';
$CONF['show_undeliverable_exceptions']=array("unixmail.domain.ext","exchangeserver.domain.ext","gmail.com");
$CONF['show_popimap']='NO';
$CONF['show_popimap_color']='darkgrey';
$CONF['show_custom_domains']=array("subdomain.domain.ext","domain2.ext");
$CONF['show_custom_colors']=array("lightgreen","lightblue");
$CONF['recipient_delimiter'] = "";
$CONF['create_mailbox_subdirs_prefix']='INBOX.';
$CONF['used_quotas'] = 'NO';
$CONF['new_quota_table'] = 'NO';
$CONF['theme_logo'] = 'images/logo-default.png';
$CONF['theme_css'] = 'css/default.css';
$CONF['xmlrpc_enabled'] = false;
if (file_exists(dirname(__FILE__) . '/config.local.php')) {
include(dirname(__FILE__) . '/config.local.php');
$CONF['domain_path'] = 'YES';
$CONF['domain_in_mailbox'] = 'YES';
$CONF['database_type'] = 'mysqli';
$CONF['database_host'] = 'localhost';
$CONF['database_user'] = 'postfix_user';
$CONF['database_password'] = 'm/<~VN4XQ!G=jE[A/-';
$CONF['database_name'] = 'postfix_db';
- I went to domain/postfixAdmin/setup.php and domain/roundcube/installer/ and everything was ok.
db.inc.php (roundcube):
<?php
$rcmail_config = array();
$rcmail_config['db_dsnw'] = 'mysql://roundcube_user:%3D%29CYbd9bK%210Z7%29AsWU@localhost/roundcube_db';
$rcmail_config['db_dsnr'] = '';
$rcmail_config['db_persistent'] = FALSE;
$rcmail_config['db_table_users'] = 'users';
$rcmail_config['db_table_identities'] = 'identities';
$rcmail_config['db_table_contacts'] = 'contacts';
$rcmail_config['db_table_contactgroups'] = 'contactgroups';
$rcmail_config['db_table_contactgroupmembers'] = 'contactgroupmembers';
$rcmail_config['db_table_session'] = 'session';
$rcmail_config['db_table_cache'] = 'cache';
$rcmail_config['db_table_cache_index'] = 'cache_index';
$rcmail_config['db_table_cache_thread'] = 'cache_thread';
$rcmail_config['db_table_cache_messages'] = 'cache_messages';
$rcmail_config['db_table_dictionary'] = 'dictionary';
$rcmail_config['db_table_searches'] = 'searches';
$rcmail_config['db_table_system'] = 'system';
$rcmail_config['db_sequence_users'] = 'user_ids';
$rcmail_config['db_sequence_identities'] = 'identity_ids';
$rcmail_config['db_sequence_contacts'] = 'contact_ids';
$rcmail_config['db_sequence_contactgroups'] = 'contactgroups_ids';
$rcmail_config['db_sequence_searches'] = 'search_ids';
main.inc.php(roundcube):
<?php
$rcmail_config = array();
$rcmail_config['debug_level'] = 5;
$rcmail_config['log_driver'] = 'file';
$rcmail_config['log_date_format'] = 'd-M-Y H:i:s O';
$rcmail_config['syslog_id'] = 'roundcube';
$rcmail_config['syslog_facility'] = LOG_USER;
$rcmail_config['smtp_log'] = true;
$rcmail_config['log_logins'] = false;
$rcmail_config['log_session'] = false;
$rcmail_config['sql_debug'] = false;
$rcmail_config['imap_debug'] = false;
$rcmail_config['ldap_debug'] = false;
$rcmail_config['smtp_debug'] = false;
$rcmail_config['default_host'] = 'tls://localhost/';
$rcmail_config['default_port'] = 993;
$rcmail_config['imap_auth_type'] = null;
$rcmail_config['imap_delimiter'] = null;
$rcmail_config['imap_ns_personal'] = null;
$rcmail_config['imap_ns_other'] = null;
$rcmail_config['imap_ns_shared'] = null;
$rcmail_config['imap_force_caps'] = false;
$rcmail_config['imap_force_lsub'] = false;
$rcmail_config['imap_force_ns'] = false;
$rcmail_config['imap_timeout'] = 0;
$rcmail_config['imap_auth_cid'] = null;
$rcmail_config['imap_auth_pw'] = null;
$rcmail_config['imap_cache'] = null;
$rcmail_config['messages_cache'] = false;
$rcmail_config['smtp_server'] = 'tls://localhost/';
$rcmail_config['smtp_port'] = 587;
$rcmail_config['smtp_user'] = '';
$rcmail_config['smtp_pass'] = '';
$rcmail_config['smtp_auth_type'] = '';
$rcmail_config['smtp_auth_cid'] = null;
$rcmail_config['smtp_auth_pw'] = null;
$rcmail_config['smtp_helo_host'] = '';
$rcmail_config['smtp_timeout'] = 0;
$rcmail_config['enable_installer'] = false;
$rcmail_config['dont_override'] = array();
$rcmail_config['support_url'] = '';
$rcmail_config['skin_logo'] = 'sorrybutnocookie';
$rcmail_config['auto_create_user'] = true;
$rcmail_config['user_aliases'] = false;
$rcmail_config['log_dir'] = 'logs/';
$rcmail_config['temp_dir'] = 'temp/';
$rcmail_config['message_cache_lifetime'] = '10d';
$rcmail_config['force_https'] = false;
$rcmail_config['use_https'] = false;
$rcmail_config['login_autocomplete'] = 0;
$rcmail_config['login_lc'] = 2;
$rcmail_config['skin_include_php'] = false;
$rcmail_config['display_version'] = false;
$rcmail_config['session_lifetime'] = 10;
$rcmail_config['session_domain'] = '';
$rcmail_config['session_name'] = null;
$rcmail_config['session_auth_name'] = null;
$rcmail_config['session_path'] = null;
$rcmail_config['session_storage'] = 'db';
$rcmail_config['memcache_hosts'] = null;
$rcmail_config['ip_check'] = true;
$rcmail_config['referer_check'] = false;
$rcmail_config['x_frame_options'] = 'sameorigin';
$rcmail_config['des_key'] = '0JaV%FnEivx9e+JdH2g*?n3n';
$rcmail_config['username_domain'] = '';
$rcmail_config['mail_domain'] = '';
$rcmail_config['password_charset'] = 'ISO-8859-1';
$rcmail_config['sendmail_delay'] = 0;
$rcmail_config['max_recipients'] = 0;
$rcmail_config['max_group_members'] = 0;
$rcmail_config['useragent'] = 'Roundcube Webmail/'.RCMAIL_VERSION;
$rcmail_config['product_name'] = 'Test';
$rcmail_config['include_host_config'] = false;
$rcmail_config['generic_message_footer'] = '';
$rcmail_config['generic_message_footer_html'] = '';
$rcmail_config['http_received_header'] = false;
$rcmail_config['http_received_header_encrypt'] = false;
$rcmail_config['mail_header_delimiter'] = NULL;
$rcmail_config['line_length'] = 72;
$rcmail_config['send_format_flowed'] = true;
$rcmail_config['mdn_use_from'] = false;
$rcmail_config['identities_level'] = 0;
$rcmail_config['client_mimetypes'] = null;
$rcmail_config['mime_magic'] = null;
$rcmail_config['mime_types'] = null;
$rcmail_config['im_identify_path'] = null;
$rcmail_config['im_convert_path'] = null;
$rcmail_config['image_thumbnail_size'] = 240;
$rcmail_config['contact_photo_size'] = 160;
$rcmail_config['email_dns_check'] = false;
$rcmail_config['no_save_sent_messages'] = false;
$rcmail_config['plugins'] = array();
$rcmail_config['message_sort_col'] = '';
$rcmail_config['message_sort_order'] = 'DESC';
$rcmail_config['list_cols'] = array('subject', 'status', 'fromto', 'date', 'size', 'flag', 'attachment');
$rcmail_config['language'] = null;
$rcmail_config['date_format'] = 'Y-m-d';
$rcmail_config['date_formats'] = array('Y-m-d', 'Y/m/d', 'Y.m.d', 'd-m-Y', 'd/m/Y', 'd.m.Y', 'j.n.Y');
$rcmail_config['time_format'] = 'H:i';
$rcmail_config['time_formats'] = array('G:i', 'H:i', 'g:i a', 'h:i A');
$rcmail_config['date_short'] = 'D H:i';
$rcmail_config['date_long'] = 'Y-m-d H:i';
$rcmail_config['drafts_mbox'] = 'Drafts';
$rcmail_config['junk_mbox'] = 'Junk';
$rcmail_config['sent_mbox'] = 'Sent';
$rcmail_config['trash_mbox'] = 'Trash';
$rcmail_config['default_folders'] = array('INBOX', 'Drafts', 'Sent', 'Junk', 'Trash');
$rcmail_config['create_default_folders'] = false;
$rcmail_config['protect_default_folders'] = true;
$rcmail_config['quota_zero_as_unlimited'] = false;
$rcmail_config['enable_spellcheck'] = false;
$rcmail_config['spellcheck_dictionary'] = false;
$rcmail_config['spellcheck_engine'] = 'googie';
$rcmail_config['spellcheck_uri'] = '';
$rcmail_config['spellcheck_languages'] = NULL;
$rcmail_config['spellcheck_ignore_caps'] = false;
$rcmail_config['spellcheck_ignore_nums'] = false;
$rcmail_config['spellcheck_ignore_syms'] = false;
$rcmail_config['recipients_separator'] = ',';
$rcmail_config['max_pagesize'] = 200;
$rcmail_config['min_refresh_interval'] = 60;
$rcmail_config['upload_progress'] = false;
$rcmail_config['undo_timeout'] = 0;
$rcmail_config['address_book_type'] = 'sql';
$rcmail_config['ldap_public'] = array();
$rcmail_config['autocomplete_addressbooks'] = array('sql');
$rcmail_config['autocomplete_min_length'] = 1;
$rcmail_config['autocomplete_threads'] = 0;
$rcmail_config['autocomplete_max'] = 15;
$rcmail_config['address_template'] = '{street}<br/>{locality} {zipcode}<br/>{country} {region}';
$rcmail_config['addressbook_search_mode'] = 0;
$rcmail_config['default_charset'] = 'ISO-8859-1';
$rcmail_config['skin'] = 'larry';
$rcmail_config['mail_pagesize'] = 50;
$rcmail_config['addressbook_pagesize'] = 50;
$rcmail_config['addressbook_sort_col'] = 'surname';
$rcmail_config['addressbook_name_listing'] = 0;
$rcmail_config['timezone'] = 'auto';
$rcmail_config['prefer_html'] = true;
$rcmail_config['show_images'] = 0;
$rcmail_config['message_extwin'] = false;
$rcmail_config['compose_extwin'] = false;
$rcmail_config['htmleditor'] = 0;
$rcmail_config['prettydate'] = true;
$rcmail_config['draft_autosave'] = 300;
$rcmail_config['preview_pane'] = false;
$rcmail_config['preview_pane_mark_read'] = 0;
$rcmail_config['logout_purge'] = false;
$rcmail_config['logout_expunge'] = false;
$rcmail_config['inline_images'] = true;
$rcmail_config['mime_param_folding'] = 0;
$rcmail_config['skip_deleted'] = false;
$rcmail_config['read_when_deleted'] = true;
$rcmail_config['flag_for_deletion'] = false;
$rcmail_config['refresh_interval'] = 60;
$rcmail_config['check_all_folders'] = false;
$rcmail_config['display_next'] = true;
$rcmail_config['autoexpand_threads'] = 0;
$rcmail_config['reply_mode'] = 0;
$rcmail_config['strip_existing_sig'] = true;
$rcmail_config['show_sig'] = 1;
$rcmail_config['force_7bit'] = false;
$rcmail_config['search_mods'] = null;
$rcmail_config['addressbook_search_mods'] = null;
$rcmail_config['delete_always'] = false;
$rcmail_config['delete_junk'] = false;
$rcmail_config['mdn_requests'] = 0;
$rcmail_config['mdn_default'] = 0;
$rcmail_config['dsn_default'] = 0;
$rcmail_config['reply_same_folder'] = false;
$rcmail_config['forward_attachment'] = false;
$rcmail_config['default_addressbook'] = null;
$rcmail_config['spellcheck_before_send'] = false;
$rcmail_config['autocomplete_single'] = false;
$rcmail_config['default_font'] = 'Verdana';
- From what i can see, postfixadmin used and populated its database, but not roundcube.
- I can open postfixadmin and log in with no apparent errors (not that i know what to do with it instead of roundcube, but at least works...)
- Whenever i open roundcube it begins to output errors everywhere about db connection (I was only able after changing its .htaccess to Allow from all, is it a bad idea?)
DB Error in /usr/share/webapps/roundcubemail/program/lib/Roundcube/rcube_db.php (416): [1146] Table 'roundcube_db.session' doesn't exist (SQL Query: SELECT vars, ip, changed FROM session WHERE sess_id = 'pq5ofv7ja0gh2sunsg38jmd3g1')
Warning: session_start(): Cannot send session cache limiter - headers already sent in /usr/share/webapps/roundcubemail/program/lib/Roundcube/rcube.php on line 445
DB Error: [1146] Table 'roundcube_db.session' doesn't exist
DATABASE ERROR: CONNECTION FAILED!
Unable to connect to the database!
Please contact your server-administrator.
DB Error in /usr/share/webapps/roundcubemail/program/lib/Roundcube/rcube_db.php (416): [1146] Table 'roundcube_db.session' doesn't exist (SQL Query: INSERT INTO session (sess_id, vars, ip, created, changed) VALUES ('pq5ofv7ja0gh2sunsg38jmd3g1', 'dGVtcHxiOjE7bGFuZ3VhZ2V8czo1OiJlbl9VUyI7dGFza3xzOjU6ImxvZ2luIjs=', 'xxx.xxx.xxx.xxx', '2014-02-08 07:34:46', '2014-02-08 07:34:46'))
Thats all i know. Whats wrong? (i already tried to set db logins with no pw at all, but still with the same problems)
How far am i to be able to send/receive one email? Please, tell me i am close...
Mail servers could be so much more linear to set up
Thanks for your help. Time to get some sleep!The roundcube db schema needs to setup manually. See /usr/share/webapps/roundcube/INSTALL
Also, from your /etc/webapps/postfixadmin/config.inc.php:
$CONF['domain_path'] = 'NO';
$CONF['domain_in_mailbox'] = 'YES';
$CONF['maildir_name_hook'] = 'NO';
..which results in /var/mail/vmail/[email protected]
From your dovecot.conf
mail_home = /var/mail/vmail/%d/%u
...which results in /var/mail/vmail/domain.com/user
That doesn't fit together. -
Mail server no longer accepting incoming mail
First off, let me just say that yes, I broke it. This is on an iMac G4 with Server 10.4.11.
So here's the problem. I am by no means a qualified Server Administrator, but since I am a relatively knowledgeable computer geek, my boss plugged me into this position while my department is slow. I've been tasked with figuring out a few nagging problems with slow mail delivery, among other things.
I did some serious Googling on the issue of slow mail delivery, messages getting stuck in queue, etc. I determined that the issue was with spam filtering and anti-virus. Following some great documentation from osx.topicdesk.com, I updated and configured clamav, amavisd, and spamassassin. Miraculously, this actually solved the problem, and everything was working great.
Until today. Today I noticed a log entry that reverse DNS lookup of the server's IP (192.168.1.1) had failed. Googled again and found some info on setting up DNS on the server, which I did.
There was a secondary goal for doing this. We are a small company that hosts our own email and a tiny web server on a machine at our corporate office. Our remote locations have always been able to get email from the server via POP3 using the FQDN mailman.mycompany.com, which has a public IP address. Our router is configured to forward traffic to that IP to the private IP 192.168.1.1. However, all users at the corporate office had to be set up to use server IP 192.168.1.1 to get their mail because there was no way to resolve the FQDN into an IP that was visible on the private network. Or maybe there was/is, but I don't know about it. Anyway, we have a couple mobile users that work at multiple locations. They are set up to use the server's FQDN, but every time they come to our corporate office, they'd have to change their mail setup if they wanted to get mail, because once they're behind the router, the FQDN doesn't work. I think that makes sense.
The Server is also the DHCP server for this site. Prior to this morning, it was distributing our ISP's DNS IPs. Once I'd set up DNS on our Server, I changed it to distribute its own IP as the primary DNS server, and per someone's post, I modified named.conf to include our ISP's DNS IPs. The server name I set up is 'server' and the domain is 'mycompany.com'. I also set up an alias of 'mailman' and set it as a mail server. I then went to a couple of workstations in the building and did a Lookup on server.mycompany.com and mailman.mycompany.com, both of which returned an IP of 192.168.1.1. I did a lookup on the IP and it resolved back into server.mycompany.com.
Figuring I'd accomplished enough for the first half of the day, I went to lunch. When I got back, I was bombarded with complaints that mails were being bounced when sent from inside the building, and a few people had received phone calls that mails sent to them had been bounced back to their senders. The error given is:
554 554 <[email protected]>: Relay access denied (state 14).
(This came from Google. The wording varies from person to person but it's always SMTP 554, relay access denied.)
In a panic, I un-did everything I'd done this morning, turning off DNS server, telling DHCP server to begin distributing our ISP's DNS IPs again, but I'm still having the same problem. I didn't see how this could be the cause, but did it just as a precaution.
I doubt I've provided enough information, but does anyone have any initial guesses as to what's going on here?
ARMThanks for the quick, easy fix. I'm curious if you know what I might have done to cause this to happen. I don't recall changing any Mail settings.
Sometimes Server Admin "forgets" settings.
Also, apparently something I did wiped out our IMAP mail store. I had a backup thankfully but wondering how I might have done that?!
Wiped out at the file level as in no contents in /var/spool/imap/user? -
Newie Mail server and running other services
We have a small office network of 6 macs that connect to a Panther server, this server provides DNS and file sharing and thats about it a Filemaker Sever and Retrospect Server. I doesn't suffer from heavy use
I have been using a a separate mac to run Quickmail server 1 (os9) and I need to upgrade it as some of the mail protocols are out of date.
We have a static IP address assigned to our mail gateway by our service provider.
My question or advice
Should I just start using OS X server to run mail services
or
Upgrade Quickmail and continue running it separately on a new mac mini (or similar)
My concerns are at the moment any problem with email locally can be solved pretty much without effecting the other server or the network.
ThanksThe basic setup is prety simple...
Replace following with your own equivalents...
Domain name: woopee.com (the domain name after the "@" in your emails)
Host name: mail.woopee.com (the hostname your MX record points to. Does not need to match server hostname. This will be the hostname mail server uses when communicating with other servers)
Local Host Aliases: woopee.com (a list of the domains you want to accept mail for. Probably just same as Domain name?)
Local network: 192.168.10.0/24 (LAN IP range for local users. Used to bypass authentication when they send mail out)
Server Admin-> Mail-> General...
Tick:Enable POP
Tick:Enable IMAP
Tick:Enable SMTP, Allow incoming mail, Enter Domain name & Host name (from above).
Mail-> Relay
Tick: Accept SMTP relays... Enter localhost IP: 127.0.0.1/32 and Local network (from above).
Tick: Use these junk mail rejection servers. Add: zen.spamhaus.org
Mail->Filters
Tick: scan for junk mail. Minimum score: 5 (can be reduced later)
Junk mail should be: Delivered (will just tag and forward to recipient)
Tick: Attach subject tag: * Junkmail *
Tick: Scan email for viruses
Infected messages should be: Deleted
Tick: update junk mail & virus database: 1 time per day
Mail->Advanced->Security
SMTP: none (this prevents smtp authentication from anyone outside your Local network)
IMAP: Tick: Clear, Plain, Cram-md5 (or leave all unticked if only using pop accounts)
POP: Tick: APOP
Mail->Advanced->Hosting
Local Host Aliases: Add: localhost & woopee.com (separate entries, see Local host aliases, above)
That's it (I think ...although I cannot guarantee I have not missed something). There will be no problem setting this up and seeing it going whilst still using the existing mail server. Set up client accounts to send and receive from new server and you can send mail around internally to test. Last thing would be to change your firewall port-forwarding for SMTP from existing server to new one.
Watch the mail.log in Console for any errors & do plenty tests.
Ensure users have mail enabled in Workgroup Manager.
There are plenty mods available beyond this. Have a good read through the mail services manual (I know its a bit confusing at times) and you should see where the above settings fit in.
Lots of stuff on the forum here which you can search for. Spam filtering in particular can be made far more effective but requires editing of the underlying unix configuration files - again, plenty of previous discussions about that on forum. Meantime, the zen.spamhaus.org RBL will filter out a great many spammers.
-david -
I can send but cannot recieve email
This is the messege I am gewtting:
There may be a problem with the mail server or network. Verify the settings for account “MobileMe” or try again.
The server returned the error: Mail was unable to log in to the IMAP server “p02-imap.mail.me.com” using “Password” authentication. Verify that your account settings are correct.
The server returned the error: Service temporarily unavailableAlso if I go to system preferences accounts and re-enter the password it fixes the glitch sometimes.
-
Need to have mail1 play nice with upstream mail server....
Switched to new mail server and hitting a problem. We have a debian linux box doing SPAM filtering further upstream from the mail server and then sending down to the new leopard mail1 box.
On the debian box we're seeing:
2009-04-03 09:14:08 H=216-174-222-148.atgi.net (email.wdcsc.org) [216.174.222.148] F=<[email protected]> temporarily rejected RCPT <[email protected]>: remote host address is the local host
2009-04-03 09:14:08 1Lpfar-0004fh-Ku ** [email protected] R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<[email protected]>: host nescosrv.nesco.ee [194.204.28.195]: 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in local recipient table
And mail isn't piping thru to the mail1 box. Here's the main.cf
sh-3.2# cat main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#mailbox_transport = lmtp:unix:/file/name
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = _postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
mydomain_fallback = localhost
message_size_limit = 52428800
myhostname = mail1.stanwood.wednet.edu
mailbox_transport = cyrus
mydomain = stanwood.wednet.edu
mailbox_size_limit = 0
enable_server_options = yes
inet_interfaces = all
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
smtpd_use_tls = yes
smtpd_enforce_tls = no
smtpd_tls_cert_file = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpd_tls_key_file = /etc/certificates/mail1.stanwood.wednet.edu.key
smtpd_sasl_auth_enable = yes
smtpd_use_pw_server = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_pw_server_security_options = gssapi,cram-md5,login,plain
content_filter = smtp-amavis:[127.0.0.1]:10024
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
owner_request_special = no
recipient_delimiter = +
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
# 02/02/09 Server Checkup by Alex
bounce_queue_lifetime = 6h
delay_warning_time = 6h
maximal_queue_lifetime = 2d
# Topicdesk Frontline Defense
disable_vrfy_command = yes
smtpd_client_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_rbl_client zen.spamhaus.org, permit
smtpd_helo_required = yes
smtpd_helo_restrictions = permit_sasl_authenticated, permit_mynetworks, check_helo_access hash:/etc/postfix/helo_access, reject_non_fqdn_hostname,reject_invalid_hostname, permit
smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_sender, permit
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_data_restrictions = permit_mynetworks, reject_unauth_pipelining, permit
virtual_transport = virtual
virtual_mailbox_domains =
sh-3.2#Right, what was happening is that it was a big loop. We had to modify our DNS and some other settings on the spam bucket... but... wondering if there's another solution...
mail1:~ admin$ postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
bouncequeuelifetime = 6h
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
delaywarningtime = 6h
disablevrfycommand = yes
enableserveroptions = yes
html_directory = no
inet_interfaces = all
localrecipientmaps = proxy:unix:passwd.byname $alias_maps
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
maximalqueuelifetime = 2d
messagesizelimit = 52428800
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
mydomain = stanwood.wednet.edu
mydomain_fallback = localhost
myhostname = mail1.stanwood.wednet.edu
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdclientrestrictions = permitsaslauthenticated, permit_mynetworks, rejectrblclient zen.spamhaus.org, permit
smtpddatarestrictions = permit_mynetworks, rejectunauthpipelining, permit
smtpdenforcetls = no
smtpdhelorequired = yes
smtpdhelorestrictions = permitsaslauthenticated, permit_mynetworks, checkheloaccess hash:/etc/postfix/helo_access, rejectnon_fqdn_hostname,reject_invalidhostname, permit
smtpdpw_server_securityoptions = gssapi,cram-md5,login,plain
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdsenderrestrictions = permitsaslauthenticated, permit_mynetworks, rejectnon_fqdnsender, permit
smtpdtls_certfile = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpdtls_keyfile = /etc/certificates/mail1.stanwood.wednet.edu.key
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550
virtualmailboxdomains =
virtual_transport = virtual
mail1:~ admin$ -
TROUBLESHOOTING TIPS RE: iCLOUD MAIL SERVER DROPOUT
Here's what I learned throughout this and I will post a discussion in a separate thread for the rest of the folk out there.
MYTHS AND FACTS RE: iCLOUD MAIL SERVER DROPOUT- WHAT I'VE LEARNED
Hopefully this troubleshooting helps everyone that has had or having issues, for now and for the future...
Firstly, the Apple system status is a bit of a myth. Because it is a global community of people using iCloud, it does not always update in real time. The Apple techs check this when there is issues, as do the public, so odds are unless every single person is having issues around the globe, then it won't reflect an issue. http://www.apple.com/au/support/systemstatus/
Apple technicians work in territories. For example, I live in Australia so I had to deal with a tech supervisor who looks after Australasia and who is based in Singapore. They don't get a notification if a group of people in Canada are having problems, even if they are identical to mine, unless as above, the whole world is having issues.
CHECK THESE FORUMS as a first step measure to work out if the problem seems to be just you and your account, or a wider community. Particularly before you make any major change to your email accounts, passwords, computers or phones.
If you get an issue in the next week or so (and keep in mind for the future) Error Message: "MY NAME" returned the error "[AUTHENTICATIONFAILED] Authentication failed." Your username/password or security settings may be incorrect. Would you like to try re-entering your password?" and this happens multiple times when you know the password is correct, then odds are that the server is down and you are best to wait it out. Try checking your mail via iCloud to test. If you can send it through there, odds are that the glitch has nothing to do with your password or issues with your account and rather than make changes, try and wait it out.
If all of your folders in your email disappear, if they are IMAP folders, then log into iCloud mail in your web browser to check that they are still there. It just means that your mail client (Mac Mail, Outlook for Mac etc) can't access the IMAP folders via the server. Don't panic until they are gone from every device you use your email on.
Be wary of deleting ANYTHING from your computer unless you are backing it up first. For example, I had a tech guy on the first day of the server drop out, who gave me the wrong advice of deleting EVERYTHING from my keychain. This resulted in me having massive security issues for web browsers and thus, I couldn't log into my iCloud mail in my browser. Not only did I have to re-install my OS Maverick to fix it (which took 10 hours) but I could have muddled through this mess by continuing to work using web mail.
If everyone seems to be having a mail server problem based on online community discussions, then you are not alone and TELL your Apple tech this. Send copies of the links to the various conversations. Push them (nicely) to investigate internally what is going on and don't let them rely on the System support status. It also helps to put in a report to Apple down the track.
Make sure that you can get a copy of Apple tech guys email address. Thankfully, even though I was on the phone to them for in excess of 7 hours over the past two days, I could update my guy via email and also send him screen shots of things that did or didn't work using my iPhone. We would keep in contact and all I would have to do is send him an email and he would call me back straight away. No holding or dealing with any call centre issues, which is probably the only reason why I didn't lose my cool too much.
If you can get into your iCloud through your web browser, you have the options under the inbox and then the little wheel thing down the bottom (preferences) to put a vacation message, like an out of office. Put that on and explain you are having email issues and give another email address or your contact number. At least the people that you need to contact will know that things could get lost in cyberspace. I wish I had of known this earlier.
You can also forward emails emails to another email address under preferences. Also very handy.
Become friends with your tech guy rather than enemies. If you don't feel like your tech guy knows what he's talking about, politely request to speak to a supervisor. I would be having a nervous breakdown right now (small business owner, lost two days of billable hours so I am financially behind) if I didn't have a good relationship with the guy that has been helping me. We are a good team, with me updating him with the information, via these forums, to find a proper solution to the issue and to rectify the wrong information I was given by the previous Apple tech guy I spoke to.
Ask them to replicate your issue on their side of the fence to troubleshoot. For example, my tech guy Levi replicated my issue with websites by intentially removing the system certificate from his computer and he realised that was what the problem was, and thus he could quickly find out how to fix it.
Back up your stuff regularly. It might be annoying but it is peace of mind if know you are only going to lose a minimum of a week's worth of stuff.
Apple has an engineering team and tech guys raise 'tickets' to them with information on what has happened to their clients. I don't know much about this but I would assume it is having the engineering team investigate to stop this happening in future. They can only work with the feedback they get I suppose. I would also suggest doing the Apple Care survey so they also get feedback. We need to explain to them that we are asking for communication first and foremost - whilst it is inconvenient, if we all knew when and where they would be doing server upgrades (which the rumours indicate that this is what happened) then I don't feel everyone would be so frustrated.
Using your computer is like raising a child - you know when something is not right, even if you are not experienced at it yet. Sure, you may not know the lingo but trust your instincts and tell your tech guy. I have learned more in the past two days about computers and Mac's than ever before and I know when I can confidentially say that strange things were happening to my Mac and where Apple went wrong in guiding me. Don't always take a blanket or easy explanation if you don't think it is right; odds are it will result in making changes to your product that do more harm than good.
Keep a record of notes of how much time you have spent on the issue (including phone calls to Apple), what they have told you to do and at what time, changes to passwords, troubleshooting tips and the contact details (and reference numbers) of who you speak to. I'm not sure if Apple provides compensation for these issues or anything along these lines, but I certainly will be informing them so they can try and better their service to me in the future.
Anyway, I hope that helps everyone a bit - these are just things that I have learned and if anyone else has any tips please feel free to add them.Tried port 465 but it wouldn't work.
Went to our help desk and here's the reply I got (paraphrased slightly cuz the person at the help desk was trying hard to be helpful and I don't want to get him/her in trouble):
I presented this question to the university team and then waited for a long time to get the following reply:
we do not allow relay from non-university IP addresses.
port 25 for smtp is a standard worldwide.
For the most part, that went right over my head and didn’t answer anything, but I hope it means something to you.
I called him to get more clarification, but all I really got out of it was that, if you don’t use exchange which is secure via port 443, then your other option is to use smtp. And then he said something about how relay, iron ports, and authenticated accounts work together to make it secure. I know it makes me sound a lot more inept than I am, but all that made little sense to me. What I gather, is… that by selecting SSL when configuring your client, it makes it so that your login info and mail content is safe. Sorry, I can’t provide a more cohesive and comprehensive explanation, but I think the bottom line is that they have combined a non-secure protocol with other stuff to make it secure.
So, I'm hoping that checking SSL and using port 25 somehow solves the problem to the satisfaction of our IT professionals at the University ...
Again, thanks for taking the time to educate the rest of us! -
When trying to update my Mail Account Mailbox Behaviours settings, after making the changes when I try to close the settings pane the following messages occur: Invalid Incoming Mail Server The “Incoming Mail Server” field cannot be empty. The incoming mail server box has in light grey colour: p02-imap.mail.me.com in it and I cannot edit its content. Any ideas what is going on and how to fix it?
Hi all,
Mattreichenbach is probably on the right track here with a reset of settings. I think I've determined the issue has to do with cached account information and inconsistencies for the account name. This seems to crop up when I've changed my password and it hasn't propagated fully to all the servers, devices, certificates, etc.
Hopefully many here are on their way to restoration of service by now but it's clear that a lot of people are having the same issues. Very frustrating and definitely something Apple needs to resolve: incoming mail server field grayed out, incorrect autopopulation of different fields, other unanticipated behaviors. If you're still having issues, though, here's what worked for me...
First, head to the iCloud preferences pane in System Configuration and choose "Sign Out". When I did this it prompted me with a number of "are you sure" type questions about retaining information on my local machine. I chose to delete/remove the info each time simply because it should all be restored by the cloud and I didn't want to risk a massive duplication of my data... I will say, I'm back up and running with no issues so I suspect you can make the same delete/remove choices... But use your own judgment. I don't want you to lose any data (ie.. please use care as you do this because I cannot bear the thought of causing anyone to experience the pain of data loss).
Once you've signed out of iCloud, restart your system. When you get back in, head to the Mail, Contacts and Calendars section of your System Preferences and add your account back by choosing the brushed aluminum "iCloud" button. When it asks for your account name, use your @iCloud.com email address. I am all but certain my issue had started because one of my devices (iPhone or whatever) had been set up with an email alias specified instead of my @iCloud.com address.
Apple, if you're reading through any of these issues (there are TONS of users having this same problem). Take note, that your icloud service somewhat frequently is not responding and yet tells the user that the password is wrong and this prompts people to be changing their passwords unnecessarily. This has happened to me on numerous occasions. Also, I noticed that last week's outage corresponded to a VERY similar outage exactly one year ago to the day. Sounds like planned maintenance to me and I think you could do a better job notifying folks so we're not wasting HUGE amounts of time troubleshooting a problem that we have no hope of fixing.
Hope that helps some of you!
Terry Mullane
Washington, DC -
I had over 200 e-mails. I went to my webmail and deleted most of them. However, my iPhone still shows 200 e-mails. How can I force my iPhone to update from the e-mail server? Or will I have to delete each e-mail from my iPhone as well? Thanks.
You may have to try deleting all the music from your phone (by going to Settings>General>Usage>Music, swipping All Music and tapping Delete), then sync it all back on with iTunes in order to fix this.
Maybe you are looking for
-
Hangs iTunes unless using USB 1.1
I'd like to add my voice to the numerous problems on this forum with connecting and syncing the Shuffle with iTunes. While my Shuffle has been flaky as long as I can remember, it's pretty much unusable with iTunes 8. In those moments of bliss when I
-
Which MBP features best for Final Cut?
Hi folks. I need to buy a MacBook Pro that will be used primarily to run Final Cut Pro (and the other FC Studio programs). Can anyone help a fairly tech-unsavvy consumer understand which processing/memory features will have the most impact on FCP per
-
I tried deleting and re-entering the accounts, but problem with sent folder still occurs
-
XSL function or code for ASCII conversion ?
I am a newbie in XSL and I tried searching and didn't find a XSL function to convert ASCII values in an XML to its equivalent alphanumerals using XSL transformation. Is there a XSL function to do the same ? Any suggestions would be really helpful.
-
Brand new OS upgrade and I still can't get rid of
all of those crappy, redundant inboxes. Why Apply, why? They're in the way. They provide no advantage to many of us. I always have to scroll past them to get to my actual email accounts. Why Apple, why?