It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
kohlrak: Many still prefer 25 for email. I see it open all the time, actually, and more often open than closed.
What I meant was blocking telnetting anonymously to p25 (SMTP-MTA), used for server-to-server to initiate the transfer. Client fetching of mail happens over p587 (SMTP-MSA), some still uses p465 with a wrapper of some sort and are basically deprecated according to iana.

Most of the major ones with competent admins had those closed pretty fast (back then), and today it's pretty much idiotic to still allow anonymous access.

Well, you can make a hack to tunnel anything you want in/out of any port you want, but that still depends on A and B to communicate on the same level.

EDIT: The fact that you don't use tls it's pretty easy for others to snoop up your mail-address and passwords, which again is just one of many methods to gather potential targets...
Post edited May 18, 2018 by sanscript
what the fuck is r0blox sex and how do i do that
avatar
rtcvb32: I remember seeing a tutorial explaining how to talk directly to a mail server to send a mail. The return addresses aren't verified so it doesn't matter what it contains. No surprise i've had bounces of 'mail could not be delivered' as my email address was used multiple times in spam (though i'm guessing it was either randomly picked, or brute forced)
avatar
sanscript: Any sane admin would block access to p25.

In the early days these protocols were made with simple and open sharing in mind, though, the Internet changed that. But some years ago this blocking of p25 among others actually became a standard procedure in order to prevent abuse.

Btw; search for nmap and you have a nice little power-tool at your hand ;-)
nmap, ah yes, i'm aware of that tool. Been a while since i used it.

I'd honestly go for a shared key method, where public keys are set up and private keys for people on their computer. Then signing and encrypting all email and verifying (at the server level). Yeah takes a little more processing power, but 99.99% of spam would die this way because it's not raw text. You can't really fool it, unless a key gets broken, in which case you give a new key or require updating the key to the next larger size every couple years.
Post edited May 18, 2018 by rtcvb32
avatar
sanscript: Any sane admin would block access to p25.

In the early days these protocols were made with simple and open sharing in mind, though, the Internet changed that. But some years ago this blocking of p25 among others actually became a standard procedure in order to prevent abuse.

Btw; search for nmap and you have a nice little power-tool at your hand ;-)
avatar
rtcvb32: nmap, ah yes, i'm aware of that tool. Been a while since i used it.

I'd honestly go for a shared key method, where public keys are set up and private keys for people on their computer. Then signing and encrypting all email and verifying (at the server level). Yeah takes a little more processing power, but 99.99% of spam would die this way because it's not raw text. You can't really fool it, unless a key gets broken, in which case you give a new key or require updating the key to the next larger size every couple years.
With pre-shared keys? I agree, but encrypting the mail itself (inside of the already encrypted communication) is rather tiresome, especially when very few uses it, like GnuPGP, so it's dependent on both A and B to use it.

Other than Protonmail I can't think of any "easy" solution if security and privacy is a must have...
avatar
Maighstir: Mac OS X Server used SquirrelMail for its webmail interface, at least back in 2007. It didn't look good back then, and it doesn't now. I mean, yeah, sure, it probably works on a web browser from 1992 if you're into that, but personally, I much prefer RoundCube.
Take a look at their bounty page. Very amusing the things that are on offer. Things which are practically standard on any other platform and they're offering a small windfall for them.

It must be coded in something nobody wants to work with for those bounties.

Hmm, PHP and C. No wonder. At least Javascript and PHP sounds more sensible a combination.
avatar
sanscript: With pre-shared keys? I agree, but encrypting the mail itself (inside of the already encrypted communication) is rather tiresome, especially when very few uses it, like GnuPGP, so it's dependent on both A and B to use it.

Other than Protonmail I can't think of any "easy" solution if security and privacy is a must have...
If it's the default and done more or less transparently (other than entering a password when you need it) it wouldn't matter so much.

But alas, much like zlib/gz being used for compression packets on the internet, we're probably stuck with it... because it's sorta the standard and was implemented when we had far more limitations on hardware.
avatar
Darvond: It must be coded in something nobody wants to work with for those bounties.
I'm enjoying the idea that Valve hired half a dozen programming students and their stuff is all in C but every block ends with a goto pointed at another block. Or else Gaben was a personal friend of Larry Wall and hired him for it, so Wall programmed the client in C but somehow using Perl syntax.
avatar
kohlrak: Many still prefer 25 for email. I see it open all the time, actually, and more often open than closed.
avatar
sanscript: What I meant was blocking telnetting anonymously to p25 (SMTP-MTA), used for server-to-server to initiate the transfer. Client fetching of mail happens over p587 (SMTP-MSA), some still uses p465 with a wrapper of some sort and are basically deprecated according to iana.

Most of the major ones with competent admins had those closed pretty fast (back then), and today it's pretty much idiotic to still allow anonymous access.

Well, you can make a hack to tunnel anything you want in/out of any port you want, but that still depends on A and B to communicate on the same level.

EDIT: The fact that you don't use tls it's pretty easy for others to snoop up your mail-address and passwords, which again is just one of many methods to gather potential targets...
While other accounts exist, i'm the only actual user for the email. Passwords have to be accessed via squirrelmail, as SMTP is only email in, email out. No logging in to do. You have to either use mail or squirrelmail to send emails, so they'd have to brute force that to get anything (to be fair, i don't really have any special protection for it, outside of the crappy hardware). TLS just offers an extra pain (probably not much, but i haven't looked into it) when something happens to my postfix config.

Though, no, i still don't see the issue with SMTP and anonymous connection, unless you mean anonymous sending. You don't have to block the port to solve that issue.

avatar
Darvond: It must be coded in something nobody wants to work with for those bounties.
avatar
OneFiercePuppy: I'm enjoying the idea that Valve hired half a dozen programming students and their stuff is all in C but every block ends with a goto pointed at another block. Or else Gaben was a personal friend of Larry Wall and hired him for it, so Wall programmed the client in C but somehow using Perl syntax.
Please, tell me more on this.
avatar
sanscript: Any sane admin would block access to p25.

In the early days these protocols were made with simple and open sharing in mind, though, the Internet changed that. But some years ago this blocking of p25 among others actually became a standard procedure in order to prevent abuse.

Btw; search for nmap and you have a nice little power-tool at your hand ;-)
avatar
rtcvb32: nmap, ah yes, i'm aware of that tool. Been a while since i used it.

I'd honestly go for a shared key method, where public keys are set up and private keys for people on their computer. Then signing and encrypting all email and verifying (at the server level). Yeah takes a little more processing power, but 99.99% of spam would die this way because it's not raw text. You can't really fool it, unless a key gets broken, in which case you give a new key or require updating the key to the next larger size every couple years.
Eh, if it became common practice, the pubkey would be available to the spammers the same avenue the email address is, which wouldn't solve anything. Sure, it'd solve the crap we're seeing now, but not for long. If the key is done privately, why not just give out the email privately as well? I've seen people have success with whitelisting email addresses, as well, and spam rarely comes from a known source (does happen, but much less common).
avatar
rtcvb32: nmap, ah yes, i'm aware of that tool. Been a while since i used it.

I'd honestly go for a shared key method, where public keys are set up and private keys for people on their computer. Then signing and encrypting all email and verifying (at the server level). Yeah takes a little more processing power, but 99.99% of spam would die this way because it's not raw text. You can't really fool it, unless a key gets broken, in which case you give a new key or require updating the key to the next larger size every couple years.
avatar
sanscript: With pre-shared keys? I agree, but encrypting the mail itself (inside of the already encrypted communication) is rather tiresome, especially when very few uses it, like GnuPGP, so it's dependent on both A and B to use it.

Other than Protonmail I can't think of any "easy" solution if security and privacy is a must have...
If you're worried about the privacy of emails, you should be using external tools to encrypt the data within the email. Things setting on storage, if you're not the admin, tends to get pulled and looked at.
Post edited May 18, 2018 by kohlrak
avatar
Maighstir: Mac OS X Server used SquirrelMail for its webmail interface, at least back in 2007. It didn't look good back then, and it doesn't now. I mean, yeah, sure, it probably works on a web browser from 1992 if you're into that, but personally, I much prefer RoundCube.
avatar
Darvond: Take a look at their bounty page. Very amusing the things that are on offer. Things which are practically standard on any other platform and they're offering a small windfall for them.

It must be coded in something nobody wants to work with for those bounties.

Hmm, PHP and C. No wonder. At least Javascript and PHP sounds more sensible a combination.
Well, squirrelmail itself isn't overly popular. Squirrelmail is meant to run as a plugin for apache, and also meant to work for a multitude of mailbox methods (file, dovecot, etc). It's a general headache. It works and is good, but a royal pain, like postfix. To be fair though, i'm surprised the devs themselves didn't claim the bounties. These are not necessarily rocket science, so it must be hard for one particular reason or another.
avatar
kohlrak: If you're worried about the privacy of emails, you should be using external tools to encrypt the data within the email. Things setting on storage, if you're not the admin, tends to get pulled and looked at.
I'm not worried. I don't use public mail services like gmail or hotmail at least, but I use encryption between me and my servers, and it's really not a hassle.

avatar
kohlrak: Though, no, i still don't see the issue with SMTP and anonymous connection, unless you mean anonymous sending. You don't have to block the port to solve that issue.
I mentioned two methods that are relatively known as security precautions. Anonymous connection and anonymous sending IS basically the same thing, it's still open for heavy abuse.

And no, I'm still not talking about blocking p25 directly - that would actually stop SMTP-MTA connection between servers.

I'm only trying to give you some pointers here... it's totally up to you what you do with that info. But if you don't see the case there then I just hope you don't work as an admin / sec admin. XD
Post edited May 18, 2018 by sanscript
avatar
kohlrak: Well, squirrelmail itself isn't overly popular. Squirrelmail is meant to run as a plugin for apache, and also meant to work for a multitude of mailbox methods (file, dovecot, etc). It's a general headache. It works and is good, but a royal pain, like postfix. To be fair though, i'm surprised the devs themselves didn't claim the bounties. These are not necessarily rocket science, so it must be hard for one particular reason or another.
I concluded as much. Even for what it does, it seems there are better, and more modern systems. And for internal server mails, I feel most are happy to make their own or use something simpler.
avatar
kohlrak: Well, squirrelmail itself isn't overly popular.
We're a DirectAdmin shop and we default to using squirrelmail.

Most of our clients are tied to their iPhones and Outlook though.
avatar
kohlrak: If you're worried about the privacy of emails, you should be using external tools to encrypt the data within the email. Things setting on storage, if you're not the admin, tends to get pulled and looked at.
avatar
sanscript: I'm not worried. I don't use public mail services like gmail or hotmail at least, but I use encryption between me and my servers, and it's really not a hassle.

avatar
kohlrak: Though, no, i still don't see the issue with SMTP and anonymous connection, unless you mean anonymous sending. You don't have to block the port to solve that issue.
avatar
sanscript: I mentioned two methods that are relatively known as security precautions. Anonymous connection and anonymous sending IS basically the same thing, it's still open for heavy abuse.

And no, I'm still not talking about blocking p25 directly - that would actually stop SMTP-MTA connection between servers.

I'm only trying to give you some pointers here... it's totally up to you what you do with that info. But if you don't see the case there then I just hope you don't work as an admin / sec admin. XD
The server's set to only allow emails sent to it to come through. Try sending an email from my server to, say, kohlrak@gmail.com. Shouldn't go through unless i have a reverted setting.
avatar
kohlrak: Well, squirrelmail itself isn't overly popular. Squirrelmail is meant to run as a plugin for apache, and also meant to work for a multitude of mailbox methods (file, dovecot, etc). It's a general headache. It works and is good, but a royal pain, like postfix. To be fair though, i'm surprised the devs themselves didn't claim the bounties. These are not necessarily rocket science, so it must be hard for one particular reason or another.
avatar
Darvond: I concluded as much. Even for what it does, it seems there are better, and more modern systems. And for internal server mails, I feel most are happy to make their own or use something simpler.
I think the bigger thing at the end of the day is that IMAP and POP3 is easier for most people. When i originally set this up, I didn't have a smartphone or tablet, so i wanted, if necessary, to be able to check my email from any computer. Naturally, webmail (email over HTTP) is the solution. Squirrelmail is the goto webmail option if you don't want to have the hassel of building your own. But, this is how dead webmail is (or, rather, email is to anyone who's not a company ad prefers a solution you pay for, because companies prefer to pay for things they can get for free).

avatar
kohlrak: Well, squirrelmail itself isn't overly popular.
avatar
drmike: We're a DirectAdmin shop and we default to using squirrelmail.

Most of our clients are tied to their iPhones and Outlook though.
Yeah, it's good for the basic needs (the whole reason i even use it). I never saw the big thing with outlook, though.
Post edited May 18, 2018 by kohlrak
avatar
kohlrak: -
When I mentioned about the anonymous telnetting p25 in post nr 14, I was speaking generally and was originally answering rtcvb32, not to you. Only about the lack of encryption, but I'm stopping there now, as this is fruitless and getting staled ;-)
avatar
kohlrak: I never saw the big thing with outlook, though.
Comes with Windows. Why install anything else?

Heck, even I use the build in email app on my ipod touch instead of downloading the separate GMail app. Works for me....