Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
This is the official Python3 package for the Paubox Email API.
The Paubox Email API allows your application to send secure, HIPAA compliant email via Paubox and track email deliveries and opens.
You will need to have a Paubox account. You can sign up here.
Once you have an account, follow the instructions on the REST API dashboard to verify domain ownership and generate API keys. Further quickstart instructions for this process can be found here.
While you can simply hard-code your authentication credentials, it's often better practice to tuck these values away in an environment or configuration file. Our following code snippets leverage the use of the config
python package to load our credentials. To set config
up, include your API key credentials in a config file (e.g. config.cfg
)
PAUBOX_HOST: 'https://api.paubox.net/v1/YOUR_ENDPOINT_NAME'
PAUBOX_API_KEY: 'YOUR_API_KEY'
Then, install the config
package using pip3 to load API credentials from the
config.cfg
file:
$ pip3 install config
$ pip3 install paubox-python3
Sending via Paubox is easy. This is the minimum content needed to send an email.
import paubox
from paubox.helpers.mail import Mail
from config import Config
with open("config.cfg") as config_file:
paubox_config = Config(config_file)
paubox_client = paubox.PauboxApiClient(paubox_config.PAUBOX_API_KEY, paubox_config.PAUBOX_HOST)
recipients = ["recipient@example.com"]
from_ = "sender@yourdomain.com"
subject = "Testing!"
content = {"text/plain": "Hello World!"}
mail = Mail(from_, subject, recipients, content)
response = paubox_client.send(mail.get())
print(response.status_code)
print(response.headers)
print(response.text)
import paubox
from config import Config
with open("config.cfg") as config_file:
paubox_config = Config(config_file)
paubox_client = paubox.PauboxApiClient(paubox_config.PAUBOX_API_KEY, paubox_config.PAUBOX_HOST)
mail = {
"data": {
"message": {
"recipients": [
"recipient@example.com"
],
"headers": {
"subject": "Testing!",
"from": "sender@yourdomain.com"
},
"content": {
"text/plain": "Hello World!",
}
}
}
}
response = paubox_client.send(mail)
print(response.status_code)
print(response.headers)
print(response.text)
If you want to send non-PHI mail that does not need to be HIPAA compliant, you can allow the message delivery to take place even if a TLS connection is unavailable.
This means the message will not be converted into a secure portal message when a nonTLS connection is encountered. For this, just pass allowNonTLS
as True
as shown below:
import paubox
from paubox.helpers.mail import Mail
from config import Config
with open("config.cfg") as config_file:
paubox_config = Config(config_file)
paubox_client = paubox.PauboxApiClient(paubox_config.PAUBOX_API_KEY, paubox_config.PAUBOX_HOST)
recipients = ["recipient@example.com"]
from_ = "sender@yourdomain.com"
subject = "Testing!"
content = {
"text/plain": "Hello World!"
}
optional_headers = {
'reply_to': 'replies@yourdomain.com',
'allowNonTLS': True
}
mail = Mail(from_, subject, recipients, content, optional_headers)
response = paubox_client.send(mail.get())
print(response.status_code)
print(response.headers)
print(response.text)
import paubox
from config import Config
with open("config.cfg") as config_file:
paubox_config = Config(config_file)
paubox_client = paubox.PauboxApiClient(paubox_config.PAUBOX_API_KEY, paubox_config.PAUBOX_HOST)
mail = {
"data": {
"message": {
"recipients": [
"recipient@example.com"
],
'allowNonTLS': True,
"headers": {
"subject": "Testing!",
"from": "Sender <sender@yourdomain.com>",
"reply-to": "Reply-to <replies@yourdomain.com>"
},
"content": {
"text/plain": "Hello World!",
}
}
}
}
response = paubox_client.send(mail)
print(response.status_code)
print(response.headers)
print(response.text)
Paubox Secure Notifications allow an extra layer of security, especially when coupled with an organization's requirement for message recipients to use 2-factor authentication to read messages (this setting is available to org administrators in the Paubox Admin Panel).
Instead of receiving an email with the message contents, the recipient will receive a notification email that they have a new message in Paubox.
To enable this, pass the forceSecureNotification
header as True
as shown below:
import paubox
from paubox.helpers.mail import Mail
from config import Config
with open("config.cfg") as config_file:
paubox_config = Config(config_file)
paubox_client = paubox.PauboxApiClient(paubox_config.PAUBOX_API_KEY, paubox_config.PAUBOX_HOST)
recipients = ["recipient@example.com"]
from_ = "sender@yourdomain.com"
subject = "Testing!"
content = {
"text/plain": "Hello World!"
}
optional_headers = {
'reply_to': 'replies@yourdomain.com',
'forceSecureNotification': True
}
mail = Mail(from_, subject, recipients, content, optional_headers)
response = paubox_client.send(mail.get())
print(response.status_code)
print(response.headers)
print(response.text)
import paubox
from config import Config
with open("config.cfg") as config_file:
paubox_config = Config(config_file)
paubox_client = paubox.PauboxApiClient(paubox_config.PAUBOX_API_KEY, paubox_config.PAUBOX_HOST)
mail = {
"data": {
"message": {
"recipients": [
"recipient@example.com"
],
'forceSecureNotification': 'true',
"headers": {
"subject": "Testing!",
"from": "Sender <sender@yourdomain.com>",
"reply-to": "Reply-to <replies@yourdomain.com>"
},
"content": {
"text/plain": "Hello World!"
}
}
}
}
response = paubox_client.send(mail)
print(response.status_code)
print(response.headers)
print(response.text)
import paubox
import base64
from paubox.helpers.mail import Mail
from config import Config
with open("config.cfg") as config_file:
paubox_config = Config(config_file)
paubox_client = paubox.PauboxApiClient(paubox_config.PAUBOX_API_KEY, paubox_config.PAUBOX_HOST)
recipients = ["recipient@example.com"]
from_ = "sender@yourdomain.com"
subject = "Testing!"
attachment_content = base64.b64encode(bytes("Hello World!", encoding="utf-8")).decode()
content = {
"text/plain": "Hello World!",
"text/html": "<html><body><h1>Hello World!</h1></body></html>"
}
optional_headers = {
"attachments": [{
"fileName": "the_file.txt",
"contentType": "text/plain",
"content": attachment_content
}],
'reply_to': 'replies@yourdomain.com',
'bcc': 'recipient2@example.com',
'cc':['recipientcc@example.com'],
'forceSecureNotification': 'true',
'allowNonTLS': True
}
mail = Mail(from_, subject, recipients, content, optional_headers)
response = paubox_client.send(mail.get())
print(response.status_code)
print(response.headers)
print(response.text)
import paubox
import base64
from config import Config
with open("config.cfg") as config_file:
paubox_config = Config(config_file)
paubox_client = paubox.PauboxApiClient(paubox_config.PAUBOX_API_KEY, paubox_config.PAUBOX_HOST)
attachment_content = base64.b64encode("Hello World!".encode('utf-8')).decode('utf-8')
mail = {
"data": {
"message": {
"recipients": [
"recipient@example.com"
],
"bcc": ["recipient2@example.com"],
'cc':['recipientcc@example.com'],
'forceSecureNotification':'true',
'allowNonTLS': True,
"headers": {
"subject": "Testing!",
"from": "Sender <sender@yourdomain.com>",
"reply-to": "Reply-to <replies@yourdomain.com>"
},
"content": {
"text/plain": "Hello World!",
"text/html": "<html><body><h1>Hello World!</h1></body></html>"
},
"attachments": [{
"fileName": "the_file.txt",
"contentType": "text/plain",
"content": attachment_content
}]
}
}
}
response = paubox_client.send(mail)
print(response.status_code)
print(response.headers)
print(response.text)
The SOURCE_TRACKING_ID
of a message is returned in the response.text of your send request. Use response.to_dict to access the response text as a dictionary.
import paubox
from config import Config
with open("config.cfg") as config_file:
paubox_config = Config(config_file)
paubox_client = paubox.PauboxApiClient(paubox_config.PAUBOX_API_KEY, paubox_config.PAUBOX_HOST)
disposition_response = paubox_client.get("SOURCE_TRACKING_ID")
print(disposition_response.status_code)
print(disposition_response.headers)
print(disposition_response.text)
The Paubox-python3 SDK is maintained by Paubox, Inc.
We want to empower our users building applications with the Paubox Email API, and so we encourage you to file bug reports/create GitHub issues and pull requests. Chances are other developers using our Email API might be having similar ideas about new features or approaches to improving the SDK, so we encourage you to upvote or comment on existing issues or pull requests!
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Copyright © 2021, Paubox, Inc.
FAQs
Python3 SDK for Paubox Email REST API
We found that paubox-python3 demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.