Re: SMTP Question
On Thu, Feb 01, 2001 at 02:46:22PM -0500, Chris McCoy wrote: I provide free hosting and have a large amount of users everyday. I only have relaying from 127.0.0.1 because of I send an email out for verification from my php signup script. I have this one issue. Someone was trying to send 1000's of emails from a script on the web making the machine thinking its 127.0.0.1 localhost. the only reason i have the 127.0.0.1 for relay is because of sending out that email for verification. other than that i dont need relay. how can i fix this problem so people cant send mail from our server on our web page? any help is greatful. (this is a freebsd machine) thanks. Why not change your php script to submit the email via the qmail-inject command rather than SMTP? Then you can turn off you 127.0.0.1 listener. It's obscurity, but another alternative is put your listener on 127.0.0.2 and create an alias on your loopback interface. Regards.
RE: SMTP Question
OK, I'm new here, but I'll reply anyway. Couldn't you use IPChains to filter incoming mail to you machine that says it is from 127.0.0.1? If this is not a good idea, why? -Original Message- From: Mark Delany [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 01, 2001 11:53 AM To: [EMAIL PROTECTED] Subject: Re: SMTP Question On Thu, Feb 01, 2001 at 02:46:22PM -0500, Chris McCoy wrote: I provide free hosting and have a large amount of users everyday. I only have relaying from 127.0.0.1 because of I send an email out for verification from my php signup script. I have this one issue. Someone was trying to send 1000's of emails from a script on the web making the machine thinking its 127.0.0.1 localhost. the only reason i have the 127.0.0.1 for relay is because of sending out that email for verification. other than that i dont need relay. how can i fix this problem so people cant send mail from our server on our web page? any help is greatful. (this is a freebsd machine) thanks. Why not change your php script to submit the email via the qmail-inject command rather than SMTP? Then you can turn off you 127.0.0.1 listener. It's obscurity, but another alternative is put your listener on 127.0.0.2 and create an alias on your loopback interface. Regards.
Re: SMTP Question
On Thu, Feb 01, 2001 at 02:46:22PM -0500, Chris McCoy wrote: I provide free hosting and have a large amount of users everyday. I only have relaying from 127.0.0.1 because of I send an email out for verification from my php signup script. I have this one issue. Someone was trying to send 1000's of emails from a script on the web making the machine thinking its 127.0.0.1 localhost. the only reason i have the 127.0.0.1 for relay is because of sending out that email for verification. other than that i dont need relay. how can i fix this problem so people cant send mail from our server on our web page? any help is greatful. (this is a freebsd machine) thanks. -- Chris McCoy [EMAIL PROTECTED] So, if I understand this right, the mail is actually coming from localhost, because the spam is being generated by a script hosted on the mail machine, right? Ouch. My first inclincation would be to kick that user off my machine, immediately and without notice, and bar him from my network. Dirty spammer. Your AUP does not allow spam, right? Given that this may be difficult or impossible, I think that Mark Delany had the right idea -- use qmail-inject directly, and deny relay for localhost -- Greg White Those who make peaceful revolution impossible will make violent revolution inevitable. -- John F. Kennedy
RE: SMTP Question
I took this message to mean that the script was a hacker located just "on the web" trying to relay with a spoffed IP address, not a user on his own box. If it were the latter I'd certainly start by giving the user the boot... which is it, though? I'm just curious... -Original Message- From: Greg White [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 01, 2001 12:24 PM To: [EMAIL PROTECTED] Subject: Re: SMTP Question On Thu, Feb 01, 2001 at 02:46:22PM -0500, Chris McCoy wrote: I provide free hosting and have a large amount of users everyday. I only have relaying from 127.0.0.1 because of I send an email out for verification from my php signup script. I have this one issue. Someone was trying to send 1000's of emails from a script on the web making the machine thinking its 127.0.0.1 localhost. the only reason i have the 127.0.0.1 for relay is because of sending out that email for verification. other than that i dont need relay. how can i fix this problem so people cant send mail from our server on our web page? any help is greatful. (this is a freebsd machine) thanks. -- Chris McCoy [EMAIL PROTECTED] So, if I understand this right, the mail is actually coming from localhost, because the spam is being generated by a script hosted on the mail machine, right? Ouch. My first inclincation would be to kick that user off my machine, immediately and without notice, and bar him from my network. Dirty spammer. Your AUP does not allow spam, right? Given that this may be difficult or impossible, I think that Mark Delany had the right idea -- use qmail-inject directly, and deny relay for localhost -- Greg White Those who make peaceful revolution impossible will make violent revolution inevitable. -- John F. Kennedy
RE: SMTP Question
hes gone. i just wanna prevent this in the future. On Thu, 1 Feb 2001, Matt Simonsen wrote: I took this message to mean that the script was a hacker located just "on the web" trying to relay with a spoffed IP address, not a user on his own box. If it were the latter I'd certainly start by giving the user the boot... which is it, though? I'm just curious... -Original Message- From: Greg White [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 01, 2001 12:24 PM To: [EMAIL PROTECTED] Subject: Re: SMTP Question On Thu, Feb 01, 2001 at 02:46:22PM -0500, Chris McCoy wrote: I provide free hosting and have a large amount of users everyday. I only have relaying from 127.0.0.1 because of I send an email out for verification from my php signup script. I have this one issue. Someone was trying to send 1000's of emails from a script on the web making the machine thinking its 127.0.0.1 localhost. the only reason i have the 127.0.0.1 for relay is because of sending out that email for verification. other than that i dont need relay. how can i fix this problem so people cant send mail from our server on our web page? any help is greatful. (this is a freebsd machine) thanks. -- Chris McCoy [EMAIL PROTECTED] So, if I understand this right, the mail is actually coming from localhost, because the spam is being generated by a script hosted on the mail machine, right? Ouch. My first inclincation would be to kick that user off my machine, immediately and without notice, and bar him from my network. Dirty spammer. Your AUP does not allow spam, right? Given that this may be difficult or impossible, I think that Mark Delany had the right idea -- use qmail-inject directly, and deny relay for localhost -- Greg White Those who make peaceful revolution impossible will make violent revolution inevitable. -- John F. Kennedy -- Chris McCoy [EMAIL PROTECTED]
Re: SMTP question.
Z [EMAIL PROTECTED] writes: I was wondering if there was a way that I can have SMTP do a database lookup in order to find out where the mail should be delivered. What i mean is let's say that the SMTP server gets a request for [EMAIL PROTECTED] I need it to search in a mySQL database with the extracted information (bob, barker, myserver). This question has nothing to do with SMTP; it's about delivery, not receipt. qmail won't do a database lookup on the fly, but you can use virtual domains and extract your database information into your /var/qmail/users/assign file to get the same functionality. paul
Re: SMTP Question
--- Martin Searancke [EMAIL PROTECTED] wrote: Most mail packages have the ability to let a user log in when sending mail. (Outlook for example.) I was looking at this and had a couple of questions... Is this part of the SMTP standard? No. Can this be used to let authorised people relay through a server? Thanks Martin There are mods to qmail that allow users who have been authenticated through pop to then send out mail through your SMTP server. I have no experience with this, but I remember seeing it on www.qmail.org. Steve Martin Searancke CommSoft Group Ltd. Level 8, CommSoft House 90 Symonds St Auckland, New Zealand [EMAIL PROTECTED] +64 21 778592 = ---Someone told me that if you play a windoze NT CD backwards, it will play satanic messages. ---That's NOTHING!! If you play it forwards, it will install windoze NT! __ Do You Yahoo!? Get Yahoo! Mail Free email you can access from anywhere! http://mail.yahoo.com/
Re: SMTP Question
On Tue, Jul 18, 2000 at 11:04:26AM +1200, Martin Searancke wrote: Most mail packages have the ability to let a user log in when sending mail. (Outlook for example.) I was looking at this and had a couple of questions... Is this part of the SMTP standard? It is not part of the original rfc821, but it's documented in a "standard" document from last year: It's often called "SMTP AUTH". http://rfc2554.x42.com/ 2554 SMTP Service Extension for Authentication. J. Myers. March 1999. (Format: TXT=20534 bytes) (Status: PROPOSED STANDARD) Can this be used to let authorised people relay through a server? Yes. Look for "Mrs. Brisby" and "Krzysztof Dabrowski" on www.qmail.org. /magnus -- http://x42.com/
Re: smtp question
Rob Genovesi wrote: I'd like to move outgoing mail services to another machine without affecting the incoming mail. Because of my previous setup all of my clients have both POP and SMTP servers set to "mail.mydomain.com" If you can discriminate by incoming IP address you can direct traffic to a different machine/port combination (all customers come in over local dial-up vs. incoming email from net coming in from a different address range). Even so you would have to be able to support both in out on both machines for those who didn't fit the above model. It's hard to think of all eventualities when you build services, but since A records and CNAMEs are free you might as well dream up as many as you want. (You could achieve a similar effect as above by having split-horizon dns, might be easier too).
