Mailbox backup on mail server
Hi,
can anybody tell me how a server based backup of individual mailboxes (done by an administrator) and the related restore is supposed to be done? Server is 10.7.4 with no third party software.
BTW: if an Open Directory user account gets deleted accidently and a new account with the same name and UID, but a different OD identifier (which seems to be used by dovecot) is created: how do I transfer the mail between them (meaning there dovecot IMAP stores)?
Kind Regards
COWegner
Hi Sultan,
1. Create a directory for storing the backup files
2. Modify the parameter "config_backup_path" in the config.inp.
3. Then run the following command:
bkp_restore.sh -m configure
Regards,
Prakash.
Similar Messages
-
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 -
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 -
The junk mailbox could not be created on the mail server
I'm getting this error message on a few of my clients. Mail.app doesn't seem to want or is not able to create a mailbox on the imap server. I can manually create a whole bunch of folders but for some reason it won't create the junk mail folder. I can't find any errors in the cyrus logs that would indicate a problem with creating the mailbox. It insist on creating a local mailbox for SPAM but i'm not interested.
Any ideas? Google search as well as this forum have come up empty...I think I just figured this out -- unfortunately, I don't have a solution. I'm having the same problem trying to create the junk mail folder on the server, so I fired up WireShark (a network sniffer) to see if that would reveal anything. Sure enough, it looks like Mail.app is trying to use an invalid name when creating the mailbox. When I try and move a message into the Junk mail folder, here's the IMAP transaction I get, my notes are in brackets:
[... truncated ...]
13.3 CLOSE [Mail.app -> Server]
13.3 OK Completed [Server -> Mail.app]
14.3 CREATE "Junk (Corp Mail Server)" [Mail.app -> Server]
14.3 NO Invalid mailbox name [Server -> Mail.app]
15.3 SUBSCRIBE "Junk (Corp Mail Server)" [Mail.app -> Server]
15.3 NO Subscribe: Mailbox does not exist [Server -> Mail.app]
16.3 LIST "" "Junk (Corp Mail Server)" [Mail.app -> Server]
16.3 OK Completed (0.000 secs 1 calls) [Server -> Mail.app]
17.3 NAMESPACE [Mail.app -> Server]
[... truncated ...]
It looks to me like it's trying to use the name of my mail profile in the name of the Junk folder, and I bet the IMAP doesn't like the (parens) ... looks like a bug to me.
Hope that helps
Swannie -
I'm using OS 10.4, Mail. Accessing IMAP accounts on mail server. The server mail boxes are filling up and bouncing mail. How can I archive the old mail on my computer and delete it from the server to make room for new mail? Will creating an archive mailbox "on my mac", copying old mail from my inbox to the archive mailbox, deleting the old mail from my inbox and then synchronizing with the server work? Will moving the old mail to the archive mailbox work? Thanks in advance for any insights.
Great news, thanks!
-
Can MoveUser move a user's mailbox from an installation of Mail Server 2.X to Messaging Server 3.X?
Can MoveUser move a user's mailbox from an installation of Mail
Server 2.X to Messaging Server 3.X?
<P>
Yes.
The 2.x server allows the postmaster to login to a user's account.
Try running MoveUser as follows:
MoveUser -u uid -s host -xPostmaster:uid -p password
-d desthost -a proxyuser -v proxypassword -m mailboxpath
Notes:
Mail Server 2.x uses a local database and not an LDAP server
for account information. The -l option
specify ldap URL and the associated bindDN password,
therefore, are not valid when moving from
Mail Server 2.x to Messaging Server 3.x.
"Postmaster:" is case sensitive.
The -a and -v options are for Messaging Server 3.x
ProxyAuthUser credentials.
We do NOT allow this login to a 3.x server
(use PROXYAUTH instead).Additionally
When I type in fasn26p (machine name) the Oracle Application Server Welcome page displays.
I can get to the Enterprise Manager via the link on the page.
On the All Programs menu, under Oracle - OraDb10g_home1 I can access the Datbase Control page and login. The line for Database Instance: Orcl is -
http://fasn26p:1158/em/consol/database/instance/sitemap?event=doloa&....
One last thought. I installed this with this on my network at home and I now have it disconnected from the network. So no IP address for the adapter and I wonder if that can cause a problem with Apache?
Sam -
Lion Server: how best to backup user mail?
What's the best way to backup user Mail on Lion Server?
Currently I do a nightly rsync of the /Library/Server/Mail directory to another off-site machine, but it strikes me that I'm not entirely sure (a) if this is capturing all necessary info, and (b) even if it is, how precisely woudl I go about restoring user mail if, for example, the server blew up and I had to reinstall a new machine?
Thanks for any advice,Another method would be to do regular copies / clones of your mail directory using Carbon Copy Cloner - I actually do this with the server boot volume regularly.
-Doug -
The sent mailbox could not be created on the mail server.
Complete message says:
The sent mailbox could not be created on the mail server. The local "Sent Messages (mail)" mailbox was created instead. Mail has changed your account's Mailbox Behaviors preferences to use the local "Sent Messages (mail)" mailbox.
I am using a gmail account with my own domain. Any ideas how to fix it?Menu: Mailbox -> User This Mailbox For
First, select folders of your IMAP account, and map them to different common folders. -
Interesting db mail issue. If i click send test mail from sql mgmt studio, it works fine, but when i execute a SP to send a mail, it fails. One thing I noticed is that the "LastModified" column in the mail log shows the domain account when a test
mail was sent from mgmt studio, but show "sa" when the SP was used to send mail.
This is from SQL 2012, did not see this in sql 2008, looks like 2008 always used the service account. any ideas ?
Get this error:
The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 1 (2013-04-30T16:36:52). Exception Message: Cannot send mails to mail server. (Mailbox unavailable. The server response was: 5.7.1 Client does not
Thanks.
RangaHi Ranga,
I also use SQL Server 2012. I send a test email through SQL Server Management and the last modified By “sa”.
If you used stored procedure to send a test email. Please use the command below:
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'Adventure Works Administrator',
@recipients = '[email protected]',
@body = 'The stored procedure finished successfully.',
@subject = 'Automated Success Message' ;
I can both send test email through SQL Server Management Studio and SP. Make sure you have the right profile. Since you could send test mail via SQL Server Management Studio, please try again to send it via SP.
Thanks.
If you have any feedback on our support, please click
here.
Maggie Luo
TechNet Community Support -
If I move a mailbox from my imap account to "on my mac" can I safely delete the folder from the mail server and still be able to read the messages?
You certainly can.
Be aware that the emails you move to local storage ("on my Mac") will be the only copies that remain. -
Mail.app mailbox selecting incorrect outgoing server
I have never run into this issue before and I am racking my brain trying to figure out how to fix it.
As of yesterday, my primary email account is using a secondary outgoing email server by default. The only way to prevent this is to manually select the primary email account after I open the email.
For example:
My mailboxes look like this (four accounts, all iMAP):
One
Two
Three
Four
When I select "One", the new email window opens as if I have selected mailbox "Two". It's defualting to "Two". If I delete "Two's" outgoing smtp information, "One" will open as itself. If I open "Three" or "Four", they open as their own default mailboxes.
In Mail preferences > composing, I have it selected to "Open as selected account". When I change it to "Open as 'One'", then mailbox "One" will open as "One". When I change it back to "Open as selected account" it goes back to opening mailbox "One" as mailbox "Two".
All of my Account Settings in preferences are set up identically. They are 4 different iMap accounts using mail.smtp.com as their outgoing server with their own SSL and username/password authentication.
I have googled the issue in every way I can think to word it and have found similar issues, but none of the fixes for those seem to solve my problem. Any help would be greatly appreciated.I have this same problem - and it is a big problem! Why can't I select the right mailbox for my email to come from any more either? Is someone from Apple looking at this?
-
Hi,
I'm not sure if it's the right section of the forum but it seems to be the most appropriate.
My question is: It's possible to setup a mail server that downloads mail from different mail accounts (given by Isp) and store them.
I need this because the space in the mail account is ridicolous.
It's possible also to let users download email from this local server instead from the Internet?
Thanks
Asterhexfukawi2 wrote:IIRC, fetchmail needs a local MTA (such as postfix) to deliver the mail to, so you would need postfix also. (I stand to be corrected)
Aha - I think that's where exim4 comes in on our network... We certainly don't have postfix installed, but we do have fetchmail fetching our mail. I have read somewhere that getmail is a lot easier to configure than fetchmail, so it is possible you don't need an MTA with getmail.
If the OP'er will be checking the mail only locally, there is not really a need for an IMAP or POP-server (like dovecot): most email clients can handle plain maildirs. I have no experience with this, so I don't know if this is a workable suggestion or not.
/EDIT: The getmail documentation states explicitly that it can deliver email locally to an mbox or maildir without the need of an MDA or MTA.
Last edited by zenlord (2010-09-30 09:09:05) -
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. -
Need to have mail1 play nice with upstream mail server....
Switched to new mail server and hitting a problem. We have a debian linux box doing SPAM filtering further upstream from the mail server and then sending down to the new leopard mail1 box.
On the debian box we're seeing:
2009-04-03 09:14:08 H=216-174-222-148.atgi.net (email.wdcsc.org) [216.174.222.148] F=<[email protected]> temporarily rejected RCPT <[email protected]>: remote host address is the local host
2009-04-03 09:14:08 1Lpfar-0004fh-Ku ** [email protected] R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<[email protected]>: host nescosrv.nesco.ee [194.204.28.195]: 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in local recipient table
And mail isn't piping thru to the mail1 box. Here's the main.cf
sh-3.2# cat main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#mailbox_transport = lmtp:unix:/file/name
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = _postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
mydomain_fallback = localhost
message_size_limit = 52428800
myhostname = mail1.stanwood.wednet.edu
mailbox_transport = cyrus
mydomain = stanwood.wednet.edu
mailbox_size_limit = 0
enable_server_options = yes
inet_interfaces = all
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
smtpd_use_tls = yes
smtpd_enforce_tls = no
smtpd_tls_cert_file = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpd_tls_key_file = /etc/certificates/mail1.stanwood.wednet.edu.key
smtpd_sasl_auth_enable = yes
smtpd_use_pw_server = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_pw_server_security_options = gssapi,cram-md5,login,plain
content_filter = smtp-amavis:[127.0.0.1]:10024
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
owner_request_special = no
recipient_delimiter = +
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
# 02/02/09 Server Checkup by Alex
bounce_queue_lifetime = 6h
delay_warning_time = 6h
maximal_queue_lifetime = 2d
# Topicdesk Frontline Defense
disable_vrfy_command = yes
smtpd_client_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_rbl_client zen.spamhaus.org, permit
smtpd_helo_required = yes
smtpd_helo_restrictions = permit_sasl_authenticated, permit_mynetworks, check_helo_access hash:/etc/postfix/helo_access, reject_non_fqdn_hostname,reject_invalid_hostname, permit
smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_sender, permit
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_data_restrictions = permit_mynetworks, reject_unauth_pipelining, permit
virtual_transport = virtual
virtual_mailbox_domains =
sh-3.2#Right, what was happening is that it was a big loop. We had to modify our DNS and some other settings on the spam bucket... but... wondering if there's another solution...
mail1:~ admin$ postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
bouncequeuelifetime = 6h
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
delaywarningtime = 6h
disablevrfycommand = yes
enableserveroptions = yes
html_directory = no
inet_interfaces = all
localrecipientmaps = proxy:unix:passwd.byname $alias_maps
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
maximalqueuelifetime = 2d
messagesizelimit = 52428800
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
mydomain = stanwood.wednet.edu
mydomain_fallback = localhost
myhostname = mail1.stanwood.wednet.edu
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdclientrestrictions = permitsaslauthenticated, permit_mynetworks, rejectrblclient zen.spamhaus.org, permit
smtpddatarestrictions = permit_mynetworks, rejectunauthpipelining, permit
smtpdenforcetls = no
smtpdhelorequired = yes
smtpdhelorestrictions = permitsaslauthenticated, permit_mynetworks, checkheloaccess hash:/etc/postfix/helo_access, rejectnon_fqdn_hostname,reject_invalidhostname, permit
smtpdpw_server_securityoptions = gssapi,cram-md5,login,plain
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdsenderrestrictions = permitsaslauthenticated, permit_mynetworks, rejectnon_fqdnsender, permit
smtpdtls_certfile = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpdtls_keyfile = /etc/certificates/mail1.stanwood.wednet.edu.key
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550
virtualmailboxdomains =
virtual_transport = virtual
mail1:~ admin$ -
Mail Services and Backup MX/mail services
I have a question regarding backup mail services and acceptance of incoming messages.
As of last week, I am new to the world of Mail Services in OS X Server 10.4. Last week, our current email server died and I was forced to take an Xserve G4 that had OS X Server 10.4.10 (unlimited) and setup mail services in order to receive and send mail. I went to a website called osx.topicdesk.com and followed their instructions for front-line spam defense and clamAV updating (and switching to clamd) which all appears to be working OK.
Because our old email server was having some hardware issues for the past several months that I had been working on, I had the feeling that failure might happen. So what I did a few months ago was sign up for Google Apps and their mail service. I added their MX records under my primary mail server so that in the case of a failure of my server, all mail would be passed to Gmail and everyone could get to their mail immediately (as any prolonged downtime won't work since this is a daily newspaper). This did work, for when my old server died, all the mail went immediately to the appropriate Google Apps mail accounts. After about a day of setup on the Xserve, I got the mail services running OK. I gave it all the same IP info as the previous server so that the mail would just start working without having to edit DNS records and such.
The problem I am having seems to be this: While I get most mail, some of my mail is still getting sent to the Google Apps accounts. For example, I have one user, Jane Doe, at [email protected] who gets most of their mail from connecting to the OS X Server, but about 2 - 3 emails a day get passed over to the Google Apps server. I have run DNSStuff.com tests on the mail connections, and I always get a good fast response out of the OS X server. My thinking was that mail would only be passed over to backup mail servers if the first server listed in the MX records was unavailable or offline. In all of my testing, my server has responded every time. The server is connecting via a gigabit network connection (good response), is a dual G4 1.33Ghz, 60GB hard drive with 2GB of RAM. This server doesn't do anything else except run Mail services (and web services for squirrelmail), it doesn't even have file sharing turned on.
My old email server was a Pentium II 400mhz with 348MB of RAM, and it caught all mail, so I know that the Xserve should be able to handle the load without being busy. Is there any reason that my Xserve would be rejecting mail and they would be siphoned off to the Google accounts?
Is this even a possible scenario to fix the problem: Setup a backup MX "queue" account somewhere with one of the BackupMX online services that will catch these stray emails and then send it back to the primary server? But then can be turned off quickly to allow mail to go to the Google Apps accounts if my server went down. In other words, the DNS record would show my primary as 1, the backup mx service as 2, the google servers as 3, 4, 5 and so on. Can Backup MX services be turned off quickly like that so that if my server is down and I need email to be accessed immediately then just "turn off" the service (without modifying the DNS since that will take too long to propogate) so that mail bounces over to Google immediately?
I guess my first troubleshooting attempt should be to figure out why my OS X Server is not accepting all mail.
Thanks in advance for any help and suggestions.
GWhen I first started with the company about 2 years ago, they had a really old Linux box (about 10 years old) that was used to host email. It was horrible. It would run OK, but if it ever went down or had a hiccup, it was an all-day project trying to deal with it. Unfortunately, the company did not want to spend any money on a new server or software of course. The answer I got was "well, it's just email". Sure, but if email EVER goes down for more than 15 seconds, all of the employees go into seizures and scream that the place will have to shut down. I work for a daily newspaper, so everything is running 24/7.
Knowing that one day that box was going to just die, I looked into some backup MX services. As pterobyte had mentioned is that with a secondary MX, the problem is that no one can get their mail at all until the primary server comes back up. I knew if that server ever went down, I had nothing to take its place, so I would have to order something or get a server from another location to use. Being unfamiliar with OS X Mail Services, I knew it would take me awhile to try to setup all the users and such. All the while at the newspaper, they would be screaming bloody murder that they needed email working for news, ads coming in, etc. And when I say if it goes down for 10 minutes they start getting into fetal positions in the floor screaming, I'm not far off exaggerating. I figured I was going to need something in place for them to check email while I worked on the primary.
Back in September/October 2007, I discovered that Google hosted free mail services call Google Apps. With Google, I could setup "matching" accounts and would still be able to use my domain name. You just had to use Google's servers as the higher numbered MX records. Luckily, I set up in time for back in November, the Linux box finally died. When it did, all email successfully went to their counterparts on the Google's servers. I had everyone go to the special Google Apps login site and they were able to check their email fine. I ended up having to take a box from another site and then I had another copy of OS X Server 10.4, so I loaded it and successfully setup email (with lots of help from pterobyte's tutorials). They were on Google's systems for about 2 days.
After the disaster, I went around and setup IMAP accounts on everyone's Thunderbird clients so that if our email server went down, they just simply check that mailbox. The nice thing with the Google IMAP is that they automatically see if emails are hitting that inbox from within their client. Right now, it still remains that the 2 original companies that hit the Google accounts still do. The city government email and email from a sister newspaper. Everything else gets directed to the primary server. Although sometimes that doesn't even work, as tonight I am having to work on a problem involving the Clamd app acting up - taking up nearly 100% of the CPU which in turn caused all the mail to be hung up in the queue. So since the mail server didn't "reject" the mail and grabbed it, their gmail "backup" didn't get anything in it. It was taking me forever to figure out what was going on, so I almost just told them to unplug the network cable from the email server so that everything definitely would be forwarded to gmail.
My wish is that I had a secondary mail server in house to not even worry about it - or better yet, I wished I could just outsource the email administration itself to someone else (like webmail.us which is now MailSafe). That way for the most part, they wouldn't lose email. But of course, the company doesn't want to spend the money or invest. Just gripe when the older equipment we have won't support what they want to do with it.
But the story above explains why I did what I did with the Google's servers. I do appreciate everyone's help and input on this particular problem. I am going to look around at the DNS and talk to at least our sister newspaper to see if I can see how they have their DNS setup.
Thanks!
G
Maybe you are looking for
-
Touchscreen Laserjet pro 200 color MFP M276nw
I have a HP laserjet pro 200 color MFP M276nw since 2 months. Since yesterday the touch-screen does not reacts anymore when I select an item. I just can touch the help icon, the home icon and the return icon. But when the touch screen is in sleep-mod
-
How can I get my music back onto my iPhone from the the cloud
I have a new primary PC. My music Library is on an old dying laptop. I have found all my music has disappeared from my phone. Some is on the cloud, but it appears to only be the music purchased on iTunes, only about 1/3 of my collection. Now I fi
-
Process of updating library and vaults?
Hi, I am wondering what the process is for updating the library and vaults? Does it require a substantial amount of time? I am also wondering about making a duplicate of the library prior to upgrading(power failure, bugs, etc.), to save having to reb
-
Hi All, Do SAP provide us with standard template for BW documentation in projects like blueprint, test script, data modelling, etc ? Please share. Thanks.
-
Total compensation Statement Error
Hi Experts, "Total compensation Statement" was working in Dev and Quality system. I have transported all request to Production system. after Tranporting Production its giving error "Error displaying Form" in portal. how to rectify this problem? give