I use phpmailer. how can I avoid bounce? I already tried to set a bounce mail address, but I do not want to send bounces to any address.
It is not possible to send SMTP email, and not provide a mechanism for remote mailers to send bounces where users are not found. All SMTP email is sent from one email address to a set of recipients - that mail server can choose to accept the the email for onward delivery, or reject the message outright. If it accepts the message for onward delivery, and it later gets rejected then a bounce message may be generated, either to the original sender, or to the bounce recipient, if specified (and supported by the remote mailer).
To minimise the number of bounces, you could look up the MX record for each recipient domain, and try and handle the SMTP exchange yourself, and handle send errors appropriately (e.g. remove the recipient from your database, etc.)
Related
My problem is about sending email out of the circle mail server, exemple:
From: name#mydomainename.com
To: name#gmail.com or any other domaine name
The message appeare on plesk under Mail Queue
Messages in queue: 47 deferred, 0 held, 0 incoming, 0 active, 0 corrupted, 47 total.
I was trying many times to re-sending all deferred emails in the queue by taping en console:
postsuper -r ALL
but the same problem all the time.
Now, when I send mail, exemple:
From: name#mydomainename.com
To: name1#mydomainename.com
it works correctly
Before going into configuration changes, have you checked if your domain is blacklisted or not? Were you able to receive E-mails from other domains such as Gmail?
Sending/receiving Emails to/from the same domain is nearly always possible. No matter how messed up the configurations are you will still manage to deliver emails within the domain itself.
Usually I've found that the reason behind this problem is the blacklisted IPs. Make sure that your domain IP is not blacklisted.
https://mxtoolbox.com/blacklists.aspx
I've written a JavaMail client to access a GMail account via POP3.
As expected, I can only read a message once. When I re-run the client, the message is not found as it has been deleted from the server.
However, when I then log onto the GMail account (IMAP enabled) via a browser, the message appears.
Why does this happen? Are separate copies of the email created for POP3 and IMAP?
POP3 clients access the inbox, and what they see is unseen mail. When the POP3 client has seen a message it's no longer unseen and the POP3 server is supposed to do something.
The gmail server probably moves the message to the Archived folder.
You may have won a prize as the last person to have written a POP3 client, BTW.
Gmail has specific special handling for POP3 account:
In the default mode, it expects a 'download and delete' client. It will only expose 300 or so messages until those are DELEted. They are not actually deleted, but they are removed from the pool of messages to be sent through POP3. This prevents some of the inefficiencies with traditional POP3 clients accessing huge mailboxes, but does allow the client to eventually access everything.
The other mode is recent mode. You can use this mode by putting "recent:" in front of your login, like "recent:bob#gmail.com". This switches it to a mode where it will only show your client the most recent 30 days worth of messages. The messages do not disappear, until they fall out of the window. Again, this limits the size of the message list to a reasonable number for efficiency reasons, but in a different way. However, deletes can be synced between clients. (This may mean archiving in the Google Way). Recent mode is currently documented here in the troubleshooting section I want to download emails on multiple email clients.
Or, you could just use IMAP. Even without using all the additional features of IMAP, you can do everything you can do with POP3, but will allow many other features as your client evolves.
I have seen many of the posts relating to sending email under linux but they do not address my particular need.
I want to implement code (C/C++) in my linux application that will send me back some kind of notification (in a stealthy way) under a certain program condition. All it needs to send me is less than 50 bytes of status data. The only thing I am guarenteed is that the box will be on a local network which will have access to the Internet via the usual gateway.
One possibility would be to send me a text to my wireless carrier like this:
mynumber#verizon_gateway.com. But that assumes that I have a mail client available on the linux box which is not a guarantee. If I programmed this at the socket layer directly using SMTP I would have to manage a TCP connection which is not what I prefer to do.
Any suggestions of what would be a possible way to send me a notification from my linux app?
Thanks,
-Andres
For email you could use something like SendGrid, specifically their WebAPI - this will allow you to send email with only a HTTP request.
For SMS you could use something like Nexmo, which will allow you to send an SMS with a HTTP request.
Note that you'll have to include your API credentials in the compiled code - a potental security issue (for your credentials).
Disclaimer: I do a bit of developer evangelism for Nexmo.
We have a dedicated server and we are sending emails from a dedicated IP. We are using PHP mailer Script and Exim to send out emails. The problem I am facing is we are sending very low volume emails eg. only 25 k emails but When we check emails in queue, its says 85k emails. We are running cron to fetch and send emails.
The sending speed is very low. It took whole day to send 24k emails and server timed out many a times in Between( ALso smtp 421 error). I am confused if I am only sending 24k emails how come 85 k emails get in queue and why it is taking so much time. I also Talked to support guys but I did not get any satisfactory answer. This issue is related to the script, cron or settings related to server?
Any help will be appreciated.
Thanks,
Anand
If your mails are 25k, but going to multiple recipients at different domains, they will need to be sent separately to each domain, so if you have at least four recipient mail servers for the message, you can easily have a queue of 85k. 4 * 25k > 85k
An SMTP response beginning with 4 (e.g. 421) means the message could not be sent immediately, so try again later. This could just mean there was a temporary problem with the recipient server, or there may be some other reason. You will need to contact the recipient about that one.
As for the speed, based on the volume of messages you are sending, you probably look very much like a spammer. When you are suspected of sending spam, a recipient mail server (or your ISP) can quite reasonably throttle or refuse your connection, causing mails to take longer to send. This is probably why you are getting a backlog.
If you aren't a spammer, hang in there. Eventually, other mail servers will learn to trust you. A new mail server is always going to look suspicious, especially if it is sending a large number of small emails. You will eventually build up a good reputation if you continuously send legitimate emails.
On the other hand, if you are a spammer, give up now, you're not going to win.
If you need to send out lots of messages and cannot afford to wait to build up your reputation, perhaps consider either sending via your ISP's mail server (fair use limits may apply), or using a bulk-mail service such as Mailchimp, or one of its competitors.
We currently have a company email server with Exchange, and a bulk email processing server that is using IIS SMTP. We are upgrading to a 3rd party MTA (zrinity xms) for bulk sending. I need to be able to keep sending the messages already queued for IIS when we switch to the 3rd party sofware. Can I simply move the IIS queue files to the Exchange server queue and have sending attempts begin automatically for them? If not, any suggestions on accomplishing this?
You should be able to move the *.eml files to the Exchange server's pickup directory. Or set the IIS SMTP service to smart host to the new MTA, assuming they (the 3rd party) allow SMTP relay from your IP address.
Moving the files will work. However, any email with a BCC line in the header will get sent out with the BCC intact. Some clients, such as gmail, will display the information to the recipient, thus breaking the whole point of BCC.
This happens when copying EML files to MS-SMTP (which Exchange also uses) because the BCC information is usually stripped out of the header in during the SMTP hand-off to (not from) MS-SMTP.
If that was how the messages were initially handed off, then it's possible that the EMLs you have were already broken into separate messages for each BCC, and that header was properly stripped.
Just a little gotcha to watch out for.