Thank you for watching out videos, and for your question. No, Mailtrap forbids cold emailing at this point.

Thank you for watching our video and for your question. Try instead of embedding long HTML content in your Java code, store the HTML content in an external file. You can load the file dynamically when sending the email. This keeps your code clean and allows easier modifications to the email content. We hope this helps. Good luck!

Thanks for watching and for your question. A few common mistakes that may lead to error in this context: - Lack of Email Authentication (Configure your SPF, DKIM, and DMARC) - Improper SMTP Settings (Invalid or misconfigured settings (e.g., wrong port, incorrect SMTP server) can cause email services to treat the email as suspicious.) Here's the code, try to use it again: from flask import Flask from flask_mail import Mail, Message app = Flask(__name__) # SMTP Server Configuration (for example, using Gmail's SMTP server) app.config['MAIL_SERVER'] = 'smtp.gmail.com' app.config['MAIL_PORT'] = 465 app.config['MAIL_USERNAME'] = 'your-email@gmail.com' app.config['MAIL_PASSWORD'] = 'your-password' app.config['MAIL_USE_TLS'] = False app.config['MAIL_USE_SSL'] = True mail = Mail(app) @app.route("/send-email") def send_email(): msg = Message("Hello from Flask", sender="your-email@gmail.com", recipients=["recipient@example.com"]) msg.body = "This is the plain text body" msg.html = "<h1>This is the HTML body</h1>" try: mail.send(msg) return "Email sent!" except Exception as e: return str(e) if __name__ == "__main__": app.run(debug=True) Make sure the MAIL_USERNAME and MAIL_PASSWORD match your SMTP server credentials, and ensure you are adhering to the SMTP provider’s guidelines for email limits. Good luck!

Hey man, I got the same error when I set up MT a while ago. The thing that bugged me was that I thought it was like Gmail SMTP, so I used my Mailtrap account name instead of 'username' that's in the credentials tab. Hope it helps my guy 🍻

Hey, thanks for your help and comment! Yes, it's true. One needs to use username from MT credentials, not the account name! Cheers! Thanks for being with us! Stay tuned!

Thank you for watching and for your question. Mailtrap is an email delivery platform for devs and marketers. We offer email sending (user-triggered emails and email marketing campaigns) and email testing. We don't offer email hosting.

Thank you for watching! We appreciate this nice feedback from you. Of course, we can make a video about email templates in GO. Stay tuned, and we'll deliver!

Thanks for watching! And thank you for your question. Let's see. The core concept of email verification in PHP is the same as in CodeIgniter 4 since CodeIgniter 4 is built using PHP. Both approaches follow similar steps: User Registration: Store user details and a verification token in the database. Email Sending: Send an email with a unique link containing the token. Token Verification: When the user clicks the link, check the token and activate the user account. However, CodeIgniter 4 provides a framework structure and built-in libraries to simplify this process compared to raw PHP. Let me break down the differences: Key Differences: Framework Support: PHP: You need to manually handle everything-database connection, query preparation, email configuration, validation, routing, etc. CodeIgniter 4: It offers pre-built classes for emailing, routing, and database handling, which reduces code complexity. CodeIgniter's built-in services like Email make it easier to send emails. Routing: PHP: You’ll need to define the routing manually or use .htaccess to handle dynamic URLs for token verification. CodeIgniter 4: Routes are configured via the app/Config/Routes.php file, simplifying the process of mapping URLs to controller actions. Security: PHP: You need to manually implement security measures, such as sanitizing input, hashing passwords, and escaping data. CodeIgniter 4: The framework has built-in security features like CSRF protection, XSS filtering, and input validation, reducing the risk of common vulnerabilities. Email Handling: PHP: You would typically use mail() or external libraries like PHPMailer to send emails. CodeIgniter 4: The framework offers its own Email library, which simplifies email sending, configuration, and error handling. Validation: PHP: You must manually validate email addresses, user input, and token handling. CodeIgniter 4: Offers a validation library that helps validate user input with predefined rules. Check out this code comparisons: Raw PHP Verification: // registration.php (User Registration) $email = $_POST['email']; $token = bin2hex(random_bytes(16)); $hashedPassword = password_hash($_POST['password'], PASSWORD_DEFAULT); // Save user and token to the database $pdo->prepare("INSERT INTO users (email, password, token) VALUES (?, ?, ?)") ->execute([$email, $hashedPassword, $token]); // Send email $subject = "Verify your email"; $message = "Please click the link to verify your email: yourdomain.com/verify.php?token=$token"; mail($email, $subject, $message); // verify.php (Verification) $token = $_GET['token']; $stmt = $pdo->prepare("SELECT * FROM users WHERE token = ?"); $stmt->execute([$token]); $user = $stmt->fetch(); if ($user) { // Verify user $pdo->prepare("UPDATE users SET token = NULL, is_verified = 1 WHERE id = ?") ->execute([$user['id']]); echo "Email verified!"; } else { echo "Invalid token!"; } CodeIgniter 4 example: // app/Controllers/AuthController.php use App\Models\UserModel; class AuthController extends BaseController { public function register() { $userModel = new UserModel(); $userData = [ 'email' => $this->request->getPost('email'), 'password' => password_hash($this->request->getPost('password'), PASSWORD_DEFAULT), 'email_verification_token' => bin2hex(random_bytes(16)), ]; if ($userModel->insert($userData)) { $this->sendVerificationEmail($userData['email'], $userData['email_verification_token']); return redirect()->to('/login')->with('message', 'Please check your email to verify your account.'); } return redirect()->back()->withInput()->with('error', 'Registration failed'); } private function sendVerificationEmail($email, $token) { $emailService = \Config\Services::email(); $emailService->setTo($email); $emailService->setFrom('no-reply@yourdomain.com', 'Your Website'); $emailService->setSubject('Verify your email'); $emailService->setMessage("Click the link to verify your email: " . base_url('auth/verify/' . $token)); $emailService->send(); } public function verify($token) { $userModel = new UserModel(); $user = $userModel->where('email_verification_token', $token)->first(); if ($user) { $userModel->update($user['id'], ['email_verification_token' => null, 'is_verified' => 1]); return redirect()->to('/login')->with('message', 'Email successfully verified!'); } return redirect()->to('/login')->with('error', 'Invalid token!'); } } We hope this helps. Let us know. Good luck!

Thank you for watching the video, and for your question! Yes, Mailtrap allows you to check how the HTML elements would look like in different mailbox providers, and offers suggestions on fixing the bugs accordingly.

@@mailtrap. Thanks for the reply. I saw the HTML checks, but nothing concerning "previews / screenshots".

Please, contact our team at support@mailtrap.io to attend to your needs, and make a quote if you need customizable, or specific solutions. We would take care of your needs instantly. And you can get all the info in the full.

Thank you for watching our video! Here are a few thoughts you could use: In your case, the error is likely happening because you're passing a function or method (like create_message) rather than the result of calling that function. The create_message should return a properly formatted message, but it seems like you're passing the function reference instead of its return value. Here's how you can fix this: Ensure that create_message is being called (i.e., the parentheses () are included), so you're passing the result of the function, not the function itself. OR The body argument in the send method needs to contain the message object returned by create_message, not the function itself. Try something like this (we use an example here): # Assuming this is your create_message function def create_message(sender, to, subject, message_text): message = MIMEText(message_text) message['to'] = to message['from'] = sender message['subject'] = subject raw = base64.urlsafe_b64encode(message.as_bytes()).decode() return {'raw': raw} # And you're sending the email like this: message = create_message("me@example.com", "you@example.com", "Test Subject", "This is a test email") # Now, you need to pass the result of `create_message` (the message object) # to the body, NOT the function itself. response = service.users().messages().send(userId="me", body=message).execute() # This should fix the issue. I hope you'll find this helpful. Good luck!

Hey, Thanks for watching the video! And thank you for your question. Well, (jokingly): how fast can you submit them? 😅 If we are talking about Mailtrap, please, contact our sales team for a quote - we can do things faster for you. Have a great day and stay tuned to learn more about emails with our channel!

Thank you for watching! Please, provide us with more context so we would be able to give you assistance. Where do you get "false", what step are you talking about? Let us know

Thank you for watching! Stay tuned for more email content

Hey, they're still available but they've been moved to Google Account settings -> Security -> 2-Step Verification (under 'How you sign in to Google'). You can also use the search bar to find them :D

Hey, thank you for watching and for helping out fellow devs! We appreciate your help 💪

Thank you for watching. Stay tuned for more email content!

Thanks for watching! We appreciate the feedback. Stay tuned for more email content!

Thank you for watching the video! We appreciate your feedback, and we always try to improve our videos based on our viewers' feedback. Stay tuned for more email content!

Hey! Thanks for appreciating our channel and the guy)))) Have a great day!

Thank you for watching. Stay tuned for more video content!

Hello. Thanks for watching and for your question! The private key should be set up in the final sending server that dispatches the email to the recipient's mail server. The DKIM signature is then validated by the recipient's server using the corresponding public key published in your DNS records. We hope this helps!

@@mailtrap. but since it's a relay smtp server, we should give our private key to the smtp relay?

Thank you for watching! Stay tuned for more email content!

Does it have email functionality?

@@mailtrap. not sure what you mean, but I only purchase a domain without any extra services.

Hey, hi. Thanks for watching! All of this is done on the laptop.

@@mailtrap. Thanks, what else is needed in the way of hardware?

@@solarwinds- Hey there, a simple laptop is enough in my opinion. For example the minimum requirement could be, Linux is known for its flexibility and ability to run on a wide range of hardware. However, there are some basic requirements to ensure a smooth experience: Processor Minimum: 1 GHz processor (32-bit or 64-bit) Recommended: 2 GHz or faster 64-bit processor RAM Minimum: 512 MB RAM Recommended: 2 GB RAM or more Storage Minimum: 10 GB of hard drive space Recommended: 20 GB or more Graphics Minimum: Basic graphics card with VGA output Recommended: Modern graphics card with at least 1 GB of VRAM for a better desktop experience Note: These are minimum requirements. For a more comfortable and responsive experience, it's generally recommended to exceed these specifications. Additional Considerations: 64-bit vs. 32-bit: While 32-bit systems can still run Linux, most modern distributions and hardware support 64-bit architecture, which offers better performance and can address more memory. Desktop Environment: The choice of desktop environment (e.g., GNOME, KDE, XFCE) can affect resource usage. Lighter-weight environments like XFCE may require less powerful hardware. Specific Distribution: The exact requirements may vary slightly between different Linux distributions (e.g., Ubuntu, Fedora, Debian). In summary, even a relatively modest computer can run Linux effectively. By considering these minimum requirements and your specific needs, you can choose the right hardware to enjoy a smooth and efficient Linux experience.

Thank you for watching! We do our best to bring value to our community. Stay tuned for more Linux API will be out VERY SOON)

Thanks for watching! Stay tuned for more!

Hey, thank you for watching our video! for starttls, you just need to use port 587: $smtpPort = 587 We hope this entire script will be helpful: # Define SMTP server and port $smtpServer = "smtp.example.com" $smtpPort = 587 # Use port 587 for STARTTLS # Define the sender and recipient $from = "your-email@example.com" $to = "recipient@example.com" # Define the email subject and body $subject = "Test Email" $body = "This is a test email sent from PowerShell." # Define your SMTP credentials $username = "your-email@example.com" $password = "your-password" # Create a new MailMessage object $mailMessage = New-Object system.net.mail.mailmessage $mailMessage.From = $from $mailMessage.To.Add($to) $mailMessage.Subject = $subject $mailMessage.Body = $body # Create a new SmtpClient object $smtpClient = New-Object system.net.mail.smtpclient($smtpServer, $smtpPort) # Enable SSL and set the delivery method $smtpClient.EnableSsl = $true $smtpClient.DeliveryMethod = [System.Net.Mail.SmtpDeliveryMethod]::Network # Set SMTP credentials $smtpClient.Credentials = New-Object System.Net.NetworkCredential($username, $password) # Send the email try { $smtpClient.Send($mailMessage) Write-Host "Email sent successfully." } catch { Write-Host "Failed to send email. Error: $_" }

@@mailtrap. what smtp server we need to put? from where will i get the credentials which you used in this video/ mailtrap smtp?

Thank you for being with us! We appreciate your trust.

That's something we cover in the upcoming videos. Stay tuned!

For all inquiries and contacts, please, check out the footer of our official webpage: mailtrap.io/

For all inquiries and contacts, please, check out the footer of our official webpage: mailtrap.io/

Hey, thanks for the comment! We appreciate your consideration, but we are good for now) Good luck!

@@mailtrap. I want to contact you I have sent you e,mail How can I contact you?

For all inquiries and contacts, please, check out the footer of our official webpage: mailtrap.io/

Thank you for watching! We are happy our video has finally reached you in 2024. Have a wonderful day!

Thank you for watching our videos and for your feedback. We always welcome our viewers considerations and suggestions. Could you help us make better content, and tell us what would you like to be explained in more details from this video? Thanks!

Hey, thanks for watching! Yes, signing into your Outlook email using SMTP through a third-party app typically registers as a login activity on your Microsoft/Outlook account. Microsoft logs access to your account, including the use of SMTP for sending emails, as part of their security monitoring. You can view this activity in your account's security settings, where it may show details such as the time, date, and location (IP address) of the login, as well as the type of access (SMTP).

Thank you for your question! Although we are not sure about the message of it, "the unrelated" group of brands are very much related altogether to improving email deliverability for marketing campaigns. The presenter of the video does various video presentations as a job, news being only one gig among many others. Hopefully, this answers your question. We wish you a very pleasant day, and looking forward to more existential questions)))

@@mailtrap. haha toché

Hey, thanks for watching our video and for your question. We will give you a general reply here. But so you know, we are planning to upload a video about Email Deliverability Audit within next few weeks. That may be helpful as well. As for now, let's start with your SMTP servers check. - Do you have correct DNS Records? Verify that your SPF, DKIM, and DMARC records are correctly configured and aligned. Even slight misconfigurations can cause issues. How to configure DNS records properly, we cover in our videos: SPF: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-3O42vhFT0j8.html DKIM: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-oPdGmJUquyM.html DMARC: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-zT1wMIz8_IU.html - Do you have reverse DNS (PTR Record) configured? Ensure that your IP has a proper PTR record that matches your domain. PTR configs here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-R8SapUwjZ-8.html Also: do you use BIMI? Another important question: how old is your domain? Do you send text emails? HTML emails? Do you use fallbacks for HTML emails where mailbox providers do not support some HTML elements? To give you proper advice, we need more context and understanding of your sending practices. However, answering these questions should help to launch the first steps of email deliverability audit. Let us know if it helps and check out our upcoming video on email deliverability audit step-by-step. Stay tuned!

Hey, hi. Just getting back to you. Our video on How to conduct email deliverability audit is premiering soon. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-U0cMhNhwSac.html Have a great day!

Thank you for watching!

Thank you for watching our video and thank yu for an excellent question. So why Mailtrap? 1) It's an email delivery platform with one of the highest deliverability rates - make sure your emails get to inboxes, not spam folders! Our infrastructure is solid and has an uptime of nearly 100%. 2) You can test all your emails including raw, HTML, email preview to debug them on staging before they actually get to your customers 3) Best in the industry email analytics: we cover all mailbox providers, including Office 365, Outlook, Gmail, and Google Workspace. You can check email performance and detailed stats for each provider. 4) Email security - highest standards of encryption, plus, let's say automatic DKIM keys rotation once in 3 months or more often. 5) Bulk email RESTful API and SMTP for mass email sending. Separate stream at one price, comes together with transactional stream. 6) Mailtrap offers ready-made code snippets for easy integration. Over 25 ready-to-use code snippets in PHP, Python, Ruby, and more. Quickly find and implement the code you need, and start sending emails in no time. 7) 24/7 HUMAN support. No AI. Personalized approach. 8) Free period of migration from other survices. Deliverability team support for free. 9) HTML checker, Spam checker, QA automation 10) Cheapest plans on the market And many other advantages that other providers do not offer. Let us know your needs, and we'll attend to them. Hope this is helpful. Looking forward to seeing you soon! Cheers!

Hello. Thank you for watching our videos! We already have two videos about IPs. There, we explain how IP warm-up works. As for the seed list, the video is coming soon! Thank you for your interest and your questions. Here are our videos on IP, and IP reputation: 1) ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-VwgBmgOA8hA.html 2) ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-SDXlLzmMaJM.html Stay tuned!

ssl.SSLEOFError: [SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1006)

I have fixed this problem,thanks, after I disconnected my VPN its working,!

Awesome! Congrats! And thanks for watching. Stay tuned for more email videos

Hey, thanks for watching. Here's what you can do to debug: 1. Check the console output: Ensure that console.log(message) shows the correct message format with all placeholders replaced correctly. 2. Check email sending: ensure that GmailApp.sendEmail has the correct parameters. The third parameter is left as an empty string '' because we are using the htmlBody option to send HTML content. 3. Verify HTML content: make sure the HTML content is correct and does not contain any syntax errors. 4. Authorization: ensure the script has the necessary permissions to send emails from your Gmail account. Here is the example for the script with additional logging: function sendEmails() { try { var sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet(); var startRow = 2; // First row of data to process var numRows = sheet.getLastRow() - 1; // Number of rows to process var dataRange = sheet.getRange(startRow, 1, numRows, sheet.getLastColumn()); var data = dataRange.getValues(); var emailTemplate = HtmlService.createHtmlOutputFromFile('emailTemplate').getContent(); for (var i = 0; i < data.length; ++i) { var row = data[i]; var emailAddress = row[0]; // First column var subject = row[1]; // Second column var message = emailTemplate.replace('{{name}}', row[2]) // Replace placeholder with data from the third column .replace('{{customField}}', row[3]); // Replace another placeholder with data from the fourth column console.log('Sending email to: ' + emailAddress); console.log('Subject: ' + subject); console.log('Message: ' + message); GmailApp.sendEmail(emailAddress, subject, '', {htmlBody: message}); } console.log('All emails sent successfully.'); } catch (error) { console.error('Error sending emails: ' + error.message); } } We hope this helps! Let us know how it went. Good luck!

Hey! Thanks for watching and for your questions. Let's deal with all of them step-by-step. To set up an App Password in Gmail: - Go to your Google Account settings. - Navigate to Security. - Under "Signing in to Google", click on App passwords. - You might need to enter your Google account password. - Under "Select app", choose Mail. -vUnder "Select device", choose Windows PC or your specific device. - Click Generate. - Copy the generated App Password (it will be a 16-character string). The app name you enter here (like "send_mail") is mainly for your reference in case you need to manage or revoke passwords later. It is not used in the PowerShell script. Now, here's a PowerShell script example to send an email using Gmail's SMTP server. This script will automate the process without requiring a username/password prompt each time. # Define email parameters $smtpServer = "smtp.gmail.com" $smtpPort = "587" $from = "your_email@gmail.com" $to = "recipient@example.com" $subject = "Test Email" $body = "This is a test email sent from PowerShell script." $smtpUser = "your_email@gmail.com" $smtpPassword = "your_app_password" # App password generated from Gmail # Create a new SMTP client object $smtp = New-Object Net.Mail.SmtpClient($smtpServer, $smtpPort) # Enable SSL $smtp.EnableSsl = $true # Set SMTP client credentials $smtp.Credentials = New-Object System.Net.NetworkCredential($smtpUser, $smtpPassword) # Create a new MailMessage object $mailMessage = New-Object System.Net.Mail.MailMessage($from, $to, $subject, $body) # Send the email $smtp.Send($mailMessage) Write-Output "Email sent successfully!" By embedding the credentials directly into the script as shown above, you will not get a popup asking for the username and password. IMPORTANT: Use environment variables to keep your credentials more secure by not hardcoding them into your script. Here's how: # Set environment variables (run these commands once to set them) [System.Environment]::SetEnvironmentVariable("SMTP_USER", "your_email@gmail.com", "User") [System.Environment]::SetEnvironmentVariable("SMTP_PASSWORD", "your_app_password", "User") # Get environment variables $smtpUser = [System.Environment]::GetEnvironmentVariable("SMTP_USER", "User") $smtpPassword = [System.Environment]::GetEnvironmentVariable("SMTP_PASSWORD", "User") # The rest of the script remains the same... That's it. We hope it helps. Let us know. Good luck!!

Hey, beautiful viewer! Thank you for your detailed and very throrough code-based review. We wish you a wonderful day!

Thank you for watching! At least 2 more Flask videos are in production now 🤠 Stay tuned!

We appreciate the compliment. Thank you! Stay tuned for all things email 😎

Hey, thanks for watching! Do you mean hyperlink in the HTML email body? Like at 09:03? Assume you want to create an email with a subject, body text, and a hyperlink. You can construct it as follows: =HYPERLINK("mailto:recipient@example.com?subject=Test Subject&body=Hello, please visit this link: www.example.com", "Send Email") If you want to include more complex body text with a hyperlink, you need to make sure the URL is correctly included in the body: =HYPERLINK("mailto:recipient@example.com?subject=Test Subject&body=Hello, please visit this link: www.example.com", "Send Email") If you still encounter issues, it might be due to how Excel handles certain characters in the URL. Use %0A for line breaks and %20 for spaces. Here’s an example with line breaks and a properly encoded URL: =HYPERLINK("mailto:recipient@example.com?subject=Test%20Subject&body=Hello,%0A%0Aplease%20visit%20this%20link:%20www.example.com", "Send Email") Hope this helps. Let us know!