Wiki Notification with other Mail Server Software
Hi everyone,
i am stucked and maybe you could help me out.
I am running a Mountain Lion Server with a wiki on it. I want to use e-mail-notifications, so a user gets an email
if someone other changes the wiki etc.
I set up everything, set the mail adress in my profile and marked the notification box in the wiki.
No mail comes in after a change.
Today i updated the kerio mail server i run on the same machine. To update it, i need to stop the
kerio mail server. After i stopped it, the wiki service sends out all the notification e-mails! So my
thought is, that the kerio mail server blocks the wiki-service (and i think the mail-service of osx-server)
so that no notification e-mails get out.
So what can i do to get the wiki-notification-emails running when the kerio-server is also up?
Maybe changing some ports of the mail/wiki-service?
Thank you for your help!
Greetings,
five
No one here who can help?
Similar Messages
-
I can send but cannot recieve email
This is the messege I am gewtting:
There may be a problem with the mail server or network. Verify the settings for account “MobileMe” or try again.
The server returned the error: Mail was unable to log in to the IMAP server “p02-imap.mail.me.com” using “Password” authentication. Verify that your account settings are correct.
The server returned the error: Service temporarily unavailableAlso if I go to system preferences accounts and re-enter the password it fixes the glitch sometimes.
-
Text limits to the "Question" link prevents a full explanation:
This is a long-time problem. I have tried to resolve it with Apple but their "Customer Support" is merely a name.
I can go online and access my e-mail but when I try to send or receive e-mail via iCloud through my internet server (Google fiber now but the same situation existed with my prior service), I receive "There may be a problem with the mail server or network. Verify the settings for 'Apple Email' and try again.
"The server returned the error: The server 'p0-imap.mail.me.com' refused to allow a connection on port 143."
Well, I have verified the setting and tried again and again and …
Well, you get the idea …JungleTaxi Cabbie wrote:
Csound1: iCloud: Configuring Mail with Mac OS X v10.6 or iOS 4
Enter your Incoming Mail Server, User Name, and Password using the following settings:
Incoming Mail Server: mail.me.com
User Name: Your iCloud email address (excluding @me.com)
Password: Your password
Last Modified: Jun 27, 2013
Maybe you should test these things before calling people out, because these settings do function perfectly well.
iCloud is not supported on Snow Leopard or lower, why bother to mention it?
The OP has an iCloud account, and that can not be opened without Lion or Mountain Lion (on a Mac), IOS5 or 6 (on an iPhone/iPad)
The document I linked to is Apples documentation for iCloud on current devices,I don't care whether you believe that you know better than they do, but it will affect the people who follow your advice as it won't work
JungleTaxi Cabbie wrote:
Also, if you're not running Lion or Mountain Lion, there is no "Mail, Contacts & Calendars" prefpane.
I never said that there was, perhaps you imagined it. -
IOS 4.1 Contacts Sync With Any Mail server Annoying Bug
Hello
i saw there was already few people that notice this but today i found about this problem and it can be very annoying.
this information was checked on more then 20 devices , and the problem started only since 4.1 version (don't know about 4.0.2)
After you will set an Exchange/Zimbra/Open-Xchange or any other Mail server account , by default the IOS 4.1 will save the contacts in Iphone local Memory , this need to be change in the Settings to use the account you setup - otherwise new added contacts would not syncronize with your server and we all know that this can be very annoying to find out when you will change to new iphone or any other reason that will make you to reset your device and find out that all the new contacts vanished.
I hope that Apple will fix this in the next update because in previous versions i never bump into such problem .
I would like to know if there is any way to sync those new contacts (not by delete them and add them again) with the Server . because after setting up Exchange server there is no way to sync your Contacts with your PC.
P.S - big thanks to Asher Karsis that Notice me about this problem.
YossiI was so glad to get multiple Exchange account support with iOS 4. I have been synching with my work account (calendar, mail) and with my Google accounts (calendar, mail, contacts). After upgrading to iOS 4.1 three days ago, my Google accounts appear to be working fine but my work account refuses to connect to the Exchange server for calendar or mail.
My company forced a passcode when I originally added the account. For troubleshooting I removed the account and recreated it. The account verifies but never requires that I have a passcode. I then removed all of my Exchange accounts, restarted my phone and recreated my company Exchange account. Again, verifies without requiring a passcode, and neither my calendar nor my mail will connect - zero events, zero emails. My mail even proudly says it updated and shows the current time/date stamp - but nothing. When I upgraded to 4.02, I had to set up a passcode. I am highly suspicious that because 4.1 is not synching properly because it is not handshaking correctly regarding the security on the Exchange Server ... that is my guess. And I echo, IT NEEDS FIXED! I am screwed not being able to get my emails and calendar events on-the-fly. -
Has there been any problems with the mail server?
Has there been any problems with the mail server? I keep getting a notice of server failure.
Unfortunately the error message does not identify the specific server, I (as many folks do) have several, Mac, yahoo, google ect.
-
When I open an encryted pdf file in my Hp Slate 7 voice Tab it was unable to open the pdf file.Tje same file was opening with other pdf reader software.Kindly Help.
[spam link removed]Could you please send the pdf to [email protected] so that we may investigate the issue?
Thanks,
Adobe Reader Team -
I am using Endorange as my main mail, but every time i wannt to send open pdf docement as e-mail my computer comes up with other mail softwere called mail, how do I chance that?
I am using Endorange as my main mail, but every time i wannt to send open pdf docement as e-mail my computer comes up with other mail softwere called mail, how do I chance that?
-
What is the best mail server software, compatible with G5 and OS X 10.5.8?
Hello.
I want to install/set up a mailserver on Mac OS X 10.5.8.
It will host approximately 35users, should have pop, imap, spam protection, webmail/admin interface, routing feature, all the usual stuff, I'm doing this because we often have to recieve very large files and having a mailserver on local network makes working with them so much faster. What would you recommend?
Thanks in advance.There isn't enough data in your post to create an informed answer.
For one, are you talking Mac OS X client, or Server?
Mac OS X Server already includes all the various mail server components you talk about, and it's based on Postfix, one of the most popular open source mail servers around.
Secondly, having your own mail server will only be 'so much faster' for local users sending/receiving local mail (i.e. from users on the same network). Every other email has to go out (or come in) over your office internet connection and having your own mail server doesn't change that one bit.
At that point, if you're only talking local users, it sounds like what you want is a file server, not a mail server. Mail is not designed for large file transfers.
Third, even if you don't want Mac OS X Server's solution, and you can deal with the bandwidth, you haven't mentioned cost - what's your budget here. You won't find a free/open source solution that's more complete and easier to use than Apple's bundle, so now you're into the commerical offerings. All of them charge, typically per user and some of them (as already mentioned) are mothballing their PPC support, meaning any invenstment in their option might be short-lived.
So I think you need to better state your goals and ideals before you can find the 'best' solution (if any of them are really 'better' than any other). -
TS3899 iOS email notification bug with exchange mail server
Hi,
Recently I noticed that my iPhone often plays new email notification sound but there is no new emails shown in notification centre and unread numbers on the email icon stays the same.
I have an email account set up and its connected to Microsoft exchange mail server, I have some sub-folders under my Inbox, I also have some rules set up to automatically move some non-impotrent emails to those sub folder.
Under fetch new data settings I choose push my inbox as default, but I didn't tick those sub-folders under my inbox.
Also under notification settings I have enabled everything for Mail app.
After some invistgation I found out that everytime this happens I have a new email in one of those sub-folders under my inbox, although it should only be updated manually..
Anyone have any Idea on how to prevent this from happening??While this is only a guess, I suppose that you have these rules set up at the server. The mail hits the inbox, and then is filtered to the sub-folder. I'm guessing that your notification comes from the mail arriving at the inbox, but before it is counted there, it has been moved to the sub-folder. Your opening mail allows the folder to get populated on the phone. I'm not sure if there is a cure for that, and again, that is pure conjecture on my part. Better than anything anyone else has posted.
-
IOS email notification bug with exchange mail server
Hi,
Recently I noticed that my iPhone often plays new email notification sound but there is no new emails shown in notification centre and unread numbers on the email icon stays the same.
I have an email account set up and its connected to Microsoft exchange mail server, I have some sub-folders under my Inbox, I also have some rules set up to automatically move some non-impotrent emails to those sub folder.
Under fetch new data settings I choose push my inbox as default, but I didn't tick those sub-folders under my inbox.
Also under notification settings I have enabled everything for Mail app.
After some invistgation I found out that everytime this happens I have a new email in one of those sub-folders under my inbox, although it should only be updated manually..
Anyone have any Idea on how to prevent this from happening??While this is only a guess, I suppose that you have these rules set up at the server. The mail hits the inbox, and then is filtered to the sub-folder. I'm guessing that your notification comes from the mail arriving at the inbox, but before it is counted there, it has been moved to the sub-folder. Your opening mail allows the folder to get populated on the phone. I'm not sure if there is a cure for that, and again, that is pure conjecture on my part. Better than anything anyone else has posted.
-
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$ -
I am running os x 10.7.5, on a macbk, I have been using all the apps fine and not changed anything or run any software updates, suddenly my mail dows not think it can connect with the outgoing server for icloud and requests my password, which I give, but it repeatedly asks again and again. I have tried re-setting all the mail for icloud up again, and it thinks its ok, except the box keeps flagging up can't access outgoing server. I have checked it all a number of times, and I can access the icloud stuff including mail from http when I log in there. Anyone know why my mac will not accept my icloud password? suddenly I cannot get any icloud mail in or out, but I changed nothing. Why does it do this and why can't i fix it?
No carrier "automatically" unlocks at end of contract - many won't do it at all, even if requested. I don't know what your carrier's policy is since you didn't say what country you're in.
However, if I understand you correctly, you didn't change carriers so it doesn't matter if it was unlocked or not. Try the following steps, as needed:
1. Reset phone - press both home and sleep/wake buttons for at least 19 seconds until the Apple logo appears
2. Settings > General > Reset > Reset Network Settings
3. Restore phone in iTunes using a backup
4. Replace SIM card (don't care what Telstra says)
5. Restore phone in iTunes as new, without using a backup
6. Take phone to Apple. -
How to configure a Windows machine with any vnc server software for ARD
I need someone to direct me in the right direction to configure and install any vnc server software so that I can control a windows machine with ARD like I control the rest of my macs in the lab. I need some suggestions as to the best and easiest software to configure and the correct settings to get the machine to be able to show in ARD. Thanks
Sort of. I found this article below that helped me to connect to the remote CF server using MXML. It seems that you have to create a regular project in Flex with Aplication Server Type set to None and connect to CF using the endpoint attribute of the RemoteObject MXML tag or via AS.
http://www.aliaspooryorik.com/blog/index.cfm/e/posts.details/post/200
However I found out after getting error using the AS3 code to use the endpoint property that
mx.rpc.remoting.RemoteObject does not support the "endpoint" property
whereas mx.rpc.remoting.mxml.RemoteObject does. See link below
http://www.mail-archive.com/[email protected]/msg101439.html//www.mail-archive.com/[email protected]/msg101439.html
So I had to change my AS3 code by adding a new channel to my RemoteObject using a code similar to the one on the link below (Note that this code uses PHP, when I instantiate myRemoteObject, I do so informing that the destination is "ColdFusion" [new RemoteObject("ColdFusion")], so no need to set destination as in the code on the link below
http://tech.groups.yahoo.com/group/flexcoders/message/120115
I hope that helps you. -
Mail trouble with outgoing mail server
For weeks now (relatively recent), MAC mail will not send consistantly. When I choose my outgoing mail server in the preferences panel and check "use only this server", Mail often will not send my message. If I leave that outgoing server as "none", my first outgoing message of the day will prompt me to choose one, and then subsequent messages are sent without asking. Inconvenient at the least - something's not right.
Any help?Thanks for response.
I have deleted ALL accounts (to start fresh) but the unused outgoing servers 'refuse' to leave
I want to delete them to keep things tidy, also I have issues with using alternate outgoing server (next issue), so trying to start from the beginning again, before attempting to address next issue. -
Trouble with outgoing mail server
When I try to send gmail I get an error message 'your acc does not have a preferred outgoing mail server'? I've had this before but can't remember what to do.Thanks.
Who is your ISP? Normally they provide you the information you need when you sign up with one, i.e. user name and password, email address, smtp server address, pop and imap server addresses, authentification requirements, etc.
If you haven't got that information to hand it's normally available with a quick Google search.
I'm with Orange and just searched 'Orange smtp server settings' - this is what I got:
http://help.orange.co.uk/orangeuk/support/personal/506007
Maybe you are looking for
-
How do you return to web page after executing servlet?
When I submit some values to my servlet from a page, using a from, how do I get back into the web page directory? When you call the servlet, the url turns to "./servlet", and if I click on submit again, it tries to find "./servlet/servlet" so obvious
-
I've been trying to upgrade the drive in my iMac. I have a 3 tb Drive in an external case (FW800). I've installed Lion on the drive but for some reason I cannot boot from the external. I'd really like to make sure it boots before I pull the iMac apar
-
'normal' battery performance MacBook pro
I have recently bought a 'replacement' battery of nominal capacity 5800 aMh. When 1st fitted it actually had a capacity of 5530 and registered 2 cycles expended. I thought maybe do a calibration; it then dropped to 5337 and 3 cycles expended. 1: is t
-
How to Generate Unique Cache Keys?
I'm trying to improve the performance of my ColdFusion 10 application by making better use of caching. I have a particular DAO/Gateway CFC that queries a particular database. I added query caching to the query in this CFC and it made a huge differe
-
I have 2 domain controllers running 2003 server, server1 and server2. I ran dcpromo on server1 and removed AD and removed him from the domain and disconnected from network. I then added a 2012 server with the same name and IP address server1 with no