Hello All,
Before you tell me I should "NOT" bounce email; I'm just trying to set up the account and TEST it in case there is something I want to bounce. When I send myself an email and bounce it it say "bounced" but I never get it back.
OR it says: forged email, which is not true, the email is a legit domain.
All setting are exactly the same in MW 6.53 as they are with my other domain, other than the SMPT server which is hosted by someone else.
Any suggestions?
Port change?
SMPT change?
THANK YOU in advance.
Mailwasher won't bounce on new domain
-
stan_qaz
- Omniscient Kiwi
- Location: Gilbert, Arizona
Post
Re: Mailwasher won't bounce on new domain
The bounce e-mail is forged, it has headers that do not accurately reflect the true origin of the message and contains an address that is not yours.
There are many reasons why bouncing can fail, some ISPs look for forged messages and reject them, others look for e-mail that may be looping and a forged bounce often triggers that test.
Rather than poking at settings it is best to see why the e-mail was rejected, if it was as the first step.
Turn off MW's automatic mail checks as the first step.
Clear the mail grid of all messages.
Go to Help then About, click the logging box and the link there to open explorer.
Select one message to bounce and process mail.
Look in explorer and you should see one socketlog file that is the record of MW's conversation with your mail server.
Go back and untick the logging box.
Now you can follow the SMTP session in the log and see exactly what happened to your message. If it was rejected by your ISP it should contain the reason. If it was accepted but not delivered you can send the socket log to your ISP and ask them to trace the message using the logged information.
Some ISPs get really testy about bouncing as it makes a lot of work for them and causes their customers a great deal of grief so be prepared for a less than cordial chat with your support folks. My ISP was quite nice, they agreed not to close my account and ban me from getting another if I quit bouncing.
Do play with the spamcop.net reporting, that actually works both to block spam and to reduce the amount you get if you report often and early.
There are many reasons why bouncing can fail, some ISPs look for forged messages and reject them, others look for e-mail that may be looping and a forged bounce often triggers that test.
Rather than poking at settings it is best to see why the e-mail was rejected, if it was as the first step.
Turn off MW's automatic mail checks as the first step.
Clear the mail grid of all messages.
Go to Help then About, click the logging box and the link there to open explorer.
Select one message to bounce and process mail.
Look in explorer and you should see one socketlog file that is the record of MW's conversation with your mail server.
Go back and untick the logging box.
Now you can follow the SMTP session in the log and see exactly what happened to your message. If it was rejected by your ISP it should contain the reason. If it was accepted but not delivered you can send the socket log to your ISP and ask them to trace the message using the logged information.
Some ISPs get really testy about bouncing as it makes a lot of work for them and causes their customers a great deal of grief so be prepared for a less than cordial chat with your support folks. My ISP was quite nice, they agreed not to close my account and ban me from getting another if I quit bouncing.
Do play with the spamcop.net reporting, that actually works both to block spam and to reduce the amount you get if you report often and early.
I am not a Firetrust employee just a MW user.
--
First rule of computer consulting: Sell a customer a Linux computer and you'll eat for a day,
sell a customer a Windows computer and you'll eat for a lifetime.
--
First rule of computer consulting: Sell a customer a Linux computer and you'll eat for a day,
sell a customer a Windows computer and you'll eat for a lifetime.