CiviCRM Community Forums (archive)

Update on resolution - still lots of passwords:
To solve the bouncing issue "No such email here", my host turned off "sender verification" on my server, seemed a little drastic to me, but since I'm on a VPS, they may have meant the effect was just for my domains.  They didn't think that the change was a big security issue.

Emails are now being sent out from Step 4 test, and also step 5 send - both by link and by cron using the site key.
= = = = = = = = = =
I'm about to reinstall CiviCRM / CiviMail on a different hosting account and see if my impression that I'm moving backwards in getting it to work is accurate.  As I'm contemplating this, I've realized that we have quite the assortment of usernames and passwords to consider, and these all have to be set correctly:

1 - Hosting Account Username and Password
2 - Email SMTP / POP 3 Username and Password for Hosting Account user
3 - CiviCRM Username and Password for user in question
4 - Email SMTP / POP 3 Username and Password for CiviMail User
5 - Administer CiviCRM Domain Information - System Generated Mail Settings
6 - Cron POP3 Username and Password (I setup a separate email account for cron messages)

7 - Administer CiviMail From email addresses (From Email Address Options)
8 - Administer - CiviMail - Mail Accounts
9 - CiviMail return path (Mail Accounts screen), see also next item
10 - Reply POP3 Username and Password (where real bounces come back to)
11 - The from email account used in CiviMail step 3 (uses previous item, I think)
12 - Settings Outbound Mail - SMTP Configuration
13 - The send test to email or group in CiviMail step 4

14 - Hosting Provider table of users allowed to run cron jobs (specific to my hosting provider)
15 - Cron job name and pass and key (I think this is for the CiviCRM user to run as)
16 - CIVICRM_SITE_KEY defined in civicrm.settings.php which is verified by cron job and uncertain about manual running by link

The above is not such a bad list when things are working, but when not and changing things late at night to test a mailing, easy to see how they could get out of whack.  I may make all the user names and passwords the same (except for key), as I sometimes do for a test to see if I can get things to run, although I don't understand how any of the above would cause bounces that are not really bounces and place emails on hold, but something must.