I am trying to assess the Spamminess of E-mails. The emails are received in Maildir (on Linux server) via Postfix.
I am completely new to the E-mail domain. So I am curious about the following things:
Do the emails with attachments usually pass through the spam filters?
Is there a size limit (attachment size) that decides this?
My actual question is (when the emails have attachments) will SpamAssassin take longer than usual to assess the email? I am using the Linux version of Apache SpamAssassin.
I can easily extract different parts of the email (including images/PDFs) with JavaMail but, at the end, when I try to pass the file to SpamAssassin, the process never ends. It works fine for smaller attachments (30-40 KB) though.
Did anyone face the same problem? Suggestions are much appreciated.
Thanks!
Related
i'm running a mail server that serves mostly architects. the usage of those guys in email is mostly for sending files. today, our mail sending files is limited to about 20MB but the limit is because many webservers reject email that are bigger then 20MB.
what i would like to achieve is that when sending files that are larger then 20MB just to save the files aside and generate a link to download instead.
i would like to know:
are there any plugin to courier that do it?
what tools to i need to use to develop such a plugins?
How to make MTA replace large attachments with links to a centrally-stored copy [MIMEDefang Milter for sendmail/postfix/...]
You may consider using MIMEDefang milter available under GPL license for sendmail and postfix.
MIMEDefang Description
Mail Inspection and Modification
MIMEDefang can inspect and modify e-mail messages as they pass through your mail relay. MIMEDefang is written in Perl, and its filter actions are expressed in Perl, so it's highly flexible. Here are some things that you can do very easily with MIMEDefang:
Delete or alter attachments based on file name, contents, results of a virus scan, attachment size, etc.
Replace large attachments with links to a centrally-stored copy to ease the burden on POP3 users with slow modem links.
[...]
I am creating a PHP system that will forward emails, (ie. someone#emailforprofession.com to someone#gmail.com) without using an SMTP server which is faster and more stable? PEAR::Mail or PHP: Mail? (or another one entirely)
I would be using extra headers and attachments but mainly trying to keep it looking and acting the same. (if anyone has an example for forwarding with attachments PLEASE provide it!)
And not exactly on the side but is there a way for people to be able to send email from they're someone#emailforprofession.com email address without having a complete inbox etc?
It would probably be better for me to use a real email provider but these are supposed to be free email addresses so paying by the email address is not an option, if anyone knows of a service that: charges by the month or year, has an API that email addresses can be created from and that can set up email forwards via the API that would be most appreciated.
I currently have a partial system together but would like to know which way I should go first.
Thank you all.
The PEAR class supports multiple mailer backends, which allows you to
switch whenever needed and you'll be able to perform some benchmarks
and see which backend suits you best. The native mail function on the
other hand is much less advanced and will show a clear difference in
performance, especially for that amount of mails.
I also suggest you have a look at PEAR's mail queue class:
http://pear.php.net/package/Mail_Queue
This is much more recommended for larger projects such as yours,
you'll also be able to implement a cron like feature which will send a
certain amount of mail per period you choose.
Here
What's the easiest way to process incoming email? Our objective is to get email into a Resque queue. We've explored and integrated a lot of options, like piping email through Postfix into Ruby (which turned out to be unreliable), piping email through Google App Engine back to our server (which turned out to be shaky), and using Sendgrid (which is expensive.)
I'm trying to explore other ways to get email processed. Any ideas?
If the email is received and hosted by an IMAP-capable server (Gmail is good enough), then the messages can be retrieved and processed once and again from almost any programming language using standard libraries.
I need to be able to make a program that looks through a mailbox of bounced messages, where the messages come back with the initial message in a .msg attachment, and open the .msg attachment for processing in ASP.NET 2.0. Is there any sort of code that might help in this? I've been looking at Reading Email using Pop3 in C# as a starting point, but can't figure out how best to open the attachment from there, or if there's some easier way I'm missing.
From your post, it appears that you are better off getting a third party component that had already implemented (POP or IMAP) the protocol.
I just googled and got one and I bet there are a bunch out there.
http://www.jscape.com/articles/retrieving_email_pop3_csharp.html
Parsing bounce messages in general is a huge task, because their formats vary greatly between different mail transport agents. So unless you are on a closed network, or you only care for bounces reported directly from your own transport agent, then you are in for a big job, and you certainly cannot count on the original messages being attached in full to the bounce answers.
If it is possible for you to regenerate the outgoing mails from a few key parameters, then you might want to consider using a VERP addressing scheme instead. Your parsing job would then be reduced to recognizing and deciphering the recipient addresses of the bounce messages, instead of their full content.
I ended up going with a solution involving reading in the messages using Microsoft.Office.Interop.Outlook ( http://support.microsoft.com/?kbid=310244 ), saving the attached .msg to the drive, then finally reading in that message using an open-source third party solution ( http://www.codeproject.com/KB/office/reading_an_outlook_msg.aspx ). It's probably not the most efficient solution overall, but it handles the specific case we needed to support.
I developed a program that sends emails (with attachments to clients). Now, some of the clients are asking what they should do with the emails with UNKNOWN_PARAMETER_VALUE.DAT? I'm quite sure that I've not sent attachments with those names. Only a few of the clients have received attachments with this. Is this a virus? If not, is this a MIME problem (FYI, some attachments have Chinese filename, I'm not sure if this might be a probable cause).
It looks like a virus. At least it's listed here.