Mail services 10.4.10 refuses to work.

Hello,
I'm a newbie to OS X, so please help - I need to get
a local eMail system going here in the office, and it
just doesn't want to work.
I've been to every site imagineable searching for answers
on how to configure OS X Mail Services, but it still
doesn't work.
DNS:
- I have DNS running on this server,
- I've checked "This machine is a mail server for the zone" for the server,
- I've added aliases "pop3", "smtp", and "mail" for the server.
User accounts:
- Open Directory seems to be running, although "start service" is greyed-out,
- this is an "Open Directory Master",
- I've checked "Enable Secure Sockets Layer" on the Protocols tab,
- I've checked all the encryption options in the Policy->Security tab.
Workgroup Manager:
I followed some tutorial to create the directory "/LDAPv3/127.0.0.1",
and added the user "dspratling" to it, which DOES show up in the
Mail Services automagically.
I'm only looking to create Mail Users ("dspratling" for starters),
but trying everything, I created a Home directory for this user,
since I was getting error messages in the LDAP log saying: "... object
class 'posixAccount' requires attribute 'homeDirectory'.
- I have checked the "Mail: Enabled" under the Mail tab,
- I checked "POP only" under Mail Access,
- I put "mail.mme.lan" for the Mail Server.
- Under the Advanced tab, I have User Password Type selected as "Open Directory".
Error Messages appearing in the logs:
Other error messages in LDAP log include:
"slapd[59]: SASL [conn=3740] Failure: GSSAPI Error: Miscellaneous failure (No principal in keytab matches desired name)"
kdc Log has:
"xserv.mme.lan krb5kdc[296](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 10.0.0.9: ISSUE authtime 1195081950, etypes {rep=16 tkt=16 ses=16}, [email protected] for krbtgt/[email protected]"
kadmin Log has:
"xserv.mme.lan kadmin.local[22270](info): No dictionary file specified, continuing without one."
however, good news in the "Password Service Server Log":
"RSAVALIDATE: success"
and
"AUTH2: {0x000000..., diradmin} CRAM-MD5 authentication succeeded."
Now, in the Mail logs...
Mail Access log has:
"xserv master[23575]: empty option value on line 19 of configuration file"
and
"xserv master[23575]: exiting"
POP log has:
"xserv pop3[23444]: AOD: getting mail attribute for user: dspratling
"xserv pop3[23444]: AOD: mail enabled"
"xserv pop3[23444]: AOD: mbrcheck_servicemembership with accessallservices"
"xserv pop3[23444]: AOD: checkServiceACL: Mail SACL not enabled"
From the Client-side (MacMini 10.4.10), it reports "The server "mail.mme.lan" refused to allow a connection on port 995."
All other network-based services work fine with the server, even in our
heterogenous PC network - only the Mail Service is not working.
Please - ANY SUGGESTIONS WOULD BE APPRECIATED
Thanks,
Dylan

Brett -
Thanks for the suggestions. This is not an internet-facing
server, however. Strictly intra-office eMail is all I'm after
for now. The DNS works well, resolving "mail.mme.lan" to the
correct IP (via the CL "host" command), and the CL "named-checkzone"
command returned OK as well. I haven't changed the DNS for weeks,
so I'm quite sure every cache has been refreshed.
I'm going with "Plan B", until this can be resolved ...
And I know it's pure evil, but: "Parallels -> Win2K -> mailEnable"
I got it configured and working in minutes. (Parallels was already
running on this server, serving printers, and mailEnable was free
Would still rather not depend on MS.
Thanks,
Dylan

Similar Messages

  • HT1430 My mail service with Yahoo just suddenly stopped working.  Can't access Yahoo.  Restart did not help.  Help

    My Yahoo mail service stopped working on my Iphone.  Works fine from my PC.  Help  Did restart but no help.

    Hello Bad Don,
    Thank you for using Apple Support Communities!
    I would recommend performing the troubleshooting steps in this article named iOS: Unable to send or receive email found here http://support.apple.com/kb/ts3899
    Try an alternative Internet connection.
    If your email is provided by your Internet provider, try connecting from the home network.
    If your iOS device has an active cellular data plan, try to disable Wi-Fi:  Tap Settings > Wi-Fi and turn off Wi-Fi.
    If not, try a different Wi-Fi network.
    Log in to your email provider's website to ensure that the account is active and the password is correct.
    Delete the account from Settings > Mail, Contacts, Calendars and then add the email account again on the iOS device.
    If you're still unable to send or receive email, contact your email provider and verify the account settings are correct. You will need to gather this information (PDF).
    If none of that resolves the issue, I would backup and restore the device with iTunes.
    iOS: How to back up and restore your content
    http://support.apple.com/kb/HT1766
    All the best,
    Sterling

  • Postfix error, no Queue, mail service dosen't work anymore.

    Hi,
    I reinstall my osx server 10.5.5 and now the mail service dosent work anymore. In the SMTP log I get this error every time anyone try to send a email to this server.
    postfix/smtpd[12554]: NOQUEUE: reject: RCPT from relais.videotron.ca[24.201.245.36]: 451 4.3.5 Server configuration error;
    this is my postconf
    alias_maps = hash:/etc/aliases
    always_bcc = [email protected]
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = all
    localrecipientmaps =
    luser_relay = leclap
    mail_owner = _postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    mapsrbldomains =
    messagesizelimit = 0
    mydestination = $myhostname,localhost.$mydomain,localhost,mail.clap.ca,clap.qc.ca,clap.ca,69.70 .105.2,production.clap.ca,production.clap.qc.ca
    mydomain = mail.clap.ca
    mydomain_fallback = localhost
    myhostname = clap.ca
    mynetworks = 127.0.0.0/8
    mynetworks_style = host
    newaliases_path = /usr/bin/newaliases
    ownerrequestspecial = no
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    recipient_delimiter = +
    relayhost =
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = _postdrop
    smtpdclientrestrictions = permit_mynetworks bl.spamcop.net permit
    smtpdpw_server_securityoptions = cram-md5
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpduse_pwserver = yes
    unknownlocal_recipient_rejectcode = 550
    I already try mailbfr, and nothing append.
    If anybody know how to completly erase the mail service to startover whithout reinstall the server, I'm willing to do that to!
    Thanks!
    Message was edited by: robinplamondon

    Edit /etc/postfix/main.cf in Terminal or a text editor (not Word).
    Change:
    smtpdclientrestrictions = permit_mynetworks bl.spamcop.net permit
    to:
    smtpdclientrestrictions = permit_mynetworks rejectrblclient bl.spamcop.net permit
    When done, issue:
    sudo postfix reload
    HTH,
    Alex
    mailbfr is for fixing the Cyrus database or backing up mail services. It has nothing to do with Postfix/SMTP

  • Mail service almost working

    I'm trying to set up a leopard home server and have rebuilt it several times now trying toiget the mail service to work correctly.
    I will no doubt omit lots of necessary information but please bear with me
    I have a registered domain and a static ip. My ISP supplies a broadband modem which just acts as a bridge to my own wireless router. I have done what I understand to be the required port forwarding - 21, 25, 80 & 110.
    I have DNS at the ISP but have also set up DNS internally since I couldn't get anything to work without it!
    Whilst I can send mail from the server my users can only send to the outside & receive no mail from inside or out.
    The SMTP since the last restart:-
    Feb 24 17:56:19 merlin postfix/master[37]: daemon started -- version 2.4.3, configuration /etc/postfix
    Feb 24 18:08:53 merlin postfix/smtpd[282]: connect from demokritos5.cytanet.com.cy[195.14.130.179]
    Feb 24 18:08:54 merlin postfix/smtpd[282]: NOQUEUE: reject: RCPT from demokritos5.cytanet.com.cy[195.14.130.179]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<demokritos5.cytanet.com.cy>
    Feb 24 18:08:54 merlin postfix/smtpd[282]: disconnect from demokritos5.cytanet.com.cy[195.14.130.179]
    Feb 24 18:12:14 merlin postfix/anvil[284]: statistics: max connection rate 1/60s for (smtp:195.14.130.179) at Feb 24 18:08:53
    Feb 24 18:12:14 merlin postfix/anvil[284]: statistics: max connection count 1 for (smtp:195.14.130.179) at Feb 24 18:08:53
    Feb 24 18:12:14 merlin postfix/anvil[284]: statistics: max cache size 1 at Feb 24 18:08:53
    Feb 24 18:12:16 merlin postfix/smtpd[317]: connect from demokritos3.cytanet.com.cy[195.14.130.227]
    Feb 24 18:12:16 merlin postfix/smtpd[317]: NOQUEUE: reject: RCPT from demokritos3.cytanet.com.cy[195.14.130.227]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<demokritos3.cytanet.com.cy>
    Feb 24 18:12:16 merlin postfix/smtpd[317]: disconnect from demokritos3.cytanet.com.cy[195.14.130.227]
    Feb 24 18:12:46 merlin postfix/smtpd[317]: connect from unknown[213.149.189.165]
    Feb 24 18:12:46 merlin postfix/smtpd[317]: NOQUEUE: reject: RCPT from unknown[213.149.189.165]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<[192.168.1.4]>
    Feb 24 18:12:47 merlin postfix/smtpd[317]: disconnect from unknown[213.149.189.165]
    Feb 24 18:12:58 merlin postfix/smtpd[317]: connect from unknown[213.149.189.165]
    Feb 24 18:12:59 merlin postfix/smtpd[317]: NOQUEUE: reject: RCPT from unknown[213.149.189.165]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<[192.168.1.4]>
    Feb 24 18:12:59 merlin postfix/smtpd[317]: disconnect from unknown[213.149.189.165]
    Feb 24 18:13:28 merlin postfix/smtpd[317]: connect from unknown[213.149.189.165]
    Feb 24 18:13:29 merlin postfix/smtpd[317]: NOQUEUE: reject: RCPT from unknown[213.149.189.165]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<[192.168.1.4]>
    Feb 24 18:13:29 merlin postfix/smtpd[317]: disconnect from unknown[213.149.189.165]
    Feb 24 18:14:09 merlin postfix/smtpd[317]: connect from unknown[213.149.189.165]
    Feb 24 18:14:09 merlin postfix/smtpd[317]: NOQUEUE: reject: RCPT from unknown[213.149.189.165]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<[192.168.1.4]>
    Feb 24 18:14:09 merlin postfix/smtpd[317]: disconnect from unknown[213.149.189.165]
    Feb 24 18:14:20 merlin postfix/smtpd[317]: connect from unknown[213.149.189.165]
    Feb 24 18:14:20 merlin postfix/smtpd[317]: disconnect from unknown[213.149.189.165]
    Feb 24 18:15:50 merlin postfix/smtpd[317]: connect from unknown[213.149.189.165]
    Feb 24 18:15:50 merlin postfix/smtpd[317]: NOQUEUE: reject: RCPT from unknown[213.149.189.165]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<[192.168.1.4]>
    Feb 24 18:15:50 merlin postfix/smtpd[317]: disconnect from unknown[213.149.189.165]
    Feb 24 18:19:10 merlin postfix/anvil[318]: statistics: max connection rate 3/60s for (smtp:213.149.189.165) at Feb 24 18:13:28
    Feb 24 18:19:10 merlin postfix/anvil[318]: statistics: max connection count 1 for (smtp:195.14.130.227) at Feb 24 18:12:16
    Feb 24 18:19:10 merlin postfix/anvil[318]: statistics: max cache size 2 at Feb 24 18:12:46
    Feb 24 18:20:09 merlin postfix/smtpd[376]: connect from merlin.2ndwivesclub.eu[192.168.1.2]
    Feb 24 18:20:09 merlin postfix/smtpd[376]: 4D4ED8123E: client=merlin.2ndwivesclub.eu[192.168.1.2]
    Feb 24 18:20:09 merlin postfix/cleanup[378]: 4D4ED8123E: message-id=<[email protected]>
    Feb 24 18:20:09 merlin postfix/qmgr[100]: 4D4ED8123E: from=<[email protected]>, size=583, nrcpt=1 (queue active)
    Feb 24 18:20:15 merlin postfix/smtpd[385]: connect from localhost[127.0.0.1]
    Feb 24 18:20:15 merlin postfix/smtpd[385]: B202081265: client=localhost[127.0.0.1]
    Feb 24 18:20:15 merlin postfix/cleanup[378]: B202081265: message-id=<[email protected]>
    Feb 24 18:20:15 merlin postfix/qmgr[100]: B202081265: from=<[email protected]>, size=1037, nrcpt=1 (queue active)
    Feb 24 18:20:15 merlin postfix/smtpd[385]: disconnect from localhost[127.0.0.1]
    Feb 24 18:20:15 merlin postfix/smtp[386]: B202081265: to=<[email protected]>, relay=none, delay=0.05, delays=0.02/0.03/0/0, dsn=5.4.6, status=bounced (mail for 2ndwivesclub.eu loops back to myself)
    Feb 24 18:20:15 merlin postfix/cleanup[378]: CBEAD81267: message-id=<[email protected]>
    Feb 24 18:20:15 merlin postfix/qmgr[100]: CBEAD81267: from=, size=2928, nrcpt=1 (queue active)
    Feb 24 18:20:15 merlin postfix/bounce[387]: B202081265: sender non-delivery notification: CBEAD81267
    Feb 24 18:20:15 merlin postfix/qmgr[100]: B202081265: removed
    Feb 24 18:20:15 merlin postfix/smtp[386]: CBEAD81267: to=<[email protected]>, relay=none, delay=0.02, delays=0.01/0/0/0, dsn=5.4.6, status=bounced (mail for 2ndwivesclub.eu loops back to myself)
    Feb 24 18:20:15 merlin postfix/qmgr[100]: CBEAD81267: removed
    Feb 24 18:20:15 merlin postfix/smtp[379]: 4D4ED8123E: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=6.7, delays=0.2/0.13/0.4/6, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as B202081265)
    Feb 24 18:20:15 merlin postfix/qmgr[100]: 4D4ED8123E: removed
    Feb 24 18:21:09 merlin postfix/smtpd[376]: disconnect from merlin.2ndwivesclub.eu[192.168.1.2]
    And conf:-
    merlin:~ alf$ postconf -n
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = all
    localrecipientmaps =
    luser_relay = postmaster
    mail_owner = _postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    messagesizelimit = 10485760
    mydestination = $myhostname,localhost.$mydomain,localhost
    mydomain = 2ndwivesclub.eu
    mydomain_fallback = localhost
    myhostname = mail.2ndwivesclub.eu
    newaliases_path = /usr/bin/newaliases
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    relayhost =
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = _postdrop
    smtpdpw_server_securityoptions = none
    smtpdrecipientrestrictions = permitmynetworks,reject_unauthdestination,permit
    smtpduse_pwserver = no
    unknownlocal_recipient_rejectcode = 550
    merlin:~ alf$
    And a rejection notice.
    Some help would be really appreciated.
    Cheers.
    John

    Add 2ndwivesclub.eu to local host aliases in Server Admin -> Mail -> Settings -> Advanced -> Hosting

  • Mail service SSL doesn't work after migration

    Well, the migration worked well, EXCEPT that I cannot get SSL to work for the mail service.
    The same SSL certificate that works fine for the web service doesn't seem to work properly for mail. Prior to the in place upgrade, everything was fine, now, mail clients get the message that certificate may have been issued by an unknown authority -- BUT ONLY FOR IMAP and POP. Using the same certificate for SMTP seems to work just fine.
    My working theory is that at one point I had to reissue the certificate completely, and that somehow, Cyrus was using the older certificate and private key, and that during the migration, things got really hosed.
    Is there any way to get the new dovecot service to use the same cert? The GUI suggests it is, but I suspect some command line trickery may be needed.
    On one final note: how does one run Keychain First Aid on the system keychain?

    For reasons I cannot explain, dovecot.conf contains a line commented out specifically excluding the CA chain file -- saying it usually isn't required.
    Removing the comment from this field (the installer generated a new file and created it on the disk, it's just commented out) resulted in SSL magically working again.
    Now the bigger question: why was option in the dovecot.conf file intentionally disabled, even though the correct information (correct imported file path, correct imported files) were populated?

  • I don't get the Mail service to work - tried everything!

    Hey there,
    I am frustrated. It's day 4 that I try to get the mail service on my machine running. Maybe someone has sme hints?
    The setup:
    - Mac Mini mid 2010
    - OS X Mavericks and Server 3.0.1
    - static IP (no Firewall or anything else, absolute in the wild)
    - registered domain-name
    - DNS A-Record: server.mydomain.org -> static IP
    - DNS MX-Record: domain, *.domain -> server.mydomain.org; server.mydomain.org -> static IP of server
    Server Configuration:
    - Server.app shows everything is fine.
    - ssh enabled for one user (works as a charme)
    - Service-Data is on another partition than Mavericks
    - Certificate: self-signed intermediate OD-Certificate (might be problematic?)
    - users: one local user and one network-user (services-only)
    - groups: workgroup, local network-group (added by the server.app itself)
    Services:
    - Websites: configured with 12 virtual-hosts some ssl (intermediate certificate) some on port 80, php enabled (All websites work perfect, no problems at all!)
    - OpenDirectory: 1 Master on server.mydomain.org
    - Mail:
    -- Service-Bubble is green, says available under server.mydomain.org
    -- Preferences: Mail available for mydomain.org (no other virtual domains)
    -- authentification: hooked everything...(any method)
    -- no relais
    -- no MB-restriction for users
    -- Filter: Virus and Junk
    I can telnet on port 110 - feedback: dovecot ready!
    I can telnet on port 995 - feedback: works... escape characeter is ' ^'.
    I can telnet on port 143 - feedback: dovecot ready!
    I can telnet on port 993 - feedback: works... escape characeter is ' ^'.
    telnet on port 25 - unable to connect, operation timed out
    telnet on port 465 - unable to connect, operation timed out
    telnet on port 587 - -feedback works: 220 server.pscience.de ESMTP Postfix
    Seems like having problem on the smtp standard ports... but why?
    When I now try to connect a client with the server (adding an OS X server Account in the System Preferences) it recognizes the server and lists its services as expected. But when Iopen Mail, the new account shows the litlle lightning and says it can't connect.
    By the way: Notes, Calendar, Reminders work fine!
    Has anyone an Idea what it could be?
    Do I need some additional DNS-stuff?
    If you need some further informations, please let me know.

    If TCP port 25 isn't open, then SMTP services won't work.  That's the port that all SMTP servers use to communicate amongst themselves.    (Sure, you can change the port your SMTP server is listening on, but you'd also have to change the port processing on all of the other SMTP servers around — and if you did manage to implement that change everywhere, the local network folks would likely just block the new port for the same reasons they blocked the old port.)
    If you have a public static IP address and have correct forward and reverse translations — host domain to IP address, and IP address to host domain name — then you don't need and very likely don't want to run your own DNS server. 
    More to help you learn how these pieces fit together and not something I'd expect you would need given you have a public static IP and public DNS here is a detailed DNS server configuration article for OS X Server; enable Show All Records and it applies to Server.app on 10.7 and later.  If you have questions after reading that, I can certainly answer them and also update the article to try to reduce the confusion or answer the question.
    Your host didn't have valid reverse DNS, so you'll want to get that cleared up, and you'll want to get the port blocks cleared, or work with the local network folks to set up a relay through one of the existing mail servers.

  • I can't get Mail Services to work...

    I've tried to setup Mail Services but when I test by setting up a client mail, following the "Checking connection to the mail server" test, I receive this;
    "The IMAP server "mail.brightmarkllc.com" is not responding."
    Here is the output of a postconf -n:
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = all
    mail_owner = _postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    messagesizelimit = 52428800
    mydomain = brightmarkllc.com
    mydomain_fallback = localhost
    myhostname = mail.brightmarkllc.com
    mynetworks = 127.0.0.0/8,10.0.1.0/24,10.0.1.192
    newaliases_path = /usr/bin/newaliases
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = _postdrop
    smtpdpw_server_securityoptions = login
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpduse_pwserver = yes
    unknownlocal_recipient_rejectcode = 550
    virtualmailboxdomains = hash:/etc/postfix/virtual_domains
    virtual_transport = lmtp:unix:/var/imap/socket/lmtp
    Thoughts? Do I have the Domain name and Host name set correctly?

    Crap, odd, but true. The ports had the wrong IP on them. I fixed that. I now see an IMAP connection, but when I send mail to the one contact I set up, the mail is rejected with this message:
    Reason: Remote SMTP server has rejected address
    Diagnostic code: smtp;554 5.7.1 <[email protected]>: Relay access denied
    My Open DIrectory service is NOT running and and the server otherwise looks standalone. Do I need to activate Open Directory and set up an Open Directory Master to get Mail to work? I'm a bit confused how I can have an IMAP connection active for a user without it, but I'm obviously a rookie at all this.
    Thanks in advance for the continued help.

  • Mail Services Stopped Working in Safari

    I have the latest versions of OS X and Safari. I noticed recently that Mail Services no longer work in Safari. I have always enjoyed the convenience of highlighting some text in a webpage and then using Services to Mail that selection. The Mail Services are now always greyed out so I can't use them. Anyone know why this might happen and how to fix it? Thanks.

    I have the latest versions of OS X and Safari. I noticed recently that Mail Services no longer work in Safari. I have always enjoyed the convenience of highlighting some text in a webpage and then using Services to Mail that selection. The Mail Services are now always greyed out so I can't use them. Anyone know why this might happen and how to fix it? Thanks.

  • Nokia browser & mail service is not working in my ...

    nokia browser & mail service is not working in my x2-02. When i select those 2 icons they didnt respond at all. Please help me.
    Solved!
    Go to Solution.

    hi mate,
    have you checked if there are any firmware updates available for your device? if there are any, please update to the latest version offered. if that fails, try reinstalling your current firmware thru Nokia Suite, and if that doesn't work, then Restore your phone to factory settings.
    Failign the above, you need to visit Nokia Care for inspection: http://nokia.com/support

  • Is there free voice mail service? if so how do i get it to work? all i see when i click the voice mail icon is the accept/decline for visual voice mail and that says theres a charge?

    Is there free voice mail service? if so how do I set it up? When I click on the voice mail icon all I see is the accept/decline agreement for Visual Voice Mail and it said something about charges will be applied on my bill so I declined.

    Your Basic voice mail is a free required program for you if you do not want Basic Visual Voice mail (free) or Premium which is a paid service. Basic Voice Mail set up is free and easy to do.
    1. Sign in to your My Verizon online account.
    2. On left side of page in Blue letters find the drop down menu. Click to open menu then go to change features and locate Basic Voice mail and click the Red add button.
    3. When you're done making this change click next at the bottom of the screen and then ok.
    4. Now go into your device and set up your  Basic voice mail program. You may continue to receive an error message for a period of time “Visual voice mail update”, just clear and disregard.

  • Mail Service Not working

    The iCloud service is down AGAIN!!!! And trying to tell apple theres a problem is virtually impossible. im not paying to tell you that the Mail service is Broken!!! I paid alot for this mac, the least you can do is ensure that mail runs correctly!!!! its dropping on a very regular bases.

    Hello;
    Ive had exactly same problem and here is the solution.
    ignore all that Microsoft updates, some how your e-mail cliant of Nokia is demaged and you have to reload it.
    http://www.nokia.com/gb-en/support/troubleshooting/?action=singleFAQ&caseid=FA139943_en_US
    This is the page and download the email client and upload it on your phone,
    all will be well.
    This is how Ive fixed mine.
    Good Luck!

  • Mail services refuse to send/receive emails.

    Hi! I think Apple Server update (PPC) 10.4.9 has screwed up my mail settings...and hence i did a clean install of OS 10.4 (Tiger) with stock software and nothing else.
    I added in the same configurations but the mail server just will not receive or send out any mails via smtp.
    Here's the postconf -n output:
    mail:~ colordoc$ postconf -n
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = all
    mail_owner = postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    messagesizelimit = 0
    mydomain = colordoc.com.sg
    mydomain_fallback = localhost
    myhostname = mail.colordoc.com.sg
    mynetworks_style = host
    newaliases_path = /usr/bin/newaliases
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = postdrop
    smtpdpw_server_securityoptions = plain,login
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpdtls_keyfile =
    smtpduse_pwserver = yes
    unknownlocal_recipient_rejectcode = 550
    And here's part of the mail.log:
    Mar 19 09:53:23 mail postfix/smtpd[339]: connect from localhost[127.0.0.1]
    Mar 19 09:53:23 mail postfix/smtpd[339]: E0D7E1E018: client=localhost[127.0.0.1]
    Mar 19 09:53:24 mail postfix/cleanup[346]: E0D7E1E018: message-id=<[email protected]>
    Mar 19 09:53:24 mail postfix/qmgr[56]: E0D7E1E018: from=<[email protected]>, size=742, nrcpt=1 (queue active)
    Mar 19 09:53:24 mail postfix/smtpd[339]: disconnect from localhost[127.0.0.1]
    Mar 19 09:53:26 mail postfix/smtpd[349]: connect from localhost[127.0.0.1]
    Mar 19 09:53:26 mail postfix/smtpd[349]: 868861E03D: client=localhost[127.0.0.1]
    Mar 19 09:53:26 mail postfix/cleanup[346]: 868861E03D: message-id=<[email protected]>
    Mar 19 09:53:26 mail postfix/qmgr[56]: 868861E03D: from=<[email protected]>, size=1137, nrcpt=1 (queue active)
    Mar 19 09:53:26 mail postfix/smtpd[349]: disconnect from localhost[127.0.0.1]
    Mar 19 09:53:26 mail postfix/smtp[347]: E0D7E1E018: to=<[email protected]>, relay=127.0.0.1[127.0.0.1], delay=3, status=sent (250 2.6.0 Ok, id=00225-01, from MTA: 250 Ok: queued as 868861E03D)
    Mar 19 09:53:26 mail postfix/qmgr[56]: E0D7E1E018: removed
    Mar 19 09:53:31 mail postfix/smtp[350]: 868861E03D: to=<[email protected]>, relay=mx2.hotmail.com[65.54.244.40], delay=5, status=sent (250 <[email protected]> Queued mail for delivery)
    Mar 19 09:53:31 mail postfix/qmgr[56]: 868861E03D: removed
    Did i forget any settings?
    I would like to get the mail service up and running before I update to apple 10.4.x.
    Please advise.
    Thanks!

    Please ignore the earlier post as I have made new progress.
    The server is up and running...
    It's a stock 10.4 Tiger server without any updates installed...
    I've madesome changes..and amazingly the system came back alive...
    I'm able to receive emails and send out emails but it's troubling me as i still see mails been deleted from queue in the mail.log
    Here's the mail postconf -n
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter =
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = all
    mail_owner = postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    messagesizelimit = 0
    mydestination = $myhostname,localhost.$mydomain,localhost,$mydomain,mail.$mydomain,www.$mydomai n,colordoc.com.sg
    mydomain = colordoc.com.sg
    mydomain_fallback = localhost
    myhostname = mail.colordoc.com.sg
    mynetworks = 127.0.0.1,202.73.35.131,202.73.35.142
    mynetworks_style = host
    myorigin = $mydomain
    newaliases_path = /usr/bin/newaliases
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    relay_domains = $mydestination
    relayhost =
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = postdrop
    smtpdclientrestrictions = permit_mynetworks permit
    smtpdpw_server_securityoptions = login,plain
    smtpdrecipientrestrictions = permitmynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpdtls_keyfile =
    smtpduse_pwserver = yes
    unknownlocal_recipient_rejectcode = 550
    and here's the mail.log:
    Mar 19 13:03:04 mail postfix/smtpd[986]: connect from unknown[202.73.35.131]
    Mar 19 13:03:04 mail postfix/smtpd[986]: warning: unknown[202.73.35.131]: SASL LOGIN authentication failed
    Mar 19 13:03:04 mail postfix/smtpd[986]: disconnect from unknown[202.73.35.131]
    Mar 19 13:03:27 mail postfix/smtpd[986]: connect from localhost[127.0.0.1]
    Mar 19 13:03:28 mail postfix/smtpd[986]: 1603122407: client=localhost[127.0.0.1]
    Mar 19 13:03:28 mail postfix/cleanup[1139]: 1603122407: message-id=<[email protected]>
    Mar 19 13:03:28 mail postfix/qmgr[747]: 1603122407: from=<[email protected]>, size=1240, nrcpt=1 (queue active)
    Mar 19 13:03:28 mail postfix/smtpd[986]: disconnect from localhost[127.0.0.1]
    Mar 19 13:03:31 mail postfix/smtp[1140]: 1603122407: to=<[email protected]>, relay=mx4.hotmail.com[65.54.245.104], delay=3, status=sent (250 <[email protected]> Queued mail for delivery)
    Mar 19 13:03:31 mail postfix/qmgr[747]: 1603122407: removed
    Mar 19 13:03:33 mail postfix/smtpd[986]: warning: 202.73.35.131: hostname brasbash.colordoc.com.sg verification failed: Host not found
    Mar 19 13:03:33 mail postfix/smtpd[986]: connect from unknown[202.73.35.131]
    Mar 19 13:03:33 mail postfix/smtpd[986]: warning: unknown[202.73.35.131]: SASL LOGIN authentication failed
    Mar 19 13:03:33 mail postfix/smtpd[986]: disconnect from unknown[202.73.35.131]
    Mar 19 13:04:40 mail postfix/smtpd[986]: warning: 202.73.35.131: hostname brasbash.colordoc.com.sg verification failed: Host not found
    Mar 19 13:04:40 mail postfix/smtpd[986]: connect from unknown[202.73.35.131]
    Mar 19 13:04:40 mail postfix/smtpd[986]: warning: unknown[202.73.35.131]: SASL LOGIN authentication failed
    Mar 19 13:04:40 mail postfix/smtpd[986]: disconnect from unknown[202.73.35.131]
    I think i'm having a false sense of security....
    Can someone please point out if I have misconfigured the server...
    Thanks!

  • Mail Service Errors

    Hi,
    I'm running Server 10.4.11 for a local newspaper and last week their e-mail services came to a crashing halt. It slowed the system down so much it started to interfere with operations between client/server, so I shut down the mail services until after their production cycle.
    Today I turned back on the service and reconstructed the database (was getting a DBError last week). I also rebuilt all of the email accounts... none of which were anywhere near full.
    I was getting this in the POP log (set to Information level logging) right after I turned back on the service this evening. It is just a small portion of the log... but it repeats basically the same thing. Can anyone point me in the direction of fixing the service?
    Thanks,
    Alan
    Jan 21 19:27:21 BuffaloBulletin pop3[12406]: DBERROR: critical database situation
    Jan 21 19:27:21 BuffaloBulletin master[28101]: service pop3 pid 12406 in READY state: terminated abnormally
    Jan 21 19:27:21 BuffaloBulletin pop3[12407]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 19:27:21 BuffaloBulletin pop3[12407]: DBERROR: critical database situation
    Jan 21 19:27:21 BuffaloBulletin master[28101]: service pop3 pid 12407 in READY state: terminated abnormally
    Jan 21 19:27:22 BuffaloBulletin pop3[12410]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 19:27:22 BuffaloBulletin pop3[12410]: DBERROR: critical database situation
    Jan 21 19:27:22 BuffaloBulletin master[28101]: service pop3 pid 12410 in READY state: terminated abnormally
    Jan 21 19:27:22 BuffaloBulletin pop3[12411]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 19:27:22 BuffaloBulletin pop3[12411]: DBERROR: critical database situation
    Jan 21 19:27:22 BuffaloBulletin master[28101]: service pop3 pid 12411 in READY state: terminated abnormally

    Thanks for the suggestion. I followed the instructions for manually reconstructing the cyrus mail database in Terminal. Once I started the service back up (did this twice with same results), here is the log that was generated:
    Jan 21 23:28:38 BuffaloBulletin reconstruct[28146]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:28:38 BuffaloBulletin reconstruct[28146]: DBERROR: critical database situation
    Jan 21 23:29:18 BuffaloBulletin deliver[28168]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:18 BuffaloBulletin deliver[28173]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:18 BuffaloBulletin deliver[28176]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:19 BuffaloBulletin deliver[28182]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:19 BuffaloBulletin deliver[28188]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:19 BuffaloBulletin deliver[28187]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:19 BuffaloBulletin deliver[28189]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:20 BuffaloBulletin master[28191]: process started
    Jan 21 23:29:20 BuffaloBulletin deliver[28193]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:20 BuffaloBulletin deliver[28194]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:20 BuffaloBulletin deliver[28198]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:20 BuffaloBulletin deliver[28204]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:20 BuffaloBulletin deliver[28201]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:20 BuffaloBulletin deliver[28200]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:20 BuffaloBulletin deliver[28203]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:21 BuffaloBulletin deliver[28206]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:21 BuffaloBulletin deliver[28208]: connect(/var/mail/socket/lmtp) failed: Connection refused
    Jan 21 23:29:22 BuffaloBulletin ctl_cyrusdb[28196]: verifying cyrus databases
    Jan 21 23:29:22 BuffaloBulletin ctl_cyrusdb[28196]: skiplist: recovered /var/mail/mailboxes.db (29 records, 4480 bytes) in 0 seconds
    Jan 21 23:29:22 BuffaloBulletin ctl_cyrusdb[28196]: done verifying cyrus databases
    Jan 21 23:29:23 BuffaloBulletin master[28191]: No address associated with nodename, disabling sieve
    Jan 21 23:29:23 BuffaloBulletin master[28191]: ready for work
    Jan 21 23:29:23 BuffaloBulletin ctl_cyrusdb[28220]: checkpointing cyrus databases
    Jan 21 23:29:24 BuffaloBulletin ctl_cyrusdb[28220]: done checkpointing cyrus databases
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29299 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29300]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29300]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29300 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29301]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29301]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29301 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29302]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29302]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29302 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29303]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29303]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29303 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29304]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29304]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29304 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29305]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29305]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29305 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29306]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29306]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29306 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29307]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29307]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29307 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29308]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29308]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29308 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29309]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29309]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29309 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29310]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29310]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29310 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29311]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29311]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29311 in READY state: terminated abnormally
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29312]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:44 BuffaloBulletin lmtpunix[29312]: DBERROR: critical database situation
    Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29312 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29313]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29313]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29313 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29314]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29314]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29314 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29315]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29315]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29315 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29316]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29316]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29316 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29317]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29317]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29317 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29318]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29318]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29318 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29319]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29319]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29319 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29320]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29320]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29320 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29321]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29321]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29321 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29322]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29322]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29322 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29323]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29323]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29323 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29324]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29324]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29324 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29325]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29325]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29325 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29326]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29326]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29326 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29327]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29327]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29327 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29328]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29328]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29328 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29329]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29329]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29329 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29330]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29330]: DBERROR: critical database situation
    Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29330 in READY state: terminated abnormally
    Jan 21 23:30:45 BuffaloBulletin lmtpunix[29331]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:30:46 BuffaloBulletin lmtpunix[29331]: DBERROR: critical database situation
    Jan 21 23:30:46 BuffaloBulletin master[28191]: service lmtpunix pid 29331 in READY state: terminated abnormally
    : fatal region error detected; run recovery
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29835]: DBERROR: critical database situation
    Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29835 in READY state: terminated abnormally
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29836]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29836]: DBERROR: critical database situation
    Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29836 in READY state: terminated abnormally
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29837]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29837]: DBERROR: critical database situation
    Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29837 in READY state: terminated abnormally
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29838]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29838]: DBERROR: critical database situation
    Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29838 in READY state: terminated abnormally
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29840]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29840]: DBERROR: critical database situation
    Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29840 in READY state: terminated abnormally
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29841]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29841]: DBERROR: critical database situation
    Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29841 in READY state: terminated abnormally
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29842]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29842]: DBERROR: critical database situation
    Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29842 in READY state: terminated abnormally
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29843]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29843]: DBERROR: critical database situation
    Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29843 in READY state: terminated abnormally
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29844]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29844]: DBERROR: critical database situation
    Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29844 in READY state: terminated abnormally
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29845]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:19 BuffaloBulletin lmtpunix[29845]: DBERROR: critical database situation
    Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29845 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29846]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29846]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29846 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29847]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29847]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29847 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29848]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29848]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29848 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29849]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29849]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29849 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29850]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29850]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29850 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29851]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29851]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29851 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29852]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29852]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29852 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29853]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29853]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29853 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29854]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29854]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29854 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29855]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29855]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29855 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29856]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29856]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29856 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29857]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29857]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29857 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29858]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29858]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29858 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29859]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29859]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29859 in READY state: terminated abnormally
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29860]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:20 BuffaloBulletin lmtpunix[29860]: DBERROR: critical database situation
    Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29860 in READY state: terminated abnormally
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29861]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29861]: DBERROR: critical database situation
    Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29861 in READY state: terminated abnormally
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29862]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29862]: DBERROR: critical database situation
    Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29862 in READY state: terminated abnormally
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29863]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29863]: DBERROR: critical database situation
    Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29863 in READY state: terminated abnormally
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29864]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29864]: DBERROR: critical database situation
    Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29864 in READY state: terminated abnormally
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29865]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29865]: DBERROR: critical database situation
    Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29865 in READY state: terminated abnormally
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29866]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29866]: DBERROR: critical database situation
    Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29866 in READY state: terminated abnormally
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29867]: DBERROR db4: PANIC: fatal region error detected; run recovery
    Jan 21 23:31:21 BuffaloBulletin lmtpunix[29867]: DBERROR: critical database situation
    Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29867 in READY state: terminated abnormally
    Jan 21 23:31:21 BuffaloBulletin master[28191]: exiting on SIGTERM/SIGINT
    Jan 21 23:31:21 BuffaloBulletin deliver[28264]: backend_connect(): couldn't read initial greeting: (null)

  • Major Mail Service Panic after upgrade! Customer about to kill me!

    Me again.
    As mentioned in another thread, I had to upgrade an Xserve from 10.3.9 to 10.4.3 for a customer. When I ran the upgrade I discovered that the volume containing the mail database was damaged. I wasted a day getting the data off this onto another drive, then did the upgrade. Because the mail database had been moved and might have the odd missing file I used mailbfr -o and mailbfr -f at this point. Now, all client mail folders are back as they should be but all new mail is stuck in the queue. Outgoing mail can be sent successfully.
    Now, I know an amateur like me shouldn't be messing with the config files willy-nilly to try and fix this without a clear idea of what's going on. However, given that the customer and his 20 staff are going mad waiting for their mail I tried to get it right by directly comparing their config files with the equivalents on my own 10.4.3 server which is set up more or less identically and is working.
    I will get lynched if I can't make this work soon. Here's postconf -n and a snippet of the smtp log. Please someone look at this and save my life!!
    mail:/var/log root# postconf -n
    alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
    always_bcc =
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    enableserveroptions = yes
    inet_interfaces = all
    luser_relay = postmaster
    mail_owner = postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    mapsrbldomains = dun.dnsrbl.net,relays.ordb.org,bl.csma.biz,bl.spamcop.net,sbl-xbl.spamhaus.org
    messagesizelimit = 0
    mydestination = $myhostname,localhost.$mydomain,mail.mandm.uk.com,192.168.1.100,mandm.uk.com,re ed-munkenbeck.com,212.18.249.218,mail.reed-munkenbeck.com
    mydomain = mandm.uk.com
    mydomain_fallback = localhost
    myhostname = mail.mandm.uk.com
    mynetworks = 127.0.0.0/8
    mynetworks_style = host
    newaliases_path = /usr/bin/newaliases
    ownerrequestspecial = no
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    recipient_delimiter = +
    relayhost =
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = postdrop
    smtpdclientrestrictions = permit_mynetworks hash:/etc/postfix/smtpdreject rejectrblclient bl.csma.biz rejectrblclient dun.dnsrbl.net rejectrblclient relays.ordb.org rejectrblclient bl.spamcop.net rejectrblclient sbl-xbl.spamhaus.org permit
    smtpdenforcetls = no
    smtpdpw_server_securityoptions = cram-md5
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpdtlsloglevel = 0
    smtpduse_pwserver = yes
    smtpdusetls = no
    unknownlocal_recipient_rejectcode = 550
    virtualmailboxdomains =
    mail:/var/log root#
    smtp log:
    Jan 5 12:35:17 mail postfix/master[20503]: daemon started -- version 2.1.5
    Jan 5 12:35:17 mail postfix/qmgr[20506]: 3C1983B7F0D82: from=<[email protected]>, size=5704, nrcpt=1 (queue active)
    Jan 5 12:35:17 mail postfix/qmgr[20506]: 8C51A3B7F13CA: from=<[email protected]>, size=4047, nrcpt=1 (queue active)
    Jan 5 12:35:17 mail postfix/qmgr[20506]: 91B7D3B7F13A8: from=<[email protected]>, size=2638, nrcpt=1 (queue active)
    Jan 5 12:35:17 mail postfix/qmgr[20506]: CF9FB3B7F13AF: from=, size=5145, nrcpt=1 (queue active)
    Jan 5 12:35:17 mail postfix/pipe[20510]: 3C1983B7F0D82: to=<[email protected]>, relay=cyrus, delay=4489, status=deferred (temporary failure. Command output: couldn't connect to lmtpd: Connection refused_ 421 4.3.0 deliver: couldn't connect to lmtpd_ )
    Jan 5 12:35:17 mail postfix/pipe[20517]: 8C51A3B7F13CA: to=<[email protected]>, relay=cyrus, delay=2301, status=deferred (temporary failure. Command output: couldn't connect to lmtpd: Connection refused_ 421 4.3.0 deliver: couldn't connect to lmtpd_ )
    Jan 5 12:35:17 mail postfix/pipe[20514]: CF9FB3B7F13AF: to=<[email protected]>, relay=cyrus, delay=2307, status=deferred (temporary failure. Command output: couldn't connect to lmtpd: Connection refused_ 421 4.3.0 deliver: couldn't connect to lmtpd_ )
    Jan 5 12:35:17 mail postfix/pipe[20515]: 91B7D3B7F13A8: to=<[email protected]>, relay=cyrus, delay=2307, status=deferred (temporary failure. Command output: couldn't connect to lmtpd: Connection refused_ 421 4.3.0 deliver: couldn't connect to lmtpd_ )
    Other symptoms since upgrade: Server Admin refuses to turn on Mailing Lists. There's one list that was in use before the upgrade. If I click 'Enable Mailing Lists' and press Save, the box goes unchecked again as soon as the screen refreshes. Mailaccess.log (as shown in SA as the IMAP log)remains empty. Like the Mailing Lists issue above, I can't change the log detail levels; they just reset to what they were before.
    Anything else anyone wants to know I'll post it.
    Xserve G5 2.0DP, 2Gb RAM, 10.4.3 (u/g from 10.3.9)   Mac OS X (10.4)  
    G4 and Xserve   Mac OS X (10.4)  

    aha. a-bloody-ha.
    I'll live to fight another day. The log entries about the stage. folder got me thinking and I realised that there was something wrong with the permissions. because I'd had to 'rescue' the mail database by moving to another volume, the permissions weren't right. Now, I had run mailbfr and watched it say it was fixing the ownerships and permissions on all this; I shouldn't have taken this for granted. The stage. folder was owned by me (admin) with read-only for everyone else. I changed it (heck, I changed the whole directory tree) to read-write for everyone and instantly mail started pouring in to everyone's accounts.
    Everything is now working normally. It still bothers me that the whole shebang seems so fragile - especially in so far as the Server Admin app has at best only a tenuous grasp on the config files it's supposed to be supporting. Looking back over the past two days I can see that the basic setup was right in the first place but the manual changes I've been making in the various conf and cf files were ones that SA was supposed to be able to do for me. The whole point of having Server Admin>Settings>Logging is so you can set the log level right there - not in bloody pico via the bloody command line. Sorry - I'm tired and a little punch-drunk. It also bothers me that, having learned my humble skills on AppleShare 6 (and MacDNS), we're now in a place where none of the key components of the server are actually made by Apple, documented by Apple, or properly supported by Apple. Since Mail Service isn't a closed box with 'Apple' written on it, but a collection of dozens of interconnected third-party processes working in tandem, there really ought to be a 'master document' that shows the complete flow through the system. Most of you guys are proper experts and I'm truly grateful you're there - but I'm not afraid to admit that I didn't actually know that every message had to pass though a folder called stage. on its way to delivery and it would have nice to have been able to find that information in one of Apple's manuals. If I'd known I might have looked at it sooner.
    The customer in this case is a firm of architects; they're creatives; non-technical; Apple-lovers precisely because they love the ease of use, the style and the non-pointy-headed approach of Apple's kit. I'm reminded that when this customer bought this Xserve 18 months ago, I made them buy the 3 year service contract for it. But when during the initial setup NAT wouldn't work properly I called Apple for help and they told me that 'setup problems aren't covered'. Good Grief. 450 quid. And let's not forget 700 quid for the 10.4 software.
    Now, having saved myself from being lynched by the customer I'm probably going to be strung up by the very people on this list that people like me have to rely on when we get into trouble.
    So, to save you all the trouble - yes, I'm a rank amateur; yes, I should do more homework; yes, I promise to keep googling and searching and reading and playing with my in-house machine... I don't promise to do a course on it since 'MacOs Server Essentials' is $2,000 to start with, and I don't have that kind of money.
    Think I'd better go have a lie down.

  • ERROR: Cannot start mail services, configuration directory does not exist

    I'm running an Xserve G5 with one internal boot drive and one RAID using the other two internal drives. I used Apple's Disk Utility to set-up the RAID.
    Back in early December, I moved my mail database and mail store to the RAID. Ever since, when I restart the server, the mailaccess.log generates the following error:
    Jan 23 18:51:33 mail master[47]: ERROR: Cannot start mail services, configuration directory does not exist: /Volumes/RAID/mail.data/db
    I'm speculating this is a timing error that gets created when Postfix initially can't find the RAID. Then, it must try again and find it because the error message does not repeat and mail starts running.
    Is this something to worry about?

    Hi Joel,
    You're right, it's a timing issues. The mail system is ready for work before the file system is mounted. It's benign.
    Jeff

Maybe you are looking for