command line email

rymus

Messing around here on various linux 9 & fedora servers with sending files via email for reporting purposes.. At the moment I'm using

cat /whatever/file | mail -s 'Subject' email@address.com

It's working, but it's tagging messages as spam. Anyway I can get around this? Or any better process I could use to achieve the same result? Had a good google around the place but cant come up with anything decent. Cheers.

EL_Loco

Hi,

what's tagging it as spam? the email account you're sending to? If that account has a filter maybe try an account you know doesn't. If it turns out that it is the filtering on the email server you could play around with that to stop it getting marked as spam.

or am I waaaaay off the mark here?

rymus

I presume it's the outgoing server that's tagging it as spam, no matter what email address I send it to the tagging is always the same *** Spam ***

Tried turning off SpamAssassin with no effect. It's happened so far on a couple of Redhat 9 servers. There are one or two fedora machines it's not happening on but I can't see what differences there are between the configurations on the two.

Rambo

rymus wrote:

Messing around here on various linux 9 & fedora servers with sending files via email for reporting purposes.. At the moment I'm using

cat /whatever/file | mail -s 'Subject' email@address.com

It's working, but it's tagging messages as spam. Anyway I can get around this? Or any better process I could use to achieve the same result? Had a good google around the place but cant come up with anything decent. Cheers.

I found using SendEmail works great for doing this type of thing
http://caspian.dotconf.net/menu/Software/SendEmail/

niallb

Could be your sender address that's causing that.
The headers should list why the message has been designated as spam.
If it has, you may need to persuade your system to give you (or 'root' by any chance?) a real email address for mails sent from the command line.
This might be in a file called genericstable or virtusertable depending on your mail system.

Send yourself an email from the command line on a machine that works and one that doesn't and compare the two. Any differences besides timestamps are worth looking at.

rymus

cheers for the help lads, I'll have to take a look at both solutions when I get ten minutes

Civilian_Target

Yeah, to elaborate on what's already been said, the usual reason for this is that the messages have a sender domain that doesn't correspond with the outgoing mail server's domain (or as the receiver's concerned, the mail server from which the message originated).

So, for example, if mail sent from the shell appears to come from rymus@rymus.com but your SMTP server is on the domain rymusesprovider.com, then your message is likely to be treated as spam by recipients (unless the DNS tree has rymusesprovider.com listed as the owner of rymus.com)