Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provider’s #2

Open
gedw99 opened this issue Nov 12, 2023 · 1 comment
Open

Provider’s #2

gedw99 opened this issue Nov 12, 2023 · 1 comment

Comments

@gedw99
Copy link

gedw99 commented Nov 12, 2023

Are you using a provider to send email ?

The code currently uses nine and I also need to send emails for conferences so figured it’s worth asking what you feeel is a good one ☝️

@xai
Copy link
Owner

xai commented Nov 13, 2023

I appreciate your interest in using xmailgun! In my experience, I have primarily used my university's and my faculty's mail servers, which have been relatively relaxed in sending large amounts of mail. With huge batches of mail (>1000), I notified the mail server admin in advance to make sure my account did not get suspended.

As you know, external email providers will have specific restrictions and limitations on bulk mailing, such as sending limits and spam prevention policies. These constraints will impact the functionality of xmailgun (i.e., only a part of the load goes through if the mail server starts rejecting mails) or even lead to suspension of the used mail account. Please carefully review any external provider's policies and maybe conduct a few test runs to ensure they're compatible with your requirements. Unfortunately, I don't have direct experience with specific external providers for mass mailing to provide a recommendation.

I implemented a cooldown feature that specifies the maximum amount of emails that are sent in a row (followed by a sleep period), which can be set in the task configuration, see

Cooldown int `json:"cooldown"`
and
if (i+1) < len(mails) && (i+1)%cooldown == 0 {

This might be used to spread the load over a more extended period and be more friendly with the mail server. This part of the code might need further tuning for specific mail providers to ensure a sufficient length of the sleeping periods.

While I used xmailgun quite a few times without significant issues with handling conference communication or sending out surveys, keep in mind that this software has, to my knowledge, not been reviewed or tested by other people at all. It was a project to help me start with Go and replace my previous mass-sending script (https://github.com/xai/send-survey) with something more flexible. So please be careful when playing with it ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants