mandrill

问题 I am trying to set up a DKIM record on Amazon's Route 53. I just choose to add TXT record with name like this: mandrill._domainkey.domain.com and the value is: "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;" but Route 53 keeps complaining about: The record set could not be saved because: - The Value field

问题 I am trying to set up a DKIM record on Amazon's Route 53. I just choose to add TXT record with name like this: mandrill._domainkey.domain.com and the value is: "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;" but Route 53 keeps complaining about: The record set could not be saved because: - The Value field

问题 The documentation isn't very clear how to use the send_at parameter. I am sending a scheduled email using the function below. I have tried different versions of the datetime required by the API documentation. All my emails are being send right away and not scheduled. def send_member_email_batch(current_user, recipient_emails, recipient_names, subject, body, scheduled) m = Mandrill::API.new ENV["MANDRILL_APIKEY"] recipient_emails.each_with_index do |recipient, index| to_address = (recipient

问题 The documentation isn't very clear how to use the send_at parameter. I am sending a scheduled email using the function below. I have tried different versions of the datetime required by the API documentation. All my emails are being send right away and not scheduled. def send_member_email_batch(current_user, recipient_emails, recipient_names, subject, body, scheduled) m = Mandrill::API.new ENV["MANDRILL_APIKEY"] recipient_emails.each_with_index do |recipient, index| to_address = (recipient

问题 I'm having enormous difficulty getting mandrill SMTP to send reliably. Or more accurately, authenticate every time. When it does authenticate the email works fine I can run the send script fine, then 2 or 3 times in succession one after the other. Then it doesn't authenticate. But on occasions it doesn't authenticate straight away. I thought perhaps it's just because it thinks I'm abusing it and blocked me for a short period. But I can see that since I started using mandrill SMTP for my

问题 I'm having enormous difficulty getting mandrill SMTP to send reliably. Or more accurately, authenticate every time. When it does authenticate the email works fine I can run the send script fine, then 2 or 3 times in succession one after the other. Then it doesn't authenticate. But on occasions it doesn't authenticate straight away. I thought perhaps it's just because it thinks I'm abusing it and blocked me for a short period. But I can see that since I started using mandrill SMTP for my

问题 Related to this question, which explains the origins of the logic in the controller, I have a question about background jobs with Delayed Job before pushing it to github and re-deploying. The model and scopes work, the logic in the controller(s) works, the conditionals in the e-mail text.erb files work, users are either readers or subscribers and can set their e-mail preferences on their "My Account" page: [Articles & Updates, Just Articles, No E-mail, etc.]. Delayed Job is set up and

问题 I commonly send transactional emails in response to certain actions on my website, some of which I delay sending by a couple of hours. The function that actually queues the email is a Celery task function called with .delay() that eventually makes an API call to Mandrill using djrill. I discovered that Mandrill offers a send_at parameter when sending an email that will have Mandrill delay sending the email until the specified time. Celery also offers eta or countdown parameters when calling

问题 I commonly send transactional emails in response to certain actions on my website, some of which I delay sending by a couple of hours. The function that actually queues the email is a Celery task function called with .delay() that eventually makes an API call to Mandrill using djrill. I discovered that Mandrill offers a send_at parameter when sending an email that will have Mandrill delay sending the email until the specified time. Celery also offers eta or countdown parameters when calling

问题 I have an issue with using Mandrill to send emails, I created an account and a new template but when I try to send a test of that template ... I get the following message even I had ever send an email. " Message not sent: queued " 回答1: I fixed it for whose who have the same pb , i sent an email to Mandrill support help@mandrill.com and they fixed it this is there replay: Hi there, Thanks for reaching out. Your account matched some of our automated abuse detection heuristics and was paused