Form Mail - server scripts

Howdy all,
I use DW 2004MX. If this topic has been addressed before, I'm
sorry. I am trying to make a very simple form mail work on my
website; name, address, phone # and send. I know for a fact there
are two types of form scripts on my server, and both are activated.
One is a CGI (gdform.cgi), and the other is a PHP (gdform.php). My
server is Godaddy if that matters. I have read many messages about
form mail, but cannot find out how to MAKE IT ALL WORK. I have been
looking for a step-by-step answer, but no luck so far. BTW, I am a
newbie. The manual I have is "aftermarket", and is near useless for
the form mail stuff. The web address is www.azaleatrail.com
Any help would be greatly appreciated,
Thanks,
MonaLisaWest

> One is a CGI (gdform.cgi), and the other is a PHP
> (gdform.php). My server is Godaddy if that matters.
my suggestion from trying to sort out questions from others
hosted with go
daddy- don't bother with either of those scripts.
I assume that you can use php files within your site?
If yes- i suggest this script:
http://boaddrink.com
-->phpformmail
the instructions are in the zipped folder.
short list of instructions i suggest (use your own info of
course)
http://groups-beta.google.com/group/macromedia.dreamweaver/search?q=alan+php
formmail+edit+recipient&start=0&scoring=d&
1)go to
http://boaddrink.com
-->phpformmail
download it.
http://www.boaddrink.com/projects/files/phpformmail/phpformmail_class...
.2.zip
extract the ZIP file.
2) open formmail.php in dreamweaver
Make the following changes (in code view, turn line numbers
on)
2a)
line 4,
define('CHECK_REFERER', true);
change to:
define('CHECK_REFERER', false);
reason: too many people use a firewall or Norton security to
restrict this.
2b)
Line 43
$referers = array('www.example.com', 'example.com');
change to the url address of your web site.
reason: this probably isn't needed since we just turned the
referrer
checking off. but change it anyway.
2c) *********this is the hard-coding of the recipient address
into the php
file, where it is totally invisble**********
Line 46
$recipient_array = array();
change to:
$recipient_array = array('me' =>
'[email protected]);
**put YOUR email address in to replace
[email protected]
reason: this sets the email address the form results will be
sent to.
3) now do a File-->Save As and save this file to within
this Local Site
folder.
4) in dw's File Panel, find formmail.php and upload it to the
remote site.
5) Now open your form html file in dreamweaver,
5a)click the mouse into the form area, and select the
<form> tag on the
lower left margin of the design window.
In the Property Inspectory, it should now show the properties
of the <form>
tag. In the Property Inspector, to the right of the ACTION
line, click the
folder icon and browse to and select the copy of the
formmail.php file
you've saved to within this site.
5b) now go to dw menu-->Insert-->Form
Objects-->Hidden Field
This inserts a hidden form field.
In the property inspector, change the NAME of this field to:
 recipient
And the VALUE of this field to:  me
the code should look like:
<input name="recipient" type="hidden" id="recipient"
value="me">
6) Save and upload the form page.
Try the form from the website.
Optional:
make a new page for a thank you for submitting message.
In the form, insert another hidden field.
Name:  redirect
Value:  the full absolute
http:// address to the new thank you page.
There is other information about that script in the Docs
folder.
Alan
Adobe Community Expert, dreamweaver
http://www.adobe.com/communities/experts/

Similar Messages

  • Is there a way to have your PS script Query the name of your local Mail Server?

    Hey Guys, 
      Really hoping someone can help me out here. I am currently working on a script that Automates the entire user creation process (AD account, Exchange Mailbox, UCM Soft phone). I want this script to be universal for all systems I have to work with.
    By this I mean that I can run the script on various systems (Different Domains) without ever having to modify the code. 
      I have run into a bit of a problem while trying to automate the PSSession component of my script. I would like to be able to run he script and it inserts the relevant Mail server name based on some sort of Lookup or query. I am currently circumventing
    the issue by having a text box pop up asking for the mail server name. It works, but its not really what I want for the end product. Its frustrating seeing as I have overcome similar issues for things like UPNs, AD Server, etc....
       I have though about having it pull from the DNS MX records, but there are a number of different records for different Mail servers.
      Any help would be awesome!

    Notice that this has drifted a whole long way from the original question.  I pointed out that it is easy with Exchange but if the servers are in different companies or are not part of an enterprise deployment then you need to look at the local AD and
    seek to the top. Any one mailbox wwil get you an exchange server to remote into and use the exchange shell to discover the network.
    ¯\_(ツ)_/¯
    Looking back over the thread, that may be my fault.  I mistook the comment about checking MX to mean he's just looking for a mail relay. 
    [string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

  • PHP Form Mail Scripts

    What is a good resource for pre-made PHP Form Mailer Scripts.
    This is for use with a website hosted on GoDaddy.
    My client has a few requirements that the GoDaddy script does
    not offer (and the script I chose from GoDaddy is uneditable). I
    know nothing about scripting but thought I could use a pre-made
    script and modify it...is that crazy thinking on my part?
    Here are the special requests from my client:
    - They'd like to see the time the form was submitted in EST
    (the GoDaddy script puts the time in military time in another time
    zone in the subject line). Can this appear in the body of the email
    as well as the subject line?
    - They'd like the form to be sent to the person submitting it
    as well as to their company
    - They would like to be able to REPLY TO the email they
    receive with the form submission and have it be addressed to the
    person submitting the form. The current script has the email
    addressed to themselves (the company) if they click REPLY TO, so
    they are replying to themselves
    - Although this has nothing to do with the Form Mailer script
    as far as I can guess, they asked that the person filling out the
    form be able to print it prior to submitting (in my opinion,
    though, if i can have a copy of the submission sent to the
    submitter, there's no reason for this). But if anyone knows how to
    do this, please let me know.
    - Finally, the client wants to know if each submission can
    have a unique tracking number assigned to it.
    Thank you all. Any feedback is appreciated.
    Richard

    Hi,
    I can without any doubt recommend Forms 2 Go:
    http://www.bebosoft.com/products/formstogo/index.php
    Very easy to use and even someone like me who don't know a
    lot of
    programming, use it extensively.
    Deon
    "RichyZee" <[email protected]> wrote in
    news:gcvkac$fcp$[email protected]:
    > What is a good resource for pre-made PHP Form Mailer
    Scripts. This is
    > for use with a website hosted on GoDaddy.
    >
    > My client has a few requirements that the GoDaddy script
    does not
    > offer (and
    > the script I chose from GoDaddy is uneditable). I know
    nothing about
    > scripting but thought I could use a pre-made script and
    modify it...is
    > that crazy thinking on my part?
    >
    > Here are the special requests from my client:
    >
    > - They'd like to see the time the form was submitted in
    EST (the
    > GoDaddy
    > script puts the time in military time in another time
    zone in the
    > subject line). Can this appear in the body of the email
    as well as the
    > subject line?
    >
    > - They'd like the form to be sent to the person
    submitting it as well
    > as to
    > their company
    >
    > - They would like to be able to REPLY TO the email they
    receive with
    > the form
    > submission and have it be addressed to the person
    submitting the form.
    > The current script has the email addressed to themselves
    (the company)
    > if they click REPLY TO, so they are replying to
    themselves
    >
    > - Although this has nothing to do with the Form Mailer
    script as far
    > as I can
    > guess, they asked that the person filling out the form
    be able to
    > print it prior to submitting (in my opinion, though, if
    i can have a
    > copy of the submission sent to the submitter, there's no
    reason for
    > this). But if anyone knows how to do this, please let me
    know.
    >
    > - Finally, the client wants to know if each submission
    can have a
    > unique
    > tracking number assigned to it.
    >
    > Thank you all. Any feedback is appreciated.
    >
    > Richard
    >
    >

  • How to Set a Form Mail Address

    I have a form all set up on a web page in DW and what it's
    supposed to do, but I don't know where the field is to put my
    e-mail address for the form to send the info to. I tried putting it
    in "action", but that's not it as a test to see if I'd get anything
    failed. So, where
    do I put my e-mail?

    There are only two ways to process form data -
    1. Use mailto:[email protected] as the action of the form
    2. Use a server-side scripting method to a) harvest the
    form's data, b)
    process it in some manner, e.g., enter it into a database, c)
    formulate and
    send an email to one or more email recipients, and d)
    redirect the visitor
    to some ending page
    Method 1 is quite simple, and is also the least reliable. It
    depends both
    on your visitor having an email client already installed on
    their computer -
    this eliminates public computers, or home users without email
    clients
    installed (more and more it seems) - and on the installed
    email client
    responding to
    the mailto call. It is not possible to use this method *and*
    send the
    visitor to a
    thank you page as well.
    Method 2a is the preferred method, since it eliminates the
    problems of
    method
    1, but it means that you have to grapple with
    server-scripting somehow (ASP,
    CF, PHP, perl, etc.).
    Method 2b would be to use some third-party form processing,
    like
    http://www.bebosoft.com/products/formstogo/.
    You would have to decide which of these methods is best for
    your needs,
    but if it's Method 2a, then start by asking your host what
    they provide for
    form
    processing. If it's 2b, then read their FAQ/instructions
    carefully.
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    ==================
    "DanMat6288" <[email protected]> wrote in
    message
    news:fm3p7l$517$[email protected]..
    >I have a form all set up on a web page in DW and what
    it's supposed to do,
    >but
    > I don't know where the field is to put my e-mail address
    for the form to
    > send
    > the info to. I tried putting it in "action", but that's
    not it as a test
    > to see
    > if I'd get anything failed. So, where
    do I put my e-mail?
    >

  • Form Mail

    I have loaded form mail into my hosting account for
    juliashipley.com not sure which code to use don't need the ones
    that create a form so that leaves 2 a very short script which does
    not work and the other folder has a huge long script. Can someone
    point me in the right direction its the only thing holding my site
    up now.
    Many thanks
    Julia

    Hi Julie,
    Don't get discouraged :-)
    I took a look at your host's instructions. It looks like the
    script resides
    in a folder called hp_formmail or some variant depending on
    which script you
    pic.
    The instructions aren't very in depth.
    So, possibly another approach?
    Can you find out what server side language your hosting plan
    supports? It
    should say in your hosting information. Look for ASP or PHP.
    Do you have a Linux or Windows hosting plan?
    If it's Windows, I can help you with a very easy ASP page
    that you can just
    upload to the host into the same folder as your contact page.
    If PHP, there's lot's of pretty straight forward tutorials we
    can point you
    to.
    There is a chance your host or plan limits this, unlikely but
    with the
    sparse instructions on form mail I'm not discounting it, so
    if worse comes
    to worst I'll be happy to help you through email where you
    can send me the
    instructions they say pop up when you choose a script, as
    well as their
    script and we can figure it out.
    Take care,
    Tim
    "Juliamay" <[email protected]> wrote in
    message
    news:foigr7$8jg$[email protected]..
    > Hi Tim,
    >
    > Have done what you said none of the info is in the
    cgi-bin you click on
    > /hp_formmail_noimg and that takes you to several items
    including samples.
    > Sorry
    > I am really confused now not difficult at 53 I am amazed
    I got this far
    > its
    > taken me twice as long as it should but I really don't
    understand this
    > bit. I
    > have emailed the college but do not expect much joy.
    Thanks for trying.
    >
    > Julia
    >

  • Form Mail CGI

    I have applications on two sites where I use a form mail CGI-bin script to allow a user to enter contact information and send. It works great, but I'm wondering if there's any easier method than what I'm currently doing. I now direct the form info e-mail to my domain server, and then forward it from there to a private e-mail address.
    With CGI form mail, is it possible to simply direct the form data to a private e-mail address, or does it need to go to the domain server first?
    Tom

    Hi KB:
    I'm not an expert by any measure, but here's how it works for me:
         1. You'll need a folder on your site root. Mine is calle "cgi-bin". In that folder, there should be several files that are provided by your host. In my case, there are four files in it. That folder needs to be on your local drive and on your host server in your website's root folder.
         2. In your code view (or split view), you'll need to insert these three lines of code, filled in with your information (I've indicated data you'll need to fill in for your site in bold italic). Once completed, these three lines of code should be inserted directly below the line that contains the code with your
    Make sure you don't lose the " marks when you edit in your info.   
    Assuming you are using the DWCS4 "form" function and all the other form fields are filled in, you'll need to be sure your "ACTION" field on the form is as follows:   http://www.yourdomain.com/cgi-sys/formmail.cgi
    Finally, I've found that, at least with my hosts, I have to direct the form data to my domain e-mail address initially. If I want to redirect it from there to my "private" e-mail address (e.g., yahoo, gmail, live.net, other), I have to set up an auto-forward of the domain e-mail to my private e-mail address using the host's C-panel function. I tried just specifying my private e-mail and I got an error message that my private mail address could not be found on the server. I think that if you want form data forwarded directly to a private e-mail address without first having to go through your host server, you'll probably need to use a PHP script -- which is even more "fun" than CGI.
    Hope this helps.
    Regards,
    Tom

  • Upgrade from Lion Server to ML 10.8.1 Broke Mail server!

    ....10.8.1 OD seems to work, files and AFP available, but Mail server not working correctly.  Now users don't see mail, postfix issues numerous errors about missing system_user_maps and delivers no mail?  Must recover mails!  Help!  Where should I look, and what to read for Diagnosis ?
    After upgrade in place from SL to Lion to ML. most services did not work correctly; except for Mail and DNS and OD.   Reinstalled.   Now most everything seems to work including Card Services, Calendars, Wiki, Web, DNS, OD.  But Mail is off and missing???  No delivery of INcoming mail, No Sending Mail, no IMAP Mail login for users.
    On Mail configuration in Server.App:  Turned off All Filtering. Have rebooted Server several times,  Restarted Mailserver from Server,app and Terninal.   Same Results.  Somewhere along the line from Server 10.5 to SL to Lion to 10.8  incoming Maill started going to [email protected] rather than simply [email protected].
        Is it possible that virtual domains are fuzzing up the works?  The error logs use the longer virtual domain (with the sevrer name prefix) rather than the domain name?
    Here are some sample Log messages:
    From SYStem Log:
    Sep  7 19:33:56 plg1.plg-law.com postfix/cleanup[1998]: warning: 8273B199E3F8: recipient_canonical_maps map lookup problem for [email protected]
    Sep  7 19:33:56 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/ECF3A196A4FE: error writing 8273B199E3F8: queue file write error
    Sep  7 19:33:58 plg1.plg-law.com postfix/pickup[1324]: warning: E5AC9199E3F9: message has been queued for 1 days
    Sep  7 19:33:58 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps is unavailable. open database /etc/postfix/system_user_maps.db: No such file or directory
    Sep  7 19:33:58 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps lookup error for "[email protected]"
    Sep  7 19:33:58 plg1.plg-law.com postfix/cleanup[1998]: warning: E5AC9199E3F9: recipient_canonical_maps map lookup problem for [email protected]
    Sep  7 19:33:58 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/ED4AB196A4FF: error writing E5AC9199E3F9: queue file write error
    Sep  7 19:33:59 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps is unavailable. open database /etc/postfix/system_user_maps.db: No such file or directory
    Sep  7 19:33:59 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps lookup error for "[email protected]"
    Sep  7 19:33:59 plg1.plg-law.com postfix/cleanup[1998]: warning: 385DD199E3FB: recipient_canonical_maps map lookup problem for [email protected]
    Sep  7 19:33:59 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/EE2A9199B211: error writing 385DD199E3FB: queue file write error
    From SMTP Log:
    Sep  7 19:35:24 plg1.plg-law.com postfix/pickup[1324]: 3652E199E487: uid=78 from=<_mailman>
    Sep  7 19:35:24 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps is unavailable. open database /etc/postfix/system_user_maps.db: No such file or directory
    Sep  7 19:35:24 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps lookup error for "[email protected]"
    Sep  7 19:35:24 plg1.plg-law.com postfix/cleanup[1998]: warning: 3652E199E487: recipient_canonical_maps map lookup problem for [email protected]
    Sep  7 19:35:24 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/8E82B199AD06: error writing 3652E199E487: queue file write error

    here's my configured postfix main.cf file from /etc/postfix/main.cf   (mountain lion server 10.8.1)
    Server.app should have somewhat configured it correctly for you in someways, but something got messed up in the import script I guess.
    Hope this helps...
    # 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 = /Library/Server/Mail/Data/spool
    # 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
    # The data_directory parameter specifies the location of Postfix-writable
    # data files (caches, random numbers). This directory must be owned
    # by the mail_owner account (see below).
    data_directory = /Library/Server/Mail/Data/mta
    # QUEUE AND PROCESS OWNERSHIP
    # The mail_owner parameter specifies the owner of the Postfix queue
    # and of most Postfix daemon processes.  Specify the name of a user
    # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
    # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
    # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
    # USER.
    mail_owner = _postfix
    # The default_privs parameter specifies the default rights used by
    # the local delivery agent for delivery to external file or command.
    # These rights are used in the absence of a recipient user context.
    # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
    #default_privs = nobody
    # INTERNET HOST AND DOMAIN NAMES
    # The myhostname parameter specifies the internet hostname of this
    # mail system. The default is to use the fully-qualified domain name
    # from gethostname(). $myhostname is used as a default value for many
    # other configuration parameters.
    #myhostname = host.domain.tld
    #myhostname = virtual.domain.tld
    # The mydomain parameter specifies the local internet domain name.
    # The default is to use $myhostname minus the first component.
    # $mydomain is used as a default value for many other configuration
    # parameters.
    #mydomain = domain.tld
    # SENDING MAIL
    # The myorigin parameter specifies the domain that locally-posted
    # mail appears to come from. The default is to append $myhostname,
    # which is fine for small sites.  If you run a domain with multiple
    # machines, you should (1) change this to $mydomain and (2) set up
    # a domain-wide alias database that aliases each user to
    # [email protected].
    # For the sake of consistency between sender and recipient addresses,
    # myorigin also specifies the default domain name that is appended
    # to recipient addresses that have no @domain part.
    #myorigin = $myhostname
    #myorigin = $mydomain
    # RECEIVING MAIL
    # The inet_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on.  By default,
    # the software claims all active interfaces on the machine. The
    # parameter also controls delivery of mail to user@[ip.address].
    # See also the proxy_interfaces parameter, for network addresses that
    # are forwarded to us via a proxy or network address translator.
    # Note: you need to stop/start Postfix when this parameter changes.
    #inet_interfaces = all
    #inet_interfaces = $myhostname
    #inet_interfaces = $myhostname, localhost
    # The proxy_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on by way of a
    # proxy or network address translation unit. This setting extends
    # the address list specified with the inet_interfaces parameter.
    # You must specify your proxy/NAT addresses when your system is a
    # backup MX host for other domains, otherwise mail delivery loops
    # will happen when the primary MX host is down.
    #proxy_interfaces =
    #proxy_interfaces = 1.2.3.4
    # The mydestination parameter specifies the list of domains that this
    # machine considers itself the final destination for.
    # These domains are routed to the delivery agent specified with the
    # local_transport parameter setting. By default, that is the UNIX
    # compatible delivery agent that lookups all recipients in /etc/passwd
    # and /etc/aliases or their equivalent.
    # The default is $myhostname + localhost.$mydomain.  On a mail domain
    # gateway, you should also include $mydomain.
    # Do not specify the names of virtual domains - those domains are
    # specified elsewhere (see VIRTUAL_README).
    # Do not specify the names of domains that this machine is backup MX
    # host for. Specify those names via the relay_domains settings for
    # the SMTP server, or use permit_mx_backup if you are lazy (see
    # STANDARD_CONFIGURATION_README).
    # The local machine is always the final destination for mail addressed
    # to user@[the.net.work.address] of an interface that the mail system
    # receives mail on (see the inet_interfaces parameter).
    # Specify a list of host or domain names, /file/name or type:table
    # patterns, separated by commas and/or whitespace. A /file/name
    # pattern is replaced by its contents; a type:table is matched when
    # a name matches a lookup key (the right-hand side is ignored).
    # Continue long lines by starting the next line with whitespace.
    # See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
    #mydestination = $myhostname, localhost.$mydomain, localhost
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
    #          mail.$mydomain, www.$mydomain, ftp.$mydomain
    # REJECTING MAIL FOR UNKNOWN LOCAL USERS
    # The local_recipient_maps parameter specifies optional lookup tables
    # with all names or addresses of users that are local with respect
    # to $mydestination, $inet_interfaces or $proxy_interfaces.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown local users. This parameter is defined by default.
    # To turn off local recipient checking in the SMTP server, specify
    # local_recipient_maps = (i.e. empty).
    # The default setting assumes that you use the default Postfix local
    # delivery agent for local delivery. You need to update the
    # local_recipient_maps setting if:
    # - You define $mydestination domain recipients in files other than
    #   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
    #   For example, you define $mydestination domain recipients in   
    #   the $virtual_mailbox_maps files.
    # - You redefine the local delivery agent in master.cf.
    # - You redefine the "local_transport" setting in main.cf.
    # - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
    #   feature of the Postfix local delivery agent (see local(8)).
    # Details are described in the LOCAL_RECIPIENT_README file.
    # Beware: if the Postfix SMTP server runs chrooted, you probably have
    # to access the passwd file via the proxymap service, in order to
    # overcome chroot restrictions. The alternative, having a copy of
    # the system passwd file in the chroot jail is just not practical.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify a bare username, an @domain.tld
    # wild-card, or specify a [email protected] address.
    #local_recipient_maps = unix:passwd.byname $alias_maps
    #local_recipient_maps = proxy:unix:passwd.byname $alias_maps
    #local_recipient_maps =
    # The unknown_local_recipient_reject_code specifies the SMTP server
    # response code when a recipient domain matches $mydestination or
    # ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
    # and the recipient address or address local-part is not found.
    # The default setting is 550 (reject mail) but it is safer to start
    # with 450 (try again later) until you are certain that your
    # local_recipient_maps settings are OK.
    unknown_local_recipient_reject_code = 550
    # TRUST AND RELAY CONTROL
    # The mynetworks parameter specifies the list of "trusted" SMTP
    # clients that have more privileges than "strangers".
    # In particular, "trusted" SMTP clients are allowed to relay mail
    # through Postfix.  See the smtpd_recipient_restrictions parameter
    # in postconf(5).
    # You can specify the list of "trusted" network addresses by hand
    # or you can let Postfix do it for you (which is the default).
    # By default (mynetworks_style = subnet), Postfix "trusts" SMTP
    # clients in the same IP subnetworks as the local machine.
    # On Linux, this does works correctly only with interfaces specified
    # with the "ifconfig" command.
    # Specify "mynetworks_style = class" when Postfix should "trust" SMTP
    # clients in the same IP class A/B/C networks as the local machine.
    # Don't do this with a dialup site - it would cause Postfix to "trust"
    # your entire provider's network.  Instead, specify an explicit
    # mynetworks list by hand, as described below.
    # Specify "mynetworks_style = host" when Postfix should "trust"
    # only the local machine.
    #mynetworks_style = class
    #mynetworks_style = subnet
    #mynetworks_style = host
    # Alternatively, you can specify the mynetworks list by hand, in
    # which case Postfix ignores the mynetworks_style setting.
    # Specify an explicit list of network/netmask patterns, where the
    # mask specifies the number of bits in the network part of a host
    # address.
    # You can also specify the absolute pathname of a pattern file instead
    # of listing the patterns here. Specify type:table for table-based lookups
    # (the value on the table right-hand side is not used).
    #mynetworks = 168.100.189.0/28, 127.0.0.0/8
    #mynetworks = $config_directory/mynetworks
    #mynetworks = hash:/etc/postfix/network_table
    # The relay_domains parameter restricts what destinations this system will
    # relay mail to.  See the smtpd_recipient_restrictions description in
    # postconf(5) for detailed information.
    # By default, Postfix relays mail
    # - from "trusted" clients (IP address matches $mynetworks) to any destination,
    # - from "untrusted" clients to destinations that match $relay_domains or
    #   subdomains thereof, except addresses with sender-specified routing.
    # The default relay_domains value is $mydestination.
    # In addition to the above, the Postfix SMTP server by default accepts mail
    # that Postfix is final destination for:
    # - destinations that match $inet_interfaces or $proxy_interfaces,
    # - destinations that match $mydestination
    # - destinations that match $virtual_alias_domains,
    # - destinations that match $virtual_mailbox_domains.
    # These destinations do not need to be listed in $relay_domains.
    # Specify a list of hosts or domains, /file/name patterns or type:name
    # lookup tables, separated by commas and/or whitespace.  Continue
    # long lines by starting the next line with whitespace. A file name
    # is replaced by its contents; a type:name table is matched when a
    # (parent) domain appears as lookup key.
    # NOTE: Postfix will not automatically forward mail for domains that
    # list this system as their primary or backup MX host. See the
    # permit_mx_backup restriction description in postconf(5).
    #relay_domains = $mydestination
    # INTERNET OR INTRANET
    # The relayhost parameter specifies the default host to send mail to
    # when no entry is matched in the optional transport(5) table. When
    # no relayhost is given, mail is routed directly to the destination.
    # On an intranet, specify the organizational domain name. If your
    # internal DNS uses no MX records, specify the name of the intranet
    # gateway host instead.
    # In the case of SMTP, specify a domain, host, host:port, [host]:port,
    # [address] or [address]:port; the form [host] turns off MX lookups.
    # If you're connected via UUCP, see also the default_transport parameter.
    #relayhost = $mydomain
    #relayhost = [gateway.my.domain]
    #relayhost = [mailserver.isp.tld]
    #relayhost = uucphost
    #relayhost = [an.ip.add.ress]
    # REJECTING UNKNOWN RELAY USERS
    # The relay_recipient_maps parameter specifies optional lookup tables
    # with all addresses in the domains that match $relay_domains.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown relay users. This feature is off by default.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify an @domain.tld wild-card, or specify
    # a [email protected] address.
    #relay_recipient_maps = hash:/etc/postfix/relay_recipients
    # INPUT RATE CONTROL
    # The in_flow_delay configuration parameter implements mail input
    # flow control. This feature is turned on by default, although it
    # still needs further development (it's disabled on SCO UNIX due
    # to an SCO bug).
    # A Postfix process will pause for $in_flow_delay seconds before
    # accepting a new message, when the message arrival rate exceeds the
    # message delivery rate. With the default 100 SMTP server process
    # limit, this limits the mail inflow to 100 messages a second more
    # than the number of messages delivered per second.
    # Specify 0 to disable the feature. Valid delays are 0..10.
    #in_flow_delay = 1s
    # ADDRESS REWRITING
    # The ADDRESS_REWRITING_README document gives information about
    # address masquerading or other forms of address rewriting including
    # username->Firstname.Lastname mapping.
    # ADDRESS REDIRECTION (VIRTUAL DOMAIN)
    # The VIRTUAL_README document gives information about the many forms
    # of domain hosting that Postfix supports.
    # "USER HAS MOVED" BOUNCE MESSAGES
    # See the discussion in the ADDRESS_REWRITING_README document.
    # TRANSPORT MAP
    # See the discussion in the ADDRESS_REWRITING_README document.
    # ALIAS DATABASE
    # The alias_maps parameter specifies the list of alias databases used
    # by the local delivery agent. The default list is system dependent.
    # On systems with NIS, the default is to search the local alias
    # database, then the NIS alias database. See aliases(5) for syntax
    # details.
    # If you change the alias database, run "postalias /etc/aliases" (or
    # wherever your system stores the mail alias file), or simply run
    # "newaliases" to build the necessary DBM or DB file.
    # It will take a minute or so before changes become visible.  Use
    # "postfix reload" to eliminate the delay.
    #alias_maps = dbm:/etc/aliases
    #alias_maps = hash:/etc/aliases
    #alias_maps = hash:/etc/aliases, nis:mail.aliases
    #alias_maps = netinfo:/aliases
    # The alias_database parameter specifies the alias database(s) that
    # are built with "newaliases" or "sendmail -bi".  This is a separate
    # configuration parameter, because alias_maps (see above) may specify
    # tables that are not necessarily all under control by Postfix.
    #alias_database = dbm:/etc/aliases
    #alias_database = dbm:/etc/mail/aliases
    #alias_database = hash:/etc/aliases
    #alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
    # ADDRESS EXTENSIONS (e.g., user+foo)
    # The recipient_delimiter parameter specifies the separator between
    # user names and address extensions (user+foo). See canonical(5),
    # local(8), relocated(5) and virtual(5) 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 = /usr/share/doc/postfix/html
    # 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
    #======================================================================
    # dovecot
    dovecot_destination_recipient_limit = 1
    # default mailbox size limit set to no limit
    mailbox_size_limit = 0
    # List of ciphers or cipher types to exclude from the SMTP server cipher
    # list at all TLS security levels.
    smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
    # Protect SSL/TLS encryption keys
    tls_random_source = dev:/dev/urandom
    # (APPLE) Credentials for using URLAUTH with IMAP servers.
    imap_submit_cred_file = /Library/Server/Mail/Config/postfix/submit.cred
    # (APPLE) The SACL cache caches the results of Mail Service ACL lookups.
    # Tune these to make the cache more responsive to changes in the SACL.
    # The cache is only in memory, so bouncing the sacl-cache service clears it.
    use_sacl_cache = yes
    # sacl_cache_positive_expire_time = 7d
    # sacl_cache_negative_expire_time = 1d
    # sacl_cache_disabled_expire_time = 1m
    #======================================================================
    mydomain_fallback = localhost
    message_size_limit = 104857600
    biff = no
    mynetworks = 127.0.0.0/8,www.yourvirtaldomain.com
    smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated reject_rbl_client zen.spamhaus.org permit
    recipient_delimiter = +
    smtpd_tls_ciphers = medium
    inet_protocols = all
    mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
    recipient_canonical_maps = hash:/etc/postfix/system_user_maps
    smtpd_use_pw_server = yes
    smtpd_sasl_auth_enable = yes
    content_filter = smtp-amavis:[127.0.0.1]:10024
    inet_interfaces = loopback-only
    smtpd_helo_required = yes
    smtpd_pw_server_security_options = cram-md5,gssapi
    header_checks = pcre:/etc/postfix/custom_header_checks
    smtpd_tls_CAfile = /etc/certificates/computer.yourdomain.com.D800DD955D66179EEA4321DAA0617A19FFCD1 5C1.chain.pem
    smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname
    relayhost =
    smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks  reject_unauth_destination check_policy_service unix:private/policy permit
    smtpd_enforce_tls = no
    smtpd_use_tls = yes
    enable_server_options = yes
    smtpd_tls_key_file = /etc/certificates/computer.yourdomain.com.D800DD955D66179EEA4321DAA0617A19FFCD1 5C1.key.pem
    smtpd_tls_cert_file = /etc/certificates/computer.yourdomain.com.D800DD955D66179EEA4321DAA0617A19FFCD1 5C1.cert.pem
    mydomain = yourdomain.com
    virtual_alias_maps = $virtual_maps hash:/etc/postfix/virtual_users
    virus_db_update_enabled = 1
    mailbox_transport = dovecot
    postscreen_dnsbl_sites = zen.spamhaus.org*2
    maps_rbl_domains =
    virtual_alias_domains = $virtual_alias_maps hash:/etc/postfix/virtual_domains
    config_directory = /Library/Server/Mail/Config/postfix

  • BC Mail Server Access?

    We'd like to have an online course automatically email the instructor when a student successfully completes the course/quiz. We can embed javascript code into the course to do that, but it needs to interact with the BC webserver that would actually send the email. We can code that script, but would need information on the BC mail server and what scripting language options can be used.  Can this be done with BC?  Can we access an send notification emails with BC that are not part of workflow?  Thank you!

    You can outfit a webform to skip the CRM and just send an email, like a form-to-email solution. Here's some more information about that: http://kb.worldsecuresystems.com/kb/setting-form-email-using-web.html
    Basically, what I suggest is having a form like the one described in the link above hidden on your page when they user completes the quiz.  Have the javascript fill out the form fields to send out and then you can try to use ajax to post the form to the server with the right action as described in the link above and that form will send the details to the email address you use for the form.
    That's the easy way.
    I'd suggest taking it a step further, though.  Create a secure zone where the quiz is so that you have access to that person's information like {tag_emailaddress}, {tag_firstname}, etc.  Then, create a web app to collect the quiz results.  Call it Quiz Results.  Then, when the person is done with the quiz, on the final page of the quiz, embed a similar form that's hidden on the page except this form is not a form-to-email but this form is a user-created web app item form where the user submits a new web app item.  You can use ajax again to submit/post the form after filling out the fields with the scores using javascript.  Once the user submits this web app item, it's attached to them and then you can use {module_webappscustomer} on a secure zone page to show them their results.  I guess your quiz script might handle this but if you want to keep a permanent record of a user's scores in the BC database/crm then having them submit a web app of the results is your best way to go.
    You'll need a plan that supports web apps though.  The first solution is easier but it doesn't keep the scores in the BC database.

  • Mail server setup issues

    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']='&nbsp;&nbsp;';
    $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$

  • Domain name/"primary DNS" name/mail host name/mail server name/mx name

    Hi,
    I have registered my domain name (N.com) with an external dns server and created an MX record (mail.N.com) for it as well. My server sits behind a router and internet traffic is port(80)-forwarded to my server's fixed internal ip address (I can access my webpages from the internet just fine). When I initially setup the server I was asked to give it a "primary DNS name." I naturally assumed that N.com was supposed to be entered here, but that just caused all kinds of problems (though I still do not understand why). So I reinstalled and currently have server.N.com as the primary DNS name of the server (although it shows up in Server Admin and Workgroup Manager as server.local--why is that?)
    I have had no luck getting any email from the internet with the default settings in mail services (domain name of N.com and host name of server.N.com). Having no luck with the defaults, I assumed that maybe I needed to change the host name to "mail.N.com" so that it matched the MX record. I also changed the user preferences in Workgroup Manager to receive mail from mail.N.com--but still no luck. Could someone tell me what I am doing wrong and how come none of the Mail Service literature mentions anything about what a mail "host name" is supposed to be? Is it supposed to be the same as the "Mail Server" name that Workgroup Manager asks each user for? and is it the same as the MX record name?
    I am just needing some help to connect all these variously named, but undefined, dots.
    Also, how come I can access webmail from the internet using www.N.com/webmail but can't do it from any computers within my physical network (I have to use IPaddress/webmail or server.local/webmail)?
    Also, should my user email addresses be [email protected] or [email protected] (which is the current default)?
    Thanks in advance and good luck!
    John

    I had been told by a friend that ... regular email coming in from the internet would go through port 80
    Unfortunately you were misinformed.
    My MX record needs the extra subname (such as "mail") in front of the domain name, right?
    Not at all. A MX record for 'N.com' is entirely valid (expected, in fact).
    An MX record tells remote mail servers where to send mail for any domain/subdomain. If you think about it, let's say you worked for Apple and you wanted people to be able to send email to [email protected], well then you need an MX record for 'apple.com'.
    You can see if you dig MX apple.com that they actually have 9 MX records, but the point still stands.
    Now, you might also have MX records for subdomains so that you can have [email protected], [email protected], [email protected], etc. Each of these subdomains would need a separate MX record.
    So, in general, for any set of email addresses @[anything.]domain.com you have a MX record telling remote mail servers where to send that mail.
    Of course the MX record name is mail.N.com, but I think you are implying that the in the Mail settings of Server Admin where it asks for domain name all I need to put there is the N.com, right?
    What I mean is that you need to set the domain name to whatever domain name you expect to receive mail at.
    If you want users to have email addresses in the form of [email protected], then you enter 'N.com'.
    If you want users to have email addresses in the form of [email protected] then you enter 'mail.N.com'.
    If you want both forms, enter one in the main domain and add the other(s) in the Advanced -> Hosting -> Local Host Aliases section.
    Is there anything in the Mail settings that needs to have the full MX record name (mail.N.com)?
    Yes. Either the 'domain name' or the 'Local Host Aliases' needs to contain the same thing as your MX record. That's because the MX record tells remote servers to send mail to this machine, but the machine won't accept the mail unless it is configured to do so.
    What is the "host name" supposed to be?
    This should be the name that remote servers see when this machine tries to send outgoing mail.
    Ideally this should match the reverse DNS of your IP address, that way when it connects to a remote server it says "Hi, I'm $hostname" and the remote server can lookup the machine's IP address and see the same result. This will reduce the problem of remote servers thinking you're sending them spam.
    If you only have a single IP address then this probably needs to be something like 'N.com'. If you don't have control over your reverse DNS then you're going to run into a problem.
    Also in the user accounts (in Workgroup Manager) what should the "mail server name" be? Is it the host name or the domain name?
    Off hand, I don't know.
    Also, why are all the default user email addresses [email protected] (the name I gave the server at setup)? Why doesn't the user accounts create [email protected] as the default address?
    Presumably because the mail server says it is 'server.N.com' and therefore any accounts on that machine would be [email protected]. Changing the domain name (as above) should fix that.

  • "Unable to establish a connection between WebEx and the mail server."

    Hi,
    I installed Cisco WebEx and integrated with our Microsoft exchange server.  It showed server "UP".  everything's came up and working fine after that and sudenlly i found this message "Unable to establish a connection with the mail server.  Please recheck settings."
    I went into the Mail Server setup to edit settings and now, it shows Server Down.  Do I need to do something on the MS Exchange 2010 or from webex server ??
    Any help is greatly appreciated.  Thanks a lot!

    Every 180 seconds, CWMS verifies the connection to the SMTP server by establishing a connection on TCP port 25 (SMTP) and then sending the EHLO command followed by the QUIT command. This check is also performed once when logging into the admin web page or when browsing to System -> Servers (where the status of the mail server is displayed).
    If  this sequence does not complete successfully, the warning “Unable to  establish a connection with the mail server. Please recheck settings.”  will show in a banner at the top of the CWMS admin pages.
    You  can verify the connection to the SMTP server manually by using “telnet  25”.
    If you have access to the CWMS unix shell be aware that CWMS does not come  with the telnet command installed.
    As an alternative, you can use this 3-lines script:
    exec 3<>/dev/tcp/x.x.x.x/25
    echo -e "EHLO\r\nQUIT\r\n " >&3
    cat <&3
    Replace x.x.x.x by the ip address or hostname of the SMTP server and save the script in a file, f.e.:
    /* script saved in a file named ehlo */
    [root@dchriste-cwms-adm1 ~]# cat ./ehlo
    exec 3<>/dev/tcp/10.48.54.79/25
    echo -e "EHLO\r\nQUIT\r\n " >&3
    cat <&3
    Then, execute it:
    [root@dchriste-cwms-adm1 ~]# sh ./ehlo
    The output should be similar to this:
    220 *******************************************************************************************************************
    250-confukdc.confuk.com Hello [10.48.52.110]
    250-TURN
    250-SIZE
    250-ETRN
    250-PIPELINING
    250-DSN
    250-ENHANCEDSTATUSCODES
    250-8bitmime
    250-BINARYMIME
    250-CHUNKING
    250-VRFY
    250-XXXXXXXXXXXXXXXXXXXXXXXA
    250-X-EXPS=LOGIN
    250-AUTH GSSAPI NTLM LOGIN
    250-AUTH=LOGIN
    250-X-LINK2STATE
    250-XEXCH50
    250 OK221 2.0.0 confukdc.confuk.com Service closing transmission channel
    Also, you can use this tcpdump command to see the conversation (replace x.x.x.x by the SMTP server’s IP address or hostname):
    tcpdump -vXs 0 host x.x.x.x and tcp port 25
    If you have HA, it is not certain which admin VM talks to the smtp server, so best to check both.
    If you don't have access to the CWMS unix shell, best to span the switch ports and run packet capture.

  • Home mail server setup help.

    I admit that I am pretty much clueless when it comes to setting up a mail server.
    The setup:
    I have a local network at home with about 5 computers. Inside the network we have a router, a store-brought one that has bulit in DSL modem and wireless. It is out central DNS server and provides us with a local network domain name. Then we have a domain for the outside world to see us. Let's just call it "shadow.dot.com". I opened up the ports on the router to allow in port 80 and all POP3 addresses. I installed apache, php, mysql, and postfix on my Linux machine. I used webmin to configure postfix. Users can recieve emails, let's say from my hotmail account to [email protected] However, when I use webmins view usermail feature fromt he postfix area, I click on a user, then compose but my home local domain is listed instead of my shadow.do.com domain. I had in the configuration to place that outside domain in the address. Well, either way, I cannot send a message. It remains in the message queue and refuses to send.
    I do not have smtp ports open because I want this secure. I only want to be able to send email from inside my local network. This way there is no chance at someone hacking my smtp part and sending tons of email spam with my address.
    For this setup, what do I need in my main.cf configuration file? Can someone just put all the options in there that I need so I can copy and paste for the most part? I need to be able to send out, and I also need PHP to use it to send email to people. Do I need to unblock smtp? Do I need to change any settings with PHP or will it use postfix by default?
    Thanks.

    There is a send mail queue that is viewable via webmin. I don't know if it errored or not, it just stayed in the queue and never sent.
    I uninstalled postfix and then reinstalled it with default configs again. I modified a few settings to reflect my outside domain. Then I set up sasl to log into my ISPs mail server. Not mail sorta sends. Some PHP scripts still have trouble with it. I guess I need to fix those manually because some PHP scripts work and some don't so it might be an error with the script itself.
    Mail is only sent via smtp via port 25, not recieved. Recieving port is in the one hundreds. That is the only port needed to be open for recieving of mail.
    Thanks for you tips. I have I dynamic IP so liem clued me in on what to do. I don't know if it was a combination of bad config and dynamic IP, but it sorta works now, so I guess have more tweaking to do.

  • Mail server setup for LAN only (no Internet)

    Hello,
    I need a mail server on the solaris machine to send and receive messages vie local area network only.
    I got me a script for zfs scrub which sends the status via Email - however the machine is not connected to the internet.
    How can this be done?

    Do you need this mail server just for the zfs scrub reports or for all e-mail? How are clients currently getting e-mail? If you already have a mail server inside the company, or if you already have hosted mail server for company e-mail, that should be sufficient.
    If you do have an internal mail server, you should be able to set the DS parameter in sendmail.cf to specify the mail server. If you don't have an internal mail server, and you are all using external e-mail accounts, that should still work. By default, sendmail (if running) should be able to send e-mail outside the LAN. Sendmail uses DNS to locate the mail server for the recipient.
    You can verify that dns is working on the client with nslookup or dig
    -> nslookup -query=mx gmail.com
    Server:          -------------
    Address:     -------------
    Non-authoritative answer:
    gmail.com     mail exchanger = 5 gmail-smtp-in.l.google.com.
    gmail.com     mail exchanger = 10 alt1.gmail-smtp-in.l.google.com.
    gmail.com     mail exchanger = 20 alt2.gmail-smtp-in.l.google.com.
    gmail.com     mail exchanger = 30 alt3.gmail-smtp-in.l.google.com.
    gmail.com     mail exchanger = 40 alt4.gmail-smtp-in.l.google.com.
    I don't know if Solaris 11 Express has a companion CD. Solaris 10 does- and you can MAYBE install packages from it. On OpenSolaris there is the /usr/bin/updatemanager and /usr/bin/packagemanager commands. I suspect Solaris 11 Express also has the same. On OpenSolaris you could download packages from the OpenSolaris internet repository. It MAY include the IMAP server. (it does not for the OpenSolaris server I have.)
    Alternately, you could look for it on sunfreeware.com ( the Solaris 10 packages might work) or compile it from source.

  • Mail server no longer receiving external emails

    After a disastrous upgrade to Lion & then a full TIme Machine restore back to Snow Leopard, I've had some mail server issues. (Web services not working but fixed with this method).   Now noticed my server is now not receiving mail from external accounts... 
    Lots of posts suggested DNS problems but DNS does seem to be pointing some services to my server:
    - Webmail page is working but on login returns an error:  Error connecting to IMAP server: localhost. 61 : Connection refused
    - Mail Client log in works (but not with the 'mail.' prefix) & can send email both internally & externally.   External mail sent in to my server is returned with the error:  Host or domain name not found. Name service error     type=A: Host found but no data record of requested type
    I'm guessing it might be an IMAP problem but I'd be very grateful if anyone could suggest what could be happening here.
    Details:
    Domain & DNS  Web Log Errors   postconf -n    ps U postfix  .

    Yikes...  Time machine doesn't back up mail.
    http://docs.info.apple.com/article.html?path=ServerAdmin/10.6/en/asafc284c9.html
    You may be out of luck.  OS X Server shouldn't be backed up using time machine unless you've configured it specifically to back up things within it's limitaitons.
    Personally I use TM to back up user home folders and Shared Drives.  Then use retrospect to back up Mail and OD.  Lastly I use a script that runs a MySQL dump every night to take care of the web server.

Maybe you are looking for