samplensa.blogg.se

Generally, SMTP is a 7-bit-only protocol, which means any non-ASCII characters need to be escaped for safe transport.

ISPs may redirect traffic on certain ports, which might determine which port you need to use. There is no configuration change needed within Mailchimp Transactional to activate one of the alternate ports. For secure SSL connections, use port 465. You can also use the STARTTLS extension (also known as TLS encryption) on these ports. Use ports 25, 587, or 2525 for non-encrypted communication between your system and Mailchimp Transactional. Since the API key is sufficient for authentication, Mailchimp doesn’t use the SMTP username to authenticate your request, but we recommend using your Mailchimp account’s primary contact email as the username. You can use any active API key for your account as your SMTP password. Credentials and configurationĪfter you’ve created a Mailchimp Transactional account, you can find your SMTP credentials on the SMTP & API Info page. If you’re trying to decide between sending with SMTP or with the API, you can read more about the two routes in Fundamentals. Note: While SMTP offers the same sending capabilities as the Transactional API, the latter also lets you view or parse reporting data in your own app or system.