Visitor
•
3 Messages
Relaying my SMTP causes Xfinity to deactivate my account / require password reset
Hi,
This is a bit of a long standing issue:
- I use Comcast's SMTP for my personal email
- I use an SMTP relay to send said personal email
- Sometimes, I have more email to send (50-100)
- When that happens, Xfinity's/comcast triggers some automatic response which flags my account and deactivates the account until i reset the password
Each time, i do this, send the remaining emails, then its fine.. obviously, the access is not malicious, the emails are personal (I do not run a business, i just forward my email from one account to another so i have all the email in one place). Is there any way to turn that automatic flagging off?
Accepted Solution
user_f97e81
Visitor
•
3 Messages
2 years ago
@flatlander3, I appreciate your efforts, however, I know what I'm doing. No, the outbound address is not listed by RBLs. I understand Postfix and SMTP quite well, or IMAP and POP for that matter. And no, I'm not "holding it wrong" (Apple reference). I pay comcast xfinity for a service I'm expecting works, until they officially stop providing it.
The amount of connections is reasonable and the amount of email is fairly reasonable. I made some more tests and their SMTP will in fact allow quite a bit of connections/s and concurrently, far more than I'd use. My current assumption is that they have a script or similar that is set when you change your user password, which expires after a while, at which point you'll have to re-authenticate and change your password again (3 month ish?), or something similar, maybe a maximum total count, who knows. You don't and I don't either.
I don't expect that you will solve this or that they will solve it at this point, while I appreciate your attempts, please stop telling me to pay for something else or assume that I don't know how this works. I get there's a million questions that can be answered as such, and may be what people want - but in this case this won't be helpful for me. Thanks!
0
0
flatlander3
Problem Solver
•
1.5K Messages
2 years ago
Send limits are here -- if this is current: https://www.xfinity.com/support/articles/limitations-on-sending-email
100 addresses on a single email (more won't send). 1000 total recipients in a day (I would assume an single email with two people on it, would leave you 998 possible left for that day).
Business accounts can do more. Depends on exactly what your use case is.
You could run your own mail server somewhere offsite. Rent a VM at a hosting company with your own domain name. Then you are the system administrator and you can set whatever limits you want. There are various hosting companies that will handle email for you too if you buy a domain. In either case you would use your own domain, and it's email server settings as your default outbound mail server (usually submit on port 587). They might have email limits too. Depends on who you go with.
Alternatively, Gmail has an option to check mail on another email service, so you can setup Gmail to check your Xfinity account, and then your mail would be on Gmail in one place. If you log into Gmail in a browser, Select the Gear icon in the top right and select "See All Settings". From there, click on the "Accounts and Import" tab. In that list, you can "Add a Mail Account". Enter your Xfinity account an it's server settings/your password there.
I don't know if that's what you were looking for or not.
1
0
flatlander3
Problem Solver
•
1.5K Messages
2 years ago
Well, your use case is probably where the issue is.
You say SMTP relay -- how exactly, and what is the goal? Local outbound with something like postfix? Configuration is important there. You might have issues with Xfinity with the queuing if you are mail bombing and exceeding postifix max_connections. That looks like virus propagation. You'll have to check the mail logs to see what's going on there (flip on debugging and see what you are spawning).
Since Xfinity blocks port 25, you can actually run an INBOUND mail server, or failover MX with an SMTP port redirect service, and also use an external SMTP service for an OUTBOUND mail server on a submit port -- but you are actually using SMTP service server, not XFINITY for outbound mail in that configuration. Dynu is a service that does exactly that, but most of the domain registers do it to. There's quite a few others. You're going to want to see if their mail servers are blacklisted on RBL lookups though. Quite a few of them are pretty spammy.
If it's just archiving, you can set an email forward anywhere by logging into xfinity.com with a browser, and in web email settings you can set an auto-forward. It's pretty lame and doesn't allow filtering. Thunderbird can do message filtering, then forward email based on some condition, but it will only work when Thunderbird is running. The benefit there is there isn't a connection flood. For just syncing or saving some email, that's what IMAP is for or grab everything with POP3.
0
0