Hi Howard,
If you're sending through gmail then the IP address is not an issue - it
only becomes an issue if you are sending directly to the recipients'
mail servers.
I only point it out because I have encountered these same problems while
implementing a solution (using ICS) to send over 10,000 subscribed
e-mails per day ;-)
However, just to clarify what I meant, imagine that you write an
application which sends directly to the recipients' mail servers, and
you run this on your desktop machine at home or at an office. Also,
let's assume that the sender's e-mail address is some...@example.com.
For each e-mail sent, the receiving mail server could (and many seem to)
check the sending IP address against the list of MX (Mail eXchange)
records for the domain of the sender. If it doesn't find a match, then
the message is rejected or put into the recipient's spam folder
(depending on the mail server).
For 550 e-mails three times a month it might be easier to use gmail, but
this is probably something you need to consider when/if the list grows
or the number of e-mails per month increases.
Regards,
Bevan
On 7/10/2014 9:55 a.m., H M wrote:
Bevan,
It probably doesn't matter if the boucebacks come into the inbox.
The account is only ever to be used for this mailshot so it will help us to
know which addressess in our database are incorrect so we can contact the
members by post .
As for your last point I don't really understand what you mean about the IP
address
not being associated with the domain - or more importantly how to prevent the
issue.
Currently we simply manually send three emails each month directly from the
gmail web site, each with lots of bcc .
I simply want to do the same thing, or at least achieve the same effect, from
my application.
Howard
Date: Tue, 7 Oct 2014 08:54:53 +1300
From: be...@achieve.co.nz
To: twsocket@lists.elists.org
Subject: Re: [twsocket] Help with sending mail through gmail please
I agree with Angus, you would be better off to send the e-mails
individually to the recipients' mail servers. A good reason for this is
the consideration and handling of send failures and bouncebacks - all of
which are going to end up in your gmail inbox if you are sending through
gmail.
At some point you will want/need to process the failure and bounceback
e-mails to ensure that the affected addresses are automaticallly removed
from the mailing list(s).
However, having said that, if you are going to send directly to the
recipients' mail servers, you need to ensure that you avoid basic spam
detection - such as the sending IP address not being associated with an
MX record for the sender's domain, etc.
Bevan
On 7/10/2014 7:33 a.m., Angus Robertson - Magenta Systems Ltd wrote:
OK, will do, that sounds like just what I need as each month the
system will have to send about 6 emails, each with about 90 bcc in
order to send an email with a 1 Mb attachment to around 550 people
max without falling foul of gmails limits.
One reason I wrote the mailer in the first place was so I could send
individually addressed emails in bulk, rather than using BCC mailing lists.
Takes longer if the body is large, but our bandwidths are now vast.
Not sure if Gmail is happier with single or multiple addresses, I have my own
public mail server so can do what I like.
Your application only requires the addition of domain lookup code to find the
MX host, and you can send directly to their mail server avoiding Gmail.
I intend to add that to the Mail Queue component, but have not got around to it
yet. When combined with the SMTP server I wrote last year, that would give us
a forwarding email server.
Angus
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
