Uzman Posta
The Uzman Posta connector integrates the Netmera platform with the Turkish email sending service, positioning it as a key email delivery channel, particularly serving as a fallback option for both marketing campaigns and internal system notifications.
Overview
Connector Name
Uzman Posta
Category
Email Providers / Email Sending Service (Turkey)
Primary Function
Outbound email delivery for system and campaign emails.
Netmera Adapter Class
UzmanPostaMailAdapterImpl (for campaigns)
Fallback Mechanism
Utilized by the NetmeraMailSender class for internal system emails.
Data Flow
Outbound (Netmera > Uzman Posta)
Priority Ranking
Low Priority (Rank 4/Fallback), following SetRow, Amazon SES, and Postal.
The Uzman Posta integration is defined as a robust email service, specifically designed to ensure high deliverability within the Turkish market. Its most critical role in the Netmera architecture is acting as the primary fallback provider for email traffic.
Use Cases and Benefits
Campaign Email Delivery: Uzman Posta is available as an option for sending standard bulk marketing campaigns created via the Netmera Control Panel. This occurs primarily when higher-priority email connectors (such as SetRow or Amazon SES) are either inactive or unconfigured.
System Email Fallback (Internal Mail): It provides a reliable channel for Netmera's internal communications. System-generated emails—including password resets, verification links, notification alerts, and report emails—are routed through Uzman Posta if other preferred system mail services (like Local Mail or specialized external services) are not utilized or fail.
Reliability in the Turkish Market: As a provider focused on Turkey, Uzman Posta ensures optimized delivery rates for email recipients in this region.
Guaranteed Delivery Channel: Because of its role as a fallback, configuring Uzman Posta ensures that Netmera has a reliable, operational channel for critical email transmission, minimizing the risk of communication failures.
Data Flow
The data flow is purely Outbound, involving API communication from Netmera's mail services to the Uzman Posta API.
Message Request: An email is triggered (either a campaign or an internal system alert).
Provider Selection:
For Campaign Emails: The MailSenderServiceImpl checks email providers in priority order (SetRow $\rightarrow$ Amazon SES $\rightarrow$ Postal). If none are active, the system falls back to Uzman Posta.
For System Emails: The NetmeraMailSender class checks the appropriate configuration settings and uses Uzman Posta if other primary system mail services are not available.
API Call: The dedicated adapter (UzmanPostaMailAdapterImpl) uses the configured API Key to authenticate and submit the email payload to the specified Request URL (API endpoint).
Configuration Reference

Configuration requires obtaining two essential parameters from the Uzman Posta service panel.
apiKey
String
The unique API key assigned to the Netmera account by Uzman Posta.
Used for API authentication during message submission.
requestUrl
String
The specific API endpoint URL provided by Uzman Posta.
Defines the destination endpoint for all email sending requests.
Setup Instructions
The setup process requires coordination with the vendor and inputting the credentials into the Netmera Control Panel.
Prerequisites: Contact Uzman Posta, complete the account setup process, and obtain your designated API Key and API Request URL.
Access Netmera Connectors: Navigate to the Netmera Control Panel, select the Connectors (or Integrations) section.
Configure Uzman Posta: Select the Uzman Posta connector.
Input Data: Enter the API Key and the Request URL into the configuration form.
Save: Click Save Configuration.
After saving, the connector is immediately registered within the MailSenderServiceImpl and NetmeraMailSender as a viable, low-priority email channel.
Usage Notes & Considerations
Priority Dependence: Uzman Posta has a low priority for campaign emails. Messages will only be routed through it if all higher-ranked connectors (SetRow, Amazon SES, Postal) are not configured or are inactive. If you intend to use Uzman Posta as the default campaign provider, the higher-priority services must be unconfigured.
Dual Role: Its function as a fallback provider for internal system emails is independent of its function as a campaign connector. A configuration error, however, could impact both transactional and marketing communications relying on it.
Credential Failure: The integration relies entirely on the correctness and validity of the apiKey and requestUrl. If these are incorrect or change on the vendor side, all email routing attempts via this connector will fail until the Netmera configuration is manually updated.
Last updated
Was this helpful?