Postfix trigger when mail sent [closed] - email

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I need run script after postfix sent mail and get status of it (success, defered etc). Is filters help me? I think it trigger only for incoming mail but i need for outgoing.
I think about parsing logs by message-id. But it is not good idea. Is there better way?

Filters aren't going to have access to delivery status, so I don't think outgoing (after-queue content) filters will help. You could add return-receipt in the header, but it would be easier to turn on Delivery Status Notification in postfix. That still just gets the status back to the originating user, and I suspect you meant something system-wide.
Taking DSN a step further, you could hack postfix's bounce templates to contain a "To:" or "Bcc:" header (if the user requested status too?), sending status messages to a specific central mailbox. That may take a change to bounce itself, to allow those headers.
Personally, I'd go with parsing the logs, but you don't explain why that's bad or what specifically you want to accomplish.

you can check if any mail is deferred by issuing postfix utility postqueue -p

Related

how do I know if my webserver becomes listed as a spamserver [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm working on a app which sends notifications emails. I know this is stereotypical for spam servers. I know the first question ist "How can I ensure what my server will not be listed as a spam server?" However I believe I should monitor my mailserver to ensure what every customer becomes his mails.
So the question: How can I check/monitor whether my server is listed as a spam server?
I really appreciate your help.
MXtoolbox (disclosure: I hold no relation to this site) has a great blacklist checking tool that checks all the major blacklists.
As for staying off them, make sure all your e-mails are opt-in and have an unsubscribe link within the e-mail body of every notification sent. Keep a record of all clients opting in, some hosting companies will charge you a small fortune if you get their IPs blacklisted.

how does Mailchimp recognize that email was marked as spam? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Mailchimp, the online service for sending newsletters, has an statistics about how many people marked email you sent as spam. Does anybody know how this works? I am asking because I was thinking about how to implement this into my CMS which sends newsletters as well. Thanks for replies!
It's called FBL (feedback loop) and means that you register your MTAs (email sending servers) at the ISPs that supports FBLs (Yahoo, Hotmail etc.)
All you have to do is to sign up for every available FBL via their forms and then they will send you an email every time someone mark email sent from those servers as spam (spam complaints).
Then you'll have to parse those emails to get the information from it.
Have you checked Mailchimp Support?
http://kb.mailchimp.com/article/how-spam-filters-think
An abnormally high bounce rate is another indicator. Look through your hard bounces, and read the SMTP replies. Spam filters sometimes leave little clues about why they blocked your campaign (See: http://kb.mailchimp.com/article/why-did-my-email-bounce-smtp-replies).

Automated handling of Un-Deliverable email [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We are using a 3rd party email relay service to send mass emails to our client's subscribers. Problem is that when there is a "soft bounce" i.e domain accepts email and then subsequently bounces for whatever reason (as opposed to a hard bounce), the client's replyto/from email address is the one the undeliveable message goes to.
Atleast with one client, we have the ability to host their email. So for example, support#thisclientofours.net is hosted by us and we can query the IMAP server to see the return codes.
Questions:
Is there a way for us have the Non-Delivery Report/Receipt (NDR) be
sent to a different email (one that we own) vs a genuine reply from
the subscriber to the client ? Does the answer reside in the
"Return-Path" header ?
If 1) is not possible, then whats the most efficient way of
gathering the NDR status flags and then forwarding non NDR (replys) to
the client ?
You can set the 'Return-Path' header and 'Reply-To' header to be different. All bounces are to be sent to the 'Return-Path' address, not the 'Reply-To' address.

noreply email address. [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
I'm sending out a notification email every day to our customers, when new data in our service becomes available. No, it's not spam, it's a notification that customers have asked for, and can be turned off - just in case you were wondering. :)
I noticed that some websites have a noreply#domain.com address which they use to send all the notifications?
Why not just use an email address that is an alias to the support email. That way, if somebody replies to a notification (meaning they have a question) it goes directly to support. Why even bother explaining that "BTW, this email is not supposed to be used for support, please don't reply - use something else instead" when you could just have both pointing to the same inbox anyway? Or is there some other reason that I'm missing?
Maybe they don't want to read all the vacation and failure notices.
Small web sites probably do that, but eBay would be getting 10's of thousands of support emails per day (more than already) if that were the case. They could implement an automated filter of the noreply email address to find some that might need answering.
I guess it also comes to down to the fact that sending you an email from a noreply#* address isn't actually instigating a conversation. If they send you an email to which they want or need a response, or are responding to an email you've sent them, of course it makes no sense to use such an address.
So I don't think it's particularly down to technology, and more about expectations and conforming to people's existing mental models of how conversations and general sales pitches work.

Preventing Email Spam? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am working on an email program and I want to add a basic way to detect spam based on the domain/sender of the mail. One service that I was looking at was gossip (http://gossip-project.sourceforge.net/) but I don't want to go to the hassle of setting up a dedicated Gossip server. I know that there are a lot of email blacklists (DNSBL's) and stuff out there that can give you an estimate of whether or not an email is spam based on the domain it was sent from. I'm wondering if anyone knows of one that I can just query from within a program by passing it the sender's domain and having it return the likelihood that the email is spam. I don't want a service that requires me to set up a server for it.
Anti-Spam Blacklists do list only IPs not domains. They can't list domains (of the sender) as the sender address can be (and usually is) forged.
So you can either lookup an IP in a DNSBL from where the mail was originating. Or you have to determine the probability of spam by analyzing the mail content. The latter is "expensive" in CPU cycles and other resources. In both cases you do not need a special server for that.
The better solution to prevent spam is at the server level. Block the mail before it enters your mail system. Then you don't have to mess with mail filters.