Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SMTP/S interaction does not received on custom ports #642

Open
schreddies opened this issue Aug 22, 2023 · 0 comments
Open

SMTP/S interaction does not received on custom ports #642

schreddies opened this issue Aug 22, 2023 · 0 comments
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@schreddies
Copy link

Interactsh version:

version 1.1.5

Current Behavior:

I wasn't able to receive SMTP/S interaction notification on different ports (both udp and tcp). The DNS from SMTP communication notification was received to the interactsh-client, but no communication marked as SMTP.

Expected Behavior:

SMTP communication should be visible on the interactsh-client.

Steps To Reproduce:

I am running AWS EC2 instance, with open security group and aws nlb. The nmap result are :

53/tcp  open  domain
80/tcp  open  http
443/tcp open  https
587/tcp open  submission

running the interactsh-server:

interactsh-server -d <redacted> -ip <nlb> -smtp-port 587 -token <redacted>
@schreddies schreddies added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Aug 22, 2023
@ehsandeep ehsandeep changed the title SMTP/S does not received SMTP/S interaction does not received on custom ports Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

1 participant