mailboxer sent messages not appearing in recipients inbox

What could the problem be?

The problem is you’re not reading directions or doing your own research. Take the advice of everyone who’s offered to help you and go through some basic Rails tutorials. Nobody is going to write your app for you.

That’s not the problem The problem is you’re not helping, but replying for reasons unexplained

Can’t help someone who can’t help themselves. Do the work, do the research, then ask questions.

What makes you say I haven’t done any research since you didn’t ask how much time I spent researching and I didn’t tell you

Likely no-one here knows the answer to your problem. We are trying to
help you by pointing to the code so that you can look through it and
work it out for yourself. Once you work out the answer make sure you
post it here so the next person to have similar problems will find it
and understand what is going on.

Colin

The problem is you’re not reading directions or doing your own research.
Take the advice of everyone who’s offered to help you and go through some
basic Rails tutorials. Nobody is going to write your app for you.

What could the problem be?

--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to rubyonrails-ta...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/0329d1af-23e5-4f47-a286-c7556789a6ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

That's not the problem The problem is you're not helping, but replying for
reasons unexplained

Likely no-one here knows the answer to your problem. We are trying to
help you by pointing to the code so that you can look through it and
work it out for yourself. Once you work out the answer make sure you
post it here so the next person to have similar problems will find it
and understand what is going on.

Colin

Let me second this last point -- I have found answers through Google to current questions where I wrote the answer years ago. Memory is a fickle thing.

And there is a (fairly snarky) essay out there, old as dirt, to the tune of "ask smart questions", which crystallizes the replies you have found here in this thread, and what they point out to you. But I prefer Julia Evans' take on this: https://jvns.ca/blog/good-questions/

Take a deep breath, read the whole thing, reflect on what people have been hinting to you here. Then gain a little humility, and realize that people take their own time out to answer your question. You owe them the effort to make that question a good one, and to take their answer -- even if it means more work for you -- seriously.

Walter

No one is harassing you. But your lack of effort shows. We are all trying to help you but you fail to even put forth effort to do your own research. We are basically writing your app for you.

The problem is you’re not reading directions or doing your own research.
Take the advice of everyone who’s offered to help you and go through some
basic Rails tutorials. Nobody is going to write your app for you.

What could the problem be?

--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to rubyonrails-ta...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/0329d1af-23e5-4f47-a286-c7556789a6ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

That's not the problem The problem is you're not helping, but replying for
reasons unexplained

Likely no-one here knows the answer to your problem. We are trying to
help you by pointing to the code so that you can look through it and
work it out for yourself. Once you work out the answer make sure you
post it here so the next person to have similar problems will find it
and understand what is going on.

Colin

Let me second this last point -- I have found answers through Google to current questions where I wrote the answer years ago. Memory is a fickle thing.

And there is a (fairly snarky) essay out there, old as dirt, to the tune of "ask smart questions", which crystallizes the replies you have found here in this thread, and what they point out to you. But I prefer Julia Evans' take on this: https://jvns.ca/blog/good-questions/

And if you do want to go to the waterfall instead of the well, here's the original: http://catb.org/~esr/faqs/smart-questions.html I had forgotten it was written by Eric Raymond and peers! Talk about old as dirt.

Here's a "money quote" from early in the introduction:

The first thing to understand is that hackers actually like hard problems and good, thought-provoking questions about them. If we didn't, we wouldn't be here. If you give us an interesting question to chew on we'll be grateful to you; good questions are a stimulus and a gift. Good questions help us develop our understanding, and often reveal problems we might not have noticed or thought about otherwise. Among hackers, “Good question!” is a strong and sincere compliment.

Despite this, hackers have a reputation for meeting simple questions with what looks like hostility or arrogance. It sometimes looks like we're reflexively rude to newbies and the ignorant. But this isn't really true.

What we are, unapologetically, is hostile to people who seem to be unwilling to think or to do their own homework before asking questions. People like that are time sinks — they take without giving back, and they waste time we could have spent on another question more interesting and another person more worthy of an answer. We call people like this “losers” (and for historical reasons we sometimes spell it “lusers”).

Walter

You are right, sorry, it was on your other thread I posted the link to
the source. I thought both threads were referring to the same
problem.

Colin

You do realize that falsifying a police report is a state felony, right? And if it crosses state lines, then it’s a Federal felony.

And while we’re on the topic, exchanging emails on a public mailing list with no direct contact is not stalking nor harassment. In fact there has not been one single communication that can be legally construed as “harassment” or “stalking”.

When you’re ready for some help, let us know. Until then it’d be in your best interest to change your attitude and drop the threats.

-N

Fine, agreed I’ll let you know when I get it working what was wrong

e