Re: Reporting Spam via Cyrus

Forrest Aldrich <[email protected]>
Newsgroups gmane.mail.spam.spamcop.help
Organization SpamCop
Message-ID <[email protected]>
Sorry, I should have been more specific.

I have had setup a series of scripts that handled reporting of spam via 
different macros - for Spamcop, the reports are sent as MIME attachments.

Now that I have a different folder format, I need to come up with a 
better way to streamline this.   It's a good opportunity to combine some 
of the other mechanisms that I'd been doing separately, like Razor2 
reporting, et al.

The format of a Cyrus file is not exactly mbox - and I believe sa-learn 
had a problem with it (I'm using the latest SpamAssassin).

So I figured I'd ask here to get some ideas before going completely 
blind ;-)


Thanks.


Mike Easter wrote:
> Forrest Aldrich wrote:
> 
>>I just switched to Cyrus IMAP - and it didn't occur to me that my
>>reporting habits (to Spamcop) would need to change, due to the
>>structure of how the mail is stored.  (I had mutt macros).
> 
> 
> I'm not clear on what you are asking.
> 
> Cyrus is mail /server/ software which can be used with lots of different
> email clients.  Here is an IU page instructing people how to use their
> clients with Cyrus http://kb.iu.edu/data/alyn.html  Reading your Cyrus
> mail using a desktop client
> 
> Apparently you were using mutt with something other than Cyrus.  Since
> you are using the past tense 'had mutt macros' -- it implies that you
> are planning to be using something other than mutt now.  Cyrus is not a
> mail client.  What client will you be using with Cyrus?
> 
> That client is what will be used to submit your spams.
> 
> 
>>I wonder whom else is using Cyrus here and how they may streamline
>>their reporting to their Spamcop Submit address.
> 
> 
> Here's a discussion of using mutt with cyrus IMAP
> http://mutt.sourceforge.net/imap/
> 1. Getting started
> 1.1. How to write an IMAP mailbox in mutt
> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.