Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: SpamAssassin: users

Spam in qmail queue

 

 

SpamAssassin users RSS feed   Index | Next | Previous | View Threaded


marcin at 2fluid

May 23, 2008, 2:52 AM

Post #1 of 8 (177 views)
Permalink
Spam in qmail queue

Hi,

I am not sure that I am writing to correct list, but maybe you will help me.

On one of my server qmail has been installed, SpamAssassin and qmail-scanner.
There is a several virtual domains, and Spam filter is working quite OK.

But I have some message which I am worried about:

For example: on sever is domain: somedoamin1.com

Somebody will send SPAM to HYPERLINK "mailto:user[at]somedomain1.com"user[at]somedomain1.com, and:
- Spamassassin marks it as SPAM (which is correct)
- But user doesn’t exist on somedomain1.com (it happen)
- So qmail is storage this mail in queue as long as it can.

My question is, what is the best practice and how can I configure following scenario:

Scenario:
Spam marks message as SPAM, qmail is trying deliver that message to not exited user,
And if is not exist – message is deleted.

BUT if message is not SPAM – and user doesn’t exist, bounce message should be send to sender.

Thank you very much for your help.

Marcin Praczko

No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.24.0/1461 - Release Date: 22/05/2008 16:44


evan at espphotography

May 23, 2008, 6:47 AM

Post #2 of 8 (167 views)
Permalink
Re: Spam in qmail queue [In reply to]

As this really is a qmail question, if you don't get any answers here,
I'd suggesting posting to a qmail forum.

Marcin Praczko wrote:
>
> Hi,
>
> I am not sure that I am writing to correct list, but maybe you will
> help me.
>
> On one of my server qmail has been installed, SpamAssassin and
> qmail-scanner.
>
> There is a several virtual domains, and Spam filter is working quite OK.
>
> But I have some message which I am worried about:
>
> For example: on sever is domain: somedoamin1.com
>
> Somebody will send SPAM to user[at]somedomain1.com
> <mailto:user[at]somedomain1.com>, and:
>
> - Spamassassin marks it as SPAM (which is correct)
>
> - But user doesn’t exist on somedomain1.com (it happen)
>
> - So qmail is storage this mail in queue as long as it can.
>
> My question is, what is the best practice and how can I configure
> following scenario:
>
> Scenario:
>
> Spam marks message as SPAM, qmail is trying deliver that message to
> not exited user,
>
> And if is not exist – message is deleted.
>
> BUT if message is not SPAM – and user doesn’t exist, bounce message
> should be send to sender.
>
> Thank you very much for your help.
>
> Marcin Praczko
>
>
> No virus found in this outgoing message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 269.24.0/1461 - Release Date:
> 22/05/2008 16:44
>


richard.frovarp at sendit

May 23, 2008, 6:54 AM

Post #3 of 8 (166 views)
Permalink
Re: Spam in qmail queue [In reply to]

Marcin Praczko wrote:
>
> Hi,
>
>
>
> I am not sure that I am writing to correct list, but maybe you will
> help me.
>
>
>
> On one of my server qmail has been installed, SpamAssassin and
> qmail-scanner.
>
> There is a several virtual domains, and Spam filter is working quite OK.
>
>
>
> But I have some message which I am worried about:
>
>
>
> For example: on sever is domain: somedoamin1.com
>
>
>
> Somebody will send SPAM to user[at]somedomain1.com
> <mailto:user[at]somedomain1.com>, and:
>
> - Spamassassin marks it as SPAM (which is correct)
>
> - But user doesn’t exist on somedomain1.com (it happen)
>
> - So qmail is storage this mail in queue as long as it can.
>
>
>
> My question is, what is the best practice and how can I configure
> following scenario:
>
>
>
> Scenario:
>
> Spam marks message as SPAM, qmail is trying deliver that message to
> not exited user,
>
> And if is not exist – message is deleted.
>
>
>
> BUT if message is not SPAM – and user doesn’t exist, bounce message
> should be send to sender.
>
>
>
> Thank you very much for your help.
>
>
>
> Marcin Praczko
>
Do not bounce! If the user does not exist, reject the message at SMTP
time. Problem solved. If you accept the message, it is up to you to deal
with it. Bouncing will just send messages back to people who don't
deserve it. Look up "joe jobbed".


Bowie_Bailey at BUC

May 23, 2008, 6:56 AM

Post #4 of 8 (166 views)
Permalink
RE: Spam in qmail queue [In reply to]

Marcin Praczko wrote:
> Hi,
>
> I am not sure that I am writing to correct list, but maybe you will
> help me.
>
> On one of my server qmail has been installed, SpamAssassin and
> qmail-scanner.
> There is a several virtual domains, and Spam filter is working quite
> OK.
>
> But I have some message which I am worried about:
>
> For example: on sever is domain: somedoamin1.com
>
> Somebody will send SPAM to user[at]somedomain1.com, and:
> - Spamassassin marks it as SPAM (which is correct)
> - But user doesn't exist on somedomain1.com (it happen)
> - So qmail is storage this mail in queue as long as it can.
>
> My question is, what is the best practice and how can I configure
> following scenario:
>
> Scenario:
> Spam marks message as SPAM, qmail is trying deliver that message to
> not exited user,
> And if is not exist - message is deleted.
>
> BUT if message is not SPAM - and user doesn't exist, bounce message
> should be send to sender.
>
> Thank you very much for your help.

Do not accept mail for non-existent users. If the user doesn't exist,
the server should reject the mail with a "550 User Unknown" and it will
never get to your mail queue in the first place.

If the message is legitimate, the sender will receive the error message.
If the message is spam, the spambot will receive the error message.
Either way, the error goes directly back to the sender through the same
connection used to send the mail.

--
Bowie


jonas_lists at frukt

May 23, 2008, 7:12 AM

Post #5 of 8 (167 views)
Permalink
Re: Spam in qmail queue [In reply to]

Marcin Praczko wrote:

> - Spamassassin marks it as SPAM (which is correct)
> - But user doesn’t exist on somedomain1.com (it happen)
> - So qmail is storage this mail in queue as long as it can.

Do you have any special reason to receive mail for users that
doesn't exist?

> My question is, what is the best practice and how can I configure
> following scenario:

The best practice is to never accept messages to non-existant users.

Regards
/Jonas
--
Jonas Eckerman, FSDB & Fruktträdet
http://whatever.frukt.org/
http://www.fsdb.org/
http://www.frukt.org/


sahil at tandon

May 23, 2008, 7:53 AM

Post #6 of 8 (166 views)
Permalink
Re: Spam in qmail queue [In reply to]

> Marcin Praczko wrote:
>
>> - Spamassassin marks it as SPAM (which is correct)
>> - But user doesn’t exist on somedomain1.com (it happen)
>> - So qmail is storage this mail in queue as long as it can.
>
> Do you have any special reason to receive mail for users that
> doesn't exist?
>
>> My question is, what is the best practice and how can I configure
>> following scenario:
>
> The best practice is to never accept messages to non-existant users.

Agreed. There is no reason to accept then bounce. That's ==
backscatter. Either REJECT or DISCARD.

- Sahil


hamann.w at t-online

May 23, 2008, 9:19 AM

Post #7 of 8 (167 views)
Permalink
Re: Spam in qmail queue [In reply to]

>>
>> Hi,
>> =20
>> I am not sure that I am writing to correct list, but maybe you will help =
>> me.
>> =20
>> On one of my server qmail has been installed, SpamAssassin and =
>> qmail-scanner.=20
>> There is a several virtual domains, and Spam filter is working quite OK.
>> =20
>> But I have some message which I am worried about:
>> =20
>> For example: on sever is domain: somedoamin1.com
>> =20
>> Somebody will send SPAM to HYPERLINK =
>> "mailto:user[at]somedomain1.com"user[at]somedomain1.com, and:
>> - Spamassassin marks it as SPAM (which is correct)
>> - But user doesn=92t exist on somedomain1.com (it happen)
>> - So qmail is storage this mail in queue as long as it can.=20
>> =20
>> My question is, what is the best practice and how can I configure =
>> following scenario:
>> =20
>> Scenario:
>> Spam marks message as SPAM, qmail is trying deliver that message to not =
>> exited user,=20
>> And if is not exist =96 message is deleted.=20
>> =20
>> BUT if message is not SPAM =96 and user doesn=92t exist, bounce message =
>> should be send to sender.=20
>> =20
>> Thank you very much for your help.
>> =20
>> Marcin Praczko
>>

Hi Marcin,

you can modify qmail-scanner to exit with error code if spam score is over a given value
(usually higher than default score, e.g. 10 rather than 5)
Unpatched qmail would return - during the smtp session, not as a bounce - an
"administratively prohibited" message to the sender.
It is straightforward to add a new exit value to qmail and have that tell the sender that their
message was considered spam.
You can do this right away, but you are still encouraged to install whatever matches your system
setup and rejects mail to non-existant users

Wolfgang


jhardin at impsec

May 23, 2008, 9:34 AM

Post #8 of 8 (168 views)
Permalink
Re: Spam in qmail queue [In reply to]

On Fri, 23 May 2008, Richard Frovarp wrote:

> Marcin Praczko wrote:
>
>> BUT if message is not SPAM - and user doesn't exist, bounce message
>> should be send to sender.
>
> Do not bounce! If the user does not exist, reject the message at SMTP
> time. Problem solved. If you accept the message, it is up to you to deal
> with it. Bouncing will just send messages back to people who don't
> deserve it. Look up "joe jobbed".

In addition, behavior like that can get you blacklisted.

Marcin, please do not accept-then-bounce mail sent to nonexistent users or
mail blocked for spamminess. You may find it increasingly difficult to
communicate with the rest of the world, and you _will_ be hated.

--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin[at]impsec.org FALaholic #11174 pgpk -a jhardin[at]impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
If Microsoft made hammers, everyone would whine about how poorly
screws were designed and about how they are hard to hammer in, and
wonder why it takes so long to paint a wall using the hammer.
-----------------------------------------------------------------------
2 days until the Mars Phoenix lander arrives at Mars

SpamAssassin users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.