SMTP SERVICE

Hi,
Please let me know how to activate the SMTP service in SRM .
Regards,
Manu

MANU AGRAWAL wrote:Hi
Please go through the SAP OSS Note details below ->
Note 455140 - Configuration of e-mail, fax, paging or SMS using SMTP
>
>
>Summary
Symptom
How do you configure e-mail, fax, paging or SMS in the SAP Web Application Server using SMTP?
Which prerequisites and settings are required outside the SAP system?
Other terms
INT, FAX, PAG, SAPconnect, SMTP
Reason and Prerequisites
Some information is missing.
Solution
General information, architecture, prerequisites, system environment
When e-mails are transferred using SMTP, the SAP Web Application Server communicates directly with a mail server. No gateway or connector is necessary.
You can use any SMTP-compatible product as a mail server.
The SAP system always transfers the outbound mails to a single mail server. You can set its host address and port number.
The SAP system can receive inbound mails from any number of mail servers. You can reach each client using separate, configurable port numbers. You can address the SAP system or its client most effectively by using an individual subdomain for each client (for example, "crm-prod.company.com"). The assignment of these subdomains to host name and port numbers of the SAP system is defined by the routing rules on the mail servers.
As of Release 6.20, you can also send and receive fax and SMS or paging messages using SMTP. These are packed in e-mails for this purpose. When sending, the mail server refers to the domain of the recipients' addresses, and directs the e-mails either to a internal company fax/SMS server (for example "[email protected]") or to an external provider (for example, "[email protected]"). When receiving, the fax or SMS server or the provider sends e-mails to addresses with the domain of the SAP system (for example "[email protected]").
Configuration
1. Profile parameter
To be able to use the SMTP functions, you must adjust the profile of the SAP Web Application Server. We recommend that you activate SMTP on all application servers of an SAP system. If this is not the case, the SAPconnect send job may only be scheduled for servers on which SMTP is active. The scheduling is then done by the standard job definition (transaction SM36) rather than by the SAPconnect administration (transaction SCOT, for a description, see 4.c).
For SMTP, you must set the profile parameters listed below. The placeholder <*> stands for a number with which the parameters that can occur several times are numbered sequentially, starting with 0.
a) icm/server_port_<*> = PROT=SMTP,PORT=<port>
This opens a TCP/IP port for receiving mails by the SMTP Plug-In. <port> specifies the number of the port that you should use.  This must not be occupied by any other program on this host (for example, Sendmail usually uses port 25). If no mails (including status notifications) are to be received in this SAP system, <port> can be set to 0.
You can use the TIMEOUT option to define a maximum wait time for a response from the mail server (in seconds).
b) is/SMTP/virt_host_<*> = <host>:<port>,<port>,...;
This defines a "virtual mail host" for receiving mails. If all incoming mails (including status notifications) are to be received and processed in a single client of this SAP system, this parameter is not required (an entry is/SMTP/virt_host_0 = : is then assumed by default). If you want several clients to be able to receive, you must create a virtual mail host for every client. <host> specifies the name of the host to which incoming mails are addressed. The "*" value can also be specified here if the mail distribution is to occur independently of the addressed host. Important: If the mail is to be distributed according to host names, you must assign different IP addresses to these host names. <port> specifies the number of a port to which incoming mails are addressed. Several ports may be specified for each host, and several hosts (with several ports if necessary) may be specified for each virtual mail host. Important: The parameter line must always be completed with a semicolon (even if only one host is involved).
The assignment of virtual mail hosts to clients is carried out in the SAP system (see 3).
              Example:
With two clients capable of receiving mail, the profile parameters could read as follows (as of Release 6.20):
   icm/server_port_0 = PROT=HTTP,PORT=1080
  icm/server_port_1 = PROT=HTTPS,PORT=1443
  icm/server_port_2 = PROT=SMTP,PORT=25000,TIMEOUT=180
  icm/server_port_3 = PROT=SMTP,PORT=25001,TIMEOUT=180
  is/SMTP/virt_host_0 = *:25000;
   is/SMTP/virt_host_1 = *:25001;
2. User administration (transaction SU01)
a) System user
In each client of an SAP system in which incoming mails (or status notifications for sent mails) are to be received, a system user must be created to process the incoming messages. To do this, use transaction SU01 to create a user of the type "system", and assign the "S_A.SCON" profile to this user.
Important: Contrary to the documentation for user types, users of type "system" are also subject to password expiry, which can prevent the receipt of mails. To avoid this, use user type "service" until a correction of the incorrect behavior of type "system" is available.
b) User addresses
Each individual user who wants to receive e-mails in an SAP system needs an Internet mail address. This is also used as a sender address for sending e-mails. In transaction SU01, enter the Internet mail address of a user in the field "E-Mail" under "Address". As a domain, use the domain of the SAP system client if possible (see "General information" above and 4.a), for example "[email protected]".
3. Client assignment (transaction SICF)
For each client of an SAP system in which incoming mails (or status notifications for sent mails) are to be received, and processed if necessary, you must create an SMTP server in which the assignment to a virtual mail host as well as the logon data is defined. In transaction SICF, an SMTP server (envelope icon) should already be available in every SAP system. This is delivered by SAP. Use this for the first client that you want to be able to receive mails, and create a new SMTP server for every other client. You must make the following settings on the SMTP servers:
a) Host data
For "Profile Parameter Number", enter the sequence number of a parameter is/SMTP/virt_host_<*> from the profile. If you have only one client and did not create such a parameter in the profile, enter 0.
b) Service data
Enter the client into which the mails received using this virtual mail host are to be directed, as well as the logon data (user, password, language) of the service user that was created for inbound mails (see 2.a).
c) Handler list
Enter CL_SMTP_EXT_SAPCONNECT in the first position.
              As of Release 6. 20, you must activate the SMTP server after you create or change it (Service/Virt.Host --> Activate, or right-click).
4. SAPconnect administration (transaction SCOT)
You have to make the SAPconnect settings separately in each client from which e-mails are to be sent or in which e-mails are to be received.
a) Default domain
The domain of this SAP system client is defined here, for example, crm-prod.company.com. It is used for the following purposes:
The SMTP Plug-In logs on to the mail server with the domain as ID.
The message ID of outgoing mails is created with this domain.
If an SAP user who has not entered an Internet mail address in their user master record sends an e-mail, a sender address is generated from the SAP user name and this domain, for example [email protected].
b) Nodes
There are different types of node in SAPconnect:
SMTP nodes (for the SMTP function of the SAP application server)
HTTP nodes (for paging or SMS providers using Web services, as of 6.20)
RFC nodes (for old RFC-compatible e-mail/fax/paging gateways)
                       There is always a single SMTP node in each client. It is created automatically by the system and cannot be deleted. It is configured as follows (double-click on the node name):
Select "Node in use".
Under "Mail Host" and "Mail Port", specify the mail server to which outbound mails are to be transferred.
Select "Set" for "Internet".
Specify address areas of recipient addresses that are to be reached using these nodes (usually "*" if all e-mails are to be sent using SMTP).
For "Output Formats for SAP Documents", the following is recommended:
   SAPscript / Smart Forms      PDF
   ABAP List                    HTM
   Business Object / Link        HTM
   RAW Text                      TXT
                       If fax messages are also to be sent using SMTP:
Select "Set" for "Fax".
Specify address areas of recipient addresses that are to be reached using these nodes (usually "*" if all faxes are to be sent using SMTP).
For "Output Formats for SAP Documents", the following is recommended:
   SAPscript / Smart Forms      PDF
   ABAP List                    PDF
   Business Object / Link        TXT
   RAW Text                      TXT
For "Conversion into Internet Address", enter the domain of the fax server or fax provider. The local part of the Internet address is generated automatically by the system. The address then has the form "FAX=+recipientnumber@domain".
                       If paging or SMS messages are also to be sent using SMTP:
Select "Set" for "Pager(SMS)".
Specify address areas of recipient addresses that are to be reached using these nodes (usually "*" if all paging or SMS messages are to be sent using SMTP).
For "Conversion into Internet Address", enter the domain of the paging or SMS server or paging or SMS provider. The local part of the Internet address is generated automatically by the system. The address then has the form "SMS=+recipientnumber@domain".
                       Important: To be able to use paging or SMS in the SAP system, names must be defined for the messaging services to be used (e.g. "SMS"). You can do this using transaction SA14.
c) Send job
E-mails that are sent from an SAP application are merely put into a queue. A periodically running background process, the SAPconnect send job, takes the e-mails from the queue and sends them by Internet. This job can be scheduled from SAPconnect administration as follows:
Choose "View" --> "Jobs". Check whether a job is already scheduled (displayed as a calendar icon).
Choose "Job" --> "Create", and specify a job name.
Place the cursor on the "SAP&CONNECTALL" variant, and choose "Schedule Job".
Choose "Schedule periodically".
Specify a time interval (for example, 10 minutes), and choose "Create".
d) Receiving
With the settings made so far, SAP users can already receive e-mails in their inbox in the Business Workplace (transaction SBWP) at the address entered in the user master record.
If, on receipt of e-mails to a specific address or with specific contents (for example XML documents), you want a program that processes these e-mails to start automatically, you can configure this under "Settings" --> "Inbound Processing".
If, on receipt of e-mails to a specific address or from a specific sender, you want these to be directed automatically to another recipient or a distribution list, you can configure this under "Settings" --> "Inbound Distribution".
5. Settings on the mail server (SAP-external configuration)
To be able to receive mails in the SAP system, you need to set your mail server so that certain mail addresses are forwarded to one or several SAP systems or clients. For this purpose, you need to define routing rules that assign a mail host and/or port to address areas (generic address parts, usually the domain), for example:
      *@crm-prod.company.com  -->  SAPWASHost:25000
      *@crm-test.company.com  -->  SAPWASHost:25001
For more information about the exact setting procedure, see the mail server documentation. Note 546147 describes where the documentation can be found for the Microsoft Exchange 2000 Server, and what to do if your mail server does not allow routing to ports other than port 25.
Header Data
Release Status: Released for Customer
Released on: 01.10.2007  13:43:04
Priority: Recommendations/additional info
Category: Installation information
Primary Component: BC-SRV-COM Communication Services: Mail, Fax, SMS, Telephony
Secondary Components: BC-SRV-COM-SPL eMail, Fax and Paging using SMTP Plug-in
Affected Releases
Software
Component Release From
Release To
Release And
subsequent
SAP_BASIS 60 610 640  
SAP_BASIS 70 700 700 X
Related Notes
960088 - FAQ: Sending SD messages externally
833396 - Notification of tester with status changes of message
779972 - SURVEY: Configuration required to receive emails
622464 - Change: Password change req. entry for "SYSTEM" user type
607108 - Problem analysis when you send or receive e-mails
594428 - SXC: Exchange 2003 Server is not supported
581035 - Problems with SMTP and virtual hosts with the same port
546147 - SMTP plug-in: MS Exchange sends only to port 25
519664 - Installation of SAP SEM Release 3.1B GA
519658 - Upgrade to SAP SEM Release 3.1B GA
511025 - Bid invitation: No confirmation of receipt
455142 - SAPconnect: Configuration paging/SMS via HTTP
455129 - Paging/SMS in different SAP releases
455127 - E-mail (SMTP) in different SAP releases
101573 - Internet Mail Gateway: Versions
17194 - Telefax in various SAP Releases
Print Selected Notes (PDF) 
Attributes
Attribute Value
Transaction codes EMAIL
Transaction codes HIER
Transaction codes SA14
Transaction codes SBWP
Transaction codes SCOT
Transaction codes SICF
Transaction codes SM36
Transaction codes SU01
weitere Komponenten 0000036371
>

Similar Messages

  • SMTP service failure

    I have been quite happy with JES messaging server 2005Q4 until recently. The other night SMTP service failed at around 1:04am. I had to restart the processes using "imsimta restart". Then, last night, the same thing happened again but this time at 1:29am. I had to restart the process again. I got the following alarm message from the server before it stops responding (similar alarm for the other night as well);
    Server instance: /opt/SUNWmsgsr
    Alarmid: serverresponse
    Instance: smtp
    Description: server response time in seconds
    Current measured value (13/Jun/2006:01:26:21 -0700): 80
    Lowest recorded value: 0
    Highest recorded value: 80
    Monitoring interval: 600 seconds
    Alarm condition is when over threshold of 10
    Number of times over threshold: 10
    I checked my cron list to see if something is running around that time, but nothing. There is also no clue in any log files including /var/adm/messages and /var/opt/SUNWmsgsr/log/* . Nothing has been logged about any failure or error.
    I enabled the watcher to restart the failed processes now, but I need to know why it started failing.
    I also tried to find a correlation between the number of SMTP connections and that failure. Although it seems to be unneededly high due to spams, there are some other times that it hits much higher values, and it survives. So, it does not seem to be the number of connections handled by the server. It is something else, but what?
    Any comments!

    Here are the details;
    1) lithium# imsimta version
    Sun Java(tm) System Messaging Server 6.2-3.04 (built Jul 15 2005)
    libimta.so 6.2-3.04 (built 01:43:03, Jul 15 2005)
    SunOS lithium 5.10 Generic sun4u sparc SUNW,UltraSPARC-IIi-Engine
    2) - SMTP was not responding.
    - No core file.
    - I do not know how to allow/disallow a core file. But, I guess, the system can produce a core file, because I have seen core files couple of times so far while I was trying to get it running during the installation phase.
    3) The followings are taken before the restart:
    lithium# imsimta process
    USER PID S VSZ RSS STIME TIME COMMAND
    mailsrv 349 S 32528 6552 Jun_12 01:08 /opt/SUNWmsgsr/lib/dispatcher
    mailsrv 351 S 32360 6624 Jun_12 00:11 /opt/SUNWmsgsr/lib/job_controller
    mailsrv 22888 S 33016 11232 01:25:21 00:00 /opt/SUNWmsgsr/lib/tcp_smtp_server
    mailsrv 22895 S 33728 13280 01:25:59 00:01 /opt/SUNWmsgsr/lib/tcp_smtp_server
    mailsrv 22896 S 33744 13344 01:25:59 00:01 /opt/SUNWmsgsr/lib/tcp_smtp_server
    lithium# top
    load averages: 0.23, 0.14, 0.13 01:45:12
    64 processes: 55 sleeping, 7 running, 1 zombie, 1 on cpu
    CPU states: 96.0% idle, 1.6% user, 2.4% kernel, 0.0% iowait, 0.0% swap
    Memory: 384M real, 17M free, 618M swap in use, 119M swap free
    PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND
    499 root 48 59 0 0K 0K run 385:57 2.95% ns-slapd
    23666 mailsrv 1 59 0 32M 10M sleep 0:00 2.54% msprobe
    23665 root 1 59 0 3720K 1368K cpu 0:00 0.72% top
    658 mailsrv 3 59 0 121M 7696K sleep 138:01 0.48% mshttpd
    23654 root 1 59 0 8304K 4624K sleep 0:00 0.31% sshd
    349 root 14 59 0 32M 6552K sleep 1:08 0.27% dispatcher
    597 root 70 59 0 99M 5760K run 69:51 0.24% ns-httpd
    747 root 118 59 0 413M 53M run 85:45 0.22% webservd
    730 root 31 59 0 138M 18M run 55:02 0.19% webservd
    79 daemon 3 59 0 4256K 1544K sleep 0:02 0.09% kcfd
    656 mailsrv 2 59 0 103M 2680K run 18:42 0.06% stored
    23657 root 1 59 0 8088K 2448K sleep 0:00 0.05% sshd
    23659 root 1 59 0 1272K 1000K sleep 0:00 0.05% sh
    655 mailsrv 3 59 0 9080K 528K sleep 11:50 0.04% enpd
    778 root 1 59 0 2600K 312K run 11:13 0.04% magt
    4) No messages in /var/adm/messages, not even a line
    5) details in (3)
    6) No response to SMTP port connection

  • RFC1845: SMTP Service Extension for Checkpoint/Restart

    Hello, I'm wondering if it's possible to enable this extension to the Mac OS X Server 10.5.6 SMTP service. My internet provider requires it because of some "security policy": my server has been "grey listed" because it is not compliant with this RFC.
    Does anyone knows anything about it? How to obtain and install, how to deal with configuration files and so on.
    Thank you

    The mail server is working perfectly, sending and receiving mails without problems. No errors in log files and no clues in /var/log/mail.log.
    My ISP told me that my mail server has been automatically GREYlisted (by one of their customers' smtp server) for being not compliant with this RFC. He told me that a message could not be "re-sent", and this was the reason for the greylisting. He also told me that he manually removed my server from the greylist so I do not have any "mail problem".
    But I'm worried about it, so I need to understand what happened and maybe find a solution.
    Are you sure that RFC1845 compliance is not necessary?
    Thanks for your help and sorry for my bad english!

  • Windows SMTP service - restrictions

    Hi
    I have installed a SMTP service under IIS 6.0 in windows 2008 R2
    I would like to know if is possible to restrict the SMPT traffic to specific domains
    Example: i only want that only relay traffic to google.com
    Thanks in advance.

    Hi,
    Please refer to Don's suggestion in following thread and check if can help you.
    restrict destination domain on SMTP service
    In addition, for your current issue, I suggest that you should post it in
    IIS forum. I believe we will get a better assistance there.
    Hope this helps.
    Best regards,
    Justin Gu
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Remove SMTP Service from SA Certificate that was accidentally added

    I inadvertently assigned the SMTP service to an SA certificate that was meant for IIS only. I already tried to highlight the certificate and run "Assign Services to Certificate", uncheck SMTP, it runs, but doesn't remove it. I also tried to Export
    it, but when I attempt to Remove it, I get an error the it would stop the Transport service and cause instability. It won't remove it anyway, I just get an OK to check. I can certainly use the EMS, but is this going to work?
    The root issue is that Outlook clients get a certificate error as this stepped on the self-signed certificate. My concern is that I don't want to a CSR for a New Certificate and get a new one as the CA already issued this to me. Can someone give an
    assurance that I can:
    1. Stop Transport service.
    2. Export my SA Certificate.
    3. Remove the SA Certificate.
    4. Import the SA Certificate.
    5. Assign it to IIS Service only.
    At this point my SA certificate would be only assigned to IIS. Right now, both my internal and SA Certificates have SMTP assigned to them. I am assuming I will have to back and reissue the internal certificate for SMTP again to fix the Outlook client warnings?
    Michael Maxwell

    Depending upon the version of Exchange, yes there is different logic for selecting the SMTP cert.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • SMTP Service crashes when i enable reserve lookup?

    I have got NMS 4.15 running on linux. When i enable reverse lookup my SMTP services starts crashing. Can anybody tell me what is the solution to this?

    I'm not an NMS guru by any means.
    First, 4.15 is older, get 4.17, at least the SMTP daemon.
    Second, get off of NMS ASAP. :) Seriously, NMS has problems and the sooner you migrate to iMS the happier you will be. I realize that iMS does not run on Linux right now. I suspect that iMS 6 will be supported on Linux.
    Why do you want to turn on reverse lookup? Sure you'll get some nice name in your headers instead of only IP address but your performance will also suffer.
    -Chad-

  • SMTP service Migration on MDM server

    Hello
    We are migrating the SMTP services on the MDM server.
    Do we need to make changes to the MDM configuration files, if any ?
    I had installed MDM earlier and I don't remember any config file changes.
    Please guide me. Thanks
    Prakash

    Thanks Christian
    I had already checked the mds.ini file and I don't see any SMTP server entries.
    It means that SMTP server is not configured on MDM server so far?
    Nathan

  • SMTP service not responding (ims 5.2)

    Are rebooting our NT server, the SMTP service (dispatcher) is running, but not responding to SMTP commands such as helo. I ran imsimta dirsync -F and nothing changed. The only solution that I found was to backup the directory services and queues, then uninstall and re-install the software. I hope that isn't the only fix.

    Jerry I'm running into the same problem this is an issue the is supposed to be fixed in 5.2. Try stopping the SMTP inbound service and starting the other services. If that does not work disable the SMTP inbound and mail delivery service reboot navigate to server_root\msg-servername\imta\tmp delete all the locked files switch the services back to automatic and start them. I hope this helps and iPlanet fixes this issue

  • Ramifications of assigning a wildcard certificate to the SMTP service (needed for Exchange 2010 Hybrid Configuration - Office 365)

    Hello All:
    I am receiving an error when I run the Manage Hybrid Configuration wizard - ERROR:Updating hybrid configuration failed with error 'Subtask NeedsConfiguration execution failed: Configure Recipient Settings. I have opened a SR, but figured I'd try the forums,
    too. I have a wildcard certificate from GoDaddy (MS says they support wildcards from GoDaddy) & that cert has only the IIS service applied to it on the CAS. I've read in the Exchange Server Deployment Assistant that it should have the SMTP & IIS services
    assigned to it, but my question is - SMTP on the CAS (separate server) or on the Mailbox/Hub Transport (separate server)? And what are the ramifications of assigning the SMTP service to, let's say, the CAS? We have had multiple issues every time the servers
    get updated/changed; I do not want to disrupt services further, as the Manage Hybrid Configuration will be done during business hours.
    If anyone can provide any assistance/clarification, it would be most appreciated.
    Thank you.

    Hi,
    We can enable a Wildcard certificate with SMTP service for Exchange Hybird Deployment. The SMTP service can be assigned to multiple certificates. For some Exchange services such as OWA, Ecp, ActiveSync, Autodiscover service, OOF, it is used with Exchange
    certificate with IIS service. And there is usually only one certificate can be assigned with IIS service.
    Please just make sure your Wildcard certificate can contain all namespaces which are used for all internal URL and External URL configuration in Exchange services. About how to import an existing wildcard certificate on the Exchange 2010 Hybird servers,
    please refer to the Import & Enable Third Party Certificate on Hybrid Servers
    part in the following article:
    http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-hybrid-deployment-migrating-to-office-365-exchange-online-part9.html
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please
    make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Regards,
    Winnie Liang
    TechNet Community Support

  • 554 No SMTP service here

    Hi All,
    i am facing problem with incoming mail, some time  outside mail bouncing back with following error
    Eg: [email protected]  
     SMTP error from remote mail server after initial connection:
    host mail.example.com
    [ 3.3.3.3 ( static ip)]: 554 No SMTP service here.
    90% of mail getting 10 % only have problem.
    my setup as follows,
    sonicwall email securty i am using for mail filtering. all incoming and outgoing email through Sonicwall Email security
    waiting for valuable advice ....
    Bino
    Thomas

    First (and I've been waiting to find someone with Sonicwall email security), see this gartner report:
    http://imagesrv.gartner.com/reprints/214000/214080/214080_1.png;pv3a303be6c24debfe
    (http://www.gartner.com/technology/reprints.do?id=1-16XZCJZ&ct=110811&st=sb)
    You should really dump Sonicwall for email protection.  :)
    ok, ok, as for your actual question, you should telnet to port 25 from an external address to the value of your internet MX record.  See
    here for more.  Your email routing may not be configured as you expect.  Additionally, maybe the sonicwall is configured to ignore email traffic from
    certain addresses.
    Mike Crowley | MVP
    My Blog --
    Planet Technologies

  • How to remove SMTP service from third-party cert

    I mistakenly assigned the SMTP service to my commercial cert.  I say this because I did not include the server name on the cert (the cert has the
    CASarray.domain.com, webmail.domain.com, and autodiscover.domain.com names).  I've tried just clearing the radio button in the wizard, but it does not remove the service.  Can someone please tell me how to do this?
    Thanks!

    Hi,
    We don’t need to remove the SMTP service. Just generate a new certificate with the server name on the certificate and assign SMTP service to it.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • SMTP service is not starting

    on my Maverik Server 3.1.1 my SMTP service is not starting. IMAP is OK
    when i use:
    "sudo serveradmin fullstatus mail"
    I get :
    mail:startedTime = "2014-03-26 19:11:38 +0000"
    mail:setStateVersion = 1
    mail:state = "STARTING"
    mail:protocolsArray:_array_index:0:status = "ON"
    mail:protocolsArray:_array_index:0:kind = "INCOMING"
    mail:protocolsArray:_array_index:0:protocol = "IMAP"
    mail:protocolsArray:_array_index:0:state = "RUNNING"
    mail:protocolsArray:_array_index:0:service = "MailAccess"
    mail:protocolsArray:_array_index:0:error = ""
    mail:protocolsArray:_array_index:1:status = "ON"
    mail:protocolsArray:_array_index:1:kind = "INCOMING"
    mail:protocolsArray:_array_index:1:protocol = "POP3"
    mail:protocolsArray:_array_index:1:state = "RUNNING"
    mail:protocolsArray:_array_index:1:service = "MailAccess"
    mail:protocolsArray:_array_index:1:error = ""
    mail:protocolsArray:_array_index:2:status = "OFF"
    mail:protocolsArray:_array_index:2:kind = "INCOMING"
    mail:protocolsArray:_array_index:2:protocol = "SMTP"
    mail:protocolsArray:_array_index:2:state = "STOPPED"
    mail:protocolsArray:_array_index:2:service = "MailTransferAgent"
    mail:protocolsArray:_array_index:2:error = ""
    mail:protocolsArray:_array_index:3:status = "OFF"
    mail:protocolsArray:_array_index:3:kind = "OUTGOING"
    mail:protocolsArray:_array_index:3:protocol = "SMTP"
    mail:protocolsArray:_array_index:3:state = "STOPPED"
    mail:protocolsArray:_array_index:3:service = "MailTransferAgent"
    mail:protocolsArray:_array_index:3:error = ""
    mail:protocolsArray:_array_index:4:status = "OFF"
    mail:protocolsArray:_array_index:4:kind = "INCOMING"
    mail:protocolsArray:_array_index:4:protocol = ""
    mail:protocolsArray:_array_index:4:state = "STOPPED"
    mail:protocolsArray:_array_index:4:service = "ListServer"
    mail:protocolsArray:_array_index:4:error = ""
    mail:protocolsArray:_array_index:5:status = "ON"
    mail:protocolsArray:_array_index:5:kind = "INCOMING"
    mail:protocolsArray:_array_index:5:protocol = ""
    mail:protocolsArray:_array_index:5:state = "STOPPED"
    how do I fix it ?
    regards
    Norbert

    To clarify, the problem in my case was a corrupted OD database.  Your case may be different.  Check your SMTP logs for further clues.
    /var/log/mail.log
    /Library/Logs/Mail/mail-err.log
    Bryan Dulock

  • Where to configure SMTP services .???

    Hi Experts,
    If you want to allow users to send e-mails outside the company domain using the portal. where to configure SMTP server settings in the portal for achieving this..? I need the path to configure SMTP services..

    Vineet,
    This wiki should help you to get started.
    http://wiki.sdn.sap.com/wiki/display/EP/MSOutlookConfigrationguideForSAPPortal
    Cheers!
    Sandeep Tudumu

  • SMTP service on in oracle database to send mail directly from oracle databa

    I want to send mail from my oracle database.
    I have followed the steps below:
    1> Run utlmail.sql & prvtmail.plb
    2>set smtp_out_server parameter
    3>To send mail, execute utl_mail.send(sender=>'',recipients=>'',message=>'ABC');
    My concept is to provide smtp/mail server ip & port in smtp_out_server parameter's value.
    But One person said that oracle database server can make itself as a smtp server.So that we can assign database server ip & port in smtp_out_server parameter's value.We have to just on the smtp service in oracle database itself.There is no requirement of smtp/mail server ip & port.Is it true?How can we do that?
    In google to Add an SMTP Service,the document said in the 1st line that on the Services tab on the left, select a Process tree node (for example, the default Oracle Enterprise Gateway).
    I am sorry to say that I did not find that.Anyone can help me please?
    Please reply anyone.
    Edited by: 979620 on Feb 6, 2013 3:20 AM

    Hi Richa:
    As you mentioned, it has been working for the last six moneth. Was there any changes before it stopped working?
    Also you mentioned you were able to recieve mails from Domain user. Could you please get the Internet Headers: Open a mail from domain sender -> file ->property -> Internet Headers, send it with a mail to me:[email protected]
    Meanwhile, as this is a Office 365 related issue, it is better to post your quesetion in
    this forum. Thank you.

  • Exchange 2013 SMTP service delayed / slow acknowledgement

    Hey Guys,
    since we upgraded from Exchange 2010 to Exchange 2013 (SP1) any SMTP Receive Connector we create (including the default one) show the same strange behavior. When you send an email (no matter if internal or external) it sometimes takes
    up to 30 seconds for the exchange server to acknowledge the message. Using the SMTP log I see the following entries:
    2014-08-08T08:58:29.053Z,                       MAIL FROM:<[email protected]>,
    2014-08-08T08:58:29.053Z,                       SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set
    Session Permissions
    2014-08-08T08:58:29.053Z,                       receiving message
    2014-08-08T08:58:29.053Z,                       250 2.1.0 Sender OK,
    2014-08-08T08:58:29.053Z,                       RCPT TO:<[email protected]>,
    2014-08-08T08:58:29.053Z,                       250 2.1.5 Recipient OK,
    2014-08-08T08:58:29.053Z,                       DATA,
    2014-08-08T08:58:29.053Z,                       354 Start mail input; end with <CRLF>.<CRLF>,
    2014-08-08T08:58:29.068Z,                       Proxy destination(s) obtained from OnProxyInboundMessage event
    2014-08-08T08:58:40.960Z,                       "250 2.6.0 <5160cd2a-9160-4a35-9007-1f9c17761bc0@--------> [InternalId=17776869639170,
    Hostname=-----------] Queued mail for delivery",
    As you can see there’s a delay between 08:58:29 and 08:58:40 where nothing happens. The sending smtp service waits for the server to acknowledge the message – at least that’s what I guess. Since we use this kind of connector a lot for
    internal mail traffic with non-Outlook clients it is essential to get rid of this issue. For example using Trac Ticket system or Subversion also leads to slow or delayed responses. Creating a ticket in Trac sometimes takes up to a Minute since several emails
    are created and sent in background processes. We didn’t have this issue with Exchange 2010 and I actually couldn’t find much using google. 
    Since there's no error showing it's quite difficult to track down the issue. After I did some researching I tried configuring the receive connector to change this behavior but nothing helped. I tested the following options:
    MaxAcknowledgementDelay 00:00:00
    TarpitInterval 00:00:00
    MessageRateSource None
    MessageRateLimit unlimited
    MaxInboundConnectionPercentagePerSource: 20
    MaxInboundConnectionPerSource 100
     I Also took a look at the Throttling Policies with no luck either. 
    Calling the Microsoft support simply led to the typical “we do not support 3<sup>rd</sup> party issues”. In fact this is NOT a third party issue but arguing didn't help. I tested every possible solution I found and after weeks
    I simply dont' have the slightest idea any more, how to solve the problem.
    Some information about our Exchange environment:
    Exchange DAG with 2 servers
    Windows Server 2012 (latest updates)
    Exchange 2013 SP1 installed
    Disabling DAG members also didn’t help and all the members show the same behavior no matter which connector I choose to use.  
    Any hint or idea would be very much appreciated.
    Thanks,
    Christoph

    Hi Christoph,
    From the SMTP session, the delay happened when processing data. This can be caused by several factors, such as the length of message content.
    In Exchange 2013, we have the function called shadow redundancy, the transport server makes a redundant copy of any messages it receives before it acknowledges successfully receiving the message back to the sending server. This helps to ensure that all messages
    in the Exchange 2013 transport pipeline are made redundant while they're in transit. If Exchange 2013 determines the original message was lost in transit, the redundant copy of the message is redelivered.
    For more information about shadow redundancy, we can refer to the article:
    Shadow redundancy
    http://technet.microsoft.com/en-us/library/dd351027(v=exchg.150).aspx
    By default, it is enabled, and if we want to disable it, we can use the command:
    Set-TransportConfig –ShadowRedundancyEnabled $false
    Best Regards,
    Tracy Liang

Maybe you are looking for