I'm responding to several emails in this one:
Guy - Thanks for the leads; I'll work with my client regarding ISPs.
Bruce Chitiea also mentioned sending too many emails too fast. At this
time, we're probably sending a few dozen, but I may try a PAUSE 3 for 2
after the PRINT command within the WHILE loop..
Karen - I assumed AUTHENTICATION was normally OFF, but that's not
documented so I'll add EMAIL_AUTHENTICATION OFF to the PRINT command.
Javier - Thank you for the insights into the blacklisting process. It's
a valuable lead for client and me to follow.
Thanks all, I appreciate the feedback and will update on progress.
Doug
"There are a ton of possibilities..." - Biggest understatement since
Noah said "It looks like rain." :)
On 2/3/2025 2:24 PM, Guy W. Ellenberger wrote:
Doug,
I'm going to go from the Rbase side is working fine for now.
There are a ton of possibilities of why they are not getting through,
most dealing with the email servers involved. I'll throw a few ideas
out for now.
I'm "assuming" you are relaying them to your ISP, and not sending them
directly from your app to the receivers email server. . . meaning your
ISP takes the email and they sent it to whomever.
Some thoughts. . .
Sending too many too fast to your ISP and they may be limiting or
blocking the sending, or believe it's spam.
Your ISP may be looking at your may be looking at the sending (public)
ip which may need to be whitelisted on their server, especially if
your "internet provider" and "email provider" are not both the same
company.
What you really need to do is get your email provider to look at their
logs. Have them look at a few that didn't go through. They can tell
you if they got them, and if they were blocked by the customers email,
and the 3 digit code giving the general reason they were blocked.
Other things depending on the email setup (outside of RBase) could be
SPF records, reverse DNS.
See what you may be able to find. With additional information I could
probably give you a better place to start. . . but you have to start
somewhere.
------------------------------------------------------------------------
*From: *"Doug Hamilton" <[email protected]>
*To: *"R:Base List" <[email protected]>
*Sent: *Monday, February 3, 2025 3:00:59 PM
*Subject: *[RBASE-L] - Emailing Invoices
I'm looking for advice/direction/ideas from the list's collective
experience in emailing invoices to customers.
I've set up a client to email their invoices to certain selected
customers of theirs.
I'm using the PRINT command with EMAIL ON in a WHILE loop - the PRINT
command is below.
I don't think guts of the WHILE loop are important cuz the variables are
correctly defined and invoices are getting emailed as an attached PDF.
The PDF file name is ('.\ARInvoices\Invoice'+ (CTXT(.vInvoice#)) +
'.PDF') - e.g. Invoice12345.PDF in the ARInvoices subfolder.
The email address to which they are being sent, ,vInvEmailAddress, is a
specific address to the customer's payables dept for invoices.
The custom subject, .vSubject, for each email is ('Invoice for PO#' &
.vPONum & 'from ClientName')
The custom body of each email is ('Attached please find ClientName's
invoice number' & (CTXT(.vInvoice#)) & 'for your Purchase Order'
&.vPONum +'.')
The results: Some customers are getting their emailed invoices (good)
and paying them (better).
The problem is that a significant number of emailed invoices are not
getting through to the customer's Payables dept (worst) for several
possible reasons that we can think of:
* The email is treated as junk mail - we had customers white list
[email protected].
* In some cases, it seems that customer's ISP may be intercepting the
emails because customer claims they never received them. I'm not sure
how likely that is - ISPs shouldn't be filtering (mine sure doesn't). I
suspect customers received but can't find the emails.
Could ISPs be filtering based on client's old/unrecognized (but working)
ISP, optonline.net ?
* The email was rejected because it had an attachment, though we don't
know where it went - junk folder, automatically deleted...?
The solution is to code the invoice info into the body of the email to
eliminate the attachment but could be more cost than its worth.
* Could anti-virus software be intercepting the emails (and not paying
them :)?
* Use RMail to request a return receipt? If we can get this to work
using the PRINT command, RMAIL won't be needed.
I'm proposing this checklist for emailing invoices:
* Personally contact each customer before starting to email invoices.
* Confirm email address for customer's AR Invoices
* White list Client's email address on customer's email software and
anti-virus & spam filters.
* Email one invoice to customer and confirm it was properly received and
processed.
Any other ideas, suggestions or advice?
TIA,
Doug
PRINT InvoiceEM +
WHERE INVOICE# = .vInvoice# +
OPTION PDF|FILENAME .vPDFName +
|EMAIL ON +
|EMAIL_TO_LIST .vInvEmailAddress +
|EMAIL_SUBJECT .vSubject +
|EMAIL_BODY .vBody +
|EMAIL_FROM_NAME ClientName +
|EMAIL_SHOW_DIALOG OFF +
|EMAIL_FROM_ADDRESS [email protected]
R:Base ver X.5E
--
This email has been checked for viruses by Avast antivirus software.
www.avast.com
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/rbase-l/c8e3f582-2c51-4e8c-96c2-cd991fd7c42b%40wi.rr.com.
-
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/rbase-l/805070380.4296185.1738614245984.JavaMail.zimbra%40gwenetworks.com
<https://groups.google.com/d/msgid/rbase-l/805070380.4296185.1738614245984.JavaMail.zimbra%40gwenetworks.com?utm_medium=email&utm_source=footer>.
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/rbase-l/7ff3b74a-d6d3-4fb8-85e4-a8b19d1c6f78%40wi.rr.com.
