7 ms·

Thanks for providing this great service. Pardon me if this sounds ignorant, but won't other email providers like google, yahoo flag an email coming from @pawnma

Thanks for providing this great service. Pardon me if this sounds ignorant, but won't other email providers like google, yahoo flag an email coming from @pawnmail.com as junk because of the word "pawn" (synonymous with pawn shops etc) in the domain name?

NicoJuicy 12y ago
It's for "custom domains", pawnmail is just an example and the name of the project. Check it out at : https://pawnmail.com/register https://pawnmail.com/register
- TheDong 12y ago
  Regardless that it's for custom domains, the smtp server will call itself "mx.pawnmail.com" during the SMTP protocol negotiation. The parent comment is not correct in thinking that matters, but they are correct that it will be identified as pawnmail, just not as part of the email address itself.
  - evbogue 12y ago
    I suppose the nutgraf is: running your own email server is a better/recommended solution over pawnmail?
TheDong 12y ago
Junk/spam is far more complex than that. That alone will not be an issue almost certainly. HOWEVER, there are many issues with this site that will cause messages to get marked as spam with a high frequency (including my innocuous test message to a gmail address). 1) There's no recommendation to setup SPF for your domain. This is the big one. SPF is a big deal, and not having any spf will give you a higher spam score. 2) The creator of this service did not setup a reverse dns entry for the ip to the mx domain. There's no reverse dns at all (even though he's hosted with ramnode and ramnode supports rdns). 3) The creator does not allow you to add dkim signing keys; you can't dkim sign your messages. The above factors ensure that google has a high chance of marking you as spam, as well as any other sufficiently strict spam software. amavisd did not mark it as spam for me, giving it only a spam score of a little over 2, though I have mine configured at a high threshold compared to many people. Because of the above reasons, I wouldn't consider using this. The lack of a rdns entry is especially unforgivable because it's so easy and helps with your spam rating so much. The other factors are all additional complexity because the owner of the domain (user) would have to do additional work beyond the dns record, but those should also be there. Perhaps the creator will see this and improve these problems.
- jstalin 12y ago
  This is why I've moved over to Fastmail. They allow up to 100 custom domains and provide SPF. It's only $40 a year.
vortico 12y ago
Only Pawnmail staff have @pawnmail.com email addresses. Domain owners can register email addresses under their own domain (such as @joesmith.com), which may or may not contain filtered words. However, you have a good point. It would probably not be the ideal name for a service like to GMail, in which all users live under the @gmail.com domain.
- UVB-76 12y ago
  Irrespective of whether users use their own domain, email sent through the pawnmail service will be associated with the pawnmail domain via their MX records.

NicoJuicy 12y ago

It's for "custom domains", pawnmail is just an example and the name of the project. Check it out at : https://pawnmail.com/register https://pawnmail.com/register

TheDong 12y ago
Regardless that it's for custom domains, the smtp server will call itself "mx.pawnmail.com" during the SMTP protocol negotiation. The parent comment is not correct in thinking that matters, but they are correct that it will be identified as pawnmail, just not as part of the email address itself.
- evbogue 12y ago
  I suppose the nutgraf is: running your own email server is a better/recommended solution over pawnmail?

TheDong 12y ago

Junk/spam is far more complex than that. That alone will not be an issue almost certainly. HOWEVER, there are many issues with this site that will cause messages to get marked as spam with a high frequency (including my innocuous test message to a gmail address). 1) There's no recommendation to setup SPF for your domain. This is the big one. SPF is a big deal, and not having any spf will give you a higher spam score. 2) The creator of this service did not setup a reverse dns entry for the ip to the mx domain. There's no reverse dns at all (even though he's hosted with ramnode and ramnode supports rdns). 3) The creator does not allow you to add dkim signing keys; you can't dkim sign your messages. The above factors ensure that google has a high chance of marking you as spam, as well as any other sufficiently strict spam software. amavisd did not mark it as spam for me, giving it only a spam score of a little over 2, though I have mine configured at a high threshold compared to many people. Because of the above reasons, I wouldn't consider using this. The lack of a rdns entry is especially unforgivable because it's so easy and helps with your spam rating so much. The other factors are all additional complexity because the owner of the domain (user) would have to do additional work beyond the dns record, but those should also be there. Perhaps the creator will see this and improve these problems.

jstalin 12y ago
This is why I've moved over to Fastmail. They allow up to 100 custom domains and provide SPF. It's only $40 a year.

vortico 12y ago

Only Pawnmail staff have @pawnmail.com email addresses. Domain owners can register email addresses under their own domain (such as @joesmith.com), which may or may not contain filtered words. However, you have a good point. It would probably not be the ideal name for a service like to GMail, in which all users live under the @gmail.com domain.

UVB-76 12y ago
Irrespective of whether users use their own domain, email sent through the pawnmail service will be associated with the pawnmail domain via their MX records.