3/5/2023 0 Comments Surgemail review![]() – Tested to work: IE7+, Safari 3.1+, Firefox 3.0+, Google Chrome 1+. Note: A modern browser is needed to use the standard (Ajax/Web 2.0) interface. SurgeWeb ©2009-2019 Netwin Ltd, about SurgeMail Custom look ACTIVE (associated with ) Drop your favourite image anywhere on the login window to personalise your surgeweb background. ![]() Note: Other modern browsers such as recent Opera etc will probably work but … – Will NOT work in : various other older browsers including IE6. – Mostly works in : Opera 9.51, Firefox 2.0, Camino 1.69. g_surgeweb_backend_server – Backend machine to connect to This specifies the backend machine where Surgeweb connects for email and to store… The Spam Control features work without requiring your input, but you can also customize these features to make them work best for you. It will quarantine some suspicious messages for you to review before they clutter your email. SurgeWeb will filter out many spam messages before they arrive in your Inbox. Preview SurgeWeb | Web-Based Email | HTC | Waterloo IL – Tested to work: IE7+, Safari 3.1+, Firefox 3.0+, Google Chrome 1+ – Mostly works in : Opera 9.51, Firefox 2.0, Camino 1.69 – Will NOT work in : various other older browsers including IE6 But unless I can stem the tide of SMTP non-delivery report spam, I guess I'll have to.SurgeWeb ©2009-2021 Netwin Ltd, about SurgeMail Custom look ACTIVE (associated with ) Drop your favourite image anywhere on the login window to personalise your surgeweb background. I hate to buy a commercial mail server to replace the simple STMP and POP3 services provided with Windows Server 2003. That, along with the built-in tarpit support, should break spammers. What I really need is some way to make the default SMTP service in Windows Server 2003 reject emails for invalid recipients prior to accepting the message. In addition it also means normal users that perhaps make a typo in an e-mail address will never receive an NDR informing them of the issue. This is possible but unfortunately doing so breaks RFC 2821, which states that a NDR must be returned if an e-mail message for an invalid recipient is accepted. Some of you might think it would be better to simply turn off recipient filtering, rely on your 3rd party antispam product, and suppress NDRs (as spammers typically use spoofed domains anyway). I thought about suppressing non-delivery reports entirely, but this breaks the email protocol: The validation of the address occurs after the email delivery process begins, which is too late. As you can see from the above sniffer trace, the basic SMTP service is not smart enough to perfom "recipient filtering"- to reject email for users that don't exist at the time of submission. I did find this cool STMP tar pit feature which sounds appropriate - but unfortunately, will have no effect in my case. I've pored over the SMTP settings in Windows Server 2003 and I can't figure out a way to fix this. This is also known as a "Reverse NDR attack", because the non-delivery report goes to the recipient (eg, the victim) instead of the sender. ![]() The person in the "from" address will get a non-delivery report from my server that includes the original spam message as an attachment. This repeats dozens of times, with different from and to email address. Here's a representative sniffer trace from earlier today: In other words, spammers are intentionally sending email messages to nonexistent email addresses on my domain. Although I have email relay disabled, spammers are still managing to send spam through my SMTP service - via non-delivery reports! I have modest email needs, so I use the default SMTP and POP3 services in Windows Server 2003. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |