Mail not being able to read inbox/sent mail??

Hey guys,
I have a system that is running OS X 10.3.9 with Mail: 1.3.11 and it seems to constantly have issues reading the inbox and sent mail folders.
When I launch mail, it shows that I have messages in my inbox and my sent mail but when I go to click on the headers, nothing shows up in the preview screen. Rebuilding my mailboxes and also trying to re-import them into a different box does not help. When I try importing them, the file is not recognizable by the mail importer.
When I restore these mailboxes from back up, mail is able to read them for a few minutes, then it goes right back to the same issue.
Has anyone encountered this and know how to address it or can even tell me what it is?

Hello,
I've same problem on Mac OS 10.2 system. Only in sent mail box.
Sent mail box appear empty but state bar says 782 messages.
Clicking on a ghost message show selection bar. Double click on subject and subject of message appears, same operation on date, sender...
Inbox, junk mail work fine.
Other problem : Mail always crash down when I quit application (Application does not respond).
Sure I've repaired files permission, delete preference file, rebuild mail boxes but problem still here.
Someone can help me ?
Message was edited by: Sebastien Rousseau

Similar Messages

Why wont my mail open? The mail not being able to open is making me not be able to shut down my laptop.

Why wont my mail open? The mail not being able to open is making me not able to shut down my macbook.

Press power button down and hold up to 30 secs to force shut down and then start up and see how u goes on ur mail....

Mail not being able to find the SMTP server

hi there,
I am trying to use a new mailbox account but Mail cannot find the SMTP server and refuses to send emails. It is a pop account and it can find the incoming server ok. I know that the server is ok because I can send emails from a webmail version of the account but in Mail..nada.
Does anyone know why Mail is not finding the server?
Many thanks
Shark

What version of OSX were you using before upgrading to Snow Leopard? Since introduction of Leopard and Mail 3.x, the Outbox has only been seen in the Sidebar when there is one or more messages not yet sent.
Sending with webmail is no test of the SMTP, since it is not used when sending via webmail. What Port are you presenting the SMTP on, and what does the provider recommend in that regard? Who is that provider?
Ernie

Is there a solution to Adobe Bridge CS6 not being able to read raw files from the 5D Mk lll

I like to use Bridge as my overall file organizer. I operate on a Mac version OSX version 10.8.3 and cannot read my raw files in bridge cs6. Does anyone have a solution for this.
Also is Canon putting any pressure on Adobe to fix this?

Not bridge but camera raw. You'll need to update your camera RAW.
You can either do it directly in Photoshop, or you can download it here: http://blogs.adobe.com/crawlspace/2011/03/keeping-photoshop-up-to-date.html
At the bottom, there is a link to download Camera Raw 7.4 for Mac and WIndows. Adobe hides there link from their main site to force people to update via Photoshop update feature.
Weekend Travelers Blog | Eastern Sierra Fall Color Guide

The display of my ipod touch comes up as usual and then goes faint to the extent of not being able to read anything. In the meantime it has lost all the contents. what can be the course/

When switched on the display of my my Apple Ipod Touch comes up as usual and then dimms to such an extend that I cannot see anything. Also when connected to the PC, It shows that there is no content in the Music and Video folders. I restored the OS and upgraded it to 4.2. But the display is even worse. Do help me to sort this out.

If you restored to factory defaults/new iPod and still have a problem then you likely have a hardware problem. An appointment at the Genius Bar of an Apple store is in order.

Yahoo Mail not being downloaded, never stops "Checking for Mail"

Since the first time I synced since the new itunes version and the 1.0.1 update, I have not received any mail populating into my Yahoo account. I tried the restart, shutting off the other email accounts, etc.
I does not push, and when I try the Refresh, it never stops "Checking for Mail".
My gmail works fine.
Anyone have any ideas to correct?

Same here but a little stranger. Two items:
(1) If I go into my Yahoo Drafts, or Sent, or Trash, check mail works fast and I get the "Updated 8/26/07 time" message fine and it's accurate.
If I switch to Yahoo In, the initial footer says "Updated 8/14/07 xxx" and has said that for a week or so. It quickly changes to "Checking for Mail" and then never stops.
Anyone else see the "Checking for Mail" only on the IN box but not the others.
(2) I have been sending test emails to Yahoo (basic account). #1 happens as above (ie no mail seems to arrive). But if I scroll to the bottom of the IN box and click "Load 25 more messages", it does seem to pick up the new messages. "Checking for Mail" is still going strong. This seems to work most of the time.
Anyway. Not sure it this may help anyone figure this out.
[I have tried the approaches suggested here such as deleting Yahoo, turning off other emails, resetting network, changing IMAP inbox location, etc]

Solved Problem - mail not being sent and kept in Outbox....

I've posted a few messages here about mail not being able to be sent and kept in the Outbox.
It is solved. I believe.
Everything seems to be back to normal. I guess it was a problem of me over stepping limitations for .Mac e-mail, and getting locked out for a 24 hour period. So, I will be more care next time I need to e-mail large files to numbers of people ! Probably will invest in something like Stuffit and use there compression facility to reduce the size of files I want to send over the internet and via e-mail.
Thanks to those who took interest and gave advice.

You don't have to invest in Stuffit.
Built-in compression is included with the Finder.
To compress files before sending them, use the Archive command in the Finder's File menu. Select the file or files you want to compress, then choose File > Create Archive.
A compressed archive of the files is created. If you archive a single item, the archived file has the name of the original item with a ".zip" extension. If you archive multiple items at once, the archived file is named Archive.zip.
Recipients can open the archive by double-clicking regardless the platform - Windows or OS X.

I just wrote about not being able to send messages on my IPad.Someone responded-thanks-I did what they said and now I have no sent mail category.Help!!!!

I just wrote about not being able to send messages on my IPad.Someone wrote back,thanks,about going to settings,outgoing mail etc. and I did that.Now I have no sent mail category.Help.

When you reset the password, you need to enter the password into the outgoing server setting again. I have reset my email passwords a couple of times and I had to enter the password into the outgoing server setting before I could send mail again.
Did you try that? If you did try it, did you try sending an email? You can send yourself an email to test it.

Mail not being sent by phone

My iPhone is giving me a pop-up that says, "Cannot send mail" and says that "the sender address was invalid."
I've sent mail without problems with my iPhone for a year now and this just began to happen.
Whats up?
Jeremy

Hello all
I've had the same problems not being able to send (and sometimes receive) mail as well. I have three email accounts set up on my phone, and I noticed that one of the accounts worked, but not the other two. That tells me that it's not a defective iPhone as I first suspected. What I found out is that on the account that works, the SMTP Server Port Setting is set to 25. On the two accounts that weren't working, the Server Port was set to 587 and that's why I couldn't send out email. After changing the settings on both non-working email accounts, everything now works perfectly.
So, if you go to Settings>Mail, Contacts, Calendars>Accounts>Outgoing Mail Server SMTP>Primary Server>Server Port: 25
This worked for me. Hopefully it'll work for all of you here and anyone else with this problem.
Good Luck!
Warmest Regards,
Mike.

My gmail accounts are connected to Apple Mail. The issue I'm having is in not being able to attach documents from folders and subfolders. Can anyone direct me to a resolution.

My gmail accounts are connected to Apple Mail. The issue I'm having is not being able to attach documents from folders and subfolders to an email. Can anyone provide insight on how to drill down to the documents I need?

Hello Wilsonneedshelp,
Thanks for the question. After reviewing your post, it sounds like you need some help adding attachments in Mail. I would recommend that you read this article, it may be able to help the issue.
Mail (Yosemite): Add attachments
Thanks for using Apple Support Communities.
Have a nice day,
Mario

Problem with Adobe Reader not being able to run with Maverick 10.9.2?

problem with Adobe Reader not being able to run with Maverick 10.9.2?

Have you updated your version of Adobe Reader?

Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - 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,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - 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, $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

Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint.

Not being able to remove the voice mailbox number ...

Hello
I would like to ask you guys here at Nokia why you can't remove the voice mail box phone number after setting it the first time. Why is it so?
To reproduce this "bug" go Menu -> Messaging -> Voice call messages -> Voice mailbox no.
Set the voice mailbox number.
Then, try to restore the settings to what it was originally.
It won't work.
I have tried this on several newer Nokia phones.
Why is it so? Could "OK" maybe move to the left soft key? No. Of course not.
Did you know everyone doesn't have voicemail?
Therefore some users use the 1 key as any other quick dial key.
I suppose that in any good user interface you should be able to restore a setting to it's original setting. Not being able to do so without any warning of some kind is simply ridiculous.
If there is some other limitation that prevents you from doing this, please let me know.

Why is nobody answering this?
I would be very happy to discuss this.

Rules in Mail not being applied after Mavericks update

Hi everyone, I know there are a lot of threads already discussing similar issues, but so far I've been unable to find one that helps resolve my particular issue. Ever since upgrading to Mavericks my rules are not being applied in Mail. I will give you a screenshot of one of my rules:
I have about five rules that follow the same pattern: search for particular string in the FROM field and mark it with a color if the string is present. These rules all worked fine in Snow Leopard. All of my rules are still present after the upgrade and all checked as active. When I "select all" messages in my inbox and press Option-Cmd-L the rules are applied properly. However, the rules are not applying themselves when new mail comes in. As far as I can tell this does not have anything to do with the mail not being recognizes “as a new message” like, for example, because the mail was already read on my phone. It happens even if my other devices are offline and the only thing I am using to check mail is my laptop.
I am using a MacBook Pro 2.3 GHz Intel Core Duo with OS X 10.9.1, in case that matters.
Thanks for any advice!

I think I've found at least a partial solution to the Mail - Rules Don't Work problem:
In "Mail" go to the menu Mailbox and click on Rebuild.
If you have a lot of stuff, this will take several minutes to finish.
I also reviewed all my rules and made a few minor changes.
Mixed results: I found that running "Apply Rules" didn't work on email already received; but new mail did. I don't quite understand that, but I call it a partial success.

Anybody else tired of not being able to play half the videos on the web with there Apple products - just a rant.

Anybody else tired of not being able to play half the videos on the web with your Apple products - just a rant. Thanks

Constant problems: asking for password, not retrieving mail from the server,leaving things in the outbox. Then it can be fine for days. iPad and iPhone apps sometimes hang for a bit as well.
A friend just bought an iMac and has had nothing but trouble with ROGERS mail. Support guy walked us through the whole set up today and everything was fine for a while and then it just quit.
I am wondering if having an IPad, computer and phone all communicating with server at the same time causes problems.

Mail not being able to read inbox/sent mail??

Similar Messages

Maybe you are looking for