Any one can me tell that how i can resolve this?

Thanks

header_checks = regexp:/etc/postfix/maps/header_checks

And the in /etc/postfix/maps/header_checks:

# Sample For Dropping Headers:
#/^Header: IfContains/ IGNORE
/^Received: from domU-12-34-56-78-90-AB.compute-1.internal/ IGNORE
/^Received: by domU-12-34-56-78-90-AB.compute-1.internal/ IGNORE

Thanks for the tutorial. How can I adjust the config file to allow all my frontend instances relay through one centralized postfix server in the same security group? I can’t figure out how to get it to allow connections from my other instances.

Thanks!

So I asked the support of AuthSMTP. They suggest to fill the form from Yahoo:
http://help.yahoo.com/l/us/yahoo/mail/postmaster/bulkv2.html

Have filled that form, but so far, no feedback and no help at all.

Any idea? Seems that other people have the same problem too.

I haven’t tested that though, it’s just what I think will happen.

Regarding the Postfix failures, I was referring to the case where Postfix has fallen over for some reason and your attempt to queue an outbound email thus fails…in other words, the message never gets queued to begin with. I suppose you would have to persist that message somewhere (db/local queue) to be sent again at a later time. But at that point you’re in the situation where you need an async process to pull things off of this failure queue, and then you’re kind of back at square one again, and why not just put things into a queue to begin with? Assuming your assertion of SQS latency is accurate, perhaps that’s a local fast queue instead.

I realize these are edge cases, and these aren’t exactly financial transactions we’re talking about here either, so a lost email here and there isn’t exactly the end of the world. I’m just curious how other people out there have approached this problem in the context of Rails where throughput depends on getting in and out of the HTTP request/response cycle as quickly as possible.

Thanks.

In general I’d say that queueing a small job which causes the email to be sent from another process is a good idea, especially if you’re queueing other things to speed up your page loads, but I’d recommend not using SQS for this because SQS is *extremely* slow (i.e. high latency). I find that queuing SQS messages frequently takes well over 100ms which is way too slow to do while responding to a web request.

If you’re using a queue to speed up page loads, use a fast local queue. If the only thing you’re queueing is email sending, and you’re sending just one or two emails per web request, you might consider just using a local postfix instead for simplicity.

To address your two questions: yes, I find the response time adequate to keep Rails throughput acceptable (though some queues would definitely be faster) and yes there’s a small chance that a message could be lost while in transit in the local postfix (e.g. if the instance dies), but the messages don’t stay in there for long, postfix sends them out quickly enough that it doesn’t build up a queue.

Question: I had been planning on using Amazon SQS to queue emails that need to be sent (not the actual email, but a small data structure of what email needs to be sent to whom). Then, using the activemessaging plugin (or similiar), I would pull things off the queue and actually send the email. The goal of all of this machinery is to keep the actual sending of the email out of the HTTP request/response cycle so Rails throughput doesn’t get bogged down with potentially long running actions. I have this all running locally and it works fine.

However, I’m now wondering if this is all overkill if mail is delivered to a local Postfix server on an ec2 instance. Do you find the response times of the local Postfix adequate to keep Rails throughput acceptable? How do you deal with failures if Postfix goes down for some reason, such that you don’t lose emails?

Thanks again.

Thanks for your gr8 post on authsmtp configuration. I am using an EC2 server for sending mails through authsmtp. I am not using any mail queue system; which I don’t think will be an issue for mails going to SPAM folder of hotmail / yahoo boxes. With yahoo is the main issue.

Kindly suggest what more can I do to fix the issue.

Thanks in advance.

“Rather than deliver directly to the AuthSMTP mail server from your web app it’s a good idea to deliver to a local queueing mail server, which will forward via the AuthSMTP gateway. Your web app will deliver mail to localhost (or perhaps a dedicated instance if you prefer), port 25.”
What’s the best strategy for doing this in a dynamic environment? Multiple web app servers will be going up and down, so how can I configure postfix to forward to a queueing server?